A work order is a job for a technician — the dispatchable unit that comes out of a ticket when someone needs to go on site. It carries scheduling, parts, labor, a checklist, and a sign-off — the record that the field work order management system turns into a closed, invoiced job.
Lifecycle
DRAFT → SCHEDULED → DISPATCHED → IN_PROGRESS → COMPLETED
(plus ON_HOLD and CANCELLED)
Create
Create a work order (optionally straight from a ticket). It starts as a draft.
Schedule
Assign a technician and a time window. A scheduled order can be re-scheduled later.
Dispatch
Send it to the technician — it appears in their field app.
Check in & work
The technician checks in on site (moving it to in progress), does the work, and logs what they used.
Complete
Complete the order with a sign-off. Non-terminal orders can be put on hold or cancelled.
A work order records its number, title, description, linked ticket/site/asset, assigned technician, scheduled window, check-in/out and completed times, and the check-in location.
What's captured on the job
- Parts — line items with quantity and unit cost. Pull them from the inventory catalog (which decrements stock and snapshots the name and cost) or add them ad hoc. Removing a catalog part returns the stock.
- Labor — time entries in minutes, with an optional note and the technician.
- Checklist / tasks — an ordered task list you can add to, reorder, tick off, edit, and remove.
- Sign-off — on-site signature capture: signed-by name, signer title, and time.
- Comments & attachments — a timeline and photo/document uploads per order.
Note
Parts drawn and labor logged flow straight into invoicing — a completed order becomes a draft invoice priced from its parts plus labor × your labor rate.