A preventive maintenance report is almost always read by somebody who is not in maintenance and has about two minutes. That constraint should shape the whole document, and usually does not: most reports are exports of everything the system can produce, which guarantees that nothing in them gets acted on. Three numbers and one list is closer to the right size.
The three numbers worth reporting
How much of the planned work got done on time. How much of the total work was planned rather than reactive. And what is outstanding that matters, expressed as a count and a consequence rather than a list. Those three answer the only questions a reader outside maintenance actually has: are we on top of it, is it getting better, and is anything about to hurt. Everything else the maintenance dashboard can produce is context for the team rather than content for the report.
The list that earns its place
One list belongs in the report: the things that will need money or a decision in the next period. Each entry with what it costs, what happens if it waits, and when it stops being optional. That list is the reason a report is read at all, because it is the only part the reader can act on. Assembling it is genuinely work, which is why reports padded with maintenance data tend to omit it, and why omitting it makes the rest pointless.
Costing and goals, without inventing numbers
A preventive maintenance cost calculation that sums labour hours and parts against a schedule is straightforward and worth having. Comparing it to avoided failure cost is not, because the avoided failures are hypothetical and any figure you produce is an argument rather than a measurement. Say so. For maintenance goals examples, the ones that survive scrutiny are behavioural and controllable: raise schedule compliance, reduce the reactive share, close the backlog of a named category. Goals expressed as reduced downtime depend on too much the maintenance team does not control.
Questions people ask about preventive maintenance report
What belongs in a preventive maintenance report?
Schedule compliance, the planned versus reactive split, what is outstanding that matters, and one list of things needing money or a decision next period, with consequences and timing.
How do you calculate preventive maintenance cost?
Sum labour hours and parts against the schedule, which is straightforward. Comparing that to avoided failure cost produces an argument rather than a measurement, and should be presented as one.
What makes a good maintenance goal?
Something the team controls: schedule compliance, the reactive share, closing a named backlog. Goals stated as reduced downtime depend on far too much that maintenance does not decide.