A collection of observations and recognitions from across RSE’s engagement work. Part I addresses design-stage conditions; Part II addresses operational-stage conditions.
Permanent access systems carry consequences that span the asset’s lifecycle. The conditions that produce events are most often not equipment failures. They are the consequences of engineering questions that were not asked, were asked of parties whose interests were not aligned, or were addressed at stages of the lifecycle when the answers were no longer flexible.
This page is a collection of observations and recognitions from across RSE’s engagement work. The first section addresses design-stage conditions — the patterns that recur in projects where engineering work is happening or could happen. The second section addresses operational-stage conditions — the patterns that recur in the decision contexts of asset owners, operators, and the institutional architecture around assets.
Extended treatments of these patterns appear in the Articles section.
Neither section is exhaustive. Both are intended to make recognizable, in writing, the engineering conditions that bring RSE engagement into focus.
Most access and fall-protection failures do not occur because equipment failed. They occur because access was never fully considered at the design stage.
Compliance asks whether something meets the minimum. Access readiness asks whether it will actually work — safely — over the life of the asset.
Many access systems appear viable on drawings. They break down when real conditions, constraints, and users are introduced.
“Later” typically means less flexibility, reduced budget, and increased risk. Access is one of the few elements that must be resolved early.
Design-stage access validation is not about fault. It is about identifying exposure while change remains possible.
Access readiness is not a checklist exercise. It requires disciplined evaluation before assumptions harden.
Access systems rarely fail at commissioning. They fail years later — during maintenance, retrofit, or emergency response.
Most access risk is not created by a single decision. It forms through small coordination gaps across disciplines.
Access risk rarely resides within one scope. It exists in the interfaces between them.
Serious access incidents typically trace back to early decisions that were never pressure-tested. The incident reveals the condition — it does not create it.
Access failures rarely surface as headline events. They appear as injuries, workarounds, delays, and near-misses.
Accountability is extending beyond what was built to how serviceable and rescuable it is over time.
Access is often assumed to be addressed. Responsibility is often assumed to be assigned.
If an access system cannot be used safely for routine maintenance, it will eventually be bypassed.
Early access validation is often viewed as optional. Late-stage correction consistently carries greater cost and risk.
Access decisions affect individuals beyond the original project team. The responsibility extends across time.
When access is not resolved early, risk is deferred to the field. To technicians. To responders. To workarounds.
Anchorage, reach, clearance, rescue paths, and sequencing must function together. Fragmented solutions rarely resolve system conditions.
Rescue planning is often addressed last. Its feasibility is determined by early access decisions.
Equipment selection does not resolve system-level access conditions. Geometry, reach, and sequencing are established through design.
Drawings and specifications do not confirm access viability. Unexamined documentation can create false confidence.
The question is not whether something is compliant. The question is whether it works — for everyone required to use it.
RSE does not design access systems or supply equipment. At the design stage, RSE’s role is to test whether access, fall-protection, and rescue conditions hold together — before they become embedded.
As infrastructure and buildings increase in complexity, access-related exposure becomes more difficult to ignore. Early clarity reduces downstream consequence.
Each description below addresses a decision-maker variant within the asset-owner organization. None requires sequence; each is freestanding.
You are responsible for the day-to-day operation of permanent access systems on a building you did not specify, did not procure, and did not install. The systems were in place when you arrived. The documentation you inherited is incomplete. The service company that comes to perform inspections is the same company that came before you, and they do their work in roughly forty-five minutes, and you have never been entirely sure whether what they actually do is what your asset requires.
You have noticed things. The behavior of one of the units under load is not what you would expect. The wire rope guides are showing wear patterns that seem early for the service life of the system. There are areas of the equipment you cannot inspect from the positions you can safely access, and you have begun to suspect that those areas have not been inspected by anyone for some time.
You have raised these concerns through internal channels. The response has been that the equipment is inspected and certified, and that the service company is the same one the building has used for many years. You have observed that this answer does not actually address what you raised.
Independent engineering can be asked the questions you have not been able to get answered. The questions have engineering answers. The answers are available.
You are responsible for multiple buildings, multiple systems, multiple service relationships. Permanent access systems are one piece of the portfolio. They are not the piece you spend the most time on because they are not, on most days, the piece that produces operational problems. Until they do.
You have been through this once before — perhaps not at this building, perhaps at a portfolio property you previously managed. A BMU that had been inspected and certified produced a failure during operation. The investigation that followed revealed conditions that the inspections had not captured. The conversation with the insurer was protracted. The conversation with the owner was more so. The consultant engaged after the failure produced engineering findings that were starkly different from the service company’s reports.
You learned, from that experience, that the routine service relationship is not the same as engineering visibility into the system. You learned that the engineering questions about a permanent access system are not the same as the questions the service inspection answers. You learned that the cost of asking the engineering questions before a failure is materially smaller than the cost of being asked the same questions after one.
You are now in a position where you can ask the engineering questions for the assets currently under your responsibility. Doing so is not a reflection on the service relationship currently in place. It is an exercise of the engineering visibility your role requires.
The asset is part of a portfolio. The asset’s value is part of the portfolio’s value. The asset’s exposure is part of the portfolio’s exposure. You are responsible for what the asset returns and what the asset costs over a holding period that extends across operational cycles you cannot fully anticipate.
Permanent access systems on the asset are a category of risk you carry but do not directly manage. The operations team handles them. The service contracts are in place. The certifications are renewed on schedule. The line items in the operating budget are stable. There is no current evidence of operational distress.
There is also no current independent engineering assessment of the systems’ condition. The certifications are produced by parties whose work is the subject of the certification. The service reports are produced by parties whose interest is the continuation of the service relationship. The lifecycle posture of the systems is a function of representations made by parties with commercial stakes in those representations.
From the portfolio level, this is a category of exposure that compounds. A retrofit event on a major building’s BMU systems is a multi-million-dollar capital event. A safety incident is an event of an entirely different category. Both events are made materially more likely by the absence of independent engineering visibility — and made materially less probable, or at least materially better managed, by its presence.
The cost of obtaining engineering visibility is small relative to the exposure it addresses. The decision to obtain it sits at the asset-management level — not at the building-operations level, where the systems live, but at the portfolio level, where the consequences land.
You represent the principal whose asset this is. The principal does not engage directly with the operational details of the asset’s permanent access systems and would not be expected to. What the principal expects is that the people representing them — you, the broader advisory architecture, the building operations team — have addressed the questions the principal would have asked if the principal had been the operational expert.
The questions you would have asked, on the principal’s behalf, about the permanent access systems are questions that have engineering answers you have not yet obtained. You have not obtained them because the systems are not, at present, producing problems. You have not obtained them because the routine service relationship has continued without disruption. You have not obtained them because there has been no triggering event.
You are aware, however, that representing the principal well is not a matter of waiting for triggering events. It is a matter of having addressed the questions that would otherwise be asked of you after a triggering event. The questions are available now. The cost of having addressed them is small relative to the cost of being asked the same questions in retrospect.
Independent engineering on the asset’s permanent access systems produces a record. The record is the principal’s. Whatever the principal does or does not do with it, the record exists. Your representation of the principal is materially different where the record exists than where it does not.
Your function is to identify, quantify, and address exposures the organization carries. The exposure profile of permanent access systems is structurally distinct from the exposure profiles you address through more conventional risk mechanisms. The systems are infrequent in their loss events; their loss events are severe; the loss events are difficult to anticipate from indicators normally available to risk and insurance review.
The distinction between certification and engineering visibility surfaces wherever the owner’s posture is examined by a party with something at stake in the answer — an insurer at underwriting or at claim, a counterparty in a transaction, counsel after an event. Where documented engineering posture exists, those examinations are answered from the owner’s own record; where it does not, they are answered from representations produced within the service and supply chain. From the corporate-risk side, the same dynamic operates internally: board-level risk reporting on these systems is strengthened by documented engineering posture, and better assembled before the question is asked than in response to a triggering event. The questions have engineering answers, and the record can exist before it is asked for.
The cost of engineering visibility is bounded. The exposure it addresses is not.
The asset is yours. The exposures it carries are yours. The decisions about how it is administered, maintained, and represented are yours — even where you have delegated the operational responsibility to staff, advisors, or institutional structures acting on your behalf.
Permanent access systems on the asset have been in place for some period of time. They were installed at a point when the asset was in a different operational phase than its current one. The original suppliers, installers, and consultants who were present at installation may or may not still be reachable. The institutional memory of how the systems were specified, procured, and accepted may or may not be intact within your organization.
What is certain is that the consequences of an event on these systems will land on you. Not on the supplier who delivered the equipment a decade ago. Not on the installer who completed the work. Not on the consultant who oversaw acceptance. The consequences will land on the entity that owns the asset and is responsible for its operation.
Independent engineering on the systems is not an inspection in the sense of confirming routine condition. It is the establishment of an engineering record — your engineering record — addressing the systems’ current condition, lifecycle posture, and decision-relevant findings. The record exists once it is produced. What you do with it follows from your assessment of your own position. Either way, you are in a different position than you were before the record existed.