Work a trip in the Trip Workspace

Every trip has one record: the Trip Workspace. It opens from a trip link anywhere in the OS — a quote, the readiness board, a leg on the dispatch board — never by typing in an id.

1. Open the trip. The header shows its highlights (legs, PAX, route span, tails) and an ordered leg list, each with PIC/SIC, OOOI status, ground-ops state, and its billing line.
2. Start on Overview, the default tab — the leg list, the whole-trip Swap Tail action (see Swap a tail on a leg or a trip), and a billing strip that links to the trip's invoice once one exists.
3. Before departure, check Briefing — the briefing studio for this trip.
4. Assemble Packet whenever you need the trip's documents pulled into one packet. Its provenance strip always shows the compliance state as PENDING_VERIFICATION — the packet mirrors on-screen sections verbatim; it never issues a compliance determination of its own.
5. Watch Milestones / ETA as legs progress, for the trip's milestone and ETA cascade.
6. If the trip is disrupted, work it from Recovery — IROPS recovery lanes that reuse the same dispatch and compliance blocks you'd see elsewhere on the trip.
7. Use Support for support-desk context tied to this trip.
8. Once every leg is terminal, finish on Close-out — reconcile quoted vs actual and mint any adjustment. See Close out a trip and settle the invoice.

To build the trip this workspace shows, see Build a trip from a quote. To add or change a leg on it, see Add and edit legs.