Network Rail scaffolding: what triggers a CAT III check?
On rail jobs, “it’s only a scaffold” is the sort of sentence that ends with a possession overrun and a very grumpy Asset Protection Engineer.
Network Rail projects sit inside a formal engineering assurance / technical approval culture. Where temporary works (including scaffolding) could affect the operational railway, you’re often into independent checking and formal submissions — not just a drawing and a handshake.
A useful rule of thumb is:
If scaffold failure could affect the railway (people, trains, assets, access/egress, or interfaces), expect a higher assurance route — commonly including a CAT III independent check and the relevant Network Rail forms/submissions.
First: what do we mean by “CAT III” in this context?
Across UK temporary works practice, BS 5975 is commonly used to define design check categories. A Category 3 check is the highest level, used for complex/novel/high-risk temporary works and requires independent checking by an appropriately competent, separate organisation/team.
On Network Rail schemes, that level of checking is frequently expected because the consequence of failure is high.
The big triggers for CAT III checking on Network Rail scaffolding
1) Proximity to operational railway and consequence of collapse
If collapse or instability could:
foul the running line,
impact OLE/third rail/signalling,
strike a train,
or drop materials onto track,
…you’re typically in CAT III territory (or at least you should be planning for independent checking and formal acceptance).
2) Anything over / spanning / cantilevering towards the track
Common examples:
bridging scaffolds spanning near/over track
cantilevers, needles, or over-sailing arrangements
protection fans and crash decks with trackside exposure
temporary roof structures near/over the railway footprint
These are “high consequence” configurations because a local failure can become a railway incident fast.
3) Temporary works that provide structural support (not just access)
If the scaffold is doing more than access — for example:
façade retention interface
propping, shoring, or support to elements during works
support to plant/MEWP runways or significant hung loads
…that’s squarely in temporary works engineering. HSE is explicit that temporary works need to be planned and managed.
4) Heavy loads, dynamic loads, or concentrated loads
Designers get nervous (for good reason) when you introduce:
heavy-duty loading bays (palletised materials)
hoists, lifting points, gin wheels with meaningful duty
impact/dynamic effects from loading operations
On rail jobs, the question is always: what’s the worst credible event, and what happens if it goes wrong?
5) Increased wind actions: sheeting, netting, wrap, large signage
Sheeted or wrapped scaffolds behave like a wind structure. Tie forces and global stability demand can climb sharply.
If you’re adding sheeting/wrap in a rail environment, you’re often beyond “standard scaffold thinking” and into engineered temporary works with independent checking expectations.
6) Novel / non-standard analysis or “first time we’ve done this” geometry
If the arrangement is:
unusual in load path,
irregular in plan/elevation,
dependent on advanced modelling,
or includes atypical connection details,
…BS 5975 logic points you towards CAT III checking.
7) Third-party technical approval / formal acceptance routes
Network Rail’s Asset Protection / engineering submission processes include forms and defined roles for design and checking.
For example, the Network Rail “Design Check” concept is described as an independent check of the design to confirm adequacy and compliance with technical requirements, and references use of formal forms/sign-off in the CIV/003 family.
Also, Network Rail’s Developer / Asset Protection guidance explicitly flags that a formal temporary works submission (e.g., an F003) may be required where failure could adversely affect railway assets, and notes linkage to a Category 3 design check as good practice in those scenarios.
The “CAT III” reality check (so you don’t get blindsided)
Two projects with identical scaffolds can land differently depending on:
distance to running lines and electrification
what’s underneath/adjacent (critical assets)
possession arrangements and public interface
consequence of failure (risk profile)
So the best approach is: assume CAT III may be required early, then confirm with the project’s engineering assurance route (often via the CRE/CEM/Asset Protection Engineer pathway).
What we need from you (so we can design it and package it for rail assurance)
To move quickly and avoid rework, send us:
Location + rail interface
Exact location, access constraints, possession type (if known)
Proximity to running lines/OLE/third rail/critical assets
Any “no-go” zones and protected assets
Scaffold purpose + configuration
Access only vs support / propping / temporary roof / bridging
GA sketches, heights, spans, plan shape, returns/cantilevers
Working platform classes and intended loading
Add-ons that change the engineering
Sheeting/netting/wrap/signage
Hoists, loading bays, chutes, lifting points, hung loads
Stability + ties
Tie restrictions, substrate type, anchor approach/testing assumptions
Any requirement for buttressing/rakers/kentledge/anchorage
Assurance requirements
Known submission requirements (e.g., forms, independent check expectations)
Any client/PC standards that sit alongside Network Rail requirements
What it protects you from
Getting the CAT III / technical approval route right up front protects you from:
last-minute “this needs independent check” stoppages
redesign during possession windows
rejected submissions because assumptions weren’t evidenced
programme slippage caused by assurance paperwork being treated as an afterthought
Key takeaway
On Network Rail projects, CAT III isn’t a badge of honour — it’s a risk-control mechanism. If scaffold failure could affect the railway, or the scaffold is complex/non-standard/wind-sensitive/heavily loaded, plan for independent checking and formal acceptance from day one.