Preventive maintenance report: Word template and example

A preventive maintenance report records what happened during a planned maintenance visit: the asset, referenced maintenance plan, checks completed, observed condition, exceptions and next actions. It complements the schedule by showing what was actually done. This guide includes a free editable Word template and a completed fictional example.

Preventive maintenance report, schedule or checklist?

The report should refer to the applicable maintenance plan rather than inventing an interval or a procedure. IBM's preventive maintenance overview provides background on planned maintenance. This template is for documenting a visit; technical checks and acceptance criteria come from your equipment documentation and approved procedures.

What to include in the visit report

Identify the asset, visit and plan version. For each planned item, record whether it was completed, not completed or not applicable, and explain exceptions. Keep an observed condition separate from a proposed remedy.

Use “not measured” when a reading was not taken. Use “not checked” when an inspection did not occur. “Not applicable” needs a reason linked to the task or asset; it should not quietly replace a missed check.

Copyable preventive maintenance report template

JOB — Visit reference, date, technician and site
ASSET — Description, asset identifier and location
PLAN — Maintenance plan or checklist reference and version
PLANNED WORK — Tasks assigned for this visit
COMPLETED WORK — Task reference, operation performed and observed result
OBSERVATIONS — Condition or measurements actually recorded, with context
EXCEPTIONS — Tasks not completed or not applicable, with reasons
MATERIALS — Parts or consumables used; requested items listed separately
FINAL STATE — Observed condition after the visit and unresolved limitations
FOLLOW-UP — Action, owner, dependency and agreed date or “to be confirmed”
NEXT VISIT — Date from the maintenance plan or scheduling decision still pending
REVIEW — Reviewer and the organization's approval process

Repeat the completed-work and exception fields for every relevant task. A report may document a completed visit with an open exception; keep those two states visible.

Completed example: a planned pump visit with an open exception

This example is fictional. The plan reference and observations illustrate reporting, not a maintenance procedure, an acceptance threshold or a Notefield customer result.

JOB — PM-208, 4 November 2026, technician Jules, north plant room
ASSET — Pump P12
PLAN — Internal maintenance checklist PM-P12, revision B
PLANNED WORK — Checklist items assigned for this visit: filter service and external seal inspection
COMPLETED WORK — Filter cleaned; flow observed during the on-site functional check; no numerical flow measurement recorded
OBSERVATIONS — Leak still visible at the seal during the check
EXCEPTIONS — Seal replacement not part of this planned visit; corrective work requires a separate decision
MATERIALS — No replacement seal used; required part reference not yet confirmed
FINAL STATE — Flow observed during the check; seal leak remains open
FOLLOW-UP — Jules confirms the seal reference with the maintenance lead on 5 November; the lead decides the corrective work and scheduling
NEXT VISIT — Date to be confirmed against the maintenance plan

The report records completed work and an unresolved finding without claiming that the asset passed every check. It also separates a part to identify from a part already ordered.

Dictate the visit, then review each exception

Finish your spoken recap with missed tasks and dependencies. Those details are easy to omit when the routine work has been completed.

For the example: “PM-208, pump P12, checklist revision B. Filter cleaned. Flow seen during the test; no flow reading taken. Seal still leaks. Seal not replaced and reference not confirmed. Jules checks the reference with the lead on 5 November. Corrective work and next visit still to schedule.”

This is an illustrative structure, not a live product test result. Notefield for field service shows how a spoken recap can organize findings and next actions. Try it with a maintenance debrief, then check asset identifiers, units, negative statements and every unresolved item before sharing.

Link findings to corrective work

An exception may need a separate work order. Record the new job reference when it exists and keep the original preventive report attached to the asset history. If access, a part or approval blocks the action, name that dependency.

Use the maintenance service report to document the later intervention. The field action tracking guide helps keep an owner and a completion check attached to the open finding.

Review before sharing

• Check the asset and maintenance plan references against the source records.
• Verify that completed tasks match the operations actually performed.
• Leave missing readings and skipped checks explicit.
• Separate an observed defect from its hypothesized cause.
• Confirm owners and dates rather than assigning them from context.
• Keep approval fields for the people authorized to complete them.

The voice note to report method provides a reusable drafting prompt that keeps missing information visible.

Practical questions

Can this report replace the maintenance checklist?

It can summarize the visit and reference the completed checklist. It does not define the checks, intervals or acceptance criteria for your equipment.

What if part of the planned work was not completed?

List the task, reason and action needed to resume it. Distinguish “visit ended” from “all planned tasks completed.” Leave the responsible person's review of consequences explicit.

Can I combine several assets in one report?

Yes, if every finding, task and follow-up retains its asset identifier. Separate reports may be easier when assets have different plans, owners or open issues.