Maintenance Work Order Template
One sheet that carries a maintenance job from the moment it is raised to the moment it is signed off.
- Asset ID on every job, so the history follows the equipment
- Twenty task rows, with the reported fault kept separate from the fix
- Parts, labour and rates that total into a job cost
- Downtime from two timestamps, not from memory
Maintenance Work Order
Job record and completion sign-off
| # | Work performed | Done | Hrs | Notes |
|---|---|---|---|---|
| 1 | Attend site and confirm the reported fault | |||
| 2 | Isolate the asset and apply lockout/tagout | |||
| 3 | Record asset condition and meter reading |
The document you will get. Download for the full, editable file.
Who this maintenance work order is for
Four people read this document, and each of them wants a different line out of it.
Facilities manager
You are answering whether the asset is fixed and what it cost. The downtime total and the job cost are the two entries that tell you, and both are on the form rather than in someone's head.
Maintenance planner
You are deciding what to schedule and what to stock. Work type, parts consumed and the follow-up flag are what turn one job into next month's plan.
Maintenance technician
You are the one filling it in, on site. The lockout row and the function test protect you: they record that the asset was made safe and that the fix was proved rather than assumed.
Finance or asset owner
You are attributing cost to equipment. The Asset ID against parts and labour is what makes cost-per-asset a number rather than an argument.
Which field matters the most in your sector
The form is the same shape everywhere. What changes is which field carries the weight, and that is usually the one your auditor or your operations lead asks about first. If you run one of these, the sector page goes further than the template does.
- Commercial real estate
Tenant impact drives everything. Target completion and the downtime block are what a service charge conversation is held against.
Portfolio maintenance software - Healthcare
Traceability outlives the job. The two signatures, the meter reading and the root cause have to still make sense to an auditor years later.
Healthcare maintenance software - Retail and malls
Trading hours constrain the visit. Whether the asset was left running, and the follow-up flag, decide whether the store opens tomorrow.
Retail maintenance software - Education
Term patterns and access. Site, building and location matter more than elsewhere, because the same asset ID exists on four campuses.
Campus maintenance software - Data centres
Redundancy and risk. Work type and the isolation row decide whether the job can happen live or waits for a window.
Data centre maintenance software - Corporate facilities
One team, many buildings. Raised by and assigned to carry the weight, because the requester rarely owns the asset.
Corporate facilities software
What a maintenance work order should include
A maintenance work order is the document that authorises a maintenance job and records what happened to a specific asset. It carries the request, the asset ID, the assignee, the work performed, the downtime, the labour hours, the parts consumed and the sign-off that closes the job.
A. Fields specific to a maintenance work order
| Field | What goes in it | Why it earns its place |
|---|---|---|
| Asset ID and asset name | The tag on the equipment, and its plain name | The field that does the most work on the form. Free-text descriptions drift and cannot be counted; an ID turns a pile of jobs into one asset's history. |
| Work type | Corrective, PM or inspection | One form for both job types. Maintaining separate corrective and preventive templates is how the same asset ends up with two disconnected histories. |
| Priority | Low, medium, high or urgent | Set at intake, from the contract, before anyone has walked to the plant room and formed a view. |
| Asset out of service and back in service | Two timestamps, with the total downtime derived from them | The number operations asks for and the one most maintenance logs leave out. Derived from two times it stays true; typed as a total it stops being true the next day. |
| Work performed | Twenty numbered rows with done, hours and notes against each | What was reported goes at the top. What you actually found and did goes here, and the gap between the two is where the useful information lives. |
| Parts and materials | Part number, description, quantity, unit cost and line total | Every part needs a line. A blank is an unbilled part discovered at month end, or a spare nobody knew was consumed. |
| Cause and follow-up | Root cause found, fault cleared, follow-up needed with a new work order number, parts to reorder | The rows that stop a job ending at the signature. A follow-up without a reference is a job nobody raised. |
| Sign-off | Carried out by, accepted by, and closed and filed by | Three blocks, not one. The technician's signature says the work is done; the acceptor's says someone else agrees; the third says it reached the file. |
If you cut the form down, keep the Asset ID and the two downtime timestamps. Everything that makes maintenance data worth having is built on them: cost per asset, mean time between failures, and the ability to answer how long the line was actually stopped without reconstructing it from memory a week later.
B. What it looks like filled in
The same fields above, on a real job. This is what the Excel version totals for you.
| Line | Detail | Value |
|---|---|---|
| Asset | AHU-14, air handling unit, Level 2 plant room | Corrective |
| Downtime | Out 09:10, back 11:40 | 2.50 hrs |
| Work performed | Six of twenty rows used, function test passed | 3.00 hrs |
| Parts | FLT-2040 air filter, 20 x 40, two at 18.50 | 37.00 |
| Labour | A. Technician, HVAC, 2.5 hrs at 45.00 | 112.50 |
| Job cost | Parts plus labour | 149.50 |
| Cause and follow-up | Filters blinded, fault cleared, reorder raised | No follow-up |
Work order WO-0000, AHU-14, corrective. Read the downtime line rather than the cost line: two and a half hours out of service against three hours booked means the technician was on site before the asset stopped being needed, which is the outcome the target completion field exists to produce. Parts and labour total themselves in the Excel version. Root cause recorded as blinded filters, so the reorder is raised on the same form rather than remembered.
Word to edit, Excel to total the downtime and cost, PDF for the clipboard. Free, and yours to rebrand.
How do you fill in a maintenance work order?
Fill it in the order the job happens, and write the downtime timestamps as they occur rather than reconstructing them at the end. Six steps, and the second is the one that gets skipped.
Raise it against the asset, not the room
Asset ID and asset name, plus site, building and location. A job raised against a room cannot build the equipment's history, and history is the whole point of the ID.
Timestamp the asset out of service as it happens
And back in service when it returns. Two times, taken live, give you a downtime total that stays true. A total typed at the end is an estimate.
Set work type and priority at intake
Corrective, PM or inspection, from the contract rather than from the mood of the shift. This is what keeps one form serving both job types.
Record what you found, not just what was reported
The reported fault is at the top of the sheet. The work performed rows are for what was actually wrong and what you did about it.
Book hours and parts on the visit
Not at the end of the week. Every part gets a line with a cost; every hour gets a name and a rate. Costs recorded later are estimates.
Answer cause and follow-up, then take both signatures
Root cause, whether the fault cleared, and any follow-up with its own work order number. Then the technician signs and the acceptor signs.
Maintenance work order vs preventive maintenance
They are two work types on one form, and confusing them is how maintenance data goes wrong.
| Aspect | Corrective | Preventive |
|---|---|---|
| What starts it | A fault, a complaint or a breakdown | A schedule: a date, a meter reading or a runtime |
| What it proves | That something broken was fixed | That a defined task list was performed on time |
| The load-bearing fields | Reported fault, root cause, downtime | Work type, meter reading, next due date |
| Downtime | Usually unplanned, and the number operations asks about | Usually planned, and often none at all |
| What it feeds | Failure history and the replacement case | Compliance evidence and interval tuning |
| On this form | Work type set to corrective | Work type set to PM |
The rule worth enforcing is that a PM which uncovers a fault raises its own corrective work order rather than absorbing the repair. Absorbed repairs make a failing asset look cheap to run, because the PM records that it was serviced and never records what it needed.
When the template starts to feel limiting
A form handles one job well. It handles an estate badly, and the failure modes are consistent.
There is no version control
Somebody edits the task rows, emails the form round, and two versions are in use on the same site. Nothing tells you which job used which.
Target completion is not a clock
It sits on a sheet in a van. Nothing warns you an hour before it breaches, which is the only moment the information could still change the outcome.
There is no audit trail
A signed sheet proves a signature existed. It cannot show that a root cause was added a week later, or by whom, which is what an audit asks.
You cannot total the asset
One form describes one job. Cost per asset, mean time between failures and which equipment fails most exist only across forms, and a folder will not add them up.
What running this in Facilio looks like
The template is the paper version of this record. The fields below are the same ones; the difference is that Facilio can act on them.
Work Completion Validator
Sign-off stops being a signature
On paper, a job is complete when someone signs it. Work Completion Validator checks the completion record against what the job required, so a job closed with no hours, no root cause or an empty downtime block is caught while the technician is still on site.
Ops Performance Intelligence
Target completion becomes a live clock
The date you set at intake drives an SLA that warns before it breaches, and rolls up so you can see which assets and which sites are running hot rather than reviewing it a quarter later.
Audit Report Intelligence
The sign-off block becomes retrievable evidence
Who carried out the work, who accepted it and when, logged once against the asset and assembled into the report an auditor asks for instead of being searched for across a year of sheets.
Contractor Work Tracker
Parts and labour total themselves per asset
Every part with a charge-to and every labour line at an agreed rate become the running cost of that asset, so the replacement case is built from records rather than assembled in a hurry.
Permission-aware by default. Atom AI inherits RBAC from your Facilio config, so if a user cannot see it in Facilio they cannot see it via Atom AI.
Frequently asked questions
What is a maintenance work order?
A maintenance work order is the document that authorises a maintenance job and records what happened to a specific asset. It carries the request, the asset ID, the assignee, the work performed, the downtime, the labour hours, the parts consumed and the sign-off that closes the job.
It is not the same as a work request. A request is what someone asks for. A work order is what you commit to doing, against a named asset, with a cost attached.
What should a maintenance work order include?
At minimum: a unique work order number, the date raised and by whom, priority, site, building and location, the asset ID and name, the work type, the assignee, the reported fault, target completion, the downtime timestamps, numbered work-performed rows with hours, parts and materials, labour, the job cost, root cause and follow-up, and the sign-off blocks.
Should corrective and preventive jobs use the same form?
Yes, with a work type field to separate them. Maintaining two templates is how the same asset ends up with two disconnected histories that nobody can add together.
The one discipline worth keeping is that a PM which finds a fault raises its own corrective work order rather than absorbing the repair into the checklist.
Why record downtime as two timestamps?
Because a total typed at the end of the job stops being true the moment anyone questions it. Out of service and back in service are two facts; the total is derived from them and stays correct.
It is also the number operations asks for and the one most maintenance logs leave out entirely.
What makes the Asset ID so important?
It is what turns a pile of forms into asset history. Without it you can say a pump was repaired; with it you can say this pump has been repaired four times this year and here is what it cost.
Cost per asset, mean time between failures and any replacement case are all built on that one field being filled in consistently.
How is this different from a job card or a work request?
A work request is what someone asks for, before anyone has agreed to do it. A job card is usually the single sheet a technician carries for one task.
The maintenance work order is the authorising record: it says this job was approved, against this asset, and here is what it cost when it closed.
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 task rows, the work types or the wording; the Excel version is the one to use if you want downtime hours, parts and labour to total themselves.
In one paragraph
A maintenance work order records one job against one asset. Raise it against the asset ID rather than the room, and timestamp out of service and back in service as they happen so the downtime total stays true. Set work type at intake so corrective and preventive live on one form. Record what you actually found, book hours and parts on the visit rather than at the end of the week, then answer root cause and follow-up before taking both signatures.
The template is the floor, not the ceiling
Take the template; it will carry a job from raised to signed off. When one form per job stops being enough, a connected CMMS runs the estate: downtime that totals itself, target completions that warn before they breach, and cost that attaches to the asset instead of the month.
