Check trip readiness before you fly
The fleet-wide dashboard that shows which trips are ready to go, and which gate is holding each one back.
- Open Trip Readiness from the Dispatch & Ops navigation.
- Read the summary strip: how many trips fall in the −30/+120-day window, and how many are READY, NOT READY, BLOCKED, or UNCHECKED — plus a chip for each gate with outstanding trips.
- Use the status pills (All / Not Ready / Ready / Unchecked) to filter the table, and sort or filter by column to find what needs attention.
- Read the table: one row per trip, one column per readiness gate — crew, manifest, fuel, pax, permits, briefing, and compliance — plus BLOCKED for a grounded tail or a canceled leg.
- Select a row to drill into that trip's detail: a trip-level ready/not-ready badge and the per-leg gate grid behind it.
Every gate state — SATISFIED, PENDING_VERIFICATION, or BLOCKED — is rendered exactly as the API returns it. The board recomputes nothing and only shows a trip as ready when every gate on every leg is SATISFIED; from seeded or modeled data a gate reads PENDING_VERIFICATION, never a pass. This is an advisory rollup — the release decision itself is made at dispatch, not on this board.
On a demo tenant, some human-in-the-loop steps that feed these gates — like generating a leg's manifest — can auto-complete elsewhere in the trip's lifecycle and are recorded as DEMO-AUTO, never silently skipped. This board only ever reflects records that already exist; it never manufactures a SATISFIED state, demo tenant or not.
If a trip is blocked on crew, go assign or reassign it from Assign crew and aircraft to legs.