CMMS & Maintenance Guide 12 min read

The maintenance work order process — request to closure

The work order is the instruction at the centre of every repair. Follow its real lifecycle — raised, assigned, diagnosed, spares issued, downtime captured, closed — and see how a status history and audit trail turn a repair into a record you can trust.

12 min read Vidya Kathare · July 18, 2026 Foundations
The work order lifecycle
01
Request / trigger
Breakdown reported or PM falls due
Raised
02
Create & authorise
Work order against the asset
Draft
03
Assign technician
Status to in-progress
Assigned
04
Diagnose & repair
Fault, root cause, actions
In repair
05
Spares & downtime
Issue against WO, capture cost
Costed
06
Close
History, MTTR/MTBF update
Closed

What a work order is

A maintenance work order is the authorised instruction to carry out a defined maintenance job on a defined asset. It is the single record that answers, for one repair: what needs doing and why, on which machine, by whom, using which spares, taking how long, and at what cost. It exists from the moment the need is raised until the job is closed — and while it lives, it accumulates everything that happens to the asset during that job.

In a CMMS, the work order is not a paper slip that gets lost; it is a document in the system, linked to the asset, carrying its own status and history. That single idea — the work order as a linked, tracked record rather than a scrap of paper — is what turns maintenance from anecdote into evidence. For where it sits in the wider system, see the pillar, what is CMMS software.

Work order vs job card

People use "work order" and "job card" interchangeably, but they are two faces of the same job. The work order is the management and authorisation record — the approval, the asset, the assignment, the cost, the status. The job card is the technician-facing work sheet — the tasks and checklist, the readings, the labour time, the spares used at the machine. On a shared document engine they are the same underlying record viewed for different purposes, so nothing is re-keyed and the two never drift out of sync. The planner sees the work order; the fitter sees the job card; both are looking at one document.

The six stages, in detail

Whether it starts as a breakdown or a preventive task, a work order moves through the same lifecycle. Here it is, stage by stage.

01
Request / trigger
A breakdown is reported, or a preventive schedule falls due, creating the need
02
Create & authorise
A work order is opened against the asset, with the task and any work permit
03
Assign technician
The planner assigns it; status moves to in-progress
04
Diagnose & repair
Technician records fault, root cause and the repair actions taken
05
Spares & downtime
Spares issued against the WO; downtime, labour and cost captured
06
Close
Completed then closed; asset history and MTTR/MTBF update

Notice that stages 1 and 2 differ by origin but converge immediately. A breakdown is reported by a production supervisor and the downtime clock starts at once; a preventive job is generated when its schedule falls due and appears on a PM-due list. From stage 3 onward — assign, repair, spares, close — the flow is identical, which is why one work order engine can carry both kinds of work.

Status history and audit trail

What makes a CMMS work order more than a digital form is the status history that travels with it. Every state the work order passes through — Draft, In-Progress, Completed, Closed — is recorded with who moved it and when. Layered underneath is the audit trail: every change to the record itself is logged. Together they answer the questions an auditor, a customer or your own management will eventually ask: what was done, when, by whom, against which work permit, and what was replaced?

Why the trail matters
A repair without a status history is a story someone remembers. A work order with a status history and audit trail is a record you can stand behind — in an ISO 9001 audit, a warranty dispute, or a failure investigation.
The evidence only exists if it is captured as the work happens. You cannot reconstruct a genuine audit trail the night before the assessor arrives.

Want to see a real work order move from raised to closed?

We can walk a breakdown ticket and a preventive job through the full lifecycle — assignment, spares, downtime, closure — on your own assets in 30 minutes.

Get a demo

Spares against the work order

Stage 5 is where maintenance and stores meet, and doing it properly is what makes cost figures honest. When a technician needs a part, it is issued from stores against the specific work order. The issue decrements stock and attaches the spare's cost to that job — so consumption is tied to the asset and the repair, not lost in a general stores figure. Because each asset carries a spare bill of materials, the work order already knows which spares fit the machine and whether they are on hand.

If a required spare is not in stock, a maintenance purchase can be raised to procure it — the same connection that lets a reorder alert flow through to Fast Inventory & Purchase. This is also the discipline that keeps MTTR honest: the biggest reason a work order sits open is a part that has not arrived, and the spare BoM plus reorder levels are what stop that from happening. For the wider treatment, see preventive vs breakdown maintenance.

Preventive vs breakdown work orders

The two origins of a work order differ in a few important ways once you look closely.

AspectBreakdown work orderPreventive work order
OriginReported failure — reactiveSchedule falls due — planned
Downtime clockStarts on reportUsually done in a planned window
ContentFault, root cause, repair actionsChecklist tasks, readings, permit
Not-OK findingIs the failure itselfCan spawn a corrective work order
FeedsMTTR, downtime, breakdown frequencyPM compliance, MTBF over time
LifecycleIdentical from assign to close — one engine, two triggers

What the closed work order feeds

Closing a work order is not the end of its usefulness — it is where its data goes to work. On closure, the job joins the asset's maintenance history and updates its reliability numbers. A breakdown work order, with its downtime timestamps, feeds MTTR and breakdown frequency; a preventive one feeds PM compliance — planned versus completed — and, over time, a rising MTBF. Labour and spare cost roll up per asset, so maintenance spend becomes attributable.

This is the quiet payoff of doing the process properly: every closed work order makes the dashboards a little truer. The reliability metrics a plant head watches are not entered by hand — they are the arithmetic of thousands of well-closed work orders. Skip the discipline at the work-order level and the KPIs above are fiction; keep it and they become a management instrument.

The work order is the instruction at the centre of maintenance: a defined task on a defined asset, tracked from raised through in-progress to closed, with the spares it consumed and the time it took recorded against it.

How Fast Maintenance runs it

Fast Maintenance Software runs the work order on the shared Fast Suite document engine — the same header-plus-lines record with a status history that drives tickets across the platform — so maintenance inherits the platform's audit trail, approvals and reporting for free:

1
One engine, two triggers. Breakdown tickets and preventive jobs both become work orders on the same document engine, with a Draft → In-Progress → Completed → Closed lifecycle.
2
Assign, diagnose, record. Technician assignment, fault and root-cause capture, labour time and photos travel on the work order — the job card and work order being one record.
3
Spares issued against the WO. Parts drawn from the spare BoM decrement stock and cost the job, with procurement via Fast Inventory & Purchase when stock is short.
4
Status history & audit trail. Every transition is logged with who and when, producing the ISO 9001 / IATF 16949 evidence auditors ask for.
5
Closure feeds the KPIs. Closed work orders update asset history, PM compliance and MTTR/MTBF dashboards automatically — with alerts over email, SMS and WhatsApp along the way.

The same lifecycle serves manufacturing plants, facilities and utilities and equipment and fleet operators, cloud or on-premise. To see how the whole system fits together end to end, read how CMMS software works.

Frequently asked questions

What is a maintenance work order?

A maintenance work order is the authorised instruction to carry out a defined maintenance job on a defined asset. It records what needs doing and why, the asset it applies to, the technician assigned, the tasks or checklist, the labour time spent, the spares consumed, any external service, and the resulting cost — tracked from the moment it is raised, through in-progress, to completed and closed. The technician-facing version of that record is often called a job card. In a CMMS the work order is a document that carries all of this as one linked record with a status history.

What are the steps in the maintenance work order process?

The maintenance work order process runs through six stages: (1) request or trigger — a breakdown is reported or a preventive schedule falls due; (2) create and authorise the work order against the asset; (3) assign a technician and move it to in-progress; (4) diagnose and repair, recording fault, root cause and actions; (5) issue spares from stores against the work order and capture downtime, labour and cost; and (6) close the work order — completed then closed — updating the asset's maintenance history and its MTTR/MTBF. Every transition is written to a status history and audit trail.

What is the difference between a work order and a job card?

They are two faces of the same maintenance job. The work order is the authorised instruction and the management record — it holds the approval, the asset, the assignment, the cost and the status. The job card is the technician-facing work sheet — the tasks, checklist, readings, labour time and spares used at the machine. In a CMMS built on a shared document engine they are the same underlying document viewed for different purposes, so nothing is re-keyed and both stay in sync.

Why is a status history and audit trail important on a work order?

The status history shows every state a work order passed through — raised, assigned, in-progress, completed, closed — with who did what and when. The audit trail records every change to the record. Together they make maintenance traceable and defensible: you can prove what was done, by whom, against which work permit, and what was replaced. That is exactly the evidence an ISO 9001 or IATF 16949 auditor expects, and it only exists if the steps are captured as the work happens rather than reconstructed from memory afterwards.

How are spare parts linked to a work order?

When a technician needs a part, it is issued from stores against the specific work order — the issue decrements stock and attaches the spare's cost to that job. Because each asset carries a spare bill of materials, the work order already knows which spares fit the machine and whether they are in stock. If a required spare is not available, a maintenance purchase can be raised to procure it. Issuing spares against the work order is what makes per-asset spare consumption and maintenance cost accurate.

See a work order run from request to closure

A 30-minute Fast Maintenance Software demo walks a breakdown ticket and a preventive job through assignment, spares issue, downtime capture and closure — with the status history and audit trail — cloud or on-premise, on your own assets.

Get a demo
No commitment. No slides. Your plant on screen.