Inspection Work Order
A job ticket that says go and inspect this. Pass, fail or not applicable on every point, and every fail leaves with a photo reference, a corrective work order number and a date, so a finding cannot quietly become a note.
- Fourteen standard inspection points, plus room for asset-specific ones
- Every fail gets a photo reference and a corrective work order number
- Deficiencies counted high, medium and low, with a pass rate
- A next-due date set before the ticket closes
Inspection Work Order
Go and inspect this, and prove it
| # | Inspection point | Pass | Fail | N/A |
|---|---|---|---|---|
| 1 | Asset present, correctly identified and labeled | |||
| 2 | General condition, no damage, corrosion or wear beyond tolerance | |||
| 3 | No leaks, drips or staining |
The document you will get. Download for the full, editable file.
Who this inspection work order is for
This document is a ticket and a record at once, which means it is read by one person before the round and a different person afterwards.
The inspector on the round
You carry it and complete it as you go. The fourteen points and the observation column are your working surface, and section 5 is where anything specific to this asset goes.
Whoever raised the ticket
You set the type, the priority, the due date and why it is being raised. Scheduled round and following an incident produce very different inspections, so the reason belongs on the ticket.
The area or asset owner
You sign to accept the result. The fit to remain in service line is the one you are actually signing, and a High severity deficiency left open makes that your decision rather than an oversight.
Safety or compliance lead
You read these in a stack, months later. The severity counts, the corrective work order numbers and whether last time's deficiencies were closed are the three lines that tell you if the process works.
Which section matters the most in your sector
The fourteen points hold up across most plant and most buildings. What changes is what a failure means and how fast it has to be acted on. If you run one of these, the sector page goes further than the template does.
- FM service providers
The corrective work order number. When inspection is subcontracted, a finding with no raised job is the gap that turns up in a client review months later.
FM service provider software - Healthcare
Fit to remain in service. In clinical areas that line decides whether equipment keeps being used tonight, so it needs a name against it rather than a default yes.
Healthcare maintenance software - Data centres
Statutory certification in date and available. In critical environments the certificate being current and the certificate being findable are two different failures, and both get inspected.
Data centre maintenance software - Commercial real estate
Previous deficiencies closed. Across a portfolio the same finding recurring at the same asset is the signal that the corrective process, not the asset, is what needs fixing.
Portfolio maintenance software - Retail and malls
Access and occupancy constraints. Inspecting plant behind a trading floor means the round is scheduled around opening hours or it does not happen at all.
Retail maintenance software - Education
Frequency and next due. Term-time buildings inspect on a calendar that has gaps in it, so the next due date has to be set deliberately rather than rolled forward.
Campus maintenance software
What an inspection work order should contain
An inspection work order is a job ticket instructing a named inspector to inspect a specific asset by a given date. It carries the standard points marked pass, fail or not applicable, the observations behind them, every deficiency with a severity and a corrective work order number, the photo evidence, and the next inspection date.
A. Fields specific to an inspection work order
| Field | What goes in it | Why it earns its place |
|---|---|---|
| Inspection type | Safety, compliance, routine or audit | The type decides how a failure is treated and whether certification is required of the inspector. A compliance inspection that fails is a different conversation from a routine one. |
| Why it is being raised | Scheduled round, after an incident, regulatory, complaint or pre-handover | The reason changes what good looks like. An inspection raised after an incident is looking for something specific, and recording that keeps the result readable later. |
| Priority and due by | Urgent, scheduled or routine, with a date | A ticket without a due date is a suggestion. Priority is what decides whether this one displaces other work or joins the queue behind it. |
| Access requirements | Keys, permits, escort, height access, isolation | The practical reason rounds do not get completed. Naming the access up front is what stops an inspector arriving and finding they cannot reach half the items. |
| Inspector and competence | Name, company, and any certification the type requires | Some inspection types are only valid if the person holding the clipboard is qualified to hold it. Recording it on the ticket makes that checkable rather than assumed. |
| Fourteen standard points | Each marked pass, fail or not applicable, with an observation | The same fourteen every time, so two inspections of the same asset are comparable. Consistency is what turns a round into a trend rather than a series of opinions. |
| The observation column | Used on every fail, and on any marginal pass | This is where a deteriorating condition gets caught. A bare tick says it was acceptable today and nothing about whether it is worse than last quarter. |
| Additional points | Anything specific to this asset, with a result and a reference | The standard list cannot cover a particular machine's own checks. This section takes them without breaking the comparability of the fourteen. |
| Deficiency table | Location, the deficiency, severity, photo reference, corrective work order, date | The heart of the document. Every fail above becomes a row here, and the corrective work order number is the field that turns a finding into work somebody owns. |
| Photo and evidence register | A reference per image, what it shows, where, by whom and when | Referenced images rather than a folder of pictures. A photo that cannot be tied to a specific finding is not evidence of anything six months later. |
| Result and pass rate | Severity counts, points inspected and passed, and the overall result | Satisfactory, satisfactory with actions, or unsatisfactory, alongside whether the asset is fit to remain in service. One High severity finding settles both on its own. |
| Next inspection | Due date, frequency confirmed or changed, and what to verify next time | Set before the ticket closes. Deficiencies to verify at the next visit is what makes the following inspection start from this one rather than from nothing. |
The corrective work order column is the field that separates this from a checklist somebody filled in. A finding recorded without a job number attached to it has no owner, no date and no way to be closed, so the next inspector arrives, finds the same cracked guard, and writes it down again. Run that for a year and you have twelve inspections, a healthy-looking pass rate and a guard that has been broken the whole time. The document is deliberately built so that path is awkward: every Fail in section 4 is meant to produce a row in section 6, and that row has a column for a work order number sitting empty until somebody fills it. If your inspections consistently produce findings and rarely produce corrective work orders, that is not an inspection problem, and no amount of extra inspecting will fix it.
B. What it looks like filled in
One safety round on a plant room pump, from the log. Twelve points passed, two did not, and the two failures are the only part of this that matters.
| Point | Result | Observation | What it raised |
|---|---|---|---|
| Asset present and labeled | Pass | Tag legible, matches asset register | n/a |
| Guards, covers and panels secure | Fail | Guard cracked, one fixing missing | WO-1188, High, IMG-0412 |
| Safety devices and interlocks | Pass | Emergency stop tested, functional | n/a |
| No leaks, drips or staining | Fail | Light staining under the seal, not dripping | WO-1189, Medium, IMG-0413 |
| Instruments reading in range | Pass | Discharge pressure at the top of range | Marginal, noted for next visit |
| Previous deficiencies closed | Pass | Last quarter's coupling guard verified fitted | n/a |
Read the third bold entry, the one that passed. Discharge pressure at the top of its range is not a failure and should not be recorded as one, but writing it in the observation column is what gives the next inspector something to compare against. If it is at the top of range again next quarter it is a trend; if the column was left blank, it is a first observation all over again. The two genuine failures show the rule working: each left the round with a severity, a photo reference and a corrective work order number, so neither can quietly become a note. The High severity one also decided the result on its own, which is why the overall line reads satisfactory with actions rather than satisfactory, and why somebody had to make an explicit call about leaving the pump in service rather than letting it default.
Word for the ticket an inspector carries and completes on the round, Excel for the severity summary and pass rate that calculate themselves plus the Inspection Log that exposes repeat findings, PDF for the printed copy with the photo register. Free, and yours to rebrand.
How do you raise and complete an inspection work order?
Part A is filled in when the ticket is raised, part B on the round, part C before it closes. Six steps.
Raise the ticket with a reason and a due date
Work order number, date issued, who issued it, the inspection type, the priority, the due by date and the frequency. Then why it is being raised: a scheduled round, following an incident, a regulatory requirement, a complaint or a pre-handover check.
Scope what is being inspected, and how to get to it
Site, area or route, the asset or asset group with its ID range, and how many items are on the round. Then the access requirements, keys, permits, escort, height access or isolation, and any occupancy or timing constraints.
Name the inspector and their competence
Who is doing it, their role or company, and any certification the inspection type requires. Then the times started and finished and the conditions during the round, since lighting and whether plant was running change what could actually be seen.
Work the fourteen points, writing observations as you go
Pass, fail or not applicable on each, with an observation on every fail and on any pass that was marginal. Anything specific to this asset that is not on the standard list goes in section 5 with its own result and reference.
Turn every fail into a deficiency with a job number
One row per failure: location or asset, what the deficiency is, severity spelled high, medium or low, a photo reference, the corrective work order number raised against it, and a date. Then log each photo in the evidence register.
Set the result and the next inspection before closing
Severity counts, points inspected and passed, the pass rate, and the overall result. Any High severity finding decides that and the fit to remain in service line. Then the next due date, what to verify next visit, and the signatures.
An inspection work order versus a safety inspection checklist
These two get used interchangeably and they are not interchangeable. One is a ticket against an asset; the other is a walk around an area. Most sites need both, for different reasons.
| Aspect | This inspection work order | A safety inspection checklist |
|---|---|---|
| What it is | A ticket issued to a named inspector, with a due date | A walkthrough of an area, done by whoever is walking it |
| What it covers | One asset or asset group, against fourteen fixed points | Whatever hazards are present, wherever they are |
| How findings are scored | Pass, fail or N/A per point, then high, medium or low | Severity against likelihood, banded into a risk level |
| Where a finding goes | A numbered corrective work order, on the form | An action with an owner and a date |
| Scheduling | Has a frequency and a next due date built in | Run when you decide the area needs walking |
| If it is the only one you run | You inspect the assets and miss the trailing cable | You walk the site and never open the panel |
The split is asset versus area, and it decides which document answers your question. If you need to know whether PUMP-02 is fit to stay in service, you need a ticket against that asset, inspected against the same fourteen points it was inspected against last quarter, by somebody competent to judge it. A general walkthrough will never produce that, because it looks at whatever is visible rather than at a fixed list. If instead you need to know whether the plant room is a safe place to work this week, the walkthrough is the right instrument and the asset ticket is nearly useless, since it is looking at one machine and ignoring the extension lead running across the floor next to it. The practical test is what triggers the document. An inspection work order is triggered by a schedule, an incident or a regulation and is aimed at a thing. A safety walkthrough is triggered by a place and a period of time. Running one and calling it the other is how sites end up with a folder full of evidence that answers a question nobody asked.
When the template starts to feel limiting
The form runs one round well. It is the second, third and twelfth round where paper stops keeping up, in four familiar ways.
Next due dates that nobody chases
Every completed ticket sets the next inspection date, and then gets filed. Nothing surfaces the round that was due three weeks ago, which is how an annual inspection becomes a fourteen-month one.
Open deficiencies are invisible between rounds
The corrective work order numbers exist on the form. Whether those jobs were actually done is somewhere else entirely, so the answer only arrives when the next inspector checks the previous deficiencies line.
The inspection and the corrective job live apart
One is a completed round in a folder, the other is a work order in a system. Nothing connects them, so a corrective job can be closed without the finding closing, or the reverse.
Repeat findings never assemble themselves
The same deficiency at the same asset across four rounds is the single most useful thing these documents contain, and seeing it means reading four separate forms side by side and noticing.
What running this in Facilio looks like
The template is the paper version of this round. The fourteen points are the same ones; the difference is that a deficiency becomes a job attached to the asset rather than a line on a filed sheet.
Work Completion Validator
A finding cannot close without the corrective work done
On paper a deficiency is closed when somebody writes Yes in the Done column. Work Completion Validator holds that against the corrective job itself, so a finding marked closed with the work order still open is caught.
Ops Performance Intelligence
Next due dates chase themselves
Frequency and next due sit against the asset rather than on the last completed form, so an overdue round surfaces on its own instead of waiting for somebody to leaf through the folder.
Audit Report Intelligence
Repeat findings assemble automatically
Because each deficiency is recorded against the asset, the same guard failing across four rounds reads as one unresolved problem rather than four separate findings, which is the pattern worth acting on.
Contractor Work Tracker
Inspector competence is checked before the round
Who is approved for which inspection type, and whether their certification is current, sits against the contractor record, so a compliance inspection is not discovered afterwards to have been done by somebody unqualified.
Hallucination-free by design. Atom AI answers from the records in your tenant rather than generating plausible text, so an empty field reads as empty rather than filled in for you.
Frequently asked questions
What is an inspection work order?
An inspection work order is a job ticket that instructs a named inspector to inspect a specific asset or area by a given date. It carries the reason the inspection was raised, the access it needs, the inspector and their competence, a fixed list of inspection points marked pass, fail or not applicable, the observations behind them, every deficiency with a severity and a corrective work order number, the photo evidence, the overall result and the next inspection date.
It is both the instruction and the record. The same document is issued, carried on the round, completed as you go, and signed off at the end.
How is it different from a safety inspection checklist?
An inspection work order is aimed at an asset and triggered by a schedule, an incident or a regulation. A safety inspection checklist is aimed at an area and triggered by the need to know whether that place is safe to work in right now.
The fixed point list is the other difference. Because this document inspects the same fourteen things every time, two rounds on the same asset are directly comparable, which is what turns inspections into a trend. A walkthrough looks at whatever hazards are present, which is the right approach for an area and the wrong one for judging whether a specific pump is fit to stay in service.
What should an inspection work order include?
The ticket details, work order number, type, priority, due date, frequency and why it is being raised. What is being inspected, with the asset IDs, access requirements and any timing constraints. The inspector, their competence and the conditions during the round.
Then the inspection itself: fourteen standard points with pass, fail or N/A and an observation column, a section for asset-specific points, a deficiency table with severity, photo reference and corrective work order number, a photo register, a result block with the pass rate and whether the asset is fit to remain in service, the next inspection date, and sign-off.
What happens when a point fails?
It becomes a row in the deficiency table with a location, a description, a severity of high, medium or low, a photo reference, a date and, critically, a corrective work order number. That number is what gives the finding an owner and a route to being fixed.
A deficiency recorded without a corrective work order number will be found again at the next inspection, unchanged, because nothing has been raised that anybody is accountable for. If your rounds regularly produce findings but rarely produce corrective jobs, inspecting more often will not help.
What counts as high severity?
Use high, medium and low, spelled exactly that way so the summary counts them, and reserve high for anything affecting safety, statutory compliance or whether the asset can stay in service.
It matters because a single high severity finding decides the overall result and the fit to remain in service line on its own. Leaving an area or asset in service with an open high severity deficiency should be an explicit decision somebody signs for, not something that happens by default because nobody looked at the severity column.
Why record an observation on a point that passed?
Because a bare tick tells the next inspector nothing. A reading at the top of its normal range is a pass today and a trend if it is at the top of range again next quarter, and the only way anybody sees that is if the first observation was written down.
The document asks for observations on every fail and on any pass that was marginal. That is what makes the fourteen points a comparison between rounds rather than a fresh opinion each time.
How do photos work on this form?
Every photo gets a reference, and that reference is quoted in the deficiency row it belongs to. The evidence register records what each image shows, where it was taken, by whom and at what time.
The alternative is a folder of images that nobody can match to a specific finding months later, which is not evidence of anything. Referencing them takes seconds on the round and is the difference between a defensible record and a pile of pictures.
Can I edit and rebrand this template?
Yes. It is free to use, edit, rename and put your own logo on, internally or for clients. No attribution required.
The Word version is the one to edit if you want to change the fourteen points to match your own asset classes or standards. The Excel version is the one to use if you want the severity summary and pass rate to calculate themselves, plus the Inspection Log tab, which puts one row per round side by side so repeat findings at the same asset become obvious.
In one paragraph
An inspection work order is a ticket aimed at an asset, not a walk around an area, and the difference decides which document you should be using. Raise it with a type, a priority, a due date and a reason, because an inspection following an incident is looking for something a scheduled round is not. Name the inspector and any competence the type requires, and record the access it needs, since that is the usual reason rounds come back half finished. Work the same fourteen points every time so two rounds are comparable, and write an observation on every fail and on any pass that was marginal, because that column is where a deteriorating condition gets caught early. Then turn every failure into a deficiency with a severity, a referenced photo and a corrective work order number, since a finding without a job number will be written down again next time, unchanged. Let any high severity finding decide the result rather than overriding it, and set the next due date before the ticket closes.
The template is the floor, not the ceiling
Take the ticket; it will run one round properly and leave a record that stands up. When a folder of completed rounds stops answering whether the findings were ever fixed, a connected CMMS closes the loop: deficiencies raised as jobs against the asset, corrective work tracked to completion, overdue rounds surfacing on their own, and the same finding recurring at the same asset visible on the second round rather than the fifth.
