Equipment Maintenance Checklist
An equipment maintenance checklist template for machinery rather than buildings, scheduled on running hours instead of the calendar. A press that ran nine hundred hours last quarter and an identical one that ran ninety do not need the same attention on the same date, and the hours column is the only thing on a service sheet that shows the difference.
- Scheduled on running hours, cycles or calendar, stated which
- Condition readings trended against a baseline and a limit
- Running hours recorded at the moment a part is fitted
- Nine safety devices, tested rather than inspected
Equipment Maintenance Checklist
Hours, not dates
| # | CONDITION MONITORING | THIS | LAST | BASELINE |
|---|---|---|---|---|
| 1 | Drive end bearing, vibration | |||
| 2 | Non-drive end bearing | |||
| 3 | Gearbox |
The document you will get. Download for the full, editable file.
Who this equipment maintenance checklist is for
One machine, and four people with different definitions of a good service.
The maintenance technician
The five check sections and the condition readings, taken before anything is adjusted. The order matters as much as the content on this sheet.
The reliability or planning engineer
The trend columns and the parts history at hours. Between them they turn a service record into a replacement forecast rather than a list of what happened.
The production manager
Criticality, duty and downtime taken. Planned downtime is the cost production actually feels, and a program that cannot state it always looks more expensive than it is.
Whoever owns machine safety
The nine safety devices, each operated and recorded. Emergency stops tested individually, interlocks proved to stop the machine, light curtains tested through their field.
Where machines are maintained on hours
The structure suits any powered machine with a duty cycle. What changes is what stops when it stops. If you run one of these, the sector page goes further than the template does.
- FM service providers
Workshops, plant and process equipment across a contract, where machines of the same model accumulate wildly different hours.
FM service provider software - Retail and malls
Conveyors, balers, compactors and back-of-house machinery that runs hard and is serviced around trading.
Retail maintenance software - Healthcare
Plant and process equipment supporting clinical operations, where criticality is a clinical judgment rather than a production one.
Healthcare maintenance software - Education
Workshop and laboratory machinery, where duty is intermittent and term-driven rather than continuous.
Campus maintenance software - Corporate facilities
Building-adjacent machinery like pumps, compressors and generators, maintained on hours rather than on a building schedule.
Corporate facilities software - Commercial real estate
Estate plant with meters, where two identical pumps on the same date are frequently thousands of hours apart.
Portfolio maintenance software
What a machine preventive maintenance checklist should contain
An equipment maintenance checklist is the planned maintenance record for a machine, scheduled by running hours rather than by date. It covers drives and bearings, lubrication, hydraulics and pneumatics, electrical and control, and safety devices tested individually, then carries condition readings against a baseline and records the hours at which each part was fitted.
A. Mechanical, then electrical, then condition
| Field | What goes in it | Why it earns its place |
|---|---|---|
| Machine details | Criticality, duty, running hours at this and the last service, and what governs the interval | Criticality graded by what happens when it stops: line stops, reduced output, or no immediate effect. That grading should drive the interval more than the model plate does. |
| Running hours | Recorded at every service, even where the interval is set by the calendar | Two identical machines serviced on the same date can be a thousand hours apart. Without the hours column nothing on the sheet reveals that. |
| Drives, bearings and transmission | Nine checks including bearing temperature and vibration against the last reading | Compared with the last reading rather than against a limit alone, because a bearing well inside limits and climbing steadily is the one that will fail. |
| Readings before adjustment | Taken on arrival, not after work | A temperature or vibration figure recorded after a belt has been retensioned describes the repair. The condition the machine was found in is the thing worth trending. |
| Lubrication | Eight checks including grease applied to the specified quantity | To the quantity on the chart rather than to refusal. Over-greasing destroys more bearings than under-greasing, by pressurizing seals and churning grease until it overheats. |
| Hydraulics and pneumatics | Nine checks from system pressure to valves operated through full travel | Includes accumulator pre-charge, which is checked rarely and fails silently, and cylinder rods inspected for scoring that will take a seal out later. |
| Electrical and control | Nine checks including motor current on each phase and the drive fault log | Reading and clearing the inverter fault log is the electrical equivalent of downloading a fault history: it describes what happened between visits. |
| Safety devices | Nine devices, every one operated and recorded rather than looked at | Emergency stops operated individually, interlocked guards proved to stop the machine, light curtains tested through their field, two-hand controls tested for simultaneity. |
| Condition monitoring readings | Eleven points shown this service, last service and at baseline, with a limit and a trend | The section that makes the document predictive. A reading inside its limit with a rising trend is more actionable than one near its limit and stable. |
| Parts replaced | Part number, quantity, running hours at fit, expected life and next due at hours | Hours at fit rather than date fitted. That single column turns a parts history into a replacement forecast you can plan a shutdown around. |
| Defects and follow-up | Component, defect, severity, corrective work order and target date | Severity is Critical, Major or Minor, spelled exactly that way, and Critical means the machine does not run until it is fixed. |
| Service result | Completion, hours since last service, labor hours, downtime taken and next due at hours | Downtime taken is recorded separately from labor hours, because planned downtime is the cost a production manager actually feels. |
Scheduling on running hours rather than dates is the decision that separates machine maintenance from building maintenance, and it is the reason this is a different document from a building PM checklist. A building's systems run more or less continuously and age more or less with the calendar, so a quarterly or annual interval is a reasonable proxy for wear. Machines do not behave that way at all. Two identical presses on the same line, bought together and serviced on the same date every quarter, can be thousands of hours apart by the end of a year because one took the overflow work and the other sat idle through a slow season. Servicing both at the same interval means one is being over-maintained, which costs money and introduces the risk that comes with every intervention, while the other is being under-maintained and is accumulating wear nobody is looking at. The hours column fixes that, and it costs one reading per visit. The second thing worth copying is the trend column on the condition readings. A single vibration figure is almost useless in isolation unless it is already alarming: 2.8 against a limit of 7.1 is comfortably fine, and a technician reporting it will reasonably mark the machine as healthy. The same figure read as the third point in a sequence of 2.1, 2.4 and 2.8 is a different statement entirely, because the rate of change is consistent and the limit is now a date rather than a threshold. That is what converts maintenance from reacting to failures into scheduling them.
B. What it looks like filled in
One service on a press. Every reading inside its limit, and the sheet still predicts when a bearing will need changing.
| Line | Value |
|---|---|
| Machine and hours | PRESS-04, 14,820 hours |
| Hours since last service | 920 |
| Drive end bearing vibration | 2.8, against a limit of 7.1 |
| Last service, baseline | 2.4, and 2.1 |
| Bearing fitted at | 14,820 hours, 20,000 hour life |
| Next bearing due at | 34,820 hours |
A reading of 2.8 against a limit of 7.1 is a pass by any reasonable reading, and the sequence it sits in is the actual finding. The baseline for this bearing was 2.1 when the machine was new. The last service read 2.4. This service reads 2.8. Nothing is wrong today, the machine was released to production, and a service sheet without the previous two figures on it would say so and stop there. With them, the shape is unmistakable: roughly 0.35 per service, consistent, and at 920 hours between services the limit is a calculable number of hours away rather than an unknown. That is the difference between knowing a bearing will fail and knowing roughly when, and the second one can be planned into a shutdown instead of discovered during a production run. The parts line does the same job from the other direction. The replacement bearing went in at 14,820 hours with a twenty thousand hour expected life, so it is due at 34,820 hours, and because the machine's hours are recorded every visit that figure converts into a date as soon as anybody wants it to. Recording the date it was fitted instead would have produced a parts history. Recording the hours produces a forecast.
Word for the version a technician takes to the machine, Excel for the one that carries condition readings forward against the baseline and holds a Service History to build a replacement forecast, and PDF for the copy that goes in the machine file. Free, and yours to rebrand.
How do you schedule maintenance on running hours?
Set the interval from what the machine actually did, not from what the calendar says. Six steps.
Grade the machine by what stops when it stops
Line stops, reduced output, or no immediate effect. That grading should influence the interval more than the manufacturer's nameplate recommendation does.
State what governs the interval, then record hours anyway
Hours, cycles or calendar, declared explicitly. Record running hours at every service even on a calendar interval, because that is the only thing that reveals two identical machines drifting apart.
Take the condition readings before touching anything
Bearing temperature and vibration on arrival. A reading taken after a belt has been retensioned tells you about the adjustment rather than the condition the machine was in.
Work the mechanical sections, greasing to the chart
Drives and bearings, then lubrication to the specified quantity rather than to refusal, then hydraulics and pneumatics including the accumulator pre-charge that fails silently.
Test every safety device individually
Each emergency stop operated and reset, interlocks proved to stop the machine, light curtains tested through their field. Looking at them proves nothing and the test needs a date against it.
Record hours at fit and set the next service in hours
Every part logged with the running hours it went in at, and the next service due at an hours figure rather than a date, so the schedule follows the work the machine actually does.
An equipment maintenance checklist versus an equipment maintenance log
Two documents with almost the same name that do opposite jobs, and keeping both is the point rather than choosing between them.
| Aspect | The checklist | The log |
|---|---|---|
| Which way it looks | Forward, at the next service | Backward, at everything done |
| What it contains | Checks, readings, a trend | Every job, planned and reactive |
| When it is used | At a scheduled service | Continuously, by anyone |
| What it answers | Is this machine healthy | What has this machine cost |
| What it drives | The next intervention | The repair or replace decision |
| Its unit | Running hours | Jobs and money |
An equipment maintenance checklist and an equipment maintenance log sit next to each other on any keyword list and are genuinely different documents, which is worth being explicit about because using one for the other is common. This page is the planned service itself: the things checked at a scheduled interval, the readings taken, the trend they form and the next service due. The log is the machine's whole history, planned and reactive together, with what each job cost, and it exists to answer whether the machine is still worth repairing. Use only the checklist and you have a healthy maintenance regime with no idea what the machine has consumed in parts and labor over five years. Use only the log and you have an excellent cost record and nothing that tells you a bearing is trending toward its limit. They also hand off to each other: a defect found here becomes an equipment work order, and that job then appears in the log. Separately, this is machinery rather than building systems. Air handling, electrical distribution, plumbing and fire systems run on a building PM regime and belong in a preventive maintenance checklist.
When the template starts to feel limiting
The file is built for one machine, serviced on an interval, recorded on paper. Four things start to hurt as soon as that is not the shape of the problem.
Nothing watches the hours
The next service is due at a running-hours figure and the machine does not announce when it reaches it. Somebody has to read a meter and compare it with a sheet.
The trend only exists if the sheets are together
Carrying readings forward means having the last service sheet in hand. The reading taken without it is a number with no meaning attached.
The parts forecast is manual arithmetic
Hours at fit plus expected life gives a due figure, and converting that into a date anybody can plan around means somebody doing it deliberately.
Downtime is recorded and never aggregated
Downtime per service is the number that defends a maintenance budget, and on paper it is a column nobody totals across a year.
What running this in Facilio looks like
The service does not change. What changes is that the hours are watched and the trend draws itself.
Work Order Intelligence
Services are raised on hours
The next service comes round when the machine reaches the hours figure rather than when somebody compares a meter reading with a sheet.
Asset Intelligence
Condition readings trend automatically
Each service adds to a history against the machine, so a bearing climbing toward its limit is visible as a slope rather than as three numbers on three sheets.
Ops Performance Intelligence
Parts forecasts become dates
Hours at fit plus expected life, read against the machine's actual usage rate, turns into a planning date instead of arithmetic somebody has to do.
Audit Report Intelligence
Downtime aggregates
Planned downtime per service totals across the year, which is the figure that defends a maintenance program to whoever runs production.
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 equipment maintenance checklist?
It is the planned maintenance record for a machine, scheduled by running hours rather than by date. This one carries 44 checks across drives and bearings, lubrication, hydraulics and pneumatics, electrical and control, and safety devices.
It also carries eleven condition monitoring points trended against a baseline and a limit, and a parts table that records the running hours at which each part was fitted.
What should a machine preventive maintenance checklist include?
Bearing temperature and vibration compared with the last reading, alignment and transmission, lubrication to a specified quantity, hydraulic and pneumatic pressures and filtration, motor currents on each phase, and the drive fault log.
Then safety devices tested individually, condition readings carried forward, and parts recorded against running hours rather than dates.
Why schedule on running hours instead of the calendar?
Because two identical machines on the same quarterly service date can be thousands of hours apart by the end of a year, depending on what each one was asked to do.
Servicing both identically over-maintains the idle one, which costs money and carries the risk that comes with any intervention, and under-maintains the busy one.
Why take condition readings before adjusting anything?
Because a vibration or temperature figure recorded after a belt has been retensioned or a bearing regreased describes the repair rather than the condition the machine was found in.
The trend is built from arrival readings. Mixing in post-adjustment figures makes the sequence meaningless.
What does a rising trend inside limits actually mean?
That you now have a predictable failure date. A bearing at 2.8 against a limit of 7.1 is fine today, and a bearing that has gone 2.1, 2.4, 2.8 across three services at a consistent rate will reach the limit at a point you can calculate.
That is the difference between knowing something will fail and knowing roughly when, which is what makes it plannable.
Why record running hours when a part is fitted?
Because hours at fit plus expected life gives a next-due figure, and that converts a parts history into a replacement forecast. The example bearing went in at 14,820 hours with a 20,000 hour life, so it is due at 34,820.
Recording only the date fitted produces a record of what happened rather than a prediction of what is needed.
Why does every safety line say tested?
Because looking at an emergency stop proves nothing about whether it operates. Each one has to be pressed and reset individually, interlocks proved to actually stop the machine, light curtains tested through their field.
The test also needs a date recorded against it, because the question later is not whether the device exists but when it was last proved to work.
Is this the same as an equipment maintenance log?
No, and the two are easy to confuse. This is the forward-looking planned service: what gets checked, the readings, the trend and the next service due in hours.
An equipment maintenance log is the backward-looking history of every job on the machine with what each one cost, and it exists to answer whether the machine is still worth repairing. Most operations need both.
In one paragraph
An equipment maintenance checklist works when it is scheduled on running hours rather than dates, because two identical machines serviced on the same day can be thousands of hours apart. Take the condition readings before adjusting anything and carry them forward against a baseline, since a rising trend inside its limit gives you a predictable failure date while a single figure gives you nothing. Test every safety device individually, and record the running hours at which each part was fitted so the parts history becomes a forecast.
The trend is the finding, not the reading
Grade the machine by what stops when it does, schedule on hours, read before you adjust and log parts at the hours they went in. Once nothing watches the meter, or the trend only exists when two sheets are side by side, the paper version has reached its limit.
