What this is
What is a corrective work order?
What is a corrective work order?
A record of unplanned work to restore an asset to working condition following a failure or fault. It captures what was found, what was done, what parts were used, how long it took, and the controls applied while the work was performed.
Why does the failure description matter so much?
Because the corrective history is the only systematic record of how assets actually fail. Analysis of recurring failures, of which components dominate downtime, and of whether a preventive regime is working all depend on the fault being described consistently. Free text saying broken supports none of it.
Scope
When is a corrective work order required?
This covers unplanned corrective work. Planned maintenance and improvement work have their own records.
Use this template when
- Unplanned work to restore function after a failure, fault or performance loss
- Faults found during inspection or operator checks requiring corrective action
- Temporary repairs, recorded as temporary with the permanent fix scheduled
- Work arising from an incident, near miss or audit finding against an asset
- Any intervention where the asset was not performing as intended
Do not use it for
- Preventive maintenance work orders, which are scheduled and have different analysis value
- Modification and improvement work, which changes the asset rather than restoring it
- The permit to work, which authorises the activity where required
- Root cause analysis, which belongs separately for significant or recurring failures
- Asset criticality assessment, which determines how the asset is maintained overall
Compliance mapping
Which ISO 55001 cl.8.2 requirements does this satisfy?
Corrective maintenance sits under asset management requirements and, in regulated production, under equipment and hygiene obligations.
| Clause | Requirement | Where it lands |
|---|---|---|
| ISO 55001 cl.8.1 | Operational planning and control of activities to achieve asset management objectives | Header |
| ISO 55001 cl.9.1 | Evaluation of asset performance and the effectiveness of asset management | Verification |
| ISO 9001 cl.7.1.3 | Infrastructure maintained to ensure conformity of products and services | Repair |
| 21 CFR 117.40 | Plant and equipment maintained in a condition preventing contamination of food | Safety and food controls |
| 29 CFR 1910.147 | Energy control applied during servicing and maintenance, including corrective work | Safety and food controls |
| BRCGS Issue 9 cl.4.7 | Maintenance with hygiene clearance and sign-off before equipment returns to production | Verification |
| NFPA 70B 2023 | Documented electrical maintenance programme, with corrective work forming part of the record | Repair |
| ISO 14224 | Collection and exchange of reliability and maintenance data, including failure and cause coding | Fault detail |
What it does not cover
- Preventive maintenance records, which are scheduled work with different analytical value.
- Modification and improvement work, which changes the asset and may trigger conformity questions.
- Permit to work, authorising the activity where the work is high risk.
- Root cause analysis, for significant or recurring failures.
- Hygiene clearance in food production, which is a specific release step before restart.
How to complete it
How to complete a corrective work order, step by step
Four fields carry the analytical value, and one of them is usually a single line of prose.
What was found: which component, what condition, what symptom. What was done: what was replaced, adjusted or repaired. These are different pieces of information and merging them makes both unusable. The fault supports reliability analysis; the action supports cost and spares planning.
Component, failure mode and, where known, cause. ISO 14224 provides a structure and any consistent internal list works. Without coding, the same bearing failure appears as bearing gone, noisy bearing, drive end failure and seized, and none of them aggregate into a number anyone can act on.
Isolation, permits, hygiene measures, temporary guarding removal and its reinstatement. In food production the hygiene clearance before restart is a specific release step, and in any setting the record of what was removed determines what must be restored before the asset runs again.
A repair intended to hold until the next shutdown should be flagged as temporary with the permanent work raised at the same moment. Temporary repairs recorded as complete become invisible, and they are found later either by the next failure or by an auditor asking why a hose clip is holding a guard on.
What auditors find
Most common corrective work order findings
Corrective work order findings mostly concern data quality, which is why they persist.
| Finding | Clause | What fixes it |
|---|---|---|
| Fault and action recorded in a single free text field. | ISO 14224 | Separate them; merged text supports neither reliability nor cost analysis. |
| No failure coding, so recurring failures never aggregate. | ISO 55001 cl.9.1 | Code component and failure mode against a controlled list. |
| Temporary repairs closed as complete. | ISO 55001 cl.8.1 | Flag as temporary and raise the permanent work at the same time. |
| Corrective failures on assets under preventive maintenance not fed back. | ISO 55001 cl.9.1 | A failure under PM means the PM is wrong, mistimed or not being performed. |
| Energy control not recorded for corrective work. | 1910.147 | Corrective work is servicing; the isolation applies and belongs on the record. |
| Hygiene clearance not evidenced before restart in food areas. | BRCGS 4.7 | Clearance is a release step, not a formality; record it explicitly. |
| Downtime recorded as a single figure with no split between waiting and working. | ISO 55001 cl.9.1 | Split it; where waiting dominates, the fix is spares or access rather than skills. |
| Guards or interlocks removed during work with no reinstatement verification. | 1910.212 | Record removal and verify reinstatement before restart. |
| Recurring failures on one asset never triggering analysis. | ISO 55001 cl.9.1 | Set a threshold that raises root cause analysis automatically. |
| Parts used not recorded against the asset. | ISO 55001 cl.8.1 | Parts history is the fastest route to identifying a component that keeps failing. |
Case in point
Case in point: eleven ways to say the same thing
A plant reviewed two years of corrective work orders on a filling line to understand why availability was falling. The system held over four hundred corrective jobs against the line, each with a completed notes field.
The most frequent failure, once someone read every entry, was a particular drive coupling. It appeared as coupling worn, coupling replaced, drive noise, drive fault, replaced coupling and bolts, vibration on drive, and five other descriptions, spread across four technicians and two shifts. No report had ever surfaced it because no two entries matched.
The line had been under a preventive regime throughout, and the coupling was not on it.
The template
The template, field by field
The form exactly as it installs. Every field, option, score and conditional rule is editable, and the links to other templates come with it.
5 sections
- Reference
- MNT-003
- Archetype
- Record
- Record ID
- WO-2026-000
- Scoring
- Not scored
- Direction
- n/a
- Singleton
- No
- Basis
- ISO 55001 cl.8.2
- Links
- Links Asset, Breakdown
- Tags
- Maintenance, Corrective
- Sections
- 5
- Fields
- 54
- Follow up fields
- 13
- Repeating sections
- 0
- Links out
- 9
Header
16 fieldsWork Order ID*
Auto sequence. Format WO-2026-00000.
The record's own ID. Other templates point at this value.
Status*
Drives who this goes to next.
- Planned2 pts
- In progress2 pts
- Complete3 pts
- Deferred0 pts
- Open0 pts
- Closed3 pts
- Overdue0 pts
Date and Time*
Raised By*
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Area
The area within the site.
Exact Location
Drop a pin for anything hard to find.
Asset*
Asset ID*
Format AST-0000.
Links to FDN-002 Asset ID
Case ID
The failure or finding that caused this repair.
Thread key. Every record in this chain carries this value
Parent Type
What kind of record this follows.
Parent ID
The reference of that record.
Immediate predecessor record
Raised Date*
Failure Report ID
Links to MNT-013 Case ID
Priority*
- High0 pts
- Medium1 pt
- Low3 pts
Fault detail
8 fieldsReported Fault*
Fault Found On Arrival*
Frequently different from what was reported. Recording both improves future diagnosis.
Failure Mode*
Failure Mode Record ID
Links to MNT-014 Record ID
Root Cause Suspected
Repeat Of Previous Failure*
- No3 pts
- Yes0 pts
Previous Work Order ID
Links to MNT-002 Work Order ID
Repeat Failure Review ID
Links to MNT-017 Review ID
Safety and food controls
10 fieldsPermit Required*
Permit Type
Permit ID
Links to SAF-048 Permit ID
Food Contact Area*
Work in or above a food area needs protection before, during and after.
Product Removed Or Covered
- Yes3 pts
- Partly1 pt
- No0 pts
Area Screened Off
- Yes3 pts
- Partly1 pt
- No0 pts
Tool And Part Count Agreed
Count tools and fasteners in, count them out. A missing washer becomes a foreign body.
- Yes3 pts
- No0 pts
Food Grade Materials Only
Lubricants, sealants and gaskets in food areas must be food grade or incidental contact rated.
- Yes3 pts
- No0 pts
Post Work Sanitation Required
Sanitation Inspection ID
Links to QUA-030 Inspection ID
Repair
6 fieldsRepair Method*
Parts Replaced
Old Parts Retained For Analysis*
The failed component is the best evidence you will get about why it failed.
- Yes3 pts
- No0 pts
Assigned To*
Actual Hours
Downtime Hours
Verification
14 fieldsFunction Tested After Repair*
- Yes3 pts
- Partly1 pt
- No0 pts
Guards And Controls Restored*
- Yes3 pts
- No0 pts
Safety Devices Tested*
- Yes3 pts
- Not applicable3 pts
- No0 pts
Running Parameters Normal*
- Yes3 pts
- Marginal1 pt
- No0 pts
Handed Back To Production*
- Yes3 pts
- With restrictions1 pt
- No0 pts
Status*
- Planned2 pts
- In progress2 pts
- Complete3 pts
- Deferred0 pts
- Open0 pts
- Closed3 pts
- Overdue0 pts
Action Required*
Raise the action record, then enter its reference here.
- No2 pts
- Yes0 pts
Priority
- High0 pts
- Medium1 pt
- Low3 pts
CAPA ID
Format CAPA-2026-00000.
Links to FDN-014 CAPA ID
Action Owner
Technician*
Signature*
Area Owner*
Second Signature*
MNT-003 · record IDs look like WO-2026-000 · Links Asset, Breakdown
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The work order is a record of a repair. What fails is the coding that never happened and the temporary fix that closed as complete.
Separates fault from action, applies failure coding at closure, and flags temporary repairs with the permanent work raised alongside.
Aggregates coded failures by asset and component, surfacing dominant failure modes that free text history conceals.
Links isolation, permits and guard removal to the job, and requires reinstatement verification before restart.
Holds hygiene clearance as a release step in food areas, so restart depends on it rather than on the repair being finished.
This template lives in KnowMaintain — asset maintenance. Work orders, planned maintenance, calibration, reliability and shutdowns.
Meet KnowMaintain→Glossary
Corrective Work Order definitions and key terms
- Corrective maintenance
- Unplanned work to restore an asset to working condition after a failure or fault.
- Failure mode
- The manner in which a component fails, coded consistently so that recurrences aggregate.
- Mean time between failures
- A reliability measure only computable where failures are recorded consistently against the asset.
- Temporary repair
- A fix intended to hold until a scheduled opportunity, requiring the permanent work to be raised at the same time.
- Hygiene clearance
- The release step in food production confirming an asset is clean and safe to return to production after maintenance.
- Waiting time
- Downtime spent waiting for parts, access or authorisation, distinct from time spent working on the asset.
- ISO 14224
- The standard for collecting and exchanging reliability and maintenance data, providing failure coding structures.
- PM effectiveness
- Whether the preventive regime is preventing failures, measured by corrective work on assets that are under it.
FAQ
Frequently asked questions about corrective work order
Why separate the fault from the action?+
Because they answer different questions. The fault, which component and what condition, supports reliability analysis and tells you what to prevent. The action, what was replaced or repaired, supports cost, labour and spares planning. Merged into one note, they support neither, and the asset history becomes prose that must be read rather than data that can be queried.
What does failure coding actually give us?+
The ability to see recurrence. Without a controlled list, the same failure is described a dozen ways by different technicians and never aggregates, so the dominant failure mode on an asset stays invisible in a history that records it repeatedly. Coding takes seconds at the point of closing and is what converts maintenance activity into reliability information.
What should corrective work tell us about preventive maintenance?+
Whether it is working. A failure on an asset under a preventive regime means the PM did not cover that component, was scheduled at the wrong interval, or was not actually performed. That feedback loop is the main reason to analyse corrective work, and in most operations it does not exist.
How should temporary repairs be handled?+
Flagged as temporary on the record, with the permanent work raised at the same moment rather than later. A temporary fix closed as complete becomes invisible immediately, and it is then found either by the failure it causes or by someone asking why a component is held on with a hose clip.
Why split downtime into waiting and working?+
Because they have different fixes. Where the technician was working for twenty minutes and waiting three hours for a part, the constraint is stores rather than skills, and training or headcount will not touch it. Most systems record a single downtime figure and conceal which of the two is the actual problem.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Planned Maintenance
Asset Register
Holds every piece of equipment, machine, vehicle and tool you track
Tool and Equipment Register
Holds portable tools, gauges, lifting accessories and small equipment that sit below asset level but still need control
Maintenance Request
Asks maintenance to look at a problem or carry out a job
Work Order
The main record for a planned maintenance job, covering what, where, who and when
Emergency Work Order
Covers urgent work where equipment has stopped or become unsafe
Work Order Closeout
Confirms the job is finished, the area is safe and the equipment is fit to run
More in Work Orders
Maintenance Request
Asks maintenance to look at a problem or carry out a job
Work Order
The main record for a planned maintenance job, covering what, where, who and when
Emergency Work Order
Covers urgent work where equipment has stopped or become unsafe
Work Order Closeout
Confirms the job is finished, the area is safe and the equipment is fit to run
Job Plan
Sets out the steps, parts, tools, permits and time needed for a repeatable job
Permit Linked Work Record
Connects maintenance work to the safety permits it requires, such as isolation, hot work or confined space
Written and reviewed by
Siddarth Singh
Founder & Chief Executive Officer, Knowella
Certified Safety Professional and industrial and systems engineer with more than a decade inside food supply chain, freight and manufacturing operations. This page was written against the current text of the standards it cites, not against secondary summaries of them.
- Certified Safety Professional (CSP), Board of Certified Safety Professionals
- MBA, University of Chicago Booth School of Business
- MS and BS, The Ohio State University, Industrial and Systems Engineering
- Six Sigma Black Belt
Sources and last review. Reviewed 16 August 2026 against:
- ISO 55001:2014, asset management, clauses 8.1 and 9.1
- ISO 14224:2016, collection and exchange of reliability and maintenance data
- 21 CFR 117.40, plant and equipment requirements, FDA
- 29 CFR 1910.147, control of hazardous energy, OSHA
- BRCGS Food Safety Issue 9 clause 4.7, maintenance
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.