Pending squawk confirmations
What it is
Section titled “What it is”The Pending Squawk Confirmations screen is an admin queue listing every pending squawk across the syndicate’s aircraft, that is, member-reported squawks that no admin has yet confirmed or dismissed. Each squawk appears as an expandable card headed by the aircraft name, the severity (with its icon and colour), the reporter, and the squawk title, with a PENDING badge. Expanding a card reveals the description, severity, reporter, and report date, plus the Confirm and Dismiss actions and a View Detail link through to the full squawk detail screen.
The queue only fills when the syndicate has Require admin confirmation for squawks switched on (configured on the Booking policy screen, off by default). When the setting is off, or the reporter is an admin, squawks open immediately and never enter this queue.
Who can use it
Section titled “Who can use it”- Admins: full access. Opening the screen as a non-admin shows an Admin access required error instead of the queue.
- Members: do not see this screen. Members see the status of squawks they reported on the aircraft’s squawk list.
Where to find it
Section titled “Where to find it”In the app:
- Open the syndicate.
- Go to the Admin tab and open Pending (or tap the pending-actions icon at the top of the syndicate screen, which opens the same page). The Squawks section comes first.
- On the Pending screen, tap the Squawks row or its Review button.
Route: /syndicates/:syndicateId/squawk-approvals.
Fields / options
Section titled “Fields / options”Each card in the queue shows:
| Field | Notes |
|---|---|
| Aircraft | Card title. |
| Severity | Icon and colour-coded label (grounding, caution, info). See Squawk severities. |
| Reported by | The member who reported the squawk. |
| Title / Description | The squawk title on the card; the full description when expanded. |
| Date | When the squawk was reported, in your timezone. |
| Confirm | Primary action. Opens the Confirm squawk dialog, where you check the severity (pre-selected with the member’s choice, and changeable) and confirm with Confirm as the severity chosen. Moves the squawk to open at that severity and stamps the confirming admin. |
| Dismiss | Secondary action. Requires a reason; closes the squawk as not a real defect. |
| View Detail | Opens the full squawk detail screen, where defer and resolve live. |
Behaviour rules
Section titled “Behaviour rules”- Only
pendingsquawks appear here. Open, deferred, resolved, and dismissed squawks are not listed. The queue spans every aircraft in the syndicate. - Confirming takes effect immediately. The squawk moves to
open; if its severity is grounding, the aircraft is grounded and the bookings spanning the squawk suspend automatically. See Squawk statuses. - The severity is checked as part of confirming. The confirm dialog starts on the severity the member reported. Picking another one confirms the squawk at that severity in the same step, so a report over-called as grounding never grounds the aircraft, and the change goes on the squawk’s record with an optional reason. Cancel leaves the squawk pending.
- Dismissal requires a reason. The card’s Dismiss button opens a dialog whose own Dismiss button (filled, in red) stays disabled until a non-empty reason is entered; Cancel backs out and leaves the squawk pending. The reporter is notified, with the reason, whether the squawk is confirmed or dismissed.
- A dismissed squawk keeps its reason on record. Its detail screen shows a Dismissed as not a defect card with the date and time, the admin who dismissed it, and the reason, to everyone who can open the squawk, the reporter included. It no longer counts as an outstanding defect, so the asset returns to All OK once nothing else is outstanding.
- Confirm and dismiss are the only inline actions. Deferring or resolving a squawk happens on the squawk detail screen, reached via View Detail; a pending squawk must be confirmed before it can be deferred or resolved.
- The queue is live. Cards disappear as this or another admin acts on them, and new reports appear as members submit them. If someone else acted first, your action fails with Couldn’t confirm this squawk. Nothing has changed, so please try again in a moment. (or Couldn’t dismiss this squawk…).
- The count covers only pending squawks. The Squawks count on the Pending page, and the combined count on the pending-actions icon at the top of the syndicate screen, track this queue in real time. Squawks come first on the Pending page because confirming one can ground the aircraft, which suspends bookings and can change what is left to approve.
- Empty state. When nothing is waiting, the screen reads “All confirmed!” with “No squawks awaiting confirmation”.
See also
Section titled “See also”- Pending booking approvals: the companion admin queue for bookings.
- Admin Pending page: every admin queue in one place, and the order they come in.
- Confirm or dismiss a reported squawk: step by step.
- Squawk statuses: the lifecycle a confirmation feeds into.
- Booking policy: the setting that turns this workflow on.