By Uwe Janssen · Rauch Safety & Engineering · Las Vegas, Nevada
A small set of façade access decisions must be made early in design — in concept and schematic, while massing, structure, and façade geometry are still fluid — because they are decisions the rest of the project progressively locks in place. They are: the access strategy itself, including whether the need for suspended access can be reduced or designed out; the geometry the access system must serve — reach, clearance, and coverage of the actual façade; the structural provisions the system will load — supports, anchorages, tracks, and the paths those loads take; the accommodation the system needs to live on the building — parking, storage, deployment, and maintenance access to the access system itself; and the feasibility of rescue, which is set by geometry long before it is written into a procedure. Equipment can be selected later. These conditions progressively harden because they are properties of the building, not of the machine — and each subsequent design phase converts them from choices into constraints.
The asymmetry that makes early design decisive
Façade access occupies a small part of the design process and decades of an asset’s operating life. Decisions made during concept and delivery continue to govern systems that will later be operated, maintained, inspected, and — when necessary — used for rescue across the service life that follows. The asymmetry is not anyone’s failure; it is the structure of how buildings get built. But it explains why access conditions deserve deliberate early attention rather than residual attention: the parties with the most freedom to shape the outcome hold that freedom at exactly the phase when access is easiest to treat as a detail for later.
Early design preserves the top of the hierarchy
The hierarchy of controls — eliminate the hazard, substitute it, engineer it, administer it, and only then protect against it with equipment on a person — has a property that design teams are well placed to use and operating teams are not: its upper levels are design-stage controls. Eliminating an access need — detailing a façade element to be maintained from inside, placing plant where it can be reached without exposure, choosing materials that change the maintenance cycle — is possible while the design is fluid. By the time an asset is operating, elimination and substitution are largely spent options; what remains is engineering already embedded, plus procedures and personal equipment layered onto whatever the geometry allows. Early design is therefore not simply the easiest time to address access. It is the phase in which the design team has the greatest ability to apply the full hierarchy — before building geometry itself becomes the constraint.
What hardens, and in what order
The decisions above do not all lock at once; they harden in sequence, each with a closing window. The access strategy and the geometry harden first, with massing and façade design — once the building’s form is settled, future access systems must work within that form, and equipment selection must then compensate for, rather than shape, the geometry it inherits. Structural provisions harden with the structural design: the loads a suspended system imposes — including the load cases that govern anchorages and restraint — either enter the structural calculations while those calculations are open, or arrive later as a retrofit analysis on a structure designed without them. Accommodation hardens with the roof and plant layout: a machine that has no adequate place to park, deploy, or be maintained will spend its life negotiating with the building around it. And rescue feasibility hardens with all of the above — a rescue path is a geometric fact before it is a procedural one, and a later procedure must work within the geometry it inherited. In design reviews I have conducted, rescue was addressed after the geometry that governed it had already closed — the plan was written to fit the constraint, rather than the constraint being shaped while it could be.
Where the access question lives — and where it goes missing
Façade access is a systems condition in a discipline-structured process. Its ingredients sit in different scopes: geometry with the architect, loads with the structural engineer, plant and roof arrangement with the services engineers, equipment with a supplier that may not yet be appointed, and operation with the owner’s facilities or operating team. Where no party is explicitly assigned the access question as a whole — not the components, the whole — each discipline can resolve its own scope correctly and the system-level condition can still fail to close, because the condition lives in the interfaces: between reach and structure, between parking and plant, between anchorage and rescue path. This is the same boundary behavior described in the failure modes article in this series, observed at the other end of the lifecycle: conditions concentrate where scopes meet. In design, the practical control is explicit ownership — someone holds the access system as a system, across the phases in which it hardens, with the standing to raise interface conditions while they are still design questions.
Equipment standards do not resolve building geometry
Suspended access equipment is designed and certified under equipment standards — EN 1808 for machines built to the European framework, with the US regime governing installed powered platforms addressed in the first and third articles in this series. Those standards establish requirements for the equipment and its relevant interfaces. Conformity of the machine does not, by itself, establish that the building geometry provides the reach, clearance, coverage, accommodation, and rescue conditions the completed access strategy requires: a conforming machine can still be installed on a building whose geometry does not provide the access outcome the project requires. Machine conformity and access adequacy are different propositions. This is why the correspondence between equipment and asset, examined at acceptance testing in this series, begins earlier than acceptance: the geometry the machine will be asked to serve is a design-stage output, and by acceptance it is simply a fact being verified.
The practical posture for a design team
The posture follows from what hardens. Name the access strategy in concept design — including the elimination question, asked while it can still be answered. Assign explicit ownership of the access system as a system, with the interfaces in scope. Carry the access loads into the structural design while it is still developing, rather than introducing them later as conditions the completed structure must accommodate. Reserve the accommodation — parking, deployment, storage, maintenance access — in the roof and plant layout as a design requirement, not a residual. Test rescue as geometry, at the phase where geometry can still move. And document the basis of each of these while the reasoning is current — the same principle the acceptance article develops for the machine applies to the building side: the design-stage record of what was decided, and why, becomes the baseline for the asset’s access posture. The itemized questions behind each of these belong to a checklist discipline, applied phase by phase — which is what a structured design-stage instrument is for.
Rauch Safety & Engineering works with design teams at this stage through the Rauch Access Readiness™ Assessment — an independent engineering evaluation of whether access, fall-protection, and rescue conditions hold together before they become embedded — and publishes the Comprehensive Design Guide for Work-at-Height & Access Systems, a phased reference and project checklist available through the RSE site. RSE does not design access systems and does not supply equipment; its role at the design stage is to test whether the conditions hold, while the design can still respond.