Ladder Inspection Is a Site-Level Task. Corporate Doesn't Know How Many Ladders It Owns.

Ask a facilities director at a single site how many ladders are in the building, and they can usually tell you within a walk-through: the extension ladder in the maintenance closet, two stepladders on the production floor, one in the loading dock office nobody remembers buying. Ask the same question at corporate, about every site in the portfolio, and the honest answer is almost always that no one has counted. Ladders aren't tracked as capital equipment, they don't show up on a single asset register, and the standard governing them is written to be enforced at the point of use — which means responsibility for it never travels up past the site that owns the ladder.

The standard is simple. The compliance isn't centralized.

29 CFR 1910.23 sets out what a compliant ladder looks like and what has to happen to it over its working life: it must be inspected for visible defects on a periodic basis and after any event that could affect its safe use, and a ladder found to have a structural defect — a cracked rail, a missing rung, a compromised locking mechanism — has to be immediately tagged or marked to indicate it should not be used, and withdrawn from service until it's repaired or replaced. None of that is ambiguous at the level of a single ladder. What the standard doesn't specify is who at a multi-site company is supposed to know that all of this happened, or didn't, everywhere it was supposed to.

In practice, that means the standard gets satisfied — or doesn't — entirely inside each site's own maintenance routine. A plant with a rigorous PM program folds ladder checks into its existing inspection schedule without anyone naming it a separate compliance activity. A site running leaner does the inspection only when someone happens to notice a problem. Both can be true inside the same company, and corporate has no mechanism that would surface the difference before an incident does.

What "inspected" means depends on who's holding the ladder

"Periodic basis" in 1910.23 is deliberately not a fixed interval — OSHA leaves the frequency to be set by how the ladder is used and the conditions it's exposed to. That flexibility makes sense at a single site, where whoever sets the interval also owns the consequences of getting it wrong. Across a portfolio, the same flexibility means twenty sites can each have a different definition of "periodic," set independently, none of them wrong on their own terms, and no one above the site level positioned to notice that the definitions don't agree.

The gap that creates isn't usually a site skipping inspection entirely — outright neglect is rare and easy to catch once anyone looks. It's the quieter version: a site whose competent person changed roles eighteen months ago and whose replacement was never formally told the inspection was their responsibility now, so the checks continue on paper through habit but without anyone actually re-evaluating whether the "periodic" interval still fits how hard the ladders are being used.

Tagging conventions that don't travel between sites

The tag-and-remove requirement is the part of 1910.23 most likely to be followed correctly and most likely to be followed inconsistently in its details. One site's "Do Not Use" tag is a dedicated red tag kept at the tool crib specifically for this purpose. Another site's is a strip of duct tape and a handwritten note, functionally adequate in the moment but easy to lose, easy to remove informally by someone who needs a ladder and doesn't know why this one is marked. A third site may not have a formal convention at all — a damaged ladder gets set aside "for now" and, six months later, is back in rotation because nobody remembers why it was pulled.

Every one of those sites can pass an individual audit of the specific ladders on hand that day. What none of them can answer, without someone asking directly, is what happens to a tagged ladder between the day it's flagged and the day it's actually repaired or disposed of — and whether that gap is measured in days or in the kind of months that make the tag stop meaning anything.

The acquired-site ladder inventory nobody counted

The clearest version of this problem shows up on day one of an acquisition. A new site arrives with its own equipment, its own maintenance habits, and its own idea — correct or not — of what counts as a defective ladder. Corporate inherits the safety record along with the site, but not the institutional knowledge of which ladders have been flagged, replaced, or quietly kept in service past the point someone should have pulled them. Reconciling that isn't a paperwork exercise; it requires someone physically walking the new site's ladder inventory against the standard's criteria, independent of whatever the acquired site's own maintenance team reports, because "we've always inspected these" is a claim that's worth verifying rather than accepting.

Why this stays invisible until an incident forces it

Ladders don't generate the kind of paper trail that draws attention on their own. There's no permit, no annual certification filed anywhere, no vendor contract that renews and prompts a review. A crane gets inspected by a third party on a documented schedule because the consequences of skipping it are catastrophic and obvious; a ladder gets inspected, if it gets inspected, by whoever happens to be responsible for the tool crib that week, and the record of it — if one exists — usually lives on a clipboard or a shared drive specific to that site.

That's not a criticism of any individual site's diligence. It's a description of why ladder compliance is structurally different from the equipment categories that already get portfolio-level attention. Machine guarding, process safety management, and confined space programs all involve write-ups, audits, and specialists whose job title points at the hazard. Nobody's job title is "ladder compliance," at any level of the organization, which means the standard survives entirely on the strength of whichever site-level habit happens to have taken root — good in some places, informal in others, and invisible to corporate either way until an OSHA inspection or an injury investigation asks the question directly and someone has to go find out what the actual answer is.

That's also why this tends to surface at the worst possible time: not during a routine audit, where a gap can be closed quietly, but after an incident, when the same question — how long was that ladder tagged out, and why was it still in the rotation — gets asked by an investigator instead of a safety manager, and the answer has to come from records that may or may not exist.

What actually standardizes across a portfolio

None of this argues for corporate performing ladder inspections directly — that work has to happen at the site, by someone who can put hands on the ladder, and no policy written at headquarters changes that. What can standardize is the framework around the inspection: a single tagging convention used at every site regardless of who's doing the tagging, a defined maximum window between a ladder being flagged and being repaired or removed from the building, and a simple count — updated when equipment is added or retired — so that corporate has an actual answer, not an estimate, when the question of how many ladders the company owns comes up during an audit or after an incident.

That last piece is the one most companies don't have, and it's also the cheapest to build. It doesn't require new software or a capital project. It requires deciding that ladder inventory is a number someone owns at the portfolio level, the same way headcount or square footage already is, instead of a detail that lives entirely inside whichever site happens to be asked.