Standardizing PCREE Testing Across a Multi-Facility SNF Portfolio: A Guide for Regional Compliance Teams

A single-building skilled nursing facility either has a working PCREE program or it doesn't — the administrator or maintenance director knows the vendor, knows the last test date, and can usually put a hand on the documentation binder within a few minutes of being asked. That simplicity disappears the moment an operator crosses into multiple facilities. A regional group running ten buildings, or a national operator running two hundred, doesn't have one PCREE program — it has as many programs as it has facilities, unless someone deliberately builds one standardized system on top of them. Most operators don't get there by design. They get there because a facility joined the portfolio through an acquisition with its own vendor relationship already in place, or because a new administrator at one building picked a different technician than the one three buildings up the road happens to use, and nobody at corporate ever stepped back to ask whether all forty buildings are actually being held to the same standard.

Why PCREE Programs Break Down at the Portfolio Level

NFPA 99 Chapter 10 doesn't distinguish between a standalone SNF and one building in a two-hundred-facility portfolio — the leakage current limits, ground resistance thresholds, and testing intervals are identical either way, and CMS enforces that same baseline through the Life Safety Code survey process regardless of who owns the building. The compliance obligation is uniform. What isn't uniform, in practice, is who's actually responsible for meeting it at each site. In a single-facility operation, that responsibility sits with one administrator answering to one owner. In a portfolio, it typically sits with dozens of local administrators and maintenance directors, each making their own decisions about vendor selection, scheduling, and documentation, often with minimal visibility from the regional or corporate level until a survey happens to surface a gap.

That structure works reasonably well when every local leader is diligent and every facility retains its staff for years at a time. It works far less well in an industry with the turnover skilled nursing regularly sees. A PCREE program that lived entirely in one administrator's head, or one maintenance director's personal vendor relationship, doesn't survive that person leaving — and the next person often doesn't know a program existed at all until a survey asks for documentation nobody can locate.

The Real Cost of a Fragmented, Building-by-Building Approach

The most visible cost of a fragmented approach is pricing. When forty facilities each negotiate their own PCREE contract independently, the portfolio typically pays forty different rates for functionally identical work, and rarely at the volume discount a coordinated contract would command. But the pricing gap is the smaller problem. The bigger one is that corporate compliance usually can't answer a basic question on demand: which buildings in the portfolio are currently compliant, which are coming due, and which have quietly lapsed. Without a centralized answer to that question, the first time anyone at the regional level learns a facility fell behind is often when a surveyor asks for documentation during a Life Safety Code inspection — the worst possible moment to discover a gap.

Inconsistent documentation compounds the problem. One facility's PCREE reports might be thorough, itemized by asset, and stored in a labeled binder; another facility's might exist as a loose stack of invoices with no clear record of what was actually tested. A surveyor evaluates each building on its own record, so a portfolio's overall compliance strength offers no protection to the one facility whose documentation can't stand up to scrutiny that day. See our guide on risk-based PCREE testing frequency for how testing intervals should be set and documented — a standard that's easy to apply consistently at one facility and considerably harder to enforce across dozens without a shared framework.

Building a Standardized PCREE Program Across Multiple Facilities

A workable portfolio-level program rests on a handful of decisions made once at the corporate or regional level, rather than left to each facility to solve independently.

• Centralize vendor selection. Rather than every facility sourcing its own PCREE technician, corporate or regional compliance should vet and approve a vendor or a small panel of vendors that every facility draws from. Our vendor evaluation guide covers the credentials and questions worth confirming for any single facility — apply that same diligence once at the portfolio level, and every facility inherits a pre-vetted option instead of repeating that work forty times.
• Standardize the documentation format. Every facility's PCREE report should contain the same fields — equipment ID, test date, technician name and credentials, pass/fail result, and next due date — regardless of which vendor performed the work or which state the facility sits in. A standard template makes it possible for corporate to audit any facility's file at a glance instead of learning a new format every time.
• Build one central tracking system. A shared spreadsheet or a lightweight compliance database that lists every facility's last test date, next due date, and vendor of record turns "which buildings are due this quarter" from a round of phone calls into a five-minute query. This is the single highest-leverage change most portfolios can make, and often the cheapest.
• Stagger the calendar deliberately. Testing every facility in the same month creates a scheduling crunch for whatever vendor panel is handling the volume and a budget spike for the operator. Spreading facilities across a rolling annual calendar — grouped by region to keep technician travel efficient — smooths both problems out.

Accounting for State-by-State Variation Without Losing Consistency

The NFPA 99 baseline that CMS enforces through the Life Safety Code survey process is federal and applies identically in every state, but the experience of being surveyed is not identical everywhere. State survey agencies vary in how frequently they conduct Life Safety Code surveys, how closely individual surveyors scrutinize PCREE documentation during a visit, and in some cases, whether the state layers its own supplemental licensure requirements on top of the federal floor. A portfolio spanning multiple states needs to hold every facility to the same NFPA 99 testing and documentation standard as a non-negotiable minimum, then maintain a simple reference — even a one-page table — flagging any state-specific requirements that go beyond that baseline, so no single facility's compliance program quietly falls short of what its state actually expects.

This is also where a centralized equipment management plan earns its keep at scale. Rather than each facility drafting its own plan from scratch — with all the inconsistency that invites — corporate can issue one master template that every facility customizes with its own equipment inventory and local specifics, while the core testing intervals, documentation standards, and risk-based justifications stay consistent across the entire portfolio.

What to Put in a Portfolio-Wide Vendor Arrangement

A vendor arrangement negotiated once for an entire portfolio should look different from a single facility's contract in a few specific ways. Volume pricing is the obvious one, but it's not the only one worth negotiating for.

Our comparison of contracted vendors versus in-house biomedical staff is worth revisiting at the portfolio level specifically — the math on hiring a dedicated BMET to serve multiple facilities in a regional cluster often looks very different from the math at a single 80-bed building, and larger operators frequently land on a hybrid approach: in-house staff covering a dense regional cluster, with a contracted vendor panel filling in facilities outside that footprint.

Common Mistakes Multi-Facility Operators Make

• Assuming compliance at headquarters means compliance everywhere. A strong program at the flagship facility says nothing about the smaller building acquired eighteen months ago that never got folded into the same process.
• Treating acquisitions as compliance-neutral. A newly acquired facility arrives with its own vendor, its own documentation habits, and often its own gaps — assuming it will simply adopt the parent company's standards without a deliberate onboarding step is how gaps persist for years.
• Letting local staff turnover erase institutional knowledge. When a maintenance director who managed a facility's PCREE relationship leaves without documenting the process, the facility can lose track of its own testing history even though the underlying records still exist somewhere.
• Measuring the portfolio instead of every building. A compliance dashboard that reports "92% of facilities current" sounds reassuring, but surveyors don't survey portfolios — they survey one building at a time, and the 8% that's behind carries the entire citation risk.

None of this requires a different standard than a single facility already follows — NFPA 99 doesn't scale up its requirements for larger operators. What scales is the operational discipline needed to apply one consistent standard across every building a portfolio holds, rather than allowing forty separate, informal versions of a PCREE program to run in parallel and hoping none of them happens to be the one a surveyor checks this year. See our PCREE testing cost guide for the per-facility pricing baseline worth using when evaluating whether a portfolio-wide contract is actually delivering the volume savings it should.