Temporary works fail before site teams realise the register is incomplete. While many project teams treat the temporary works register as an administrative list, London Construction Magazine analysis shows that weak register control before work starts is directly causing sequencing uncertainty, permit gaps and avoidable compliance exposure on live construction projects. A temporary works register is not just a schedule of propping, scaffolding, excavations, hoardings, falsework or access systems. It is the control point that shows whether temporary works have been identified, categorised, designed, checked, approved, inspected and authorised before the site relies on them.
Under BS 5975 good-practice procedures, the register becomes part of the management system for controlling temporary works from concept through design, construction, use, modification and dismantling. HSE guidance recognises BS 5975 as an industry consensus route for managing temporary works effectively, even though the legal duty remains with those controlling the work to prevent unacceptable risk. The operational issue is simple: if the register is weak before work starts, the site can move into live construction with missing design briefs, unclear check categories, unconfirmed permits, uncontrolled alterations or incomplete inspection hold points. That is where a document problem becomes a programme and safety problem.
Why The Register Controls The First Real Temporary Works Risk
The first serious temporary works risk appears when a site assumes an item is minor before the design, checking and approval route has been agreed. A good register forces the project team to capture the temporary works item early, define the package owner, assign a design requirement, allocate a check category, identify interfaces with permanent works and record whether the item can be constructed, loaded, modified or removed. Without that structure, responsibility becomes informal and the Temporary Works Coordinator is left trying to manage risk after sequencing decisions have already been made. This is why the register must sit inside the wider BS 5975 temporary works compliance process. The register is not the process by itself, but it is the live index that allows the process to be controlled.
| By the Numbers | Operational Reading & Delivery Risk |
|---|---|
| BS 5975-1:2024 | Current management procedure guidance places stronger focus on controlled temporary works processes, not informal site judgement. |
| One register per controlled project system | Fragmented registers create blind spots across scaffolds, propping, excavations, lifting platforms and specialist subcontractor packages. |
| Design brief before design output | Missing briefs weaken design assumptions, checking routes and responsibility for load cases or interface constraints. |
| Check category before approval | Unclear design checking can delay permits, create late technical queries and expose site teams to uncontrolled temporary works use. |
| Permit before loading or striking | Weak permit discipline can turn a sequencing shortcut into a structural, safety or commercial dispute. |
What Must Be In Place Before Work Starts
Before temporary works start, the register should show enough information for the project team to understand what is being controlled, who controls it and what evidence is required before use. The register should identify each temporary works item, the package or location, the responsible contractor, the Temporary Works Coordinator interface, the design brief status, designer details, design check category, design approval status, required inspection points, permit requirements, loading restrictions, alteration controls and dismantling or striking controls. The practical weakness appears where the register is populated after the work has already started. Once scaffold lifts are installed, excavations opened, props loaded, formwork erected or access platforms modified, the register becomes reactive evidence rather than active control.
Why Design Briefs Decide Whether The Register Is Useful
A temporary works register becomes unreliable when the design brief does not explain the real site condition the temporary works must control. The design brief should define the purpose of the temporary works, load assumptions, dimensional constraints, ground or structural support conditions, sequence of use, interface with permanent works, environmental exposure, access restrictions, loading limitations and any inspection or monitoring requirements. If these details are unclear, the register may show a temporary works item as captured while the actual design risk remains unresolved. That is why the register must connect directly to the temporary works design brief. A register entry without a clear brief can create a false sense of compliance because the item appears controlled while the assumptions behind it remain untested.
Where Check Categories Create Programme Pressure
Temporary works check categories create programme pressure when the site team discovers too late that the design needs a higher level of independent or formal checking. This often happens on packages that appear routine at tender or mobilisation stage but carry serious interface risk in delivery: façade retention, basement temporary works, propping to existing structures, crane mats, scaffold ties, excavation support, back-propping, temporary openings, temporary gantries, roof access systems or falsework supporting fresh concrete loads. A strong register makes the check category visible before procurement, fabrication, installation or permit approval begins. That link to temporary works design check categories is what prevents late-stage checking disputes from becoming site delay events.
Why Permit Control Fails When The Register Falls Behind
Permit control fails when the register does not show whether the temporary works are ready to be loaded, used, altered or struck. A permit-to-load, permit-to-use, permit-to-proceed or permit-to-strike depends on evidence that the temporary works have been designed, checked, installed, inspected and accepted against the relevant sequence. If the register is incomplete, the permit system can become a signature exercise rather than a hold-point control. This matters most where subcontractor pressure, programme acceleration, logistics restrictions or night-shift sequencing creates pressure to move before the evidence is complete. In those conditions, the register is the control mechanism that helps the Temporary Works Coordinator resist unsafe or commercially risky shortcuts.
What The Register Should Prove During Audit Or Incident Review
During an audit, dispute or incident review, the temporary works register should prove that the project team controlled risk before the temporary works were relied upon. The strongest registers show chronology. They show when the item was identified, when the design brief was issued, who designed it, how it was checked, when it was approved, who inspected it, what permit was issued, whether alterations were controlled and whether the dismantling or striking sequence was authorised. Weak registers usually fail in the same places: generic descriptions, missing ownership, late design checks, no permit reference, unclear inspection status, uncontrolled alterations and poor links between drawing revisions, site instructions and actual installation conditions.
Source Basis For This Briefing
This article is based on current HSE temporary works guidance, HSE temporary works FAQs and BSI information on BS 5975-1:2024 management procedures for the control of temporary works. The official position is important because BS 5975 is a recognised industry consensus approach to temporary works management, while the underlying legal requirement remains effective control of risk by those responsible for the work. In practical terms, the register becomes one of the clearest evidence tools for showing whether that control existed before the temporary works were constructed, loaded, altered or removed. The full contractor implications, sequencing risks and mitigation strategies are included in today’s London Construction Magazine briefing.
Evidence-Based Summary
A temporary works register appears to be an administrative document, but its real function is to prove that temporary works risks were identified and controlled before the site depended on them. The interaction between design briefs, check categories, permit controls, installation inspections and alteration records determines whether BS 5975 procedures remain defensible in practice. Where the register falls behind the live sequence, contractors face avoidable exposure through delayed permits, unclear responsibility, unsafe assumptions and weakened audit evidence.
|
Expert Verification & Authorship: Mihai Chelmus
Founder, London Construction Magazine | Construction Testing & Investigation Specialist |
