Squawk statuses

What it is

A squawk moves through a short lifecycle from first report to a terminal state. At any moment every squawk is in exactly one of five statuses.

pending ─── admin confirms ──▶ open ─── resolved
   │                            │
   │ admin dismisses            │ admin defers
   ▼                            ▼
dismissed                    deferred ──▶ resolved

Terminal statuses: resolved and dismissed. A squawk cannot move out of these.

Who can use it

• Members report squawks (creating a pending or open squawk depending on the syndicate policy).
• Admins and owners confirm, dismiss, defer, and resolve squawks.

Where to find it

• Per-asset squawk list: /syndicates/:syndicateId/assets/:assetId/squawks.
• Pending-approvals queue: /syndicates/:syndicateId/squawk-approvals.
• Individual squawk detail: /squawks/:squawkId.

Fields / options

Status	Serialised	Terminal	Counts toward “active”
Pending	pending	No	Yes
Open	open	No	Yes
Deferred	deferred	No	Yes
Resolved	resolved	Yes	No
Dismissed	dismissed	Yes	No

What each status means

• Pending — reported by a member, awaiting admin review. Used when the syndicate setting “Require squawk confirmation” is on and the reporter is not themselves an admin.
• Open — confirmed. Actively in force. Grounding squawks in this state ground the asset.
• Deferred — admin has acknowledged the issue and allowed the asset to continue operating until a stated date (deferred_until), with a recorded reason.
• Resolved — fixed. No further action needed.
• Dismissed — reviewed and judged not a real defect; dropped without a fix.

Behaviour rules

• Starting status depends on syndicate policy and reporter role:
  • Confirmation required and reporter is not an admin → pending.
  • Otherwise → open.
• Only pending squawks can be confirmed. Confirming transitions to open and stamps confirmed_by / confirmed_at.
• Only pending squawks can be dismissed through the approval flow. Dismissal requires a dismissal reason from the admin.
• Only open grounding squawks can be deferred. Caution and info squawks have no ground effect and do not need deferral. Deferral requires a deferred_until date and a deferral_reason.
• resolved and dismissed are terminal. Reopening is not supported — the correct response is a fresh squawk referencing the original.
• “Active” squawks (pending, open, deferred) appear in the asset’s squawk list; terminal squawks are filtered out of the default view.
• The pending badge on the approvals queue counts only pending squawks.

See also

• Squawk severities
• Airworthiness rules