Confirm or dismiss a reported squawk
Confirm or dismiss a reported squawk
Section titled “Confirm or dismiss a reported squawk”When the syndicate requires squawk confirmation, 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.
Before you start
Section titled “Before you start”- You must be an owner or admin.
- Only
pendingsquawks can be confirmed or dismissed here. A squawk that is alreadyopen,deferred,resolved, ordismisseddoes not appear on this queue.
- Open the syndicate.
- Go to Pending squawk confirmations. Route:
/syndicates/:syndicateId/squawk-approvals. - Review each card: Description, Severity, Reported by, Date.
To confirm
Section titled “To confirm”- Tap Confirm on the squawk card.
- You see Squawk confirmed. The squawk moves to
open. A grounding squawk immediately grounds the asset and blocks future bookings.
To dismiss
Section titled “To dismiss”- Tap Dismiss on the squawk card.
- Enter a dismissal reason (for example, Normal engine behaviour, not a fault).
- Tap Dismiss to confirm.
- You see Squawk dismissed. The squawk moves to
dismissedand does not affect the asset.
If it goes wrong
Section titled “If it goes wrong”- “Failed to confirm” or “Failed to dismiss” — check your connection and retry.
- The queue is empty — there are no pending squawks. Squawks reported by admins skip this step.
See also
Section titled “See also”- Squawk statuses — the full lifecycle
- Squawk severities — what confirming each severity does
- Report a squawk — the member-side flow that produces
pendingsquawks - Resolve a squawk — next step after confirm