As-built drawings: when they’re required and what they protect you from

“As-built” scaffold drawings are the record of what was actually erected, not what was intended at tender stage.

If the scaffold is built exactly to a compliant standard configuration (e.g., TG20/TG30) and nothing changes, you may never need an as-built drawing. But real sites aren’t that polite.

Where scaffolds are bespoke-designed (or drift into bespoke through changes), as-builts become a practical way to prove:

• the scaffold matches the engineered intent,

• the tie/bracing strategy on site is what was assumed,

• and everyone is working from the same “single source of truth”.

This matters because HSE is very clear that scaffolds must be tied/braced/stabilised, and ties must be installed/managed correctly through erection, use, and dismantle.

What is an as-built drawing, in scaffold terms?

An as-built typically captures:

• final geometry (lifts, bay sizes, returns, bridges, cantilevers)

• tie locations and tie types actually installed (including any “no-tie zones” workarounds)

• bracing and stability provisions actually used (plan bracing, façade bracing, buttresses/rakers)

• any approved deviations from the original design (with revision references)

• key limitations (SWLs, “no sheeting unless redesigned”, max loading, etc.)

Think of it as: “this is what you’ve got”, in a format that can be audited and managed.

When are as-built drawings required?

There isn’t one single line in legislation that says “every scaffold must have an as-built drawing”. What the law does require is that scaffolds are safe, competently designed/erected/managed, and inspected with records kept.

So in practice, as-builts are typically required in one (or more) of these situations:

1) The scaffold is bespoke-designed (or has bespoke elements)

If you have calculations and drawings for a non-standard arrangement, then any deviation needs managing. An as-built becomes the clean way to record the final agreed configuration.

2) The scaffold has been altered from the original design

If ties move, lifts change, openings are formed, a loading bay appears, or sheeting gets added—those are not “minor tweaks”. HSE’s guidance around ties and stability is explicit, and stability changes are exactly where undocumented alterations become dangerous.

3) Third-party governance or approvals are involved

Common examples:

• rail environments, highways interfaces, public protection

• client / insurer requirements

• principal contractor temporary works procedures

Even when not strictly a legal “must”, it’s often a contractual requirement because it provides traceability.

4) Handover and ongoing management needs clarity

Many incidents aren’t caused by the original erection—they happen after the scaffold has been “lived on” for weeks: impacts, weather, unauthorised mods, gradual tie loss, and load creep. Regular inspections are required (before first use, every 7 days, and after events likely to affect safety), and those inspections are only as good as the reference information available.

What as-builts protect you from (the practical/legal pain)

1) “We thought it was tied…”

As-builts make tie patterns and bracing explicit. That matters because ties must be within SWL and managed correctly, and tie removal requires equivalent restraint.

2) Variation disputes and blame ping-pong

If a scaffold differs from the design, everyone can end up pointing at everyone else. An as-built locks down what was agreed, and when.

3) Inspection ambiguity

Work at Height Regs require inspection records to be made and kept (until the next inspection, and longer in certain cases).
As-builts support inspectors by giving them a stable baseline: “inspect against this configuration”.

4) “It changed over time” risk

As-builts help change control. If the scaffold evolves, you can track revisions rather than ending up with a Frankenstein scaffold that nobody can honestly describe.

What we need from you to produce an as-built quickly

If you want an as-built without it turning into a drama, send:

• photos of each elevation (wide + close-ups at tie zones)

• confirmation of what changed vs the issued design (marked-up PDF is perfect)

• tie details: tie types used, substrate, any tested anchors (if applicable)

• any added items: sheeting/netting/signage, loading bays, hoists/chutes

• dates: when alterations occurred and whether the scaffold remained in use

This lets us update the drawing set and clearly show revision control.

How to keep as-builts manageable (and cheap)

• Treat any stability / loading / wind “add-on” as a design review trigger.

• Don’t wait until the end of the job when nobody remembers what changed and why.

• Keep one “live” drawing pack in circulation (controlled PDF) and kill off old versions.

The thing to remember

A scaffold doesn’t become safer because a drawing exists — it becomes safer because everyone is working to the same engineered reality, and changes are controlled.

As-builts are the paperwork version of that discipline.