Work orders — the complete maintenance operations guide
A work order is the fundamental unit of accountability in maintenance management — a structured document that authorizes a maintenance task, assigns it to a technician, enforces a response deadline, records all costs, and creates a permanent maintenance history entry when closed.
Used by healthcare, manufacturing, facilities, and education teams · No credit card required
What is a work order?
A work order is a formal authorization document used in maintenance management to initiate, track, and close a specific maintenance task. It replaces informal verbal requests, email chains, and messaging threads with a structured, auditable workflow that records what was done, who did it, when it was completed, and what it cost.
In a modern maintenance management system, a work order is not just a task description — it is an operational record that connects a maintenance event to an asset, a technician, a cost log, a photo record, an SLA deadline, and ultimately the asset's complete service history. Every work order that closes adds a permanent entry to the asset's maintenance record and increments its total cost of ownership.
Organizations that manage maintenance through work orders — rather than informal communication — gain operational capabilities that are structurally impossible with ad hoc methods: SLA enforcement, repeat-failure detection, technician accountability, cost visibility per asset, and evidence-based repair-versus-replace decisions.
Problems work orders solve
- No accountability for who fixed what — repairs done verbally leave no record
- Repair costs invisible to finance — labour and materials never reach accounting
- Preventive maintenance missed — PM schedules live in spreadsheets or managers' heads
- No evidence trail for audits — maintenance history must be reconstructed from emails
- Repeat failures undetected — same asset fails again without linking to prior repair
- SLA breaches unmonitored — no mechanism to escalate overdue maintenance
- Technician workload invisible — managers cannot see who is over- or under-capacity
Glossary
- CM
- Corrective Maintenance — reactive repair work in response to a failure or reported fault.
- PM
- Preventive Maintenance — scheduled service to prevent failure, triggered by time or usage interval.
- SLA
- Service Level Agreement — the response deadline for a work order, calculated from its priority level.
- MTTR
- Mean Time to Repair — average time from work order creation to closure.
- MTBF
- Mean Time Between Failures — average operating time between corrective maintenance events on an asset.
- TCO
- Total Cost of Ownership — acquisition cost plus all accumulated maintenance costs. Updated on every work order close.
- CMMS
- Computerized Maintenance Management System — software that manages work orders, PM scheduling, and maintenance history.
Three types of work orders — and when to use each
Each work order type serves a distinct operational purpose. Choosing the correct type determines how the work order is generated, tracked, and what it creates in the asset's service history.
Corrective Maintenance
CMReactive — fault reported or failure detected
Created when equipment breaks, degrades, or a fault is reported by an operator. The CM work order documents the fault state, the corrective action taken, parts consumed, time spent, and total cost. CM work orders are the primary mechanism for tracking reactive maintenance — the unplanned repairs that define an organization's maintenance backlog.
Common examples
- Pump motor failure on production line
- HVAC unit not cooling — fault reported by tenant
- Laptop screen cracked — user request
- Ventilator alarm on ICU ward
On close → Maintenance record + TCO update on close
Preventive Maintenance
PMProactive — service interval triggered by time or usage
Generated automatically when a PM rule interval becomes due — no manual trigger required. The PM work order is linked back to the PM rule and the asset, carrying forward the service description and checklist from the rule configuration. On closure, the PM interval is reset automatically. PM work orders are the mechanism that transforms reactive maintenance teams into proactive ones.
Common examples
- CNC spindle bearing inspection — 500-hour interval
- HVAC quarterly filter service
- Ventilator 3-month calibration check
- Generator monthly load test
On close → Maintenance record + TCO update + PM interval reset on close
Inspection
INSCompliance-driven — safety audit or regulatory check
Created for formal assessments where no corrective action is expected — the purpose is to create a dated, attributed record that a specific inspection occurred and what was found. Inspection work orders support compliance reporting, insurance requirements, and operational due diligence. The inspecting technician logs findings, condition ratings, and any compliance documents.
Common examples
- Fire extinguisher annual safety inspection
- Elevator bi-monthly regulatory check
- Electrical switchboard thermal imaging audit
- Food equipment hygiene compliance inspection
On close → Inspection record + compliance evidence on close
Four priority levels with automatic SLA deadlines
Every work order carries a priority that determines its SLA response window. Deadlines are calculated automatically at creation — no manual entry required. Asset criticality classification can tighten these windows further.
4 hours
Critical failure — safety risk, total operational stoppage, or life-safety system failure. Maximum escalation urgency.
24 hours
Significant operational impact — major system degradation, production slowdown, or key asset compromise.
72 hours
Non-critical repair — operations continue with a workaround. Asset degraded but not failed. Planned resolution.
Scheduled date
Known future maintenance — service date set at creation. Used for scheduled PM and pre-planned upgrades.
The eight-status work order lifecycle
Every work order in UniAsset moves through a defined set of statuses from creation to closure. Each transition is logged with a timestamp and the user who made the change — creating a complete, immutable accountability trail for every maintenance task.
Lifecycle State Flow
Work order created. Fault or service described, asset linked, priority set, SLA deadline calculated. Awaiting assignment to a technician.
Actor: Manager / System
Technician designated and notified. Work not yet started. Technician has all information needed to begin — asset, fault, priority, SLA deadline.
Actor: Manager
Technician actively working on the task. Time logging begins. Photos and notes are added as work proceeds. SLA clock continues running.
Actor: Technician
Work is paused — blocked by a parts order, restricted site access, or a waiting specialist. Hold reason is recorded. SLA deadline does not pause.
Actor: Technician
Technician has completed work and submitted for manager review. All costs, photos, and notes are finalized. Awaiting manager sign-off.
Actor: Technician
Manager has reviewed and approved. Work quality verified. Costs are locked. The work order is awaiting final administrative closure.
Actor: Manager
Terminal state. Maintenance record auto-created on the asset. Work order cost added to asset TCO. PM interval reset if applicable. History preserved permanently.
Actor: Manager / System
Terminal state. Original work order preserved unchanged. A new linked child work order was created because the issue recurred. Signals a repeat-failure event.
Actor: Manager
Terminal states: Closed and Reopened are both terminal — no further status transitions are possible once a work order reaches either state. Closed represents a successfully resolved and approved task. Reopened represents a task where the original resolution proved insufficient — the original record is preserved and a new child work order carries the investigation forward.
How work orders operate across industries
The same work order system serves very different operational environments. Here is how maintenance teams in four industries use UniAsset work orders every day.
Operational outcomes
- SLA met — Emergency response completed in 58 minutes end-to-end
- Full compliance evidence: fault description, technician identity, repair photos, cost
- Maintenance record feeds device lifecycle history for HTMS audit compliance
Operational outcomes
- Zero PM missed — automation eliminated manual scheduling dependency
- Service evidence logged: technician, checklist findings, photos, cost
- PM interval reset automatically — no manual schedule management
Operational outcomes
- Transparent hold management — tenant and manager informed of delay reason in real time
- Complete parts and labour cost captured against the specific HVAC asset
- Cumulative cost visible: $2,300 in 18 months — triggers replacement evaluation
Operational outcomes
- 240 compliant inspection records generated — automatically scheduled, systematically executed
- Linked CM work orders created for the 3 extinguishers requiring remediation
- Instant audit response — full inspection evidence available to fire marshal on demand
Key components of a work order management system
A work order is not a flat document — it is a structured data entity with interconnected components. Understanding these components explains the operational intelligence a work order system produces.
Work Order Record
The core entity. Each work order has a unique ID, type (CM/PM/INS), linked asset, title, description, creation date, creator, priority, SLA deadline, current status, assigned technician, and links to all sub-entities (cost log, photos, notes, maintenance record). The work order record is the hub that connects all the components below.
Links to: Asset, Technician, Cost Log, Photos, Notes, Maintenance Record
Priority & SLA Engine
The priority selected at creation (Emergency / Urgent / Routine / Planned) determines the SLA response window. The SLA engine calculates the absolute deadline timestamp at work order creation and monitors elapsed time continuously. Asset criticality classification can modify SLA windows — a Routine work order on a Critical asset may receive a tighter deadline than standard. SLA breach triggers the escalation engine.
Feeds: Escalation Engine, SLA Compliance reporting
Status Lifecycle Engine
Enforces valid status transitions — not all transitions are permitted from every state. For example, a work order cannot move from Assigned directly to Completed; it must pass through In Progress and Awaiting Approval. Each transition is logged to the audit event log with actor and timestamp. Terminal states (Closed, Reopened) cannot be exited. The lifecycle engine is the mechanism that makes the work order an accountability trail rather than a simple task list.
Logs to: Audit Event Log
Assignment & Notification System
When a manager assigns a work order to a technician, the notification system fires immediately — sending an in-app notification to the technician with the asset, fault description, priority, and SLA deadline. Managers receive notifications when work orders are submitted for approval. The Engineering Head or Owner receives notifications when PM work orders are auto-generated. The notification system ensures the right person knows about the right event at the right time.
Fires on: Assignment, submission, auto-generation, SLA approach
Cost Log
Each work order has a structured cost log with three categories: Labour (time spent × rate, entered by the technician), Materials (each part or consumable listed individually with name and cost, totalled automatically), and Additional Charges (vendor fees, specialist costs, travel). The cost log is locked when the work order reaches Completed status. On Close, the total cost is transferred to the asset's maintenance record and added to its TCO — creating the direct financial link between a maintenance event and the asset's lifetime cost.
Transfers to: Asset Maintenance Record, TCO on Close
Photo Documentation
Work orders support photo capture at three defined stages: Before (fault state — documents what the technician found on arrival), During (work-in-progress evidence for complex repairs), and After (completed repair state — confirms resolution). Photos are stored against the work order and remain accessible in the asset's maintenance history timeline after closure. Photo documentation is increasingly a requirement for insurance claims, warranty disputes, and regulatory inspections.
Stored on: Work Order, visible in Asset History
Notes (Public & Internal)
Two note types with distinct visibility. Public notes are visible to all parties with access to the work order — used for repair descriptions, findings, and technician updates. Internal notes are manager-only — used for vendor quotations, escalation decisions, budget approvals, and sensitive operational context that should not be visible to field technicians. The distinction enables a single work order to serve both field operations and management oversight without information leakage.
Public: visible to all assigned users. Internal: manager only.
Reopen & Child Work Order
When a resolved issue recurs, reopening the closed work order creates a linked child work order. The original work order transitions to REOPENED (a terminal state) and its record is preserved unchanged. The child work order inherits the asset context but opens a fresh cost log, photo record, and accountability chain. The parent-child linkage is permanent — enabling repeat-failure analysis by showing which assets have recurrence patterns. Multiple reopens create a chain of linked work orders tracing the full repair history of a persistent fault.
Creates: Child Work Order linked to original
PM Rule Integration
PM work orders are generated from PM rules configured on assets. When a work order is auto-generated by a PM rule, the link is preserved — the work order record references the PM rule ID, and the PM rule record records the work order ID. On PM work order closure, the PM rule's last-serviced date is updated and the next due date recalculates. This bidirectional link is what enables the PM system to track schedule adherence and identify assets whose PM is consistently delayed.
On Close: PM rule interval resets, next due date recalculates
Audit Event Log
Every status transition, assignment change, cost entry, photo upload, and note addition on a work order is written to the immutable audit event log — with actor identity, timestamp, and before/after values. The audit log cannot be deleted or modified. It is the system's legal and operational memory for the work order. In regulated industries, the audit log for a work order on safety-critical equipment constitutes part of the compliance evidence package for that asset.
Captures: every action on the work order — immutable
How work orders connect operational systems
A work order is not an isolated task — it is the operational hub that connects assets, people, costs, compliance, and maintenance intelligence across the entire operational system. Understanding these connections is essential for building coherent, data-driven maintenance operations.
Work Order — Operational System Map
How a single work order entity connects to every adjacent operational system
Primary system connections
Every work order is linked to a specific asset. The asset provides context — location, criticality classification, maintenance history, TCO — that shapes SLA windows and escalation behaviour. On work order close, a maintenance record is permanently written to the asset.
Work Order is linked to and writes maintenance history to Assets
At creation, the work order's priority level triggers the SLA engine to calculate a response deadline. Asset criticality can modify this deadline. The SLA engine then monitors elapsed time continuously, firing escalation notifications when thresholds are breached.
Work Order triggers SLA deadline calculation in SLA Engine
PM work orders are auto-generated from PM rules. On PM work order closure, the rule's service interval resets automatically. The bidirectional link enables schedule adherence tracking — showing which PM rules are consistently delayed.
Work Order is generated by and resets PM Rules
Work order assignment designates the responsible technician. The notification system fires immediately on assignment. The technician's actions — status transitions, time logging, photo uploads — are the primary data inputs that make the work order record meaningful.
Work Order is assigned to and logged by Technicians
Each work order contains a structured cost log: labour hours, material costs (line-by-line), and additional charges. The cost log is locked on completion. On close, the total cost transfers to the asset's accumulated TCO — making the work order the financial link between maintenance events and asset economics.
Work Order accumulates costs in and transfers total to TCO via Cost Log
When a work order approaches or breaches its SLA deadline, the escalation engine fires tiered notifications — technician, manager, executive. The escalation path and intervals are configured per asset criticality tier.
Work Order triggers tiered escalation in Escalation System
Secondary system connections
Work order automation and system intelligence
Modern work order management eliminates the manual coordination tasks that consume maintenance management capacity. These are the automation behaviours that distinguish a CMMS from a spreadsheet.
Automatic PM work order generation
When a PM rule interval passes its due date, the system generates a work order automatically. No human trigger required. The work order is linked to the PM rule, the asset is identified, the technician is pre-assigned from the rule configuration, and a notification is sent to the Engineering Head. PM scheduling ceases to be a management task.
Auto-calculated SLA deadlines
SLA deadlines are calculated the moment a work order is created — based on priority level, creation timestamp, and asset criticality classification. No manual deadline entry. The deadline is displayed on every work order view and in every notification sent to the assigned technician.
Tiered escalation on SLA breach
As a work order approaches its SLA deadline, escalation notifications fire in sequence: first reminder to the technician, then breach notification to the department manager, then continued breach to executive leadership. Escalation intervals and recipients are configured in the escalation matrix. Critical assets can trigger faster escalation paths.
Instant technician notification on assignment
The moment a manager assigns a work order, the technician receives an in-app notification with the full context: asset name and location, fault description, priority, and SLA deadline. No phone calls, no WhatsApp messages — the system delivers the task brief immediately.
Automatic maintenance record creation
When a work order is closed, the system automatically creates an AssetMaintenance record on the linked asset. The record captures work type, description, completion date, technician, and cost. The asset's service history grows with every work order closure — no manual data entry required to build the maintenance record.
TCO auto-accumulation on close
Every work order closure transfers its total cost to the asset's accumulated maintenance total. The asset's Total Cost of Ownership is always current — no manual reconciliation needed. Finance teams and operations managers see real-time asset economics.
PM interval auto-reset
When a PM work order closes, the PM rule's last-serviced timestamp updates automatically and the next due date recalculates based on the configured interval. The maintenance cycle continues without any manual schedule management. The next PM work order will generate exactly on schedule.
Cost risk signal
When an asset's accumulated maintenance costs approach a configurable threshold relative to its acquisition cost, the system surfaces a cost risk signal on the asset record. This triggers a repair-versus-replace evaluation — making the case for capital replacement before further maintenance investment is committed.
Immutable audit logging
Every action on every work order — status changes, assignments, cost entries, photo uploads, note additions — is written to the audit event log automatically. No configuration required. The audit trail is always complete, always current, and cannot be deleted or modified.
What automation changes operationally: In a manual system, a PM missed because a manager forgot to create a work order is a silent failure — it leaves no record. In an automated system, the PM work order generates whether or not anyone remembers it. The absence of action becomes visible, traceable, and correctable.
Work order management best practices
The operational discipline around work orders determines the quality of maintenance data, the reliability of cost tracking, and the strength of the compliance audit trail. These practices separate high-maturity teams from those still managing through informal channels.
Work order creation
Always create a work order before starting repair work
Repairs done before a work order is raised leave no record of the fault state, the investigation process, or who authorized the work. Even for minor repairs that take 15 minutes, the work order creates accountability, a cost record, and a maintenance history entry. There is no maintenance too small to warrant a work order.
Use the correct work order type every time
Corrective, Preventive, and Inspection work orders create different records and trigger different downstream automations. Using a CM work order for a scheduled PM service misclassifies the maintenance event — making PM compliance metrics inaccurate and PM interval reset behaviour unreliable.
Write fault descriptions at the level of a future reader
The fault description is permanent — it will be read by the next technician who works on this asset, the manager approving the work, and the auditor reviewing maintenance records two years from now. 'Not working' is not a fault description. 'Compressor unit producing grinding noise on startup — suspected bearing wear in motor housing' is.
During execution
Log all materials consumed, not just labour time
Operations teams that log only labour time consistently underestimate maintenance costs by 30–50%. Parts, consumables, and vendor-supplied materials are often the largest cost component of a corrective repair. Every item consumed on a work order should be listed individually with its cost — this is what makes TCO accurate.
Capture before and after photos on every corrective work order
Before photos are especially critical — they document the fault state that justified the work order. Without them, there is no evidence of what was wrong before the repair. After photos close the evidence loop, confirming the repair was completed. For regulated assets, this documentation is not optional.
Record the hold reason immediately when going On Hold
On Hold without a recorded reason is operationally useless — managers cannot see why work stopped, cannot take corrective action, and cannot communicate the delay to stakeholders. Every On Hold status transition should carry a specific reason: what is being waited for, who is responsible for unblocking, and estimated resolution timeline.
Approval and closure
Managers should physically verify before approving, not rubber-stamp
The Awaiting Approval stage exists for a reason: a second pair of eyes on work quality before the record is finalized. Managers who approve without reviewing work quality undermine the accountability value of the work order system. At minimum, review the photos and notes before approval.
Do not leave work orders open after work is complete
An open work order on a completed repair does not record the maintenance event against the asset, does not update TCO, and does not reset the PM interval. Work orders should be submitted and closed within 24 hours of repair completion. Backlog of un-closed work orders is a data quality problem.
Use reopen — do not create a new work order for a recurrence
When an asset fails again after a recent repair, reopening the closed work order (rather than creating an unlinked new one) preserves the parent-child relationship. This linkage is what enables repeat-failure detection — showing that the same asset has had the same issue multiple times and that the repairs are not holding.
Governance and review
Review the PM-to-CM ratio monthly
The ratio of preventive work orders to corrective work orders is the most reliable indicator of maintenance programme maturity. A ratio above 3 CM per 1 PM indicates a predominantly reactive team. Target is at least 1:1 (equal PM and CM). Moving the ratio toward 2 PM per 1 CM represents a high-maturity preventive programme.
Treat repeat-failure assets as capital planning signals
An asset with three or more linked reopened work orders within a 12-month period is a candidate for formal replacement evaluation. Reopen chains in UniAsset make these assets immediately visible. Do not continue authorizing repair spend on assets that are demonstrably failing to hold repairs.
Audit work order data quality quarterly
Common data quality failures: work orders with no cost entries (incomplete), work orders closed without photos on corrective repairs (non-compliant), work orders with no fault description (uninformative). Regular data quality audits prevent these patterns from becoming embedded practice.
Work order metrics and KPIs
Work order data is the richest source of maintenance performance information in an operations system. These KPIs translate raw work order activity into operational intelligence for maintenance managers and operations directors.
Mean Time to Repair (MTTR)
HoursAverage time from work order creation to work order closure. Measures the combined speed of response, diagnosis, repair, and approval. MTTR varies significantly by priority — Emergency work orders have a target MTTR of under 4 hours; Routine work orders under 72 hours. High MTTR on Emergency work orders indicates response capacity gaps.
Emergency < 4h · Routine < 72h
SLA Compliance Rate
PercentagePercentage of work orders closed within their SLA deadline. Target is 95% or above. SLA compliance below 85% indicates either under-staffed maintenance teams, misconfigured SLA windows (too tight for available capacity), or a systemic process failure in work order progression.
Target: ≥ 95%
First-Time Fix Rate (FTFR)
PercentagePercentage of work orders closed without subsequent reopening for the same fault within 30 days. Measures repair quality and diagnostic accuracy. Low FTFR indicates insufficient root cause analysis, parts quality issues, or technician skill gaps. Target: above 90%.
Target: ≥ 90%
PM-to-CM Ratio
RatioNumber of preventive maintenance work orders vs corrective work orders over a period. A higher PM ratio indicates a proactive maintenance culture. Ratios below 1:3 (one PM for every three CM) represent reactive-dominant operations. World-class maintenance programmes operate at 2:1 or higher.
Proactive target: ≥ 1:1
PM Compliance Rate
PercentagePercentage of auto-generated PM work orders completed within the scheduled window. PM work orders completed late extend the asset's actual service interval beyond design specification, increasing failure risk. Target: above 95% — missed PM is the leading preventable cause of premature asset failure.
Target: ≥ 95%
Work Order Backlog
Count / AgeTotal open work orders by priority and age. An accumulating backlog of Emergency and Urgent work orders is a critical operations signal — it means maintenance demand is exceeding team capacity. Backlog should be reviewed weekly by the Engineering Head to identify resource gaps before SLA breaches compound.
Emergency/Urgent backlog: should approach zero
Average Work Order Cost
CurrencyMean total cost per work order, segmented by type (CM vs PM), asset category, and facility. Enables benchmark comparisons across asset fleets and facilities. Corrective work orders that consistently cost significantly more than PM work orders on the same asset class quantify the financial case for better PM compliance.
Benchmark: CM cost ÷ PM cost ratio
Technician Utilization Rate
PercentagePercentage of technician capacity consumed by active work orders in a period. Low utilization identifies over-staffed teams or seasonality patterns. Very high utilization (above 85%) predicts SLA breach risk. Utilization data informs shift scheduling, contractor engagement decisions, and headcount planning.
Sustainable target: 70–80%
Repeat Failure Rate
PercentagePercentage of closed work orders that are subsequently reopened within 90 days for the same fault. Identifies assets with persistent failure patterns and repair approaches that are not holding. Assets with repeat failure rates above 20% should be formally reviewed for root cause analysis and replacement evaluation.
Target: < 10%
Maintenance maturity assessment — where does your team sit?
Reactive (Level 1)
PM:CM ratio < 1:4 · MTTR not measured · SLA compliance unknown · Work orders in email/WhatsApp
Managed (Level 2)
PM:CM ratio ~1:2 · MTTR tracked · SLA compliance 75–85% · Work orders in a CMMS
Optimized (Level 3)
PM:CM ratio ≥ 1:1 · MTTR on target · SLA compliance > 95% · FTFR > 90% · Data-driven operations
What happens when work orders fail?
Work order failures are rarely dramatic single events — they are patterns of operational breakdown that compound over time. Understanding these failure modes is the first step to designing systems that prevent them.
Missed SLA deadlines — accountability collapse
The failure pattern
A work order is created but no one monitors elapsed time. The SLA deadline passes without notification. The manager discovers the breach only when the requesting department complains — days later. By then, the delay has created secondary problems: a tenant without heating, a production line still stopped, a patient device still offline.
Consequence
Without SLA enforcement, maintenance commitments become suggestions, not obligations.
UniAsset approach
Automatic SLA deadline calculation at creation, with tiered escalation notifications before and after breach — from technician to manager to executive.
Maintenance backlog — demand exceeds capacity silently
The failure pattern
Work orders accumulate faster than they are closed. There is no visibility into the backlog — managers don't know how many open work orders exist, what priority they are, or how long they have been waiting. High-priority repairs sit in the same list as routine maintenance with no differentiation.
Consequence
Invisible backlog leads to emergency escalations, missed compliance deadlines, and reactive firefighting that prevents proactive maintenance.
UniAsset approach
Priority-separated backlog view showing open work orders by status, priority, and age — giving managers the capacity signal they need before SLA breaches compound.
Repair costs invisible — asset economics unknown
The failure pattern
Work is completed but costs are not logged. The labour time is done informally, parts are purchased on a general cost code, and the maintenance event leaves no financial trace. When the asset director reviews the budget, there is no data showing which assets are consuming disproportionate maintenance spend.
Consequence
Capital replacement decisions are made without evidence. Assets are maintained past their economic replacement point because the accumulated cost data does not exist.
UniAsset approach
Structured cost log on every work order — labour hours, materials line-by-line, additional charges — transferred automatically to asset TCO on close.
Repeat failures undetected — same asset, same fault
The failure pattern
An asset is repaired and the work order is closed. Two months later, the same fault recurs. A new work order is created — with no link to the previous repair. The pattern of recurring failure is invisible. The team continues authorising repair spend on an asset that is clearly failing to hold repairs.
Consequence
Without linked reopen chains, repeat-failure assets continue consuming maintenance budget until a major catastrophic failure forces an unplanned replacement.
UniAsset approach
Reopen workflow creates a permanent parent-child link between the original work order and the recurrence. Repeat-failure patterns are surfaced automatically.
Compliance audit failure — evidence cannot be produced
The failure pattern
A regulatory inspector arrives and requests evidence of the last six months of maintenance on a critical asset. The maintenance manager searches through email threads, spreadsheet rows, and paper sign-off sheets. Some records are found, some are missing, and photos are in someone's personal WhatsApp. The audit fails.
Consequence
In regulated industries, an inability to produce compliance evidence is not a minor administrative failure — it can result in enforcement action, operational shutdown, and insurance invalidation.
UniAsset approach
Every work order creates an immutable maintenance record with technician identity, photos, costs, timestamps, and audit log. Complete compliance evidence is available on-demand, instantly.
PM schedule drift — proactive programme collapses
The failure pattern
Preventive maintenance is scheduled in a spreadsheet. A manager leaves the organisation and the spreadsheet is not maintained. PM intervals are missed silently — assets accumulate deferred maintenance without anyone realising. The first indication of the problem is an increase in corrective work orders as assets begin failing ahead of schedule.
Consequence
A reactive maintenance culture is often not a choice — it is the result of PM schedule management that depends on individuals rather than systems.
UniAsset approach
PM work orders are generated automatically when intervals are due — no human trigger, no spreadsheet dependency. PM compliance is tracked and surfaced as a KPI.
Work order systems compared — informal methods vs modern CMMS
The difference between informal maintenance management and a proper work order system is not cosmetic — it is structural. Here is what changes across every capability dimension.
| Capability | Email / WhatsApp | Spreadsheet tracker | UniAsset CMMS |
|---|---|---|---|
| Task creation | Unstructured message — no standard fields | Manual row — custom columns, no validation | Structured form — type, asset, priority, SLA auto-calculated |
| Assignment & notification | Manual message — recipient may miss it | Name in a cell — no notification sent | In-app notification fired instantly on assignment |
| SLA enforcement | None — no deadline tracking | Manual column — not monitored or enforced | Auto-calculated deadline + tiered escalation on breach |
| Cost tracking | Not tracked — verbal estimates only | Manual entry — often incomplete or late | Structured labour + materials log, locked on completion |
| Photo documentation | Photos in separate threads — not linked to task | No attachment support for most tools | Before / during / after photos on each work order |
| PM scheduling | Calendar reminders — dependent on individual | Date column — manually checked, easily missed | Automatic work order generation when interval due |
| Maintenance history | No history — each repair is isolated | Rows — not linked to specific assets | Auto-created on work order close — linked to asset permanently |
| Audit trail | Email thread — deletable, searchable with difficulty | No change history — no accountability trail | Immutable event log — every action attributed, timestamped |
| Repeat failure detection | Manual memory — dependent on team continuity | Possible with filtering — no automatic flagging | Reopen chains + cost risk signal — automatically surfaced |
| Compliance evidence | Manual reconstruction — weeks of searching | Possible but incomplete — photos and docs scattered | Instant export — complete evidence package per asset |
The hidden cost of informal maintenance management is not the WhatsApp message or the spreadsheet row — it is the operational decisions made without the data those tools cannot capture. Repeat failures undetected because there is no repair history. Capital replacements unjustified because there is no cost data. Compliance audits failed because maintenance evidence was never systematically recorded. These are the real costs that a work order management system eliminates.
Evaluation guide
Looking for a detailed comparison of legacy CMMS systems vs modern platforms?
See how UniAsset compares to legacy CMMS on deployment time, pricing, UX, and operational depth.
Frequently asked questions
Detailed answers to the questions operations managers, maintenance engineers, and facilities teams ask most frequently about work order management.
What is a work order in maintenance management?
A work order is a structured operational document that authorizes, tracks, and records a specific maintenance task from creation through completion. It captures what needs to be done, which asset is affected, who is responsible, when it must be completed (SLA deadline), what was done, how long it took, what it cost, and what the outcome was. Work orders are the primary unit of accountability in maintenance operations — replacing informal verbal requests, email threads, and WhatsApp messages with a traceable, costed, auditable workflow.
What are the main types of work orders?
There are three primary work order types in maintenance management. Corrective Maintenance (CM) work orders are created reactively in response to a failure, fault, or reported issue — something broke and needs to be fixed. Preventive Maintenance (PM) work orders are generated proactively when a scheduled service interval becomes due — based on time elapsed or usage accumulated. Inspection work orders are created for compliance checks, safety audits, and condition assessments where no corrective action is expected, but a formal record of the inspection is required. Each type follows the same status lifecycle but serves a distinct operational purpose.
What is the work order lifecycle?
The work order lifecycle is the defined sequence of statuses a work order moves through from creation to closure. The standard eight-status lifecycle is: (1) Open — created, awaiting assignment; (2) Assigned — technician designated, not yet started; (3) In Progress — technician actively working; (4) On Hold — blocked, awaiting parts or access; (5) Awaiting Approval — work completed, submitted for manager review; (6) Completed — manager approved, work verified; (7) Closed — maintenance record auto-created, costs finalized; (8) Reopened — issue recurred, linked child work order created. Every status transition is logged with a timestamp and the user who made the change, creating a complete accountability trail.
How does SLA enforcement work for work orders?
SLA enforcement begins the moment a work order is created. The work order's priority level — Emergency (4 hours), Urgent (24 hours), Routine (72 hours), or Planned (scheduled date) — determines the response deadline. This deadline is calculated automatically at creation; no manual entry is required. As the deadline approaches, the system monitors elapsed time. If the work order is not progressed, escalation notifications are sent — first to the assigned technician, then to the department head, then to executive leadership — according to the configured escalation matrix. Asset criticality can modify SLA windows: work orders on Critical assets receive tighter deadlines regardless of priority level.
How are work orders created automatically for preventive maintenance?
Automatic PM work order generation is driven by PM rules configured on each asset. A PM rule defines a service type, interval (e.g., every 90 days or every 500 operating hours), lead time for notification, assigned technician, and checklist. When the system determines that an interval has become due — through a scheduled daily check — it automatically generates a PM work order linked to the asset and the PM rule, and sends an in-app notification to the Engineering Head or Owner. No manual trigger is required. The PM work order then follows the standard lifecycle: assigned to the technician, worked through the checklist, and closed to create a maintenance record and reset the interval.
How does a work order track maintenance costs?
Work order cost tracking operates at three levels. First, labour cost: the assigned technician logs actual time spent and a labour cost figure directly on the work order. Second, materials cost: each material or part consumed is listed individually with a name and cost — the system sums these automatically. Third, additional charges: external vendor fees, travel costs, or specialist charges can be added as line items. When the work order closes, the total cost — labour plus materials plus additional charges — is transferred to a maintenance record on the linked asset and added to that asset's accumulated Total Cost of Ownership. This creates a direct financial connection between every maintenance event and the asset's lifetime cost picture.
What is the difference between a corrective and preventive maintenance work order?
A Corrective Maintenance (CM) work order is reactive — it is created because something has failed or a fault has been reported. The work order documents what went wrong, what was done to fix it, and what it cost. A Preventive Maintenance (PM) work order is proactive — it is created because a scheduled service interval has come due, before any failure occurs. PM work orders are linked to a PM rule that specifies the service interval and checklist. The key operational difference is intent: CM work orders respond to failures, PM work orders prevent them. Both types follow the same eight-status lifecycle and generate the same maintenance cost records on closure.
What is a reopened work order and when should it be used?
A reopened work order is triggered when an asset that was repaired on a previous work order experiences the same issue again within a short period — indicating the original repair was incomplete, insufficient, or that a deeper underlying problem exists. When a closed work order is reopened, the system creates a new child work order linked to the original. The original work order transitions to a REOPENED terminal status and is preserved unchanged. The child work order carries forward the asset and fault context but opens a fresh cost log and accountability chain. This architecture maintains the full repair history while enabling analysis of repeat failures — the most reliable indicator that an asset may be approaching economic retirement.
What photo documentation should be captured on a work order?
Best practice is to capture photographs at three defined stages of every corrective work order. Before photos document the fault state — the exact condition of the asset when the technician arrived. During photos show significant steps in the repair process, particularly for complex mechanical or electrical work. After photos confirm the completed repair state — showing that the fault has been addressed and the asset is returned to correct operational condition. This three-stage documentation creates unambiguous evidence for warranty claims, insurance disputes, regulatory inspections, and any future analysis of asset condition progression.
How do work orders connect to asset maintenance history?
When a work order closes, UniAsset automatically creates an AssetMaintenance record on the linked asset. This record captures the work order type, description, completion date, technician, and total cost. The maintenance record becomes a permanent, immutable entry in the asset's service history — visible chronologically on the asset detail page. Over time, this history shows every repair, service, and inspection the asset has experienced, with costs and technicians attached. This history is the foundation for MTBF analysis, PM interval optimization, repair-versus-replace decisions, and compliance audit evidence.
What work order KPIs should maintenance managers track?
The most operationally important work order KPIs are: Mean Time to Repair (MTTR) — average hours from work order creation to closure, measuring response efficiency; SLA Compliance Rate — percentage of work orders closed within their SLA deadline; First-Time Fix Rate — percentage of work orders closed without being reopened, indicating repair quality; PM-to-CM Ratio — ratio of preventive to corrective work orders, indicating maintenance programme maturity (higher PM ratio = more proactive operations); Work Order Backlog — total open work orders by priority and age, indicating team capacity vs demand; Average Work Order Cost — mean total cost per work order by type and asset category, for budget planning; and Technician Utilization Rate — percentage of technician capacity consumed by active work orders.
What is work order escalation and how does it work?
Work order escalation is the automatic notification process that activates when a work order approaches or breaches its SLA deadline without resolution. In UniAsset, escalation operates in tiers: the first notification goes to the assigned technician as a reminder. If the deadline is breached, the second-tier notification goes to the department manager or Engineering Head. If the work order remains unresolved, the third tier notifies executive leadership or the Operations Director. Escalation intervals and recipients are configured in the SLA escalation matrix. Asset criticality modifies escalation behaviour — work orders on Critical-classified assets may trigger escalation sooner or skip directly to manager notification.
Can work orders be used for compliance inspections and safety checks?
Yes. The Inspection work order type is specifically designed for compliance checks, safety audits, and regulatory assessments. Unlike CM and PM work orders, an Inspection work order does not imply corrective action — it creates a formal record that a specific inspection was performed, by whom, when, and what was found. Inspection work orders can include checklists, condition assessments, and document attachments (inspection certificates, test reports). On closure, the inspection record is added to the asset's maintenance history alongside CM and PM events. Inspections are the primary mechanism for demonstrating ongoing compliance to regulators, insurers, and auditors.
Popular Searches on Work Orders
Common operational questions answered in this guide.
Continue Your Learning Path
Work Orders is the foundation. Build the complete Maintenance Operations knowledge set.
Maintenance Operations
From reactive firefighting to systematic preventive operations — the complete knowledge sequence.
A canonical reference for work order management — covering creation, prioritisation, technician assignment, escalation workflows, SLA compliance, and closure audits in modern maintenance operations.
The definitive guide to preventive maintenance programmes — schedule types, trigger logic, checklist design, frequency optimisation, KPI tracking, and transitioning from reactive to proactive maintenance models.
A comprehensive reference for maintenance SLA design, response-time tiers, escalation workflows, breach reporting, and compliance tracking — built for operations teams managing multi-site maintenance contracts.
Operational guide to corrective maintenance — failure classification, reactive work order workflows, root cause analysis, repair-vs-replace decision frameworks, and minimising unplanned downtime.
Operational guide to maintenance automation — trigger-based scheduling, condition monitoring integration, automated escalation, IoT-driven maintenance, and building a self-managing maintenance operation.
Get started
Start managing work orders in UniAsset — free.
Full work order lifecycle management — corrective, preventive, and inspection work orders with SLA enforcement, cost tracking, PM automation, and audit trail — in one system of record.
Used by healthcare, manufacturing, facilities, and education teams. No credit card required.