The equipment PM log paperwork facility coordinators and fleet managers skip — and what a passing inspection reads

Two inspections, two months apart, same finding on the paperwork shelf. A facility coordinator at a 220-bed hospital couldn't produce eleven months of preventive-maintenance records on the rooftop chiller during a Joint Commission survey, and the surveyor marked it under EC.02.05.01 — the environment-of-care standard that lives or dies on whether PM records are filed. A fleet manager running nine excavators across a regional utility couldn't produce a stamped PM record on a CAT 305.5E2 that hit 4,318 hours on the meter, and the DOT-style inspection read the gap between 2,915 h and 4,318 h as a maintenance-program failure. Both wrote checks the day of the audit, signed the corrective-action plan the following week, and still hadn't built the log that would have prevented the finding. The paperwork gap on both audits was the same — a PM log book that was opened in January and stopped in March, then restarted the week the inspector's email landed.

Most preventive-maintenance paperwork on a facility or fleet job lives in three places: a spreadsheet on the maintenance supervisor's laptop, a clipboard in the boiler room that hasn't been opened in a month, and an email thread between a contract vendor and a coordinator who never sees the actual page. What an inspector reads on the day of the audit is none of those — it is the one-page log the equipment-bound tech has been signing since the unit was commissioned, with the date, the task, the hour-meter or run-time reading, and the next-due calendar date stamped on every row. The forms that close that gap are the same forms a working super already fills out — one page per asset, dated, signed, filed by serial number.

The hospital rooftop chiller and the EC.02.05.01 finding

A facility coordinator running a small plant operations team handles the PM records for the building systems — chiller, boilers, medical air, generator, fire pump — and most of those systems ask for monthly or quarterly PM work the way Joint Commission expects a hospital to perform it. The chiller PM is the one most coordinators skip: it runs twice a year, it takes half a day on the roof, and the contract vendor files a one-line invoice with a date on it. The log never opens. The surveyor reads the gap as a maintenance-program failure and writes it up, and the corrective-action plan takes 45 days to clear because no one can produce the records that would have closed the finding on the spot.

• EC.02.05.01 EP6: the facility identifies activities that maintain the environment of care — the PM tasks that get documented are the activities the surveyor asks about, not the contracts the vendor invoiced.
• Per-asset log: one row per PM event with the chiller serial number, the date, the hour-meter or run-time reading, the task performed (coil clean, refrigerant top-off, vibration check), the technician signature, and the next-due date stamped at the bottom.
• Vendor + in-house lines: contract vendor PMs go on the same log as the in-house filter changes and the quarterly readings — so the audit reads one continuous record per asset, not two parallel ones.
• Filed by serial, not by year: the surveyor reads the binder in serial-number order, not by calendar quarter — the file structure the coordinator builds before January saves the audit in May.

The fleet excavator and the DOT / CVIP-style hour-meter gap

A fleet manager running nine machines across a regional utility deploys an excavator, a mini-loader, and a skid-steer on a rotating job list, and the PM cadence for each is hour-meter-driven (every 250 h, every 500 h, every 1,000 h) — not calendar-driven. The DOT/CVIP-style inspection a fleet manager worries about is the one where the inspector opens the hour-meter log and reads straight through it. If a 305.5E2 shows 4,318 h on the meter and the last PM row is stamped at 2,915 h, the inspector flags the gap as a maintenance-program failure even if every service interval in between was performed — because none of it was written down. The machine gets pulled, the operator loses a shift, and the corrective-action plan the fleet manager writes is the same log the tech should have been filling every 50 hours.

• Hour-meter reading + serial number: every row carries the unit serial on the left and the current hour-meter on the right, so a 50-hour pre-trip and a 500-hour service both land on the same stamped log page.
• Service-tier line: a 250-hour fluid check on the same row that carries a 500-hour filter swap — flagged by service tier, not by calendar date, so the inspector reads the cadence a mechanic actually runs.
• Tech + sign-off: the technician's signature at the row, the supervisor's signature at the page, both dated — two signatures per PM event is the audit standard a fleet manager writes against, not the one-signature convention a small operator runs with.
• Out-of-service stamp: when a unit is pulled from the fleet, the date + reason live on a dedicated row at the bottom of the log — so the corrective-action plan the fleet manager files after the inspection reads the gap, not guesses at it.

What a passing PM log contains, regardless of the asset

Across a hospital plant operations shop and a regional fleet yard, the audit-standard PM log reads the same five blocks on every page. An inspector who opens the binder can walk it row by row without asking the maintenance supervisor for context. The five blocks — asset ID, date, task, signature, next-due — are the same blocks a working foreman already writes on a daily-log page, lifted into a single per-asset binder.

• Asset + serial: the unit identifier the inspector reads first — chiller CHL-01, excavator EXC-04 — written once at the top of the page and carried forward every row.
• Date + hour-meter / run-time: the calendar stamp on the left, the meter on the right — so the cadence reads hour-meter-driven for fleet, calendar-driven for facility, on the same line.
• Task performed: a one-line description in the language the tech writes it, not the language the vendor invoices it — "Coil clean + refrigerant top-off" beats "Quarterly PM service" because the inspector reads the scope.
• Tech signature + supervisor initials: two signature lines per row, both dated — the dual sign-off a vendor-side + in-house PM event both run through, so the binder carries one continuous record per asset.
• Next-due date stamped: the calendar date the next PM is owed, written at the bottom of every row — so the maintenance supervisor sees the upcoming call-out without re-opening the spreadsheet.

How to set one up that actually stays filled

A PM log that stays filled is a PM log the tech or mechanic signs on the day the work is performed — not the binder the maintenance supervisor opens in the office on a Friday afternoon. The habit that closes the audit gap is the same one that closes the daily-log gap: the form lives at the asset (a clipboard on the chiller skid, a binder in the excavator cab), not at the desk. The facility coordinator files the page at the next Monday walk-through. The fleet manager signs the row at the next shop visit. Neither waits for the inspector's email to start the log — the next-due stamp on the bottom of the previous row is the reminder.

• One binder per asset: a half-inch binder per chiller, per excavator, per generator — the page count a tech actually walks to, not the master spreadsheet that lives on the supervisor's laptop.
• Daily-log tie-in: a working super signs the per-asset PM row on the same shift the daily log records the activity — two entries, one event, both stamped the same morning.
• Monthly review: the maintenance supervisor pulls every binder at the same time once a month, scans the next-due column, schedules the next 30 days — and files any vendor PM that landed outside the binder.
• Vendor + in-house in one column: the contract vendor's PM lines ride on the same log page as the in-house filter changes — so the binder reads one continuous record a surveyor or DOT inspector can walk without flipping between two systems.

A maintenance program without a per-asset log is a maintenance program the inspector gets to write for you. The chiller PM and the excavator PM both ship in the same five-block page — and the five-block page lives at the asset, not at the desk.

— Gridpin founder · 20 years on a clipboard

The kit that holds the PM log

WL-01 (Daily Job Site Log) carries the one-page-per-shift PM record a facility coordinator files by serial number — asset ID, date, task, tech signature, next-due stamp on every row, with the field-language a working maintenance tech writes. For a fleet manager running multiple machines, a facility ops team running a hospital plant, or a working super maintaining equipment across both worlds: the Construction Superintendent Bundle (CSB-01) carries twenty-five working-super forms in one kit, including the daily log (WL-01), the pre-trip equipment check (EQ-04), the per-asset maintenance pages, and a year-long commercial-use license covering every asset the team maintains.