Skip to content

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.

  • 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.
  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
  1. Tap Confirm in the opened squawk.
  2. You see Squawk confirmed. The squawk moves to open. If the squawk is a grounding severity, confirming it grounds the asset and suspends future bookings.
  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.
  3. Tap Dismiss to confirm.
  4. You see Squawk dismissed. The squawk moves to dismissed and does not affect the asset.
The dismissal dialog with a reason typed into the reason field, above the Dismiss buttonThe dismissal dialog with a reason typed into the reason field, above the Dismiss button
  • “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.