What has to be in a construction phase plan

A construction phase plan sets out the health and safety arrangements for a project's construction phase, and under CDM 2015 it has to be in place before construction work starts on any project requiring a principal contractor — which in practice means most multi-contractor sites.

It should cover the project's specific hazards and how they'll be managed, site rules, welfare arrangements, emergency procedures, and how different contractors' work will be coordinated where their activities could affect each other — genuinely specific to the site and the work, not a generic template with the project name changed.

What a strong plan actually contains

• –A description of the project, the work involved, and the key dates and phases
• –Management arrangements — who's in charge of what, and how contractors are expected to communicate with each other and with the principal contractor
• –Site-specific hazards identified for the actual project — ground conditions, working at height, existing services, proximity to the public — not a boilerplate hazard list
• –Welfare arrangements: toilets, washing facilities, rest areas, and how these scale if the workforce on site grows
• –Emergency procedures — fire, first aid, evacuation routes and muster points, specific to the site layout
• –How individual contractors' RAMS will be reviewed and how conflicting activities will be sequenced

Coordinating trades that affect each other

The part of the plan that gets skimmed over most often, and matters most in practice, is the coordination section — how work that could interact dangerously gets sequenced or separated. A roofer working above a groundworks crew, or hot works happening near stored materials, are the kind of interactions a generic template won't anticipate because it doesn't know the site. This is also where a plan earns its keep during a live project: when a new activity is about to start, checking the plan should tell you what else is happening nearby that it needs to be coordinated with, not just what that one activity's own risks are.

Who's responsible for keeping it current

The plan also isn't a fixed document — it should evolve as the project progresses and risks change, which is one of the principal contractor's ongoing responsibilities rather than a box ticked once at the start. In practice this means revisiting it when a new subcontractor joins, when the project moves into a phase with materially different hazards (groundworks giving way to roofing, for instance), or after an incident or near miss reveals a gap the original plan didn't anticipate.

Making sure the plan is actually read

A well-written construction phase plan that sits in a folder in the site office, unread by the subcontractors it's meant to coordinate, isn't doing its job any better than a poorly written one. It's worth building the plan's key points into induction — the site rules, the emergency procedures, the coordination arrangements relevant to that particular trade — rather than relying on new arrivals to read a lengthy document unprompted. A subcontractor turning up for a two-week job is far more likely to genuinely absorb the handful of points that affect their specific work than to read a comprehensive plan cover to cover.

How this differs from a RAMS

It's worth being clear about the distinction, because the two documents are easy to conflate. The construction phase plan is the principal contractor's overarching document for the whole site — hazards, coordination, welfare, emergency arrangements at project level. A RAMS is each individual contractor's own document for their specific task. The plan should reference how different contractors' RAMS need to be coordinated with each other; it shouldn't try to replicate the detail of every individual RAMS within itself, which would make it unwieldy and quickly out of date as different trades' RAMS get updated at different times.

What often gets missed on smaller multi-contractor jobs

The construction phase plan requirement is most visible on large, obviously complex projects, which is exactly why it's easy to under-invest in on smaller ones — a renovation with three trades involved doesn't feel like it needs the same rigour as a large new-build, but CDM 2015 doesn't scale the requirement down just because the project is modest. A short, genuinely specific plan for a small multi-contractor job is far more useful than a long, generic one copied from a bigger project template, and it's usually quicker to produce properly than people assume once the site-specific hazards are actually thought through rather than guessed at.

Reviewing the plan against what's actually happening

A useful habit is to periodically walk the site with the plan in hand and check whether what's written still matches what's actually happening — whether the sequencing described is the sequencing being followed, whether the hazards listed are the ones genuinely present, and whether new activities that have started since the plan was last updated are reflected in it at all. This kind of review tends to surface gaps faster than waiting for a formal review point, because it tests the plan against reality rather than against itself.

Common mistakes

• –Producing the plan once, before work starts, and never revisiting it as the project changes
• –Copying a previous project's plan and swapping the site address without reviewing whether the hazards genuinely transfer
• –Writing the plan at a level of generality that reads correctly but doesn't tell anyone on site anything they didn't already know
• –Treating the plan as the principal contractor's document alone, rather than something every contractor on site should actually understand
• –Losing track of how the plan connects to the project's F10 notification when key details — like the principal contractor — change
• –Trying to fold every subcontractor's RAMS detail into the plan itself, rather than keeping the plan focused on project-level coordination