The Plant Manager's Monthly Fleet Review: Compliance and Cost in One Deck

The Spreadsheet That Arrives Three Days Late

The monthly operations review is on the calendar. You need maintenance cost and PM compliance numbers by Thursday morning. So on Tuesday you ask your maintenance manager to pull the data from the tracking sheet, and by Wednesday afternoon you have a workbook with seventeen tabs, two of them broken formulas, and a "last PM" column that hasn't been touched since the third week of last month.

You spend twenty minutes turning it into something you can show in a meeting. The numbers feel approximately right. Nobody pushes back, so you move on.

That cycle — request, wait, reformat, approximate, present — repeats every month. It consumes time that neither you nor your maintenance manager has, and it produces a report that is already stale by the time it reaches the room.

This guide describes a repeatable monthly fleet review structure built on two numbers that actually drive decisions: PM compliance percentage (how much of the scheduled work got done) and projected annual maintenance cost (what the fleet will cost this year if current patterns hold). By the end, you'll have a meeting agenda, a metric set, and a clear sense of when a calculation and cost tool earns its keep versus when a spreadsheet still does the job.

---

What the Monthly Fleet Review Is Actually For

A plant manager fleet review has one job: give the leadership team enough signal to make a resource decision before a problem becomes a cost event.

That means the review is not a maintenance debrief. Your maintenance manager handles the work-order level detail. What you need at the fleet level is:

1. Which assets are overdue for PM — and by how much.
2. What the fleet is projected to cost this year — and whether that number is moving toward the budget or away from it.
3. Whether any single asset is carrying disproportionate cost — the one piece of equipment that is quietly becoming your most expensive.

Everything else — parts lead times, vendor performance, individual technician utilization — is useful context, but it belongs in a separate operational conversation, not in the thirty-minute slot you have with your operations director.

The two metrics that answer those three questions cleanly are PM compliance and maintenance cost as a percentage of replacement asset value (MC/RAV).

---

The Two Numbers That Run the Room

PM Compliance Percentage

PM compliance is the share of scheduled PM tasks completed on time within a defined window (typically within the scheduled interval ± a tolerance you set, often ±10%–15% of the interval).

PM Compliance % = (PM tasks completed on time ÷ PM tasks scheduled) × 100

A fleet running 100 assets with 200 PM tasks scheduled in a month that completes 170 of them on time posts an 85% compliance rate. Whether 85% is acceptable depends on your equipment criticality mix — a 90%+ rate is a reasonable target for high-criticality assets; lower-criticality assets may tolerate a wider band.

The number is useful in a review meeting precisely because it is directional and comparable month-over-month. A compliance rate that drops from 88% to 71% in a single month is a story — usually one of technician capacity, a parts delay, or an interval that was set too aggressively for the current maintenance team. A compliance rate that has been stuck at 65% for six months is a different story: the schedule is probably overstuffed or the intervals need recalibration.

For a practical look at how PM compliance connects to documentation and audit requirements, see PM compliance tracking for OSHA.

Maintenance Cost as % of Asset Value (MC/RAV)

MC/RAV is the standard fleet-level cost benchmark used in reliability and asset-management practice.

MC/RAV = (Annual maintenance cost ÷ Replacement asset value) × 100

Industry benchmarks, per Tractian (2026) and SMRP via Fiix (2022), put world-class performance at 2%–3% of RAV, with a typical target range of 3%–4% and a warning threshold above 5%. A figure around 2% of RAV is associated with world-class maintenance operations (Ginder, "Maintenance as a Corporate Strategy," via ReliaMag, 2026).

In a meeting, MC/RAV turns an abstract cost discussion into a ratio your CFO can evaluate the same way they evaluate any other operating ratio. If your fleet replacement value is $4,000,000 and your projected annual maintenance cost is $220,000, your MC/RAV is 5.5% — above the warning threshold, worth a conversation about whether reactive work is crowding out planned PM.

Worked example (illustrative):

Input	Value
Fleet replacement asset value	$4,000,000 (illustrative)
Projected annual maintenance cost	$220,000 (illustrative)
MC/RAV	($220,000 ÷ $4,000,000) × 100 = 5.5%
World-class band (Tractian, 2026)	2%–3%
Typical target (Tractian, 2026)	3%–4%

At 5.5%, you are spending roughly $100,000–$140,000 per year more than a world-class comparator (2%–3% of RAV) running the same asset base. The meeting question is: how much of that gap is unplanned reactive work that a tighter PM program could prevent?

For a fuller walkthrough of building the fleet cost rollup that feeds this ratio, see fleet-level maintenance cost rollup.

---

A Thirty-Minute Agenda That Uses Both Numbers

Here is a repeatable structure for a monthly plant manager fleet review. The goal is to cover both metrics, surface the decisions that need escalation, and close in under thirty minutes.

Slide 1 — Fleet health snapshot (5 minutes)

• PM compliance % this month vs. last month vs. three-month trend
• Number of assets overdue (and by how many days/hours/cycles)
• Traffic-light status by asset criticality tier (red = overdue beyond tolerance; amber = due within the next two weeks; green = current)

Slide 2 — Cost position (5 minutes)

• Projected annual maintenance cost vs. budget
• MC/RAV vs. the 3%–4% benchmark
• Month-over-month cost movement — is the projection rising or stable?

Slide 3 — Asset spotlight (10 minutes)

• The two or three assets with the highest cost-per-PM or longest overdue window get thirty seconds of airtime each
• For each: what is the next PM, what does it cost, and is there a capacity or parts constraint blocking it?

Slide 4 — Decisions and actions (10 minutes)

• Any PM interval that needs to be adjusted based on the last quarter's history
• Any asset approaching the point where repair cost per cycle exceeds replacement logic
• Budget variance items that need to go to the finance conversation

The maintenance manager runs slides 3 and 4. You run slides 1 and 2. The report package should be ready before the meeting, not assembled during it.

For a ground-level view of how a maintenance manager structures the upstream work that feeds this review, see the maintenance manager Monday morning workflow.

---

Why This Review Breaks Down in Practice

Most plant manager fleet reviews fail for one of three reasons.

The data is pulled manually every month. When the compliance number and cost projection have to be extracted, reformatted, and hand-calculated from a spreadsheet before each meeting, the review is only as current as whoever pulled it — and only as accurate as the formulas that have survived a year of copy-paste edits. Past roughly ten tracked assets, a spreadsheet stops being a fleet tool and starts being a liability.

The compliance metric and the cost metric live in different places. Compliance tracking lives in one spreadsheet; cost tracking lives in a budget sheet or an accounting export. Neither talks to the other, so the plant manager has to mentally reconcile two datasets that were built by different people using different date assumptions. The reconciliation eats the meeting.

There is no persistent calculation. A one-time PM interval estimate — whether from a free calculator page or a back-of-envelope OEM recommendation — does not update when an asset's last service date changes. A fleet review needs numbers that recalculate continuously as maintenance happens and time passes. That is the structural gap between a one-time calculation and a persistent, multi-asset planning engine.

Operations managers facing a version of the same visibility problem will recognize the pattern described in operations manager maintenance cost visibility.

---

What "One Deck" Actually Requires

Getting compliance and cost into one clean report, ready before the meeting, requires three things from your maintenance tooling:

1. A persistent asset registry with each asset's PM interval (in days, hours, or cycles), last PM date, and status indicator — so due dates recalculate automatically as time passes.
2. A per-asset cost estimate built from labor hours × labor rate + parts — rolled up to a fleet total and projected forward to an annual figure.
3. A PM compliance summary that counts scheduled vs. completed tasks across the fleet and presents the ratio without manual calculation.

These are planning and cost-forecasting functions. They do not require a full CMMS — the work-order execution layer, parts inventory management, and vendor workflow features that are standard in a per-seat CMMS add cost and complexity a planning-focused review doesn't need. But they also exceed what a spreadsheet and a one-time calculator can sustain reliably past a small number of assets.

The Maintenance Cost and Interval Planner is built specifically for this gap: a flat-rate, pre-CMMS tool that maintains the asset registry, calculates PM intervals and next-due dates, projects annual maintenance cost per asset and for the fleet, and generates the MC/RAV ratio with benchmark comparison — on Professional and higher tiers — as a shareable report your maintenance manager can hand you before the meeting without reformatting anything. You can review full feature details at /features.

For a broader grounding in how PM intervals and cost projections are built from first principles, the preventive maintenance interval and cost guide covers the underlying method.

---

A Practical Starting Point Before the Next Review

If you are running the fleet review on spreadsheets today, the fastest improvement before next month is to standardize two columns in whatever tracking sheet you have: last PM date and PM interval in days. From those two fields, you can calculate next-due date (=last PM date + interval), days overdue (=TODAY() - next due date, floored at zero), and compliance for any asset with a recorded history.

That gets you a functional compliance snapshot without new tooling. The cost projection — labor hours × rate + parts, annualized — takes a separate sheet and a consistent labor rate. If your maintenance manager has not settled on a rate, the BLS Occupational Employment and Wage Statistics survey (May 2024) reports a median of $23.38/hr for general maintenance and repair workers (SOC 49-9071) — a reasonable starting anchor, though the right rate for your facility depends on your actual wage structure and should be entered at the value your operation uses.

When those two spreadsheets stop fitting together cleanly — typically around ten to fifteen assets or when the monthly reformatting takes more than an hour — that is the signal that a persistent calculation engine earns its cost.

---

The Deck That Runs Itself

A monthly plant manager fleet review does not need to be a production. It needs two numbers — PM compliance percentage and projected maintenance cost against RAV — presented in a format that does not require your maintenance manager to spend half a day preparing it.

The structure is straightforward. The metrics are well-defined. The gap is usually the tool: a spreadsheet that was never designed to recalculate a fleet continuously, paired with a one-time interval estimate that goes stale the moment it is made.

If you want to see how the compliance and cost numbers look when they are calculated persistently across a real asset list, the Maintenance Cost and Interval Planner offers a 14-day free trial — no credit card required at signup. You can import your asset list, set intervals and cost inputs, and have the fleet report ready for your next review before the trial ends.

For an immediate, lower-commitment starting point, the PM Compliance Checklist Pack gives you a documented, per-asset compliance framework you can run alongside your existing spreadsheet while you evaluate whether a persistent tool is the right next step.

Either way, the goal is the same: compliance and cost in one deck, ready before the meeting — not assembled during it.