The gap between a task being done and a task being provable — that’s what an audit actually tests.
The Panel the Auditor Opened First
The auditor didn’t ask for a tour. He walked straight to the main switchgear room of a manufacturing campus in Singapore, opened the nearest panel, and asked for the last thermographic inspection date and the maintenance record behind it. The team had serviced that panel — recently, competently, by people who knew what they were doing. What they didn’t have was a document that proved it on demand.
That gap between “the work got done” and “the work is provable” is where most electrical maintenance programmes fail an NFPA 70B-aligned audit. It isn’t a maintenance problem. It’s a documentation architecture problem, and it shows up the moment someone outside the team asks a specific question about a specific asset.
The auditor didn’t move on after the first panel. He opened three more, at random, across two different buildings on the campus. Each one required the same scramble — a phone call to a technician, a search through a shared drive, a best guess at when a task had last been completed. None of it suggested the maintenance wasn’t happening. All of it suggested the programme had no architecture behind it.
By the end of the visit, the audit report listed nine open findings — not because nine pieces of equipment were unsafe, but because nine pieces of equipment had no documented evidence proving otherwise. That distinction rarely lands with leadership until the findings are already on paper.
Why It Happens
Most facilities run preventive maintenance from memory, runtime hours, or a maintenance team’s own informal rhythm rather than a documented, asset-categorised schedule. The equipment does get maintained — often well — but there’s no audit trail proving the interval, the method, or the sign-off. Since the standard shifted from voluntary guidance to a mandatory maintenance requirement, that gap has moved from a minor finding to a real compliance exposure.
The structural issue is that PM gets tracked at the level of the individual technician’s notebook or memory, not at the level of the system. A schedule that lives in one person’s head doesn’t survive that person’s absence, let alone an auditor’s cold-open question about a specific panel.
There’s also a subtler failure at play: teams that do keep records often keep them as a running log of completed work rather than a forward-looking schedule with defined intervals. A log tells you what happened. It doesn’t tell an auditor — or the team itself — what should happen next, on what date, and what the consequence is if that date slips.
What Good Looks Like
A PM schedule that survives an audit — not just maintains equipment — has a specific structure:
- A 12-month schedule organised by asset category, not by technician or by memory
- Intervals tied explicitly to a standard or manufacturer recommendation, documented as the basis for the frequency chosen
- Completion sign-off fields for every task, every cycle — not a retrospective summary built after the fact
- An automatic escalation trigger when an interval is missed, rather than a silent gap
- A single source of truth an auditor can open cold and find the answer in under a minute
None of this requires new maintenance activity — most facilities are already doing the physical work. What it requires is restructuring how that work gets recorded, so the record exists independently of whoever performed the task and whenever they happen to be reachable.
Real FM Example
On a manufacturing campus in Singapore running electrical distribution and process equipment across multiple production lines, we built a categorised 12-month PM calendar covering switchgear, motor control centres, and transformers, with documented thermographic and physical inspection intervals tied directly to the applicable standard.
The next audit cycle told the story: open electrical PM compliance findings dropped from nine at the first audit to one at the next, and the time spent preparing for inspection — pulling records, reconstructing history, chasing sign-offs — dropped from roughly three days to under two hours.
The team’s actual maintenance work barely changed. What changed was that every task now had a defined interval, a documented basis for that interval, and a sign-off field that made completion provable rather than assumed. The auditor’s second visit took forty minutes. The first had taken most of a day.
Equally important, the team stopped dreading audits. A programme that can prove itself on demand removes the anxiety of not knowing what an auditor might ask next — and that confidence is worth almost as much operationally as the compliance record itself.
One overdue interval, flagged immediately — not discovered three days into audit prep.
| In 20+ years of FM operations across Asia-Pacific and Europe, I have seen preventive maintenance programmes that were technically being performed fail every audit anyway — because the work existed and the record didn’t. A PM schedule only counts if it can prove itself cold, without a technician’s memory in the room. |
What It Covers
The Preventive Maintenance Calendar in the FM Operations Playbook Pack is built around auditability, not just scheduling. It includes:
- A 12-month PM framework organised by asset category and criticality
- Monthly, quarterly, and annual task cadence structured by asset type
- A completion and sign-off log for every scheduled task
- A missed-PM escalation trigger so gaps surface immediately, not at the next audit
- A cross-reference structure linking scheduled PM to work order follow-up
Get the Calendar
The Preventive Maintenance Calendar ships as part of the FM Operations Playbook Pack — Starter Tier ($29), alongside the Vendor Onboarding Checklist and Cost Variance Tracker, as ready-to-use Word and Excel templates plus an AI Prompts Reference guide.
→ Get the FM Operations Playbook Pack — Starter Tier at the BizzXpert Store