Base Camp™READ 02 OF 04

Work Order Management

The work order is the smallest unit of truth in your operation. Get it right and every KPI downstream follows.

Some operations treat the work order as paperwork — a box to close so the truck can leave the shop. But that means losing valuable information. The WO is the record: what failed, why, what it cost, how long it took, who touched it, and which parts went in. Get that record right and your upstream and downstream KPIs get sharper.

The Four Jobs of a Work Order

A work order does four jobs at once:

Operational
It authorises and sequences the work.
Financial
It captures labour, parts, and outside spend against an asset.
Safety & Compliance
It ensures minimum asset upkeep and proves a defect was resolved (critical for NSC).
Analytical
It feeds every reliability, performance and cost KPI and enables accurate forecasting.

When people say “our data is bad,” nine times out of ten it starts with work order tracking.

The WO Lifecycle — Where Time Actually Goes

Work Order Cycle Time is the elapsed time from when a unit enters the shop to when it is back in service. The repair itself is rarely the problem. The delays hide in the handoffs.

1
Intake
WO is written; priority is set.
2
Diagnosis
Fault identified; parts scoped.
3
Parts Wait
Sourcing, procurement, delivery.
4
Active Repair← everything else is a wait to attack
The only phase that turns a wrench.
5
QA / Inspection
Work verified before return to service.
6
Administrative Close
Final codes, costs, meter reads entered.

Intake — The WO Is Born Here

The call-in is where priority gets set or lost. When an operator phones a problem in from the field, details can get lost in translation and the WO opens at the wrong priority. The asset stays on the road when it should have been pulled — or ties up a bay when it could have safely waited.

Let the machine tell you before the driver does. Fleets can lean on onboard diagnostics to pre-determine the likely issue — and let qualified staff run a remote pre-diagnostic before the unit rolls in. That lets the shop stage the parts it will need ahead of time. In most cases, returning an unused part costs far less than a unit sitting down, waiting on a valve or a rebuild kit.

WO Age Is the Real Signal

Work order age is not an administrative metric — it is the diagnostic signal for the entire maintenance operation. A WO that ages is telling you something is stuck: waiting for parts, waiting for a technician, waiting for approval, or simply never closed.

Pull every WO by status and measure how long each has been sitting. The reasons cascade into their own investigations:

  • Parts delays — is this vendor-specific? Or do we have a general supply-chain problem?
  • Incomplete WOs — a required field is missing or a step was skipped.
  • Third-party delays — why is the unit delayed? Parts, labour, approval?
  • Approval bottlenecks — the work is done but stuck behind a sign-off.

WO age analysis is one of the highest-return diagnostic exercises available. It costs nothing to run and almost always surfaces actionable findings on the first review.

The Decision Catch-22

A repair decision stalls — not because the work is hard, but because leadership does not have the data, or does not trust the data they have got. Nobody wants to own the call. It gets pushed between operations, maintenance, and finance — and while everyone waits to be sure, the asset sits there quietly stacking up downtime and cost. Work order coding discipline is what fixes the data issue.

The irony: the fear of making the wrong call becomes the most expensive call of all. The fix is not another meeting — it is a clear SOP on repair approvals and a review process. Decide the decision rights once, in advance: who can approve what, at what dollar threshold, inside what time-frame, and who it escalates to when the clock runs out. Paired with clean data, the decisions are made with confidence.

Reason-Code Discipline

Everything you report about planned vs. unplanned work depends on one small act: a correctly coded WO at the time of initiation. If reason codes are not mandatory, are not trained, and are not enforced, the data cannot tell a breakdown from a scheduled PM — and every availability and reliability KPI downstream becomes unreliable.

This is a training and supervisory issue, not a system issue. The system can require the field; only the shop floor culture makes the entry honest.

From the field: Show people what their own data tells them, and they will start protecting it. I have walked into shops where mechanics saw no point in careful WO entry — until we showed them the insights built from their own records. Once people can see it, it lands differently.

Capture the Work That Never Reaches the CMMS

Your WO data is only as complete as what actually gets recorded. Three leaks quietly distort the record:

  • Field / operator work — a scheduled service done in the field that never gets a work record. The CMMS marks the PM as missed even though the work was done.
  • Credit-card repairs — a driver pays on a company card; the transaction goes straight to accounting and bypasses the CMMS entirely.
  • Accounting-routed invoices — supplier invoices for PM or repair work route to AP and never get entered against the asset.

Regularly cross-check accounts payable against the CMMS. Every dollar of maintenance work that lands in AP but not in the WO record is a hole in your cost data — and it always makes your assets look cheaper to run than they are.

WO Management & NSC Compliance

For fleets under Canada’s National Safety Code, the work order is not just an operational record — it is your compliance evidence. Two hard rules:

  • The defect-to-WO link must be enforced. Best-practice CMMS systems flag Schedule 1 defects automatically and generate a prioritised WO. If yours does not, that link has to be enforced manually and audited regularly.
  • NSC-regulated PMs have a small tolerance window. A PM performed outside the scheduled interval is recorded as non-compliant and directly affects the carrier’s Safety Fitness Certificate rating in the event of a compliance audit.

Your open-defect list and your PM-due list are compliance documents.

The Bottom Line

You do not fix work order management by working faster. You fix it by making the WO an honest, complete, well-classified record — and by attacking the waits between phases instead of just the wrench time inside them. Turn on the system controls, enforce the reason codes, reconcile the spend that hides in AP, and triage the backlog. Do that, and every KPI in this guide gets more accurate.

The One-Paragraph Version

The work order is the foundation of every performance KPI you report — availability, cost per hour, PM compliance, reliability, all of it. A WO that is incomplete, misclassified, or never closed is a lie your dashboards will repeat indefinitely. Fix the discipline at intake, enforce reason codes, reconcile the spend that bypasses the CMMS through AP and credit cards, and attack the wait phases — parts, queue, and admin close — not the wrench time; that is a stand-alone project in itself. Turn on your system controls, build a triage habit, and for NSC fleets, treat the open-defect and PM-due lists as the compliance documents they are. Get the WO right and the data takes care of itself.

— Dee

© 2026 Altitude Assets. All rights reserved. Base Camp™ and the Altitude Method™ are trademarks of Altitude Assets. This material may not be reproduced or redistributed without written permission.