The Documentation Test

The Documentation Package
Surveyors Request

When a CMS surveyor or Joint Commission surveyor enters your facility to review emergency power compliance, they follow a structured protocol. The documentation request is not random — it follows the State Operations Manual survey procedure for 42 CFR §482.41 (Physical Environment) and the applicable Joint Commission EPs under EC.02.05.01. Here is what they ask for, in the order they typically ask for it:

The 60-Second Rule

Here is a practical benchmark we use with every facility we assess: can you produce the complete emergency power documentation package within 60 seconds of a surveyor requesting it? Not 60 minutes. Not "let me call the maintenance director." Sixty seconds.

Facilities that can produce organized, complete documentation quickly send a clear signal to surveyors: this facility takes emergency power compliance seriously. Facilities that scramble — pulling records from multiple locations, searching for load bank test reports, trying to reconstruct missing months — send the opposite signal. The surveyor's scrutiny level adjusts accordingly.

Testing Log Requirements vs
What Facilities Actually Keep

There is a consistent gap between what NFPA 110 requires in a testing log and what facilities actually record. Most facilities document that a test occurred. NFPA 110 requires documentation of what happened during the test — quantitative performance data, not just a checkbox.

The Checkbox Problem

The root cause of inadequate testing logs is the "checkbox" approach to generator testing. Facilities create a simple form with checkboxes — "Generator started: Y/N," "Generator ran for 30 min: Y/N," "Transfer occurred: Y/N" — and call it a test log. This approach captures whether a test happened but not what the test revealed.

A proper test log is a performance record. It captures quantitative data that can be trended over time to identify degradation before it causes a failure. When a surveyor reviews your test logs, they are not just checking for completeness — they are looking for evidence of a systematic testing program that uses data to maintain equipment reliability.

Building a Compliant Test Log

Your monthly test log should capture, at minimum, the following data points for every test event:

• Test date and time: Start time, stop time, total duration. The duration must meet the minimum for your EPSS level (30 minutes for Level 1).
• Load data: Actual kW output during the test and the percentage of nameplate rating this represents. This is the data point that determines whether your annual load bank test requirement is triggered.
• Electrical readings: Voltage (all phases) and frequency at generator output terminals. Note whether readings are within the acceptable range (±10% voltage, ±0.5 Hz frequency from nameplate).
• Transfer time: Measured elapsed time from utility loss simulation to load pickup on emergency power. Record for each ATS tested.
• Engine parameters: Oil pressure, coolant temperature, battery voltage (at start and during operation). These are manufacturer-specified monitoring points that demonstrate the engine operated within normal parameters.
• Fuel level: Before and after test. This validates fuel consumption rates and confirms adequate fuel supply for rated run time.
• Anomalies: Any unusual conditions observed — exhaust smoke, vibration, fluid leaks, unusual sounds, slow cranking, voltage fluctuation. "None" is an acceptable entry, but the field must be present.
• Operator identification: Name or ID of the person who conducted and documented the test.

Written Maintenance Program
The Requirement Most Facilities Miss

NFPA 110 Section 8.1.1 requires a written routine maintenance and operational testing program for the EPSS. This is not the same as having a testing schedule. This is not the same as having maintenance records. This is a separate, standalone document that describes the complete maintenance and testing framework for your emergency power system.

In our experience, this is the single most overlooked NFPA 110 requirement. Approximately 70% of the facilities we assess do not have a written maintenance program — even facilities that have excellent testing records and well-maintained equipment. They do the work but do not have a document that describes what the work is supposed to be.

What a Written Maintenance Program Looks Like

A compliant written maintenance program is typically a 5-15 page document that covers every component of the EPSS and every routine activity required by NFPA 110, the manufacturer, and your facility's specific operational requirements. It should be formatted as a policy document — signed, dated, reviewed annually, and updated whenever equipment or procedures change.

The program should include:

• Equipment inventory: Generator make/model/serial, nameplate kW rating, fuel type, ATS make/model, battery type and replacement schedule, fuel tank capacity and day tank configuration.
• Testing schedule matrix: A table showing every test and maintenance activity, its frequency (weekly/monthly/annual/per event), the procedure reference, and the responsible party.
• Acceptance criteria: For each test type, define what "pass" and "fail" look like. For monthly tests: minimum load percentage, acceptable voltage range, acceptable frequency range, maximum transfer time. For annual load bank: load levels, duration per level, performance thresholds.
• Corrective action procedures: The process for documenting, prioritizing, assigning, and resolving deficiencies found during testing. Include escalation criteria for critical deficiencies (e.g., ATS failure = immediate work order).
• Record retention policy: Testing records retained for 36 months minimum. Where records are stored. Who has access. Backup/archive procedures.

Deficiency Tracking: The Third Leg of the Compliance Stool

Testing records prove you test. The written program proves you have a system. Deficiency tracking proves you act on what your testing reveals. This third element — the corrective action and deficiency tracking process — is where the strongest facilities separate themselves from the rest, and where many otherwise-compliant facilities accumulate findings.

Every generator test, every ATS exercise, every load bank event can reveal anomalies. A voltage reading 2% lower than last month. A transfer time 0.3 seconds slower. An oil pressure reading at the low end of the acceptable range. A coolant temperature that spiked briefly during full load. None of these may constitute an immediate failure — but each one represents a data point that demands documentation and, in some cases, investigation.

The surveyor's question is simple: "When your testing revealed [this anomaly], what did you do about it?" The acceptable answers are: we investigated, determined the root cause, implemented a corrective action, and verified the corrective action resolved the issue. Or: we investigated, determined the reading was within acceptable parameters and no corrective action was required, and documented our analysis. The unacceptable answers are: we did not notice it. Or: we noticed it but did not document any follow-up. Or: we wrote "will monitor" and then never monitored it.

"Will monitor" is the most dangerous phrase in compliance documentation. It acknowledges awareness of a potential issue, commits to future observation, and then — in the vast majority of facilities — creates no structured follow-up mechanism. Three months later, the surveyor finds the "will monitor" note and asks for the monitoring data. There is none. Now you have a finding that combines awareness of a potential problem with documented inaction. That is worse than never having noticed the anomaly in the first place.

Digital vs Paper Records: What Surveyors Prefer

There is no NFPA 110 requirement specifying digital or paper records — both are acceptable. However, the practical reality of a survey favors whatever system allows you to retrieve records fastest and demonstrate completeness most clearly. Some considerations:

Paper-based systems work well when they are organized, complete, and maintained by someone who takes ownership of the filing system. The advantage of paper is that surveyors can physically flip through a binder and see 36 months of records in sequence. The disadvantage is that paper records are vulnerable to loss, misfiling, water damage, and the departure of the one person who understood the filing system. If you use paper, maintain a backup — photocopies or scans stored separately.

Digital systems (CMMS, BAS-integrated logging, or even well-organized spreadsheets) offer searchability, backup, and trending capabilities that paper cannot match. The best digital systems auto-populate date/time stamps, flag overdue tests, and generate trend reports that demonstrate systematic compliance over time. The disadvantage is that digital records require a computer or tablet for the surveyor to review, and some surveyors prefer to work from printed documents. If you use a digital system, be prepared to print 36 months of records on request — and test that your printing workflow actually works before you need it.

The hybrid approach — digital records as the primary system with periodic printed summaries filed in a physical compliance binder — provides the best of both worlds. The digital system handles data entry, trending, and alerting. The physical binder provides immediate survey access without technology dependencies. Many of the facilities with the strongest compliance programs we assess use this approach.

The Pre-Survey Self-Audit: A 2-Hour Investment That Prevents Findings

The most effective survey preparation activity is a structured self-audit of your emergency power documentation. This is not a full facility assessment — it is a focused documentation review that takes approximately 2 hours and catches the majority of documentation deficiencies before a surveyor finds them.

Here is the self-audit protocol we recommend conducting quarterly:

• Completeness check (30 minutes): Pull your testing records for the past 12 months. Verify you have a record for every month — no gaps. Check that each record is signed, dated, and contains all required fields. Flag any incomplete records for immediate correction.
• Field validation (30 minutes): Select 3 monthly test records at random. For each, verify that the data makes sense: load percentage is consistent with your known connected load, voltage and frequency readings are within normal ranges, transfer times are within the 10-second window. Flag any anomalous readings and verify they have documented follow-up.
• Written program review (30 minutes): Open your written maintenance program. Verify the review date is within the past 12 months. Compare the stated testing frequencies to your actual testing records — are you doing what the program says you should be doing? Verify responsible parties listed in the program are still accurate (personnel changes are a common source of program drift).
• Deficiency tracking review (30 minutes): Pull your deficiency log. Verify every open item has a documented remediation plan with a target date. Verify every closed item has documented resolution and verification. Check for any "will monitor" entries that lack a structured monitoring plan. Flag any items open longer than 90 days for escalation review.

This quarterly self-audit takes 2 hours and catches 80-90% of the documentation deficiencies that surveyors find. It is the single highest-return compliance investment a facility can make — zero cost, minimal time, and it converts reactive survey prep into a proactive compliance program.