Construction traffic management plans that get approved

A construction traffic management plan is written for a highway engineer. That single point explains most of the ones that get refused. Developers hand the task to whoever has capacity, the document arrives as prose with a location plan and an assurance that deliveries will be managed sensitively, and the highway authority replies asking for the swept paths, the wheel washing detail and the condition survey.

Councils secure the plan by condition, usually a pre-start condition on a major permission. Discharge takes up to eight weeks and the consultation with the highway authority sits inside that period. On a scheme with a fixed contractor start date, the plan is on the critical path from the day permission is granted.

What the highway authority is actually assessing

Three questions, in this order. Can construction vehicles reach the site without conflict at the points where the route is tight. What happens to the public highway while they do it. And who is accountable when something goes wrong.

Everything in a good plan answers one of those.

The routing section needs a drawing showing the approved route from the strategic or primary road network to the site access, with the pinch points identified and swept path analysis at each. A junction that a rigid tipper can turn but an articulated delivery cannot is the sort of detail that decides whether the plan is accepted.

Vehicle types belong in a table with dimensions and expected daily numbers by phase. Demolition, bulk earthworks, substructure, superstructure and fit-out generate very different traffic, and a plan that gives one average figure across the whole programme has not been thought about.

Peak periods deserve their own line. A scheme generating twelve movements a day on average may generate forty during a concrete pour, and it is the pour that blocks the street. Engineers respond well to a plan that identifies those days in advance and proposes a specific arrangement for them, such as an early start under a temporary agreement or a holding area away from the site.

The third question, accountability, is answered by names and telephone numbers rather than by policy language. A council fielding complaints wants a person to ring.

The content list that gets a plan discharged

• a construction programme with phases and dates, and vehicle numbers per phase
• an approved routing plan with swept path drawings at every constrained junction
• the site access arrangement, including visibility splays and any temporary crossing
• wheel washing or road sweeping provision, with the location shown and the frequency stated
• on-site parking for operatives and visitors, with a number, and a statement of what happens when it is full
• delivery management, including a booking system and permitted delivery windows
• pedestrian and cyclist management past the site, with hoarding lines and any temporary footway closure
• a highway condition survey before works start and a commitment to repeat it at completion
• working hours, and the arrangements for any out of hours delivery
• a named site contact with a telephone number, and a complaints procedure
• the temporary traffic management approvals being sought and from whom

Two of those carry more weight than their length suggests. The highway condition survey protects both sides, because it settles later arguments about who broke the kerb. And the named contact converts an anonymous nuisance into a manageable one, which is exactly what a council with a ward member on the phone wants.

Where plans fail

Operative parking is the most common failure. A plan that says operatives will be encouraged to use public transport, on a site with no parking and a residents' parking zone next door, will be rejected by any experienced engineer. Give a number, show where the vehicles go, and if the answer is a leased car park half a mile away with a minibus shuttle, say that.

The second is the swept path gap. Plans routinely include swept paths at the site access and nowhere else. The problem junction is usually 400 metres away where the route crosses a narrow bridge or turns into a residential street.

The third is mismatch with the rest of the application. Where the transport assessment assumed one access and the construction plan uses another, the inconsistency is obvious and it undermines both documents.

The fourth is the plan written before a contractor was appointed. Generic documents describe an idealised site with unlimited compound space and a considerate delivery driver, and engineers recognise the template on sight. Where the contractor is still unknown at discharge stage, say so and set the parameters the eventual contractor must work within, then submit a revision naming them.

The fifth is silence on the highway works. If the scheme needs a new bellmouth, the CTMP should say that a section 278 agreement is being progressed, name the stage it has reached, and explain how construction traffic operates before it is complete.

Sequencing against the other approvals

1. Identify every highway related condition on the decision notice and the deadline attached to each.
2. Appoint the contractor early enough to write the plan around a real programme.
3. Commission swept path analysis at the same time as the site layout is finalised.
4. Start the section 278 process in parallel, because it has its own technical approval stage.
5. Apply for any temporary traffic regulation order or street works permit well before the plan is discharged.
6. Submit the CTMP with the highway condition survey already carried out.

Temporary road closures and traffic management on the public highway sit under separate legislation and require notice periods that can run to several weeks. A plan that assumes a lane closure will be available on demand is optimistic.

Coordination with other works on the same network is the hidden constraint. Highway authorities run permit schemes that sequence street works across a district, and a utility diversion booked by somebody else can block the week you wanted. Ask the street works team early what is already in the diary for the roads on your route.

Where the CTMP stops and other documents start

Dust, noise, vibration, hoarding, lighting, waste and community liaison belong in a construction management plan unless the council has asked for one combined document. Keeping them separate makes both easier to discharge, because the highway authority reviews one and the environmental health team reviews the other.

Where a scheme is large enough to need both, write the traffic plan first and cross-refer from the wider document, so that vehicle numbers are stated once.

Illustrative example: a 60 unit scheme on a former depot, accessed from a residential street with a 3.5 metre carriageway pinch at a railway bridge. The plan routes all construction traffic in one direction through the bridge with a banksman during peak delivery windows, provides a bookable delivery slot system with a maximum of eight heavy goods vehicle movements a day, locates wheel washing inside the compound with a road sweeper on call, and parks 22 operative vehicles on the cleared eastern half of the site until superstructure begins. This example is illustrative.

PlanScope drafts a construction traffic management plan structured to UK planning policy, with the standard sections laid out and site specific facts flagged where they need confirming. The swept paths, the survey and the contractor's programme still have to come from the project team.

This is general guidance, not legal advice. Check the position with your local planning authority or a qualified professional before relying on it.

PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval.