> ## Documentation Index > Fetch the complete documentation index at: https://docs.planeconnection.com/llms.txt > Use this file to discover all available pages before exploring further. # Work Order Statuses > Lifecycle statuses, transition rules, and actions available at each stage of a maintenance work order. Every maintenance work order in PlaneConnection follows a defined lifecycle from initial creation through completion, verification, and closure. This page documents each status, the allowed transitions between them, who can perform each transition, and the regulatory requirements that apply at key stages. Work orders are the central record type in the Maintenance module. They link discrepancies, parts, labor, billing estimates, and logbook entries into a single auditable package per 14 CFR 43.9. ## Status Summary | Status | API Value | Aircraft Dispatchable | Description | | ---------------------------------------------- | ------------------ | :-------------------: | ------------------------------------------------------------------------------------------- | | Draft | `draft` | Yes | Work order created but not yet opened. Used for planning and estimate preparation. | | Open | `open` | Depends on scope | Work order approved and ready for work to begin. Parts and labor can be assigned. | | In Progress | `in_progress` | No (if grounding) | Active work underway. Technicians are performing maintenance tasks. | | Awaiting Parts | `awaiting_parts` | Depends on scope | Work paused pending parts arrival. Tracks parts-related delays separately from active work. | | Pending Approval | `pending_approval` | No | Work scope or cost change requires management approval before proceeding. | | Completed | `completed` | No | All work items finished. Awaiting inspector verification before return to service. | | Verified | `verified` | Yes | Inspector has signed off. Aircraft approved for return to service per 14 CFR 43.3. | | Cancelled | `cancelled` | Yes | Work order cancelled. No further action. Record retained for audit trail. | ## Status Lifecycle ```mermaid theme={} stateDiagram-v2 [*] --> Draft : Work order created Draft --> Open : Approve scope Draft --> Cancelled : Cancel before start Open --> In_Progress : Work begins Open --> Cancelled : Cancel before start In_Progress --> Awaiting_Parts : Parts needed In_Progress --> Pending_Approval : Scope/cost change In_Progress --> Completed : All work items done Awaiting_Parts --> In_Progress : Parts received Awaiting_Parts --> Cancelled : Cancel Pending_Approval --> In_Progress : Approved Pending_Approval --> Cancelled : Rejected/cancelled Completed --> Verified : Inspector sign-off Completed --> In_Progress : Rework required Verified --> [*] Cancelled --> [*] ``` ## Detailed Status Definitions ### Draft The initial status when a work order is created. Draft work orders are used for planning: building the work scope, adding line items, estimating labor hours, and generating billing estimates before committing resources. **Who can create:** Any user with `maintenance_ops:write` permission (Director of Maintenance, maintenance staff, dispatchers). **Actions available:** * Edit title, description, priority, and assigned technician * Add or remove work order items (labor tasks and parts) * Generate billing estimates * Transition to **Open** or **Cancelled** **Work order number format:** `WO-{YYYY}-{NNNN}` (e.g., `WO-2026-0042`), assigned at creation and immutable. ### Open The work order has been reviewed, the scope is approved, and it is ready for a technician to begin work. Opening a work order signals that resources (hangar space, parts, personnel) should be allocated. **Who can transition here:** Director of Maintenance or any user with `maintenance_ops:write` permission. **Actions available:** * Assign or reassign technician * Modify work items before work starts * Transition to **In Progress** or **Cancelled** ### In Progress Active maintenance work is underway. The assigned technician is performing tasks documented in the work order items. Time tracking and parts issuance happen during this phase. **Who can transition here:** Assigned technician or Director of Maintenance. **Actions available:** * Log actual hours worked * Issue parts from inventory (creates part transaction records) * Add notes and attachments (photos, diagrams) * Add additional work items discovered during inspection * Transition to **Awaiting Parts**, **Pending Approval**, or **Completed** ### Awaiting Parts Work has been paused because one or more required parts are not in inventory. This status is tracked separately from In Progress so that parts-delay metrics can be reported independently from active work time. **Who can transition here:** Assigned technician or parts coordinator. **Actions available:** * Record parts on order (purchase order reference) * Receive parts into inventory * Transition back to **In Progress** when parts arrive ### Pending Approval During work, the technician discovered additional scope (e.g., corrosion found during an inspection) or costs will exceed the original estimate. This status pauses work until a Director of Maintenance or authorized manager reviews and approves the expanded scope. **Who can transition here:** Assigned technician (requests approval). **Who can approve:** Director of Maintenance, Accountable Executive, or any user with `maintenance_ops:admin` permission. **Actions available:** * Review expanded scope and revised estimate * Approve (returns to **In Progress**) or reject/cancel ### Completed All work items have been performed and documented. The technician has recorded actual hours, parts used, and work descriptions per 14 CFR 43.9. The work order now requires inspector verification before the aircraft can return to service. **Who can transition here:** Assigned technician (marks work as done). **Actions available:** * Review work summary * Transition to **Verified** (inspector sign-off) or back to **In Progress** (rework required) A completed work order does **not** authorize return to service. The aircraft remains out of dispatch until an authorized inspector verifies the work and transitions the order to Verified status per 14 CFR 43.3. ### Verified (Inspector Sign-off) An authorized person (IA certificate holder or authorized inspector) has reviewed all completed work, confirmed that it meets airworthiness requirements, and approved the aircraft for return to service. This is the **return-to-service authorization** required by 14 CFR 43.3 and 14 CFR 43.7. **Who can transition here:** Only users with inspector authorization (IA certificate type or Director of Maintenance with appropriate delegation). **Verification checklist (all required):** 1. All work items have been completed as specified 2. All parts used are documented with part numbers and serial numbers 3. Work complies with applicable airworthiness requirements (14 CFR 43.9) 4. Aircraft is approved for return to service (14 CFR 43.3) **What happens at verification:** * `verified_by` and `verified_at` fields are recorded * Work order costs are synced to accounting (QuickBooks integration if configured) * Aircraft status can be returned to Active * Maintenance due items linked to this work order are updated with new compliance dates ### Cancelled The work order has been cancelled and no further work will be performed. The record is retained in the system for audit purposes -- cancelled work orders are soft-deleted (`deleted_at IS NULL` filters them from normal views, but they remain queryable for compliance audits). **Who can cancel:** Director of Maintenance or any user with `maintenance_ops:admin` permission. A work order cannot be cancelled once it has reached **Completed** or **Verified** status. If rework is needed after verification, a new work order must be created referencing the original. ## Transition Rules Summary | From | To | Required Role | Condition | | ---------------- | ---------------- | ----------------------- | ------------------------------- | | Draft | Open | `maintenance_ops:write` | At least one work item exists | | Draft | Cancelled | `maintenance_ops:write` | None | | Open | In Progress | `maintenance_ops:write` | Technician assigned | | Open | Cancelled | `maintenance_ops:write` | None | | In Progress | Awaiting Parts | `maintenance_ops:write` | Parts shortage documented | | In Progress | Pending Approval | `maintenance_ops:write` | Scope change noted | | In Progress | Completed | `maintenance_ops:write` | All items marked done | | Awaiting Parts | In Progress | `maintenance_ops:write` | Parts received | | Pending Approval | In Progress | `maintenance_ops:admin` | Scope approved | | Pending Approval | Cancelled | `maintenance_ops:admin` | Scope rejected | | Completed | Verified | Inspector (IA/DOM) | All 4 checklist items confirmed | | Completed | In Progress | Inspector (IA/DOM) | Rework required | ## Priority Levels Each work order carries a priority that affects scheduling and dispatch decisions: | Priority | API Value | Description | | ------------------------------------ | --------- | ------------------------------------------------------------------------------------ | | Routine | `routine` | Standard scheduled maintenance. Normal planning timeline. | | Urgent | `urgent` | Requires prompt attention. Should be scheduled within 24-48 hours. | | AOG | `aog` | Aircraft on Ground. Highest priority. Triggers AOG labor rate multiplier in billing. | ## Work Order Types | Type | API Value | Description | | ------------- | --------------- | -------------------------------------------------------------------------------------------------------- | | Scheduled | `scheduled` | Planned maintenance per the aircraft's maintenance program (inspections, overhauls, time-limited tasks). | | Unscheduled | `unscheduled` | Corrective maintenance for reported discrepancies or squawks. | | Inspection | `inspection` | Dedicated inspection work (annual, progressive, phase checks). | | AD Compliance | `ad_compliance` | Work performed to comply with an Airworthiness Directive (14 CFR Part 39). | ## Related REST API reference for work orders, parts, and billing. Labor rates, parts markup, and the estimate-to-invoice lifecycle. AD/SB tracking, RII catalog, and FAA Form 337 requirements. How maintenance data flows between work orders, due items, and other modules.