Skip to content
Syndik8

Confirm or dismiss a reported squawk

Confirm or dismiss a reported squawk

Section titled “Confirm or dismiss a reported squawk”

When the syndicate has turned on Require admin confirmation for squawks (off by default), member-reported squawks land in pending status. As an admin, you either confirm them (they become open and take effect) or dismiss them with a reason. Squawks reported by admins, and all squawks when the setting is off, skip this queue and open immediately.

Before you start

Section titled “Before you start”
  • You must be an admin.
  • Only pending squawks can be confirmed or dismissed here. A squawk that is already open, deferred, resolved, or dismissed does not appear on this queue.

Steps

Section titled “Steps”
  1. Open the syndicate.
  2. Tap the Admin tab, then tap Pending.
  3. Tap the Squawks row.
  4. Every squawk in the queue starts collapsed. A collapsed row shows only the asset name, the severity, who reported it, a one-line summary of the title, and a PENDING chip. There are no buttons at this stage.
  5. Tap a row to open it. Only then do you get the full detail (Description, Severity, Reported by, Date), a View Detail link to the squawk’s own screen, and the Dismiss and Confirm buttons. Both actions live inside the opened panel, so open the entry before you decide.
A pending squawk opened out from the list, showing the description, severity, reporter and date above the Dismiss and Confirm buttonsA pending squawk opened out from the list, showing the description, severity, reporter and date above the Dismiss and Confirm buttons

To confirm

Section titled “To confirm”
  1. Tap Confirm in the opened squawk. The Confirm squawk dialog opens with the severity the member reported already selected.
  2. Check the severity. If the member picked the wrong one (a stiff trim wheel reported as Grounding, say), tap the right one: Grounding, Caution or Info. A Reason box appears once you change it. It is optional here, and anything you write is kept on the squawk’s record. When the severity is Grounding, whether the member picked it or you did, the dialog warns you that confirming takes the aircraft out of service and suspends its bookings straight away.
  3. Tap the button that names the severity you are confirming at, for example Confirm as Caution. Cancel closes the dialog and leaves the squawk pending.
  4. You see Squawk confirmed. The squawk moves to open at the severity you chose. If that is grounding, confirming it grounds the asset and suspends future bookings. If you changed the severity, the squawk’s detail screen says so: Severity changed from the old severity to the new one, with your name, the date and time, and your reason if you gave one.

The Confirm button on the squawk’s own screen (tap View Detail) opens the same dialog. To change the severity of a squawk that is already open or deferred, see Change a squawk’s severity.

To dismiss

Section titled “To dismiss”
  1. Tap Dismiss in the opened squawk.
  2. The Dismiss Squawk dialog asks you to explain why this squawk is not a real defect. Enter a reason (for example, Normal engine behaviour, not a fault). The dialog’s Dismiss button stays greyed out until you type something. Cancel closes the dialog and leaves the squawk pending.
  3. Tap Dismiss to confirm.
  4. You see Squawk dismissed. The squawk moves to dismissed and does not affect the asset. The member who reported it gets a Squawk dismissed notification that includes your reason, so write it for them to read. Its detail screen shows a Dismissed as not a defect card with the date and time, your name, and your reason. Everyone who can open the squawk sees it, including the member who reported it.
The dismissal dialog with a reason typed into the reason field, above the Cancel and Dismiss buttonsThe dismissal dialog with a reason typed into the reason field, above the Cancel and Dismiss buttons

If it goes wrong

Section titled “If it goes wrong”
  • “Couldn’t confirm this squawk” or “Couldn’t dismiss this squawk”: nothing has changed. Check your connection and try again. If it keeps failing, reopen the squawk: another admin may have dealt with it already.
  • No Confirm or Dismiss button on a row: the entry is still collapsed. Tap it to open it; the buttons are at the bottom of the opened panel.
  • The queue is empty: there are no pending squawks. Squawks reported by admins skip this step.

See also

Section titled “See also”