A work order is a formal, tracked instruction that authorizes a piece of work, captures who is doing it, and records the outcome. In manufacturing, the work order is the smallest accounting unit of maintenance — every breakdown, every PM, every project rolls up to a work order somewhere in the system.

This guide answers what a work order is, what it is not, the four types you will encounter in a manufacturing plant, the standard lifecycle from request to close-out, and why a plant without a real work order discipline cannot improve its reliability metrics no matter how good its technicians are.

The Working Definition

A work order, in its simplest form, is a record that contains: who requested the work, what asset it is on, what needs to be done, who is assigned, what was actually done, what parts were used, and how long it took. Anything less than that is a request, not a work order.

The distinction matters because most plants have plenty of "requests" floating around — emails, sticky notes, hallway conversations, slack messages — and very few real work orders. Requests do not generate data. Work orders do. Improvement requires data.

The Four Types of Work Orders

Most CMMS deployments lump all work into a single bucket and pay for it in unreadable reports later. Categorize early.

• 1. Reactive (or "breakdown") work orders. Triggered by an unplanned failure. Goal is restoration. These should be a minority of total work orders in a mature plant — typically 20% or less.
• 2. Preventive maintenance (PM) work orders. Scheduled, recurring work designed to prevent failures. Should be the bulk of your work order volume — 50-70% in mature plants.
• 3. Predictive / condition-based work orders. Triggered by a sensor or inspection finding (vibration spike, oil analysis, thermography). The most efficient type — work happens just before failure, not after.
• 4. Project / improvement work orders. Larger scoped work — equipment overhauls, modifications, capital projects. Often have multiple sub-tasks and approvals.

The Standard Work Order Lifecycle

Every work order, regardless of type, moves through the same six states. Mapping your CMMS workflow against this lifecycle is the fastest way to find what is broken.

• Requested. Someone identifies the need and submits the request. Could be a technician, operator, sensor, or a recurring PM trigger.
• Approved / triaged. A planner or supervisor validates the request, sets priority, and sometimes routes for budget approval.
• Scheduled. The work is placed on the schedule against a specific shift, technician, and asset window.
• In progress. The technician picks up the work. Time tracking starts here.
• Completed. The physical work is done. Often confused with "closed."
• Closed. All data captured: parts used, time spent, root cause, recommendations. This is the only state from which reports can pull useful data.

Request vs Work Order: The Difference That Matters

In high-functioning plants, requests and work orders are different objects. A request is an unfiltered "I noticed something." A work order is the validated, scoped, approved version. The triage step in between is where good maintenance organizations get good and bad ones drown.

Plants that treat every request as an automatic work order accumulate hundreds of low-value, vague items in their backlog. Plants that triage convert maybe 60-70% of requests into work orders, reject the duplicates, escalate the safety issues, and route the trivial ones to operators. The triage step itself is a performance lever.

What Data a Closed Work Order Captures

A properly closed work order is a small but rich data record. The minimum fields you should expect every closed work order to contain:

• Asset and asset hierarchy. Which machine, which line, which plant.
• Failure mode (for reactive) or task type (for PM). A short picklist, kept consistent across the plant.
• Time to respond and time to repair. Together these become MTTR and MTBF.
• Parts used by part number and quantity. Drives MRO inventory analytics.
• Root cause and recommendation. Powers reliability engineering. Without this field your CMMS is a glorified ticket queue.

KPIs the Work Order Drives

A plant that captures clean work order data can compute meaningful reliability metrics. Without the work order discipline, these are guesses.

MTBF (Mean Time Between Failures) comes from time-stamped reactive work orders on each asset. MTTR (Mean Time To Repair) comes from in-progress to completed timestamps. PM compliance comes from completed-on-time vs scheduled. Wrench time, Schedule attainment, and Backlog week-supply all derive from work order timing data.

If your reliability KPIs feel like fiction, the problem is almost always upstream in the work order data. Fix the work order discipline first; the metrics will follow.

Common Mistakes That Break the Work Order System

Three patterns kill work order systems faster than anything else:

• Verbal work orders. A supervisor tells a technician to "go take a look at the press." If it is not in the system, it did not happen, and the labor hours just disappeared.
• Bulk close-outs. A technician closes 12 PMs at once on Friday afternoon. None of them have actuals. The data is fiction.
• Over-engineered approval flow. A 5-step approval chain for a $50 part means the technician will buy it on petty cash and skip the work order entirely.

Frequently Asked Questions