Work orders are jobs for the field or internal maintenance: a header (what, where, when) and usually line items for parts or tasks. The flow is plan → start work → update lines → close when the job is done.
End-to-end workflow
Plan the job
Create a work order with type, site or asset, requested dates, and any safety or access notes. Add line items if your process uses them for materials or steps before you dispatch.
Execute and update
Technicians or assignees set status to in progress, record progress in notes, and add or correct line items (quantities, parts). Keep the order aligned with the actual visit so follow-up and billing stay accurate.
Sign off and close
When work is finished, set completion fields, capture a short result summary, and close the order. If a follow-up visit is required, some teams open a new order to keep history separate.
Common use cases
Planned maintenance on an asset
From the due date or a maintenance plan, open or generate a work order, assign a crew, record parts from stock, and close with labor and time.
Break / fix on site
Log the call with symptom and site; after repair, add line items and close with a note of what was replaced or reset.
Multi-visit or multi-crew job
One header can carry several line or note updates; if policy requires, split by visit so each has a clear record.
Practical tips
Keep line items consistent with the parts you actually use—inventory and costing often depend on them.
Use clear status on the header so dispatch and planning screens stay trustworthy.
Add photos or notes in the body if the product supports it on your build—reduces return visits.
Screens and confirmations
View, header edit, and line modals
You usually open a read view from the list, then edit the header, and open smaller overlays for each line add/edit.
Item lines
Add line opens a separate layer so the main order stays in context while you pick parts or service codes.
Confirmations
Deleting a line or the whole order may ask for confirm so nothing is lost by accident.