Skip to main content
A work order moves through states. This page documents the defaults a new organisation starts with — yours may differ, because the lifecycle is configurable.

The states

The category is what reports count, not the name. Rename “Waiting for Parts” to “Awaiting spares” and every chart still counts it as on hold. This is why renaming a status is safe.

What a status decides

Each status carries flags that change what the product does — not just what it displays:

Allowed moves

Getting started
Doing the work
Getting blocked, and unblocked A job can be blocked before anyone starts it — a vendor booked for tomorrow, parts that have not arrived — so waiting is reachable from Open, Assigned, Accepted and In Progress. Backing out
Cancel now works from any of the nine open, active and on-hold states — Open through Waiting for Approval. Earlier versions only allowed it from Open, Assigned and In Progress; everything else had to be walked back to one of those first. Every cancellation asks for a typed reason, no exceptions. This is the default model — an organisation that has customised its own status model keeps whatever cancellation rules it already configured.
Retiring the related asset cancels a work order’s open jobs for you — see asset lifecycle for what retirement does.

Service levels

Priority carries a service level: a promise about response and resolution. The clock runs while the job is open, pauses in the on-hold states, and stops at Completed. That is why “Waiting for Parts” is not a way to hide a late job — the clock pauses, but the paused time is recorded and the SLA breached view still finds jobs that ran out. Configure priorities and their service levels under work settings.

Changing any of this

Add states, rename them, and change which moves are allowed under statuses and transitions. One rule the product enforces: what a status means to records already in it cannot change while any record sits there, but what may happen next always can.