TemplateLast reviewed July 22, 2026

Preventive Maintenance Checklist Template

Download a preventive maintenance checklist template for recurring PMs, inspections, readings, findings, and CMMS handoff.

Preventive maintenance only works when the work is repeatable. A schedule tells the team when maintenance is due; the checklist tells the technician what to inspect, what to record, and when to escalate a finding into corrective work.

This template is built for maintenance teams moving from paper, whiteboards, or one-off spreadsheets into a more disciplined CMMS workflow. It is specific enough to be useful on real equipment, but generic enough to adapt for HVAC units, pumps, compressors, conveyors, fleet assets, and facilities equipment.

Free Preventive Maintenance Checklist Template (Excel)

Download the free Excel template here

The workbook includes three tabs:

  • PM Checklist for field execution, with asset details, task groups, pass/fail status, readings, notes, technician, completion date, and follow-up work order.
  • Task Library for reusable preventive maintenance tasks by equipment type and frequency.
  • Readings for expected limits, observed values, units, and corrective actions when a reading falls outside range.

Use the spreadsheet as a printable checklist, a Google Sheets starter file, or a staging document before importing tasks into your CMMS.

What to Put in a Preventive Maintenance Checklist

A good PM checklist should be short enough for technicians to complete consistently and structured enough to create useful history. Start with fields that identify the asset and the visit:

FieldWhy it matters
Asset ID / tagLinks the checklist to the asset record and maintenance history
LocationHelps technicians find the equipment and supports site-level reporting
PM frequencySeparates monthly, quarterly, seasonal, and annual tasks
Task groupGroups work into safety, visual inspection, lubrication, electrical, readings, and closeout
Pass/fail/NACreates a simple completion and exception record
Reading / valueCaptures temperatures, pressure, amps, vibration, runtime, or other measurable condition data
Follow-up work orderPrevents findings from getting buried in notes

The mistake to avoid is turning every checklist into a 70-line form. If a task does not change the technician’s work, support compliance, or improve the asset record, it probably does not belong in the standard PM template.

Example PM Checklist Sections

Most equipment-specific checklists can start from the same backbone:

  • Safety: lockout/tagout, PPE, stored energy, guards, access conditions.
  • Visual inspection: corrosion, leaks, mounts, wear, contamination, missing labels.
  • Operational checks: startup, shutdown, alarms, controls, sensors, abnormal noise.
  • Lubrication: grease points, oil level, leaks, interval, lubricant type.
  • Filters and consumables: clean/replace status, sizes, part numbers, next due date.
  • Electrical: terminals, disconnects, insulation, amperage, panel condition.
  • Performance readings: temperature, pressure, flow, vibration, runtime, cycle count.
  • Findings and actions: defects, parts needed, follow-up priority, customer or supervisor sign-off.

For safety-critical equipment, pair this checklist with a safety compliance checklist and require evidence such as photos, readings, or signatures before the PM can close.

How to Use the Template in a CMMS

If you already use a CMMS, treat the spreadsheet as a planning layer rather than the final system of record.

  1. List the asset classes you maintain most often.
  2. Copy the relevant rows from the Task Library tab.
  3. Remove tasks that do not apply to that equipment type.
  4. Add limits for measurable readings in the Readings tab.
  5. Import or manually recreate the final task list as a recurring PM template in your CMMS.
  6. Require follow-up work orders for failed checks so defects do not disappear into completed PM notes.

Teams without a CMMS can still use the workbook as a printable or shared spreadsheet. Just keep one completed copy per asset and PM date so you can reconstruct the maintenance history later.

Preventive Maintenance Checklist vs. PM Schedule

A preventive maintenance schedule answers when work should happen. The checklist answers what the technician should do during the visit.

You need both. A schedule without a checklist creates inconsistent execution. A checklist without a schedule relies on memory and usually turns into reactive maintenance again.

Frequently Asked Questions

What should a preventive maintenance checklist include?

Include asset identification, safety steps, inspection tasks, readings, pass/fail status, notes, technician name, completion date, and follow-up work order fields. Add equipment-specific tasks only when they affect reliability, compliance, safety, or maintenance history.

Can I use this checklist without CMMS software?

Yes. The Excel template works as a standalone checklist for small teams. A CMMS becomes more important once you need automatic scheduling, asset history, reminders, compliance reporting, and maintenance KPIs across many assets.

How often should PM checklist tasks be updated?

Review checklist tasks at least annually, and sooner after repeat failures, technician feedback, missed PMs, regulatory changes, or major equipment repairs. The best PM libraries evolve from field evidence rather than staying frozen after implementation.

Frequently asked questions

  1. What should a preventive maintenance checklist include?

    A useful preventive maintenance checklist should include asset ID, location, PM frequency, safety steps, inspection tasks, pass/fail fields, readings, notes, technician name, completion date, and any follow-up work order needed.

  2. Can this checklist be imported into a CMMS?

    Yes. The workbook is structured so teams can copy task rows into a CMMS task library or use the spreadsheet as a staging file before configuring recurring PM templates.

  3. How often should preventive maintenance checklists be reviewed?

    Review PM checklists after recurring failures, missed inspections, regulatory changes, major repairs, and at least annually so tasks still match the asset condition and operating environment.

Trust signal

Fact Checked & Editorial Guidelines

Every post on this site is fact-checked against the policy below before the "Last reviewed" date is updated. If a single item below fails verification, the post does not go live.

  • Every claim traces to a source.

    Pricing, feature lists, integrations, and headquarters are taken from vendor product pages, documentation, or signed contracts — never repeated from secondary blogs. Where a claim is sourced from a single vendor's marketing, it is qualified as such.

  • Vendor relationships are disclosed in-line.

    If a review covers a platform whose vendor has provided trial access, sandbox access, or paid placement on a sister property, that relationship is stated in the review's methodology footer — not buried in a sitewide disclosure page.

  • Pricing is rechecked at every review cycle.

    Vendor pricing changes constantly. The 'Last reviewed' date on each post is the date the price line was last re-verified against the vendor's public pricing page. If you spot a stale price, the contact page accepts corrections.

  • Corrections are logged, not silently rewritten.

    Material factual corrections after publication get a correction note dated and appended to the post. We don't pretend the prior version never said what it said.

Spotted an error? Send a correction via thecontact page — corrections are logged with a dated note on the post.

Trust signal

Editorial Review & Methodology

Reviews and comparisons on this site follow a single documented methodology — the same rubric, applied identically to every platform, on every review cycle.

  • Five-criteria scoring rubric, applied identically to every platform.

    Usability, pricing transparency, feature depth, support quality, and integrations. Each criterion scored 0–10 with documented weighting. The rubric is published on the methodology page and does not change between platforms in the same review.

  • Hands-on testing where vendor trial access permits.

    If a vendor offers trial or sandbox access, the reviewer spins up an account and works through the documented evaluation script before scoring. Where access is enterprise-gated, the access type is disclosed and scoring draws on product documentation, verified buyer reviews, and analyst sources.

  • Editorial independence from commercial relationships.

    No vendor pays for placement, previews scores, or controls the content of a review. Affiliate links, where present, do not change ranking — picks are ordered by score, not by commercial yield. If a conflict of interest exists for a specific review, it is disclosed within that review.

  • Reviews get re-checked, not just re-dated.

    Each 'Last reviewed' update means the rubric was re-applied — pricing, feature inventory, integration list, and any material vendor changes since the prior review. A bare date bump without re-evaluation is not a re-review.

The full rubric, weighting, and review-cycle process is on themethodology page.