Work order
Work order explained: the record that authorises the work
A work order is the formal record that authorises a specific piece of work on a specific asset, sets out what has to be done, and becomes the evidence that it was completed. It carries the asset, the task, the priority, the accountable person, and the labour, parts and cost the job is permitted to consume.
For field service
Know what the job needs before the van rolls
Venta Capture, a product of VentaVid, lets the customer show you the fault first, so the engineer arrives with the right part or does not need to arrive at all.
You will see it written as work order, works order, WO, and in some maintenance systems as a maintenance order. The authorising function is identical in each case.
What does a work order actually mean?
Two words in the definition do the heavy lifting, and both get skipped.
Authorises. A work order is permission. Until one exists, nobody should be spending labour hours, drawing parts from stores, or committing the organisation to a cost. That is why work orders carry approval states and cost codes and why raising one retrospectively, after the work is already done, is treated as a control failure in most audited environments.
Specific. A work order that says "investigate noise on line 3" is not really a work order. It is a request that has been given an ID. Anything that has to be decided on site rather than before dispatch will be decided by whoever happens to be standing there.
What a work order has to contain
- Identifier and type. Corrective, preventive, inspection, installation, emergency. Type drives how the job is scheduled and how it is reported later.
- Asset and location. The functional location and the specific asset, not just the site address.
- Scope of work. The task, the procedure or checklist to follow, and the acceptance criterion for "done".
- Priority and dates. Required-by date, contractual response and resolution commitments, and any access window.
- Resources. Skills or certifications needed, estimated labour hours, parts reserved, tools, permits.
- Safety and compliance. Permit to work, isolation requirements, risk assessment, regulatory references.
- Close-out data. Actual hours, parts consumed, findings, failure codes, and the completion evidence.
The last line is the one most operations under-invest in, and it is the one that determines whether next year's maintenance decisions rest on data or on memory.
How a work order moves through its life cycle
Most systems run some version of the same states: requested, approved, planned, scheduled, dispatched, in progress, completed, verified, closed.
Two of those transitions cause most of the reporting disputes. The first is approval, because a request that is never converted is invisible in every downstream number. The second is the split between completed and closed: a technician marking a job complete on site is not the same event as a supervisor accepting the work, and treating them as one event hides rework.
Whether a repeat visit is logged as a continuation of the original work order or as a fresh one also decides what your first-time fix rate reports. Aquant's 2025 Field Service Benchmark Report found that a failed first visit adds two more visits on average and extends resolution by 14 days (reported in TechNation). Split those into three separate work orders and the failure disappears from the metric while the cost stays exactly where it was.
Work order, work request, job card: which is which
- Work request. An ask. Anyone can raise one. It has no authority and no committed resource until it is reviewed.
- Work order. The authorising record created when that request is approved, or when a planned maintenance schedule generates one automatically.
- Job card. The shop-floor variant: the sheet a technician works from and books time against, derived from the work order rather than replacing it. Common everyday term in UK, South African and Middle Eastern workshops, where "open a job card" means the same practical thing as raising a work order does in a utility or a plant.
One work order can produce several job cards when the job crosses trades or shifts. The authority still sits with the work order.
A work order in practice: a worked example
A facilities team receives a request about a failing roller shutter at a distribution centre. The supervisor approves it as a corrective work order against asset DR-114, priority 2, estimates three hours, reserves a limit switch and a motor brake from stores, and attaches the permit for working at height. The technician closes it with two hours booked, one part consumed, a failure code of "limit switch, wear", and photographs of the reset travel positions.
That closed record is what tells the team, eleven months later, that DR-114 has now failed twice on the same component.
Where work orders go wrong
Thin intake. A description written by someone who cannot see the equipment produces a plan that is wrong before anyone leaves the depot. Structured service intake is worth more than any amount of scheduling cleverness downstream.
Free-text close-out. "Fixed" is not a failure code. Without structured findings, the work order history cannot answer the only question that matters at renewal: what keeps breaking, and why.
No completion evidence. When the invoice is queried or the warranty claim is challenged, the work order is your position. A record with structured proof of work attached settles arguments that a text field cannot.
