Temporary works design: British Standard BS 5975 and why the TWC role matters

Most people outside construction have never heard of temporary works, and that is precisely the problem. Scaffolding, excavation support, falsework, propping, formwork, crane pad foundations, trench boxes — none of these appears in the finished building, yet all of them stand between a project’s workers and some of the most dangerous conditions the industry produces. Temporary works failures account for a disproportionate share of construction’s serious incidents, not because the engineering is hard — it usually is not — but because the work is treated as routine, delegated by default and left to whatever person happens to be standing nearby with a phone and an opinion.

The British industry’s answer to this pattern is BS 5975, the code of practice for temporary works procedures. It does not tell you how to design a trench or size a prop; it does something more important — it defines the management framework that ensures every temporary structure is designed by a competent person, checked by an independent one, approved before use and inspected during it. At the centre of that framework sits a role with an unglamorous title and outsized importance: the temporary works coordinator, the TWC. Understanding how the standard works and why that role exists is the difference between a site where temporary works are a managed discipline and one where they are a recurring near-miss waiting for statistics to catch up.

What counts as temporary works: wider than you think

The definition surprises even experienced site staff. Temporary works is not just scaffolding and excavation — it is anything constructed to support the permanent works or the site during construction, and its scope is systematically underestimated. The categories that commonly catch teams out:

Excavation support. Trench boxes, sheet piling, king post walls, battered slopes — anything that keeps the ground where it was while the permanent work takes shape.
Falsework and formwork. The temporary structures that support concrete until it cures and takes over its own load-bearing role; falsework failures during concrete pours are among the industry’s most catastrophic incident types.
Propping and shoring. Loads imposed on existing structures during demolition, refurbishment or weakening works — the needle in this haystack is that the prop’s load must be assessed by someone who understands the structure receiving it, not merely the prop carrying it.
Crane and plant platforms. Outrigger pads, hardstands and tower crane foundations — arguably the most commonly unengineered high-consequence items on modern sites.
Scaffolding, hoardings and façade retention. The familiar face of temporary works, but governed by the same framework as everything else.

The unifying principle across all these categories is the one BS 5975 enforces: nothing goes up without a design or a design-check justification, regardless of how familiar the item is. Familiarity is precisely the trap — the scaffold that has been erected a thousand times is the one that fails on the thousand-and-first erection because the loading changed and nobody asked.

BS 5975: what the standard actually requires

The code of practice, currently BS 5975:2019+A1:2022 in its latest form, does not provide design formulas — that territory belongs to the supporting guides and Eurocodes. What it provides is the procedure, and the procedure has teeth. Its core requirements:

The appointment. Every organisation involved in procuring or erecting temporary works must appoint a temporary works coordinator in writing, with the authority to carry the role out. On larger or more complex projects, a temporary works supervisor may support the coordinator.
The design. Temporary works must be designed by a competent temporary works designer — who may be in-house, from the supplier, or a specialist — with the design scope, loading assumptions and limitations defined clearly.
The check. Designs must be independently checked before use. The standard defines check categories that scale the rigour of the check to the risk and complexity of the design: simple, standardised items get a lighter check; novel, complex or heavily loaded designs get a full independent check by a separate competent person.
The permit. Temporary works must be formally accepted before use — the permit to load — confirming that the erection has been inspected and the design’s assumptions hold on site.
The register. A temporary works register tracks every item from design through erection, checking, use, inspection and removal — the document trail that makes the framework auditable rather than aspirational.

The structure of these requirements mirrors the quality system of permanent-works engineering, and that is not an accident. The standard’s central insight is that temporary works failures are almost never failures of calculation — they are failures of process: a design that never happened, a check that a supplier’s brochure stood in for, a permit signed by whoever was available, an inspection skipped on a Friday afternoon.

Design classifications and the check categories

Not every temporary structure needs the same depth of scrutiny, and the standard’s classification system is where its practicality lives. The check categories scale with consequence:

Check category	Typical application	Who checks	Depth of check
Category 0	Standard, pre-approved equipment used as intended	Coordinator confirms compliance with the standard design	Confirmation, no formal recalculation
Category 1	Simple designs with low consequence of failure	A competent person, not the designer	Review of design basics and assumptions
Category 2	Conventional designs of moderate complexity	Independent competent person	Full design review with calculations
Category 3	Complex, novel or high-consequence designs	Independent competent designer or checker, often specialist	Comprehensive design scrutiny, potentially external review

The categories exist to concentrate scrutiny where the consequences and the uncertainty concentrate — a trench box used to a manufacturer’s guidance is a Category 0 matter, while a propping scheme above a live railway is unambiguously Category 3. Getting the classification wrong in either direction creates its own failure: over-classifying buries the site in paperwork that erodes compliance culture; under-classifying hands a critical design to a check that was never designed to catch its flaws.

The TWC: what the role actually does

The temporary works coordinator is not a design engineer and is not, by definition, the person who does the calculations. The role is a management one — and its value lies exactly there, in the gap between design and site that most failures occupy. The core duties:

Owning the procedure on site. Ensuring the framework — appointments, designs, checks, permits, register — operates as the standard intends, and that deviations are identified rather than absorbed.
Controlling the interface. Temporary works are the great crossroads of a project: the piling contractor needs the excavation supported before the crane arrives, the concrete crew needs the falsework accepted before the pour, the demolition contractor needs the propping engineer to speak to the structural engineer. The TWC is the person through whose hands those interfaces pass.
Verifying competence. Confirming that designers, erectors and checkers hold the competence their role requires — and that supplier designs actually cover the loading case the site will impose, which they routinely do not.
Inspection and monitoring. Ensuring erected temporary works are inspected before use and at defined intervals during it — because loads change, weather changes, and the excavation that was safe on Monday may not be safe on Thursday after rainfall.
Authority to stop the job. The role carries, implicitly and explicitly, the power to prevent loading or use of temporary works that do not comply — and the quality of a site’s temporary works culture is measured almost entirely by whether that authority is ever exercised and respected.

The reason the TWC matters — the reason the standard insists on a written appointment with real authority — is that without someone whose job it is to ask the questions, the questions do not get asked. A project manager has forty competing priorities; the TWC has one. The role exists to make sure that one thing is someone’s job.

How temporary works actually fail

The incident record is remarkably consistent across decades and countries, and the patterns repeat because the underlying pressures repeat. The dominant failure modes:

No design at all. The most common precursor to serious failure: equipment chosen from experience, loadings assumed, erection improvised. The trench that collapses rarely collapses because the box was miscalculated — it collapses because no one checked that the box suited the soil, the depth and the surcharge from the stockpile parked beside it.
Supplier designs misused. Standard designs for props, trench sheets and shoring arrive with conditions — spacing, depth, soil type, surcharge limits. Sites routinely exceed those conditions without realising that the design’s validity ended at the exceeded condition.
Loads added by other trades. Temporary works designed for one loading case acquire another: materials stacked on a prop-free zone, plant travelling alongside an excavation, facade loads hung on a scaffold that was never designed for them. Each addition is small; the reserve factor is not infinite.
Changes in ground and weather. Rainfall changes pore pressures; a dewatering system failing changes the excavation’s stability overnight. Temporary works designed in August and inspected in November are standing in a different structure.
Erection errors on standard systems. Even correctly designed proprietary systems fail when erected with missing components, wrong bracing or incomplete ties — which is why the permit-to-load inspection exists rather than trusting the erector’s word.

What these patterns share is process failure rather than calculation failure — which is why the standard attacks the process, and why the TWC’s management role, unglamorous as it sounds, is where the lives are actually saved.

Procurement and the contract problem

The commercial structure of temporary works is a recurring source of trouble, because responsibility for design is frequently assumed rather than assigned. The standard is clear that the party procuring the temporary works is responsible for ensuring the design exists and is checked — but on real sites, subcontractors buy shoring, scaffolding contractors design their own scaffold, and groundworks packages carry excavation support with varying degrees of formality. The working disciplines that keep procurement from becoming the weak link:

State the responsibility in the contract. Who designs, who checks, who coordinates across packages — written into the works information rather than assumed from trade custom.
Demand the design, not the brochure. Supplier «standard designs» are valid only within their stated conditions; requesting the actual design document and its assumptions is the coordinator’s routine duty.
Watch the interface packages. Where one subcontractor’s temporary works loads another’s permanent works — or rests on another’s temporary works — the design responsibility for the interface is the most commonly orphaned item in construction.

The sites that manage this well make temporary works a standing item at coordination meetings rather than a fire fought when it ignites; the ones that do not discover, usually during an audit after an incident, that nobody can find the design for the excavation support that has been in the ground for four months.

Conclusion

Temporary works are the most dangerous unglamorous part of construction: structures that carry lives, disappear on completion and attract less scrutiny than anything else on site. BS 5975 exists because the industry learned, repeatedly and expensively, that the failures were not failures of engineering — they were failures of management, of the missing design, the rubber-stamped check, the permit signed by the nearest available adult.

The framework the standard provides is straightforward: appointed coordinators, competent designers, independent checks scaled to consequence, permits before loading and a register that makes the whole chain auditable. And the role that holds it together — the temporary works coordinator — matters for the simplest of reasons: someone has to own the process, and in construction, whatever belongs to everyone belongs to no one. The sites that treat temporary works as a managed discipline, with the TWC empowered and the paperwork real, are not just compliant — they are measurably safer, because the standard’s requirements are, in the end, a checklist of the exact moments where temporary works decide whether people go home.