Work order types
Every work order belongs to exactly one type. The type drives which step types are available, which permissions are checked, and how the WO appears in lists and reports.
| Type | Used for |
|---|---|
PRODUCTION |
Manufacturing a product to stock ā typically built from an assembly task and BOM. |
REPAIR |
Fixing a specific customer-owned asset. Tracks serial numbers, repair tasks and shipments. |
INTERNAL |
Maintenance on the company's own machines or fleet ā internal-cost. |
PROJECT |
Long-running multi-phase job that doesn't fit Production or Repair (custom builds, installations). |
LEAVE |
Auto-generated workflow for leave, OT and custom-schedule requests. Created by the leave module ā not usually made by hand. |
Work order statuses
A work order moves through these states. Most users see a coloured chip on the WO card showing the current status.
| Status | Meaning | Can edit lines? | Can complete steps? |
|---|---|---|---|
DRAFT |
Planning ā you're still building the routing. The WO is not yet active. | Yes | No |
TEMPLATE |
Reusable blueprint. Saved routing that can spawn new WOs but is never executed itself. | Yes | No |
RELEASED |
Approved with stock soft-allocated. (Transient state ā the system flips it to IN_PROGRESS as soon as the first step activates.) | No | ā |
IN_PROGRESS |
Active on the floor. Steps are running; partial completions are allowed. | Add only at higher priority than the active group | Yes |
COMPLETED |
All steps physically done (100%). | No | No |
CLOSED |
Financials finalised and synced to Unleashed. End of life. | No | No |
CANCELLED |
Aborted. Reachable from DRAFT, TEMPLATE, or IN_PROGRESS. All non-terminal lines become CANCELLED with it. | No | No |
Status transitions
DRAFT āāāāāāāŗ IN_PROGRESS āāāŗ COMPLETED āāāŗ CLOSED
ā ā²
āāāŗ TEMPLATE (blueprint, not executable)
ā
āāāŗ CANCELLED (also from TEMPLATE and IN_PROGRESS)
The RELEASED status is real but you'll rarely see it on screen ā it's the half-step between DRAFT and IN_PROGRESS, used while the routing engine is still activating the first batch of steps.
Priority
A secondary axis. Doesn't change what the WO does ā only how urgently it's shown in lists and notifications.
| Priority | Used for |
|---|---|
LOW |
Best-effort ā pick up when nothing more urgent is open. |
NORMAL |
Default ā standard turnaround. |
URGENT |
Promote ahead of NORMAL in the queue. |
CRITICAL |
Highest visual priority. Used sparingly ā typically with a customer SLA at stake. |
Priority shows on the WO card and on the dashboard; the routing engine doesn't read it. Step-level execution order is governed by executionPriority on each line, not by the WO's priority.
Tips
- You can only delete DRAFT and TEMPLATE WOs. Anything else has to be CANCELLED ā that preserves the audit trail.
- A TEMPLATE never has a real
IN_PROGRESSlife of its own ā it spawns DRAFT WOs (manually from Work Orders ā Create New Work Order ā From Template, or automatically from the Schedules tab). - CLOSED is a one-way street. The system uses it to mark a WO as fully reconciled with Unleashed (Sales/Purchase/Inventory). Don't confuse it with COMPLETED ā that one is just physically done.
- Cancelling an IN_PROGRESS WO is a heavy action: it runs
onCancel()on every non-terminal step, which can roll back leave deductions, refund unused inventory reservations, and so on. Always read the cancel-confirm dialog.