Fall Protection Plans Are Written Per Roof, Not Per Company

Corporate issues a fall protection standard: guardrails where feasible, personal fall arrest where they are not, a minimum anchor rating, an annual inspection cadence. Every site gets the same document. Six months later an incident review at one facility turns up a rooftop anchor point rated for a load the manufacturer's own literature says it cannot support at the roof's actual pitch, installed by a contractor who followed the corporate spec to the letter because nothing in the spec addressed pitch. The standard was not wrong. It was written for a building that does not exist, because no single document can describe forty different rooflines, forty different edge conditions, and forty different combinations of equipment that happens to already be up there.

This is the shape of the problem across the whole fall protection portfolio, not just roofs. A distribution center with mezzanine picking modules, a manufacturing plant with elevated catwalks over process equipment, and a construction-adjacent maintenance yard with scaffold-height platforms are not the same fall exposure wearing three different buildings. They are three different exposures, and OSHA's own structure for fall protection reflects that by refusing to let a single number or a single method stand in for a site assessment.

The Standards Ask for a Measurement, Not a Policy

29 CFR 1910.28, the general industry walking-working surfaces standard, sets a four-foot trigger height in general industry and requires fall protection at unprotected sides and edges above it, but the method — guardrail, safety net, travel restraint, or personal fall arrest — is a site-level engineering decision driven by what is actually on that roof or platform: parapet height, the presence or absence of existing anchor infrastructure, how close the edge sits to a process area workers cross routinely versus one nobody approaches except for quarterly maintenance. In construction scopes, 29 CFR 1926.501 raises the trigger to six feet and requires a site-specific fall protection plan wherever conventional protection is infeasible or creates a greater hazard, and that plan has to be developed by a qualified person for the actual work location, not adapted from a template written for a different job.

Read together, the standards are not silent on standardization, they actively resist it. A fall protection plan that could be issued from an office without anyone visiting the roof is, by definition, not the plan the regulation describes. The site-specific requirement exists because the same hazard category — an unprotected edge — carries a different real-world answer depending on what is physically at that edge: a parapet tall enough to serve as a guardrail on its own, or a low curb that does nothing; solid roof decking rated for foot traffic, or aging membrane over insulation that was never meant to carry a worker's weight outside designated walk pads.

What a Corporate Program Can Standardize, and What It Cannot

The instinct to write one policy for every site is not wrong, it is aimed at the wrong layer. A few things genuinely do standardize well across a portfolio: the minimum equipment specification (harness class, lanyard type, anchor rating floor), the inspection frequency and documentation format, the training curriculum for authorized users, and the incident and near-miss reporting pathway. None of those depend on what a specific roof looks like.

What does not standardize is the hazard assessment itself. Anchor point locations, rescue plan logistics, and the choice between guardrail and personal fall arrest have to be determined by someone who has stood at that edge, because the variables that drive the decision — roof pitch, structural capacity, distance to the edge from the nearest safe access point, whether a rescue team can reach a suspended worker in the time cold-weather suspension trauma allows — are physical facts about that building, not policy preferences that transfer from a template.

The operators who get this wrong tend to do it in one of two directions. Some issue a single detailed procedure and treat any site variance from it as noncompliance, which pushes local safety staff toward either ignoring physical reality to match the document or quietly working around it, both of which are worse than the variance itself. Others swing the other way and delegate fall protection entirely to site discretion with no floor requirements at all, which produces the opposite failure: forty sites independently reinventing anchor rating standards, with the weakest one setting the real risk level for the whole company regardless of what the strongest site does.

Where the Gap Shows Up in an Audit

A corporate fall protection standard that has never been checked against actual roof conditions at each site tends to surface its gaps in a specific, predictable way: the written program looks complete, references the right CFR sections, and specifies equipment correctly, but the site-specific fall protection plans required for non-conventional situations either don't exist, exist as a copy of the corporate template with the site name changed, or were written once at commissioning and never revisited after a roof-mounted HVAC unit, solar array, or new equipment run changed the edge conditions the original plan assumed. Any of those three findings tells an inspector, or an internal auditor doing the same job before OSHA does, that the assessment happened at a desk rather than on the roof.

The fix is not more corporate documentation. It is a requirement, tracked at the portfolio level, that every site with elevated work has a fall protection plan developed or reviewed on-site by a qualified person, with a defined trigger for re-review — new rooftop equipment, a roof replacement, a change in how the space is used — rather than a fixed calendar date that a physically unchanged roof will pass regardless of whether anyone looked at it.

Acquisitions Make the Problem Worse, Not Just Bigger

The gap widens fastest at acquisition. A newly acquired facility arrives with its own fall protection history, sometimes well documented, sometimes not, and the instinct is to fold it into the parent company's program on the next audit cycle. In practice this often means the acquired site's equipment specification gets updated to match corporate minimums while the site-specific plan itself, the actual assessment of that roof's anchor points and edge conditions, is never independently redone. The paperwork changes letterhead. The roof does not get walked. A site that was compliant under its prior owner's program is not automatically compliant under the new one just because the binder now has the right logo on it, and the reverse is also true: a site with weak legacy practices does not get fixed by a policy update that nobody verified against the physical building.

The Question Worth Asking Across the Portfolio

The useful audit question is not "does every site have a fall protection plan," because the answer to that is usually yes and tells you nothing. It is "when was the plan for this specific roof or platform last developed or reviewed by someone standing on it, and what changed at that location since." A plan that has never been updated because the building has never changed is fine. A plan that has never been updated despite three equipment installations since it was written is the gap that a corporate template, however well written, cannot see from head office.