Skip to content
All articles

31 min read

Automatic Transfer Switch Testing in SNFs: Frequency, Documentation, and the K-Tag Risk of Missing a Log

Automatic transfer switch testing is a required life safety task in SNFs. Learn the NFPA frequency, what CMS expects in the log, and how one missed entry triggers a K-tag.

By Benjamin Terebelo

The generator test passed. The log says so. But when the state surveyor pulls the automatic transfer switch binder during an unannounced visit, she finds something the maintenance director didn't notice: three consecutive monthly entries with no transfer time recorded, one entry with no load reading, and a six-week gap between two tests that should have been four weeks apart. The generator itself is in perfect working order. The equipment never failed. But the documentation did, and in a CMS life safety survey, documentation failure and equipment failure are treated with equal seriousness.

This is the scenario that catches SNFs off guard more than almost any other in the life safety compliance world. Automatic transfer switch testing is one of those tasks that feels routine until it becomes a citation, and the gap between "we test our ATS" and "we have a defensible, complete, survey-ready ATS log" is wider than most maintenance directors realize until they're sitting across from a surveyor explaining a missing entry.

This article breaks down what the ATS testing requirement actually demands, what the log must contain to satisfy CMS and NFPA expectations, and where the documentation chain most commonly breaks down in skilled nursing facilities. It also explains how a single missing log entry creates K-tag exposure, and what a complete, audit-ready ATS compliance program looks like from the inside.

What an Automatic Transfer Switch Actually Does (and Why It's Life Safety Critical)

The automatic transfer switch is the device that stands between a power failure and the moment your emergency generator actually powers the building. When utility power drops, the ATS detects the outage, initiates the generator start sequence, and, once the generator reaches stable voltage and frequency, physically transfers the electrical load from the utility feed to the generator. When utility power is restored, the ATS transfers back and allows the generator to cool down before shutting off. The whole sequence is automatic, which is the point: in a skilled nursing facility, where residents may be on ventilators, infusion pumps, powered beds, and other life-sustaining equipment, there is no time for a manual switching process.

That automation is also what makes the ATS a life safety component in the regulatory sense, not just an electrical component. NFPA 110, the standard for Emergency and Standby Power Systems, governs ATS requirements for healthcare facilities, and it treats the ATS as an integral part of the Emergency Power Supply System (EPSS) rather than a standalone device. That classification matters enormously for compliance purposes, because it means ATS testing requirements are part of the broader EPSS testing program, not a separate checklist item that can be managed in isolation.

The EPSS Chain and Where the ATS Fits

Think of the EPSS as a chain: the generator is the power source, the transfer switch is the routing mechanism, and the downstream distribution system delivers power to critical loads. A weakness anywhere in that chain can cause the same outcome, which is why NFPA 110 requires testing and documentation of the entire chain, including the ATS, as a unit. When a surveyor reviews your EPSS records, they are not just looking at generator run hours. They are looking for evidence that every component in the transfer sequence, including the ATS, has been inspected, tested, and documented at the required intervals.

In practical terms, this means that a facility can have a pristine generator maintenance record and still receive a life safety citation if the ATS documentation is incomplete. The two records are reviewed together, and gaps in the ATS log create questions about the integrity of the entire EPSS program.

Types of ATS Found in SNFs

Most skilled nursing facilities use one of two ATS configurations. The more common is a single ATS that serves the entire facility's emergency loads, transferring from utility to a single generator. Larger facilities or those with more complex electrical systems may use multiple transfer switches, sometimes with different delay settings for different load groups. This matters for compliance because each ATS in the facility is a separate component requiring its own inspection and documentation record. A facility with three transfer switches has three ATS maintenance obligations, and a surveyor will look for records on all of them.

ATS Testing Requirements Under NFPA 110: What the Standard Actually Requires

NFPA 110 establishes the testing framework for the EPSS, and automatic transfer switch inspection is embedded within that framework at multiple intervals. Understanding the distinction between different testing intervals is essential for building a compliant documentation program, because the requirements are not all the same and missing the nuance creates gaps.

At the most frequent interval, NFPA 110 calls for regular operational testing of the EPSS, which includes verifying that the ATS operates correctly as part of the transfer sequence. These tests are typically conducted monthly, in conjunction with the generator exercise requirement. During a monthly test, the ATS should be observed to confirm that it transfers on loss of normal power, that it transfers back when normal power is restored, and that transfer times fall within acceptable parameters.

At a less frequent interval, NFPA 110 requires more comprehensive EPSS testing, which includes a load test conducted under conditions that meet minimum load thresholds specified in the standard. During these more comprehensive tests, the ATS is again part of the observed sequence, and the documentation requirements are more detailed: load readings, transfer times, and any anomalies observed during the test must all be captured.

Beyond the periodic tests, NFPA 110 also requires a written record of all EPSS inspections, tests, exercises, operations, and repairs. This is the documentation standard that drives the log requirement, and it is the standard against which your ATS records will be evaluated during a CMS life safety survey.

What "Monthly Testing" Actually Means for the ATS

The monthly generator exercise requirement is well known to most SNF maintenance directors. What is less consistently understood is that the ATS must be part of that monthly exercise in a meaningful way. Running the generator under load while the facility remains on utility power does not test the ATS. The ATS is only tested when the transfer sequence is actually initiated, meaning normal power is interrupted (or simulated to be interrupted) and the ATS performs a real or simulated transfer to emergency power.

This distinction matters because some facilities run their generators monthly in a way that exercises the engine but does not actually cycle the ATS. If the ATS never transfers during a monthly test, the ATS is not being tested at the required frequency, regardless of how good the generator run log looks. A surveyor who understands EPSS requirements will ask specifically whether the ATS was cycled during each monthly test, and a generator log that shows run hours but no transfer events will raise questions.

The Inspection Component Separate from the Load Test

In addition to operational testing during generator exercises, NFPA 110 identifies inspection tasks for ATS components that go beyond simply observing whether the switch transfers. These include visual inspection of the switch mechanism, checking for signs of wear, corrosion, or overheating, verifying that connections are tight, and confirming that the switch's manual bypass (if equipped) is functioning correctly. These inspection tasks are part of the broader EPSS maintenance program and should be documented separately from the transfer-event log.

Many SNF maintenance programs document the transfer event during monthly tests but do not have a separate ATS inspection record. This creates a documentation gap that a thorough surveyor may identify, because the testing record and the inspection record serve different purposes and the absence of one does not satisfy the requirement for the other.

What CMS Expects to See in the ATS Documentation Record

CMS life safety surveys in skilled nursing facilities use the Life Safety Code survey protocols and interpretive guidelines as the framework for evaluating EPSS compliance. The specific life safety K-tag categories that address emergency power and generator compliance require surveyors to review documentation of EPSS testing and maintenance, and the ATS record is part of that review.

What surveyors are looking for in the ATS documentation is not simply that tests occurred, but that the documentation provides enough detail to verify that the tests were conducted correctly and that the system performed within acceptable parameters. A log entry that says only "ATS tested, pass" does not satisfy this standard. A complete ATS log entry for a monthly transfer test should include, at minimum:

  • Date and time of the test, recorded contemporaneously (at the time of the test, not reconstructed later)
  • Name of the person conducting the test, with enough identification to confirm they were a qualified individual
  • Transfer time from loss of normal power to energization of emergency loads, measured in seconds
  • Retransfer time when normal power was restored, if the test included a retransfer sequence
  • Generator load readings during the transfer sequence, including voltage and frequency at the ATS input
  • Any anomalies observed during the test, including slow transfer, voltage fluctuations, or failure to transfer automatically
  • Confirmation that normal power was restored and the ATS completed the retransfer sequence

For more comprehensive periodic tests that include a load test component, the documentation requirements expand further to include load readings, exhaust temperature readings (for the generator), and confirmation that the test met the minimum load conditions required by NFPA 110.

The Contemporaneous Documentation Standard

One of the most important and least understood aspects of the documentation requirement is the contemporaneous standard. The log is supposed to be completed at the time of the test, not reconstructed from memory or notes afterward. This matters because a record completed contemporaneously reflects what actually happened, including anomalies that might be forgotten or omitted in a reconstruction. CMS surveyors review records alongside their observations of the facility and its systems, and inconsistencies between what the log says and what the surveyor observes on site are a significant concern.

Facilities that complete logs retrospectively, even when the underlying tests were conducted correctly, create risk because any inconsistency between the record and observable reality becomes difficult to explain. The simplest and most defensible approach is a log that is completed in real time, at the point of the test, by the person conducting the test.

The Chain of Custody for ATS Records

CMS surveyors typically request records covering the most recent twelve months of EPSS testing as part of a life safety survey. This means the ATS log must be retrievable, organized, and complete for that entire period. Records stored in a disorganized binder, records that are difficult to locate during the survey, and records that have gaps in the twelve-month window all create problems during the review process.

The practical implication is that the ATS documentation program needs to be designed with retrieval in mind, not just with testing in mind. A test that was conducted but not documented is functionally invisible to a surveyor. A test that was documented but whose records cannot be located during the survey window is also functionally invisible. Both outcomes carry the same risk.

How a Missing ATS Log Entry Creates K-Tag Exposure

The K-tag system used in CMS life safety surveys is a set of deficiency categories derived from the Life Safety Code and its referenced standards, including NFPA 110. The emergency power and generator compliance K-tags address deficiencies in the EPSS testing and maintenance program, and ATS documentation gaps fall within the scope of those tags.

It is important to be precise about how K-tag citations actually work, because there are common misconceptions. A surveyor reviewing ATS records exercises judgment about what they observe. A single missing entry in an otherwise complete twelve-month log may be cited as a low-severity, isolated deficiency, or it may not be cited at all depending on what the surveyor observes and the context of the visit. A pattern of missing entries, incomplete data, or irregular testing intervals is more likely to result in a citation and more likely to receive a scope and severity rating that carries enforcement consequences.

The risk of a missing log entry is not mechanical, meaning it does not automatically produce a citation at a fixed severity level. The risk is that a missing entry becomes evidence of a documentation practice problem, and a documentation practice problem is evaluated in the context of everything else the surveyor observes. A facility with excellent operational practices and a single documentation gap is in a very different position than a facility where the documentation gap is part of a broader pattern of incomplete records across multiple life safety categories.

The Scope and Severity Framework

CMS uses a scope and severity grid to evaluate deficiencies found during surveys. Scope refers to how widespread a deficiency is (isolated, pattern, or widespread), and severity refers to the potential for harm (from no actual harm with low potential to immediate jeopardy). ATS documentation deficiencies are most commonly cited in the lower severity range when the equipment itself is functioning and the deficiency is limited to the documentation record. However, when documentation gaps are combined with evidence of actual equipment problems, or when the documentation gap is so extensive that it is impossible to determine whether testing occurred at all, severity ratings can escalate.

For SNF administrators and maintenance directors, the practical implication of the scope and severity framework is that the goal is not just to avoid a citation, but to maintain documentation practices that would support an isolated, low-severity finding at worst if a gap is discovered. A pattern finding, meaning the same documentation deficiency appears across multiple months or multiple components, is harder to defend and more likely to attract additional scrutiny of the entire life safety program.

What Surveyors Actually Look for When Reviewing ATS Logs

Surveyors conducting life safety reviews examine records alongside their observations of the physical environment. When reviewing ATS logs, a surveyor is typically checking whether tests occurred at the required frequency, whether the documentation contains enough detail to verify that the test was conducted correctly, and whether the recorded results are internally consistent.

Common red flags in ATS logs include entries with identical transfer times across multiple months (which may suggest the log was completed without actually measuring transfer time), entries with no load readings, gaps in the monthly sequence, and entries that do not correspond to the facility's operational calendar (for example, a test logged on a date when the facility had a documented power outage, which would mean the ATS operated in an emergency rather than a test condition but the log treats it as a scheduled test).

None of these patterns automatically result in a citation. They are the kinds of observations that prompt surveyors to ask follow-up questions, request additional records, or observe the next test if scheduling allows. The documentation program that avoids these patterns is the one that records real data, in real time, with enough detail to be self-explanatory without verbal clarification from the maintenance director.

The Most Common ATS Documentation Failures in SNFs

Across skilled nursing facilities of different sizes and ownership structures, certain documentation failures appear more consistently than others. Understanding these patterns is useful for building a documentation program designed to avoid them.

Missing Transfer Time Data

Transfer time, the elapsed time from loss of normal power to energization of emergency loads, is one of the most important data points in an ATS test record. NFPA 110 specifies maximum acceptable transfer times for healthcare facilities, and documenting the actual transfer time during each test is how a facility demonstrates ongoing compliance with that requirement. Many SNF ATS logs record whether the transfer occurred but do not record how long it took. This omission is significant because a transfer that takes longer than the standard allows is a deficiency that may not be caught if transfer time is not measured and recorded.

Testing the Generator Without Cycling the ATS

As discussed earlier, generator run tests that do not include an actual ATS transfer sequence do not test the ATS. Facilities that run their generators on a scheduled basis without interrupting normal power to initiate an actual transfer may have complete generator logs and empty or incomplete ATS logs, because the ATS was never actually tested. This is a structural problem with the testing program, not just a documentation problem, and it requires changing the testing protocol, not just improving the log.

Incomplete Identification of the Person Conducting the Test

Logs that record test results but identify the tester only by initials, a first name, or no name at all create problems during a survey. The surveyor needs to be able to determine who conducted the test and whether that person was qualified to do so. A complete log entry identifies the tester by full name and, where relevant, by role or credential.

Retroactive Completion Without Clear Notation

Occasionally a test is conducted but the log is not completed immediately, and the entry is filled in later. If this happens, the log should clearly note that the entry was completed after the fact, with the date of completion and the date of the test recorded separately. Logs that appear to have been completed retroactively without this notation, for example, because the handwriting is identical across multiple entries that should have been completed on different days, can raise questions during a survey that are difficult to answer without undermining the credibility of the entire log.

No Separate ATS Inspection Record

The operational test log (recording transfer events) and the inspection record (recording the physical condition of the ATS components) are distinct documentation requirements. Facilities that maintain only a transfer event log without a corresponding inspection record are missing part of the required documentation program. The inspection record should document the physical condition of the switch, any signs of wear or damage, and any corrective actions taken.

Gap in Coverage During Contractor-Led Tests

Many SNFs use outside contractors for periodic comprehensive EPSS tests, including the load test. When a contractor conducts the test, they typically provide a report. That contractor report needs to be retained as part of the facility's EPSS documentation, and it needs to be cross-referenced with the facility's own internal log. A gap in this chain, for example, a month where the contractor conducted the test and provided a report but the facility's internal log has no corresponding entry, creates a documentation inconsistency that may require explanation during a survey.

Building a Survey-Ready ATS Documentation Program

A survey-ready ATS documentation program is not more complicated than the testing program itself. It is simply a documentation system designed around the requirements rather than around convenience. The following framework reflects what a complete, defensible ATS compliance program looks like in a skilled nursing facility.

The ATS Documentation Framework for SNFs

Monthly transfer event log

  • Frequency: Monthly, in conjunction with generator exercise
  • Required Data Points: Date, time, tester name, transfer time (seconds), load at transfer, anomalies, retransfer confirmation
  • Common Gap: ⚠️ Transfer time not measured or recorded

Periodic load test record

  • Frequency: As required by NFPA 110 for comprehensive EPSS testing
  • Required Data Points: Load readings (kW), exhaust temperature, voltage and frequency at ATS, transfer time, tester name, contractor report (if applicable)
  • Common Gap: ⚠️ Contractor report not retained or not cross-referenced

ATS physical inspection record

  • Frequency: Per NFPA 110 inspection schedule and manufacturer guidance
  • Required Data Points: Visual inspection findings, connection integrity, signs of wear or overheating, manual bypass test (if applicable), corrective actions
  • Common Gap: ❌ Inspection record not maintained separately from transfer log

Repair and corrective action log

  • Frequency: As needed, following any identified deficiency
  • Required Data Points: Date of deficiency identification, nature of deficiency, corrective action taken, date of completion, verification of correction
  • Common Gap: ⚠️ Repair completed but not documented in the log chain

Emergency operation record

  • Frequency: Following any actual power outage where ATS operated
  • Required Data Points: Date, time, duration of outage, transfer performance, any anomalies, post-event inspection notation
  • Common Gap: ❌ Emergency operation not logged separately from scheduled tests

The Twelve-Month Retrieval Standard

Every component of the ATS documentation program should be organized so that a complete twelve-month record can be assembled and presented to a surveyor within minutes of the request. This is not an aspirational standard; it is a practical necessity. Surveys are unannounced, and the time between a surveyor's arrival and their request for records may be measured in minutes. A documentation system that requires the maintenance director to search through multiple binders, email the contractor for a missing report, or reconstruct any part of the record is a documentation system that creates survey-day risk.

The most defensible organizations maintain a single organized record for each ATS in the facility, with monthly entries in chronological order and contractor reports filed alongside the corresponding internal log entries. Some facilities use a physical binder for this purpose; others use digital systems that allow instant retrieval. Either approach works if the underlying data is complete and organized. The method matters less than the discipline.

Multi-ATS Facilities: The Parallel Record Requirement

Facilities with multiple transfer switches need to maintain parallel documentation records for each ATS, not a single consolidated log. A surveyor reviewing a facility with three transfer switches and finding only one complete log will ask about the other two, and "we only have one log for all of them" is not a defensible answer. Each ATS is a distinct life safety component with its own testing and inspection requirements, and the documentation program must reflect that.

Integrating ATS Documentation Into the Broader EPSS Compliance Program

ATS documentation does not exist in isolation. It is one component of a broader EPSS compliance program that includes generator maintenance records, fuel management documentation, automatic load shedding records (where applicable), and the documentation of any modifications to the emergency power system. Surveyors reviewing EPSS compliance look at this record as a whole, and gaps in any component can prompt closer scrutiny of adjacent components.

The Generator-ATS Documentation Relationship

The generator log and the ATS log should be internally consistent. If the generator log shows a monthly exercise on a given date, the ATS log should show a corresponding transfer event on that date. If the ATS log shows a transfer event but the generator log has no corresponding entry, or vice versa, the inconsistency creates questions that the maintenance director will need to answer during the survey.

Building both logs from the same testing event, completed at the same time by the same person, is the most reliable way to maintain internal consistency. A single monthly test form that captures both generator performance data and ATS transfer data in a single document reduces the risk of inconsistency because both records are completed from the same observation.

Fuel Level Documentation and Its Connection to ATS Testing

Fuel level at the time of each generator exercise is another data point that connects the generator log to the ATS documentation. NFPA 110 includes requirements related to fuel supply for the EPSS, and a generator exercise that reveals a low fuel level is an event that should be documented and followed up on. If the ATS transfers successfully during a monthly test but the generator runs on a fuel tank that is below the required minimum, the EPSS is not actually compliant even if the ATS performed correctly. The complete documentation program captures both the transfer performance and the operational context in which it occurred.

What to Do When a Test Reveals an ATS Problem

When a monthly test or periodic inspection reveals a problem with the ATS, the documentation obligation expands significantly. The deficiency itself must be documented in the log with enough detail to describe what was observed. A corrective action must be initiated and documented, with a timeline for resolution. If the deficiency renders the ATS unable to perform its emergency function, the facility's emergency action plan may need to be activated, and that activation and any interim protective measures must also be documented.

Facilities sometimes make the mistake of correcting an ATS problem without creating a complete paper trail, because the instinct is to fix the problem and move on rather than document it in detail. From a compliance standpoint, an undocumented repair to a life safety system is nearly as problematic as an unrepaired deficiency. The record of how the deficiency was identified, what was done to correct it, and when the correction was verified is part of the EPSS documentation program and may be reviewed during a survey.

How Digital Documentation Systems Change the ATS Compliance Picture

The shift from paper binders to digital documentation systems in SNF life safety management is driven by a simple operational reality: paper binders do not audit themselves. A maintenance director can complete every required ATS test correctly, log every test in the binder, and still have a survey-day crisis if a page is misfiled, a form is incomplete, or a contractor report was never placed in the binder. The binder does not flag these gaps; the surveyor does.

Digital documentation platforms designed for healthcare facility compliance change this dynamic by building the audit function into the documentation system itself. Rather than passively collecting completed forms, a well-designed digital system actively monitors the documentation record against the regulatory requirements, flagging gaps before they become survey findings. For ATS compliance specifically, this means the system knows that a monthly transfer event log entry is due on or before a specific date, that the entry must include a defined set of data fields, and that the absence of any required field is a documentation gap that needs to be addressed.

What Automated Gap Detection Looks Like in Practice

In a facility using a documentation intelligence system like SEQURA, the ATS compliance workflow looks different from the paper binder approach in several important ways. The monthly ATS test is scheduled as a recurring task, assigned to the responsible person, and the task template defines exactly what data must be captured during the test. When the task is completed, the system validates that all required fields are present before accepting the entry as complete. A log entry with no transfer time recorded is not accepted as a complete entry; the system prompts the person completing the log to add the missing data before moving on.

At the review level, the system monitors the twelve-month record continuously, flagging any gap in the monthly sequence, any entry with incomplete data, and any inconsistency between the ATS log and related records such as the generator maintenance log. A maintenance director using this kind of system sees the documentation gaps in real time, before the survey, with enough lead time to investigate and correct them. A surveyor who arrives at a facility running this kind of system finds a complete, organized, self-auditing record that tells a coherent story about the ATS testing program.

The Contractor Report Integration Problem

One of the most common documentation gaps in facilities that use outside contractors for periodic EPSS testing is the failure to integrate contractor reports into the facility's own documentation record. The contractor provides a report; the facility files it somewhere; the facility's internal log has no corresponding entry; and during the survey, the two records cannot easily be reconciled. A digital documentation system that includes a contractor report upload function and links uploaded documents to the corresponding task record solves this problem by creating an integrated record that connects the contractor's findings to the facility's internal log in a single retrievable document chain.

ATS Testing in the Context of a CMS Life Safety Survey

Understanding how ATS documentation fits into the overall flow of a CMS life safety survey helps maintenance directors and administrators prioritize their preparation efforts. Life safety surveys in skilled nursing facilities are conducted by state survey agencies on behalf of CMS, and they use a standardized protocol that includes a physical walkthrough of the facility, review of life safety documentation, and observation of selected life safety systems in operation.

The EPSS documentation review is a standard component of every life safety survey. Surveyors are trained to review EPSS records as part of the survey protocol, and they have access to the interpretive guidelines that describe what adequate documentation looks like. A facility that has not reviewed its own ATS documentation through the lens of those interpretive guidelines before the survey is essentially waiting for the surveyor to find the gaps.

What Happens When a Gap Is Found During the Survey

When a surveyor identifies a gap in the ATS documentation, the typical sequence is an inquiry to the maintenance director or administrator, a request for any additional records that might explain or address the gap, and, if the gap cannot be satisfactorily explained, a notation in the survey record that may support a deficiency citation. The maintenance director's ability to respond to the inquiry is directly dependent on the quality of the documentation program. A director who can immediately retrieve the relevant records, explain the testing protocol, and address the specific gap with supporting documentation is in a much stronger position than one who is searching through a disorganized binder while the surveyor waits.

This is why the organization and retrievability of the ATS record is nearly as important as its completeness. A complete record that cannot be quickly located and presented is functionally incomplete during the survey window.

The Relationship Between ATS Documentation and Other Life Safety K-Tags

ATS documentation deficiencies rarely appear in isolation during a life safety survey. Facilities with gaps in their ATS records frequently have gaps in related life safety documentation categories, because the underlying cause is usually a documentation practice problem rather than a problem specific to the ATS. When a surveyor finds an ATS documentation gap, they are likely to look more carefully at the broader EPSS record, the fire alarm maintenance documentation, the sprinkler inspection records, and other life safety documentation that follows a similar recurring task structure.

This means that the ATS documentation program should be understood as part of an integrated life safety documentation system, not as a standalone compliance task. Improving the ATS documentation without addressing the same structural gaps in other life safety documentation categories reduces risk in one area while leaving it unchanged in others.

Generator maintenance log

  • Connection to ATS Documentation: Must be internally consistent with ATS transfer event log
  • Common Documentation Gap: ⚠️ Generator log shows exercise; ATS log has no corresponding entry

Fuel supply documentation

  • Connection to ATS Documentation: Fuel level at time of each test is part of the EPSS record
  • Common Documentation Gap: ⚠️ Fuel level not recorded at time of monthly exercise

Fire alarm system maintenance

  • Connection to ATS Documentation: Fire alarm connection to EPSS may be tested as part of ATS exercise
  • Common Documentation Gap: ⚠️ Fire alarm EPSS interface test not documented separately

Emergency lighting testing

  • Connection to ATS Documentation: Emergency lighting verification is part of EPSS load confirmation
  • Common Documentation Gap: ❌ Emergency lighting test not cross-referenced to ATS transfer event

Medical gas system documentation

  • Connection to ATS Documentation: Medical gas equipment on emergency power should be verified during ATS exercise
  • Common Documentation Gap: ⚠️ Medical gas load verification not included in monthly ATS test record

Practical Steps for SNF Administrators and Maintenance Directors

The gap between knowing that ATS documentation is a compliance requirement and having a defensible, survey-ready ATS documentation program is primarily a systems gap, not a knowledge gap. Most SNF maintenance directors understand that the ATS needs to be tested and documented. The challenge is building the operational discipline and the documentation infrastructure to make that happen consistently, month after month, with the level of detail that satisfies a CMS surveyor.

The following steps represent the practical foundation of an ATS documentation program that is designed for survey readiness rather than just operational convenience.

Step 1: Audit the Last Twelve Months of Records Before the Next Survey

The first step is to pull the last twelve months of ATS documentation and review it as a surveyor would. Check for gaps in the monthly sequence. Check that every entry includes all required data fields, particularly transfer time. Check that the ATS log is internally consistent with the generator log. Check that contractor reports are filed and cross-referenced. Any gap identified in this self-audit is a gap the surveyor would find, and finding it before the survey creates the opportunity to investigate and document the investigation.

Step 2: Standardize the Log Format

If the current ATS log is a blank form that allows testers to record whatever they choose, replace it with a structured form that includes a defined field for every required data point. The form should make it impossible to complete an entry without recording transfer time, tester name, load data, and anomaly notation. A structured form is also easier to review quickly, both internally and during a survey, because the data is always in the same location.

Step 3: Separate the ATS Inspection Record from the Transfer Event Log

If the current documentation program combines physical inspection findings with transfer event data in a single log, separate them. Create a dedicated ATS inspection record that captures physical condition data, and maintain it as a distinct document from the transfer event log. This separation makes it easier to demonstrate that both requirements are being met independently.

Step 4: Establish a Contractor Report Integration Protocol

For facilities that use outside contractors for periodic comprehensive tests, establish a written protocol for receiving, reviewing, and filing contractor reports. The protocol should specify who receives the report, where it is filed, and how it is cross-referenced to the facility's internal log. The protocol should also specify what happens if the contractor's findings identify a deficiency that requires follow-up, and how that follow-up is documented.

Step 5: Conduct a Monthly Internal Review

Designate a specific time each month to review the ATS log for the most recent test cycle before that month's entry is considered closed. This review should confirm that the entry is complete, that it is consistent with the generator log, and that any anomalies noted in the entry have been addressed or are actively being addressed. A monthly internal review creates a second check on the documentation that catches gaps while they are still recent and easier to investigate.

Frequently Asked Questions About ATS Testing in Skilled Nursing Facilities

What is an automatic transfer switch and why does it matter for SNF compliance?

An automatic transfer switch is the electrical device that routes power from the emergency generator to the facility's critical loads when normal utility power fails. In skilled nursing facilities, where residents may depend on powered medical equipment, the ATS is a life safety component regulated under NFPA 110 and subject to CMS life safety survey review. Compliance requires not just that the ATS functions correctly, but that its testing and inspection are documented in a way that surveyors can verify.

How often does the ATS need to be tested in an SNF?

The ATS is tested as part of the overall EPSS testing program. Monthly generator exercises should include an actual ATS transfer sequence, not just a generator run. Periodic comprehensive EPSS tests, which include a load test component, also involve the ATS and have separate documentation requirements. The specific intervals are set by NFPA 110, and facilities should confirm their testing program aligns with the current edition of the standard adopted in their state.

What data must be recorded in an ATS log entry?

A complete ATS log entry for a monthly transfer test should include the date and time of the test, the name of the person conducting the test, the transfer time in seconds, the load at the point of transfer, any anomalies observed, and confirmation of retransfer when normal power was restored. Entries for more comprehensive periodic tests should also include load readings (kW), voltage and frequency data at the ATS input, and any contractor report reference number if the test was conducted by an outside vendor.

What happens if a monthly ATS test entry is missing?

A single missing entry in an otherwise complete twelve-month log may or may not result in a citation, depending on what the surveyor observes during the visit and the overall context of the facility's life safety documentation. A pattern of missing entries, or missing entries combined with other documentation gaps, is more likely to result in a citation and may affect the scope and severity rating. The safest approach is to treat every missing entry as a documentation gap that needs to be investigated and, where possible, addressed before the next survey.

Can an actual power outage substitute for a scheduled monthly ATS test?

An actual power outage during which the ATS operates is a real-world test of the system's performance, and it should be documented as an emergency operation event in the ATS log. However, it should be documented separately from the scheduled monthly test, not used as a substitute for it. The scheduled monthly test should still be conducted and documented, because the emergency operation may not have tested the system under the same conditions or for the same duration as the scheduled exercise.

What is the difference between the ATS transfer event log and the ATS inspection record?

The transfer event log records the performance of the ATS during each test, capturing operational data such as transfer time and load readings. The inspection record captures the physical condition of the ATS components, including visual inspection findings, connection integrity checks, and any signs of wear or damage. NFPA 110 requires both types of documentation as part of the written EPSS record, and they serve different compliance purposes. Maintaining them as separate documents makes it easier to demonstrate that both requirements are met.

Do contractor test reports satisfy the documentation requirement?

Contractor reports from periodic comprehensive EPSS tests are part of the required documentation record and should be retained. However, they do not substitute for the facility's own internal log entries. The facility's internal log should have a corresponding entry for every test conducted by a contractor, cross-referencing the contractor's report. Both the contractor report and the internal log entry together form the complete documentation record for that test.

How far back do CMS surveyors typically request ATS records?

CMS life safety surveys typically cover the most recent twelve months of EPSS documentation, including ATS records. Facilities should maintain a complete, organized, and retrievable twelve-month record for every ATS in the facility at all times, not just in advance of a known survey. Because life safety surveys are unannounced, the twelve-month record needs to be ready for immediate presentation at any time.

What should a facility do if an ATS inspection reveals a deficiency?

When an ATS inspection or test reveals a deficiency, the facility should document the deficiency in detail in the ATS log, initiate a corrective action, and document the corrective action through completion. If the deficiency affects the ATS's ability to perform its emergency function, the facility's emergency action plan should be reviewed and interim protective measures should be documented. The complete deficiency-to-correction documentation chain is part of the EPSS record and may be reviewed during a survey.

Does a digital documentation system satisfy CMS documentation requirements?

CMS does not require life safety documentation to be maintained in paper form. Digital documentation is acceptable provided the records are complete, contemporaneous, retrievable, and auditable. A digital system that includes structured data fields, timestamps, and user identification for each entry can provide stronger documentation than a paper log because it reduces the risk of incomplete entries and makes the record easier to organize and retrieve. The content requirements for each log entry remain the same regardless of whether the record is paper or digital.

What is the relationship between ATS documentation and the Five-Star Quality Rating System?

Life safety (K-tag) citations from CMS surveys are not included in the Health Inspections domain of the Five-Star Quality Rating System. ATS documentation deficiencies cited as K-tags do not directly affect a facility's Five-Star score. However, they are part of the public survey record and may affect a facility's reputation, its relationship with referral sources, and its standing with state regulators. For facilities subject to enforcement actions beyond citations, the consequences may extend further depending on the scope and severity of the findings.

How can a multi-site SNF operator manage ATS documentation across multiple facilities?

Multi-site operators face the challenge of maintaining consistent documentation practices across facilities with different maintenance staffing, different EPSS configurations, and potentially different state regulatory interpretations of NFPA 110. A centralized documentation system that enforces consistent log formats and data requirements across all facilities, while allowing facility-level customization for different ATS configurations, is the most effective approach. Regional facilities managers should conduct periodic documentation audits at each facility, reviewing the ATS records as a surveyor would.

Key Takeaways for SNF Life Safety Compliance Teams

  • The automatic transfer switch is a life safety component, not just an electrical component. NFPA 110 governs its testing as part of the Emergency Power Supply System, and CMS surveyors review ATS documentation as part of every life safety survey.
  • Running the generator without cycling the ATS does not test the ATS. Monthly exercises must include an actual transfer sequence to satisfy the ATS testing requirement, and the documentation must capture the transfer event specifically.
  • Transfer time is the most commonly missing data point in ATS logs. Every monthly log entry must include the measured transfer time in seconds, not just a notation that the transfer occurred.
  • The transfer event log and the ATS inspection record are separate documentation requirements. Maintaining only one without the other leaves part of the required EPSS record incomplete.
  • Contractor reports are part of the EPSS record but do not substitute for internal log entries. Both documents must be retained and cross-referenced.
  • The twelve-month record must be retrievable within minutes of a surveyor's request. Organization and accessibility are as important as completeness during an unannounced survey.
  • ATS documentation gaps are rarely isolated findings. A gap in the ATS record typically prompts closer review of the broader EPSS documentation and related life safety categories.
  • Digital documentation systems that include structured data validation and gap detection reduce the risk of incomplete entries by catching missing data fields at the point of entry, before they become survey findings.
  • Multi-ATS facilities must maintain parallel documentation records for each switch. A single consolidated log for multiple transfer switches does not satisfy the individual component documentation requirement.
  • Self-audit before the survey is the most effective risk management tool available. Reviewing the last twelve months of ATS records as a surveyor would, before the surveyor arrives, identifies correctable gaps while there is still time to address them.

About the author

Benjamin Terebelo · Founder

Benjamin is the founder of SEQURA, a compliance platform purpose-built for healthcare facilities. He builds at the intersection of healthcare operations and software, maintaining a focus on bringing modern tooling to systems that the broader industry has largely left behind.

Related reading

About the author

Benjamin Terebelo · Founder

Benjamin is the founder of SEQURA, a compliance platform purpose-built for healthcare facilities. He builds at the intersection of healthcare operations and software, maintaining a focus on bringing modern tooling to systems that the broader industry has largely left behind.

Topics

  • automatic transfer switch
  • ATS testing requirements SNF
  • generator compliance documentation skilled nursing
  • NFPA 110 automatic transfer switch inspection
  • life safety utility compliance

More from the blog

View all articles