Preventive maintenance checklists: templates and best practices

What a preventive maintenance checklist is

A preventive maintenance checklist is the standard task list that a PM schedule carries — the fixed set of inspections, cleaning, lubrication, tightening and measurements a technician works through every time a machine falls due. It is not a loose reminder; it is a structured checklist template attached to the schedule, the same template-and-checksheet pattern the wider suite uses for audit and quality checks. When the schedule triggers, Fast Maintenance generates a PM ticket and the checklist is executed against that ticket, item by item.

Why it matters is simple: a schedule tells you when to service a machine, but the checklist decides what actually gets done and whether it was done well. Without a defined task list, "monthly PM" means whatever the technician on shift remembers to look at. With one, every visit covers the same points, records the same readings, and leaves a history you can trust for an audit, an AMC claim or a reliability review. The checklist is where a preventive programme stops being a calendar and becomes real, measurable work.

Anatomy of a good checklist task

A weak checklist reads "check the motor". A strong one tells the technician exactly what to inspect, how to inspect it, what "good" looks like, and how to record the answer. Every task on a well-built PM checklist carries four parts:

The technician then records the result against the auto-generated PM ticket, and alongside the item-level responses the job also captures labour time and spares used, so the cost and effort of preventive work are visible, not just the fact that it happened. A preventive maintenance module that captures all four parts turns a checklist from a compliance tick-sheet into a data source.

The three response types: OK / not-OK / measured value

The single most important design choice on a PM checklist is the response type of each item. Fast Maintenance supports three, and choosing the right one per task is what makes the data worth collecting.

Where the discipline pays off is the measured value. A tick tells you the bearing temperature was "OK" on the day; a recorded 68 °C tells you it was 52 °C last month and 61 °C the month before — a trend heading for trouble long before anyone would have ticked "not-OK". A value can be plotted; a tick cannot. For readings that drift — vibration, insulation resistance, oil pressure, coolant concentration — always capture the number, so the checklist feeds condition monitoring and the reliability dashboards rather than just confirming a box was looked at.

The closed loop: how a not-OK item spawns a corrective ticket

A checklist that only records problems is half a system. The point of inspection is repair, and Fast Maintenance closes that gap automatically: when an item is marked not-OK, it can spawn a corrective breakdown ticket against the same asset, carrying the finding straight into the repair workflow. Here is the loop, end to end:

This is what stops preventive maintenance from becoming a paperwork exercise. Without the loop, a fault spotted during PM lives on a sheet in a folder until it becomes a breakdown; with it, the inspection that found the problem is the same action that starts the fix. Read the companion guide on preventive vs breakdown maintenance for how the two work types balance.

Best practices for PM checklists

Good checklists share a handful of habits. Whether you are writing your first PM template or cleaning up a hundred, these are the rules that decide whether technicians actually engage with the list or rubber-stamp it.

• Be specific and measurable. "Check hydraulic pressure — accept 120–140 bar" beats "check hydraulics". A task you can pass or fail objectively removes judgement calls and makes the record defensible.
• Match depth to criticality. A critical CNC or DG set deserves a long checklist with measured values; a low-risk asset needs a short OK/not-OK list. Do not spend the same effort on everything.
• Attach a safety work permit. For lockout, hot work or work at height, the permit belongs on the job — Fast Maintenance attaches work permits and photo capture to the PM ticket so safety is part of the record, not a separate form.
• Get the length right. Size the list to the time available in the maintenance window. A 60-item monthly list that realistically takes two hours in a 40-minute slot guarantees skipped items and false ticks.
• Capture photos for condition. A photo of a worn belt or an oil leak is worth more than a remark, and it travels with the corrective ticket if the item is not-OK.
• Never write "check everything". A catch-all line is unmeasurable and unauditable. If it matters, make it its own task with a standard; if it does not, leave it off.

Ready-to-use checklist templates

Below are starter PM checklists for the assets most plants and facilities run. Treat them as a base — adjust the accept criteria to your make, model and OEM manual, then load them onto a schedule in Fast Maintenance so they reappear on every PM ticket that schedule generates.

CNC machine — monthly PM checklist

Air compressor — monthly PM checklist

DG set — monthly PM checklist

General electrical & mechanical — checklist

Note how the response column mixes OK/not-OK for pass-fail items and a measured value wherever a number can trend. Building your templates on a clean asset register means each checklist is tied to the exact machine it belongs to.

Frequency tiers — daily to quarterly

Not every task belongs on every visit. Split the checklist by frequency so quick daily checks stay quick and deep work happens only when it is due. A typical tiering looks like this:

Set each tier as its own schedule so Fast Maintenance generates the right ticket with the right checklist at the right cadence. The step-by-step method is covered in how to create a preventive maintenance schedule.

Common mistakes to avoid

Most failing PM programmes fail at the checklist, not the calendar. Four mistakes account for the majority:

• Vague tasks. "Inspect pump" gives no standard, so two technicians reach two conclusions and neither can be audited. Give every task an accept criterion.
• Tick-only, no values. Ticking "OK" on a reading that should be a number throws away the trend that would have warned you. Capture the value wherever one exists.
• Too long for the window. A checklist that cannot be finished in the available time is a checklist that gets false-ticked. Right-size or split by frequency.
• No owner or no loop. A not-OK item with nowhere to go dies on the sheet. Make sure failed items spawn a corrective ticket with an assignee.

How Fast Maintenance implements it

Fast Maintenance Software — built by Improsys in Pune on the shared Fast Suite platform, cloud or on-premise — turns every point above into working software. Mapping the checklist to the product:

Frequently asked questions