The overdue count is the number a surveyor asks about first.
The first number a surveyor asks for
A Joint Commission survey gets announced, or a client hospital schedules its own internal audit, and the biomed team starts pulling binders. Somewhere in that first hour, someone asks the question that decides how the rest of the walkthrough goes: how many devices are past due for preventive maintenance right now, across every modality, at this site.
If the answer takes an afternoon of cross-referencing spreadsheets and paper stickers, that delay is itself a finding. A shop that cannot produce a current overdue count on request looks like a shop that does not know its own overdue count — whether or not the underlying work is actually current.
This article covers what "overdue" should mean for a PM, why the count is different for an independent service organization running many client hospitals than for a single in-house biomed department, and how to build a view of due, upcoming, and past-due equipment that survives being asked for cold. It closes with a worked example of computing a PM interval and a grace window from a manufacturer recommendation.
What "overdue" actually means for a PM
A device is not overdue the instant its interval ends. Most PM programs build in a grace window — a number of days past the due date during which the equipment is still considered within tolerance, provided the work gets scheduled. The trouble is that this grace window is a shop policy, not a regulatory number, and it has to be documented and applied consistently or it becomes indefensible.
Under 42 CFR 482.41, hospitals must maintain facilities, supplies, and equipment to ensure an acceptable level of safety and quality. CMS guidance (S&C 14-07) allows hospitals to follow manufacturer recommendations or a documented Alternate Equipment Maintenance (AEM) program instead, with the safety determination made by qualified personnel — though imaging and radiologic equipment, medical lasers, equipment with a maintenance interval set by law, and new equipment without sufficient maintenance history are excluded from AEM. Critical access hospitals fall under a parallel requirement at 42 CFR 485.623(b)(1).
None of that removes the need for a defined, written interval per device type. "Overdue" only means something once a shop has committed, in writing, to what "on time" looks like for that specific modality — and can show the same rule applied the same way across the fleet.
Documentation aid, not a compliance guarantee
Everything in this article, and the tooling it describes, is a documentation aid. It helps a shop track, schedule, and produce evidence of PM activity. It does not replace legal, regulatory, or accreditation judgment, and the buyer remains responsible for their own compliance decisions — including which AEM exclusions apply, what interval a given device requires, and how a specific surveyor or CMS reviewer interprets a specific record.
The scope is deliberately narrow: equipment service records only. No patient health information, no EHR or EMR integration, no device telemetry. This is a facilities and asset-maintenance tool, not a clinical system, and that boundary is part of what keeps the audit trail simple to defend.
Confirm current interval requirements, AEM exclusions, and survey expectations with CMS, the Joint Commission, AAMI, or applicable state law before relying on any single source — this one included.
Tracking overdue PMs when you serve ten hospitals, not one
An in-house biomed department has one overdue count to worry about. An independent service organization running PM and calibration work across a dozen client hospitals has a dozen overdue counts, each one belonging to a different facility with its own survey date, its own equipment mix, and its own binder expectations.
Spreadsheets and paper logs handle this badly, because "overdue" starts blending across clients. A technician roster shared across sites means one missed filter or a wrong due-date entry can quietly bury a past-due infusion pump inside a tab meant for a different hospital entirely.
The fix is structural, not just diligence: one technician roster, one dashboard, but a status view that filters cleanly by client. Each hospital gets its own due/upcoming/overdue breakdown, and each hospital's audit binder can be exported on demand without dragging another client's equipment into the same document. That is the core of a multi-client compliance workflow — a single system of record that still produces a clean, client-specific answer when a surveyor asks for one.
Building an overdue view that holds up on the walkthrough
A usable overdue tracking view needs three status buckets, not one: due soon, due today, and past due — with past due further split by how many days over the grace window each device sits. A flat "not done yet" list is not enough; a surveyor or an internal auditor will ask how long something has been overdue and why.
Each record in that view should carry a manufacturer-recommended or AEM-documented interval, a last-completed date, a computed next-due date, and the technician or vendor assigned. Anything without a documented interval assigned to it should surface as its own flag — a gap in the schedule is a different problem than a device that is simply late.
Sorting by client site, then by modality, then by days overdue turns a dashboard into a work list. It also turns the same dashboard into the first exhibit handed to a surveyor: a current, timestamped answer to "how many, and which ones."
A biomedical PM schedule template built around modality and manufacturer interval gives a shop a starting structure for this even before software enters the picture — the same fields (interval, last date, next date, grace window) apply whether they live in a spreadsheet or a dashboard.
A worked example: due date, grace window, and overdue flag
Say a manufacturer recommends a 6-month PM interval for a given infusion pump model, and the shop's documented policy allows a 14-day grace window past due date before a device is flagged overdue on a report (both are illustrative figures for this example, not a published standard — confirm the actual interval and any AEM adjustment with the manufacturer or a documented AEM determination).
- Last completed PM: March 1
- Interval: 6 months → next due date: September 1
- Grace window: 14 days → hard overdue flag: September 15
If today's date is September 20, that device is 5 days past the hard-overdue threshold and 19 days past the raw due date. A well-built tracking view reports both numbers — days past due date, and days past the grace window — because a surveyor may ask for either.
The same logic applies to electrical safety testing pass/fail thresholds, which are a separate but related check: NFPA 99 chassis and enclosure leakage-current limits are commonly cited at 300 µA for general care areas and 100 µA under normal conditions for critical care areas. A device that passes its PM but fails leakage testing is a different overdue category — a safety fail, not a schedule miss — and the two should never be merged into one status in a report.
Where this fits with the rest of the schedule
Overdue tracking is one piece of a larger PM and calibration scheduling discipline — the interval-setting, the technician assignment, the audit-binder export. A PM calibration scheduling software approach ties those pieces together instead of tracking them in separate documents. A biomedical PM schedule template is a reasonable starting point for a shop still on spreadsheets, and a multi-client compliance dashboard is the next step once one roster is serving more than one hospital.
The PM/Calibration Schedule Planner by Modality & Manufacturer Interval is available as a standalone, same-day-usable template for shops that want the structure now, without a software migration. For shops ready to see the dashboard version — due, upcoming, and overdue, filtered per client, exportable on demand — book a demo or check current pricing.
