Traffic control plans
Drawings and method statements for managing traffic around an active infrastructure build — required by most permit authorities.
A traffic control plan is the deliverable that explains how a build will manage road, rail, or pedestrian traffic during construction. Often required as a condition of permit approval — the authority needs to see the build won’t strand traffic, block emergency access, or create hazards.
We prepare traffic control plans for fibre route builds, EV charging hub installations, and broader civil infrastructure projects.
Why traffic control plans matter (and aren’t optional)
Most permit-issuing authorities — state DOTs, city engineering departments, county roads, railway operators — require a traffic control plan as a condition of approval for any work that affects active traffic. The reasons are practical:
- Public safety — work zones with poor signage cause crashes
- Traffic flow — uncoordinated lane closures create gridlock and emergency response delays
- Liability allocation — an authority approving construction without seeing how traffic will be managed accepts unbounded liability for what goes wrong
- Coordination across concurrent projects — multiple construction projects in the same area need plans that don’t conflict
A weak or missing traffic control plan stops permit approval. The plan isn’t paperwork — it’s the engineering the authority approves before letting work proceed.
Standards we work to
Traffic control plans are built to whichever standard governs the relevant authority. Most common in our work:
- US — MUTCD (Manual on Uniform Traffic Control Devices, FHWA) — the federal baseline for all US public road work
- State DOT supplements — most states publish a supplement to MUTCD with state-specific requirements (California MUTCD, Texas TMUTCD, Florida MUTCD, etc.)
- County and city standards — local authorities sometimes have their own additional requirements
- UK — Chapter 8 of the Traffic Signs Manual (DfT) — the equivalent for UK road works under NRSWA
- Railway operator standards — for works adjacent to active rail (BNSF, UP, Network Rail)
The standard governs everything from sign sizes and types to lane taper geometry to flagger positioning.
What’s in a traffic control plan
A typical plan covers:
- Site location and context — where the work is, what road class, what speed limit, what daily traffic volume
- Work zone definition — boundaries of the active work area and the buffer zones around it
- Lane closure scheme — which lanes close, when, with what taper geometry
- Signage plan — every required sign with location, type, and timing
- Signalling and flagging — where flaggers are positioned, signal phasing where temporary lights are used
- Detour routes — for full road closures, the alternative route with signage
- Pedestrian and cyclist provisions — work zones on roads with active pedestrian or cycle traffic need explicit alternative paths
- Emergency access — confirmation that ambulance, fire, and police access is maintained
- Method statement — sequence of works, durations, restoration
- Phase plans — for works that move along a route, separate plans for each phase
Inputs we need
A traffic control plan needs:
- Construction work scope and method — what’s being built, how, with what equipment footprint
- Schedule — when work is happening, hours of work, total duration, weekend / overnight constraints
- Route or site context — typically from the construction or permit pack
- Authority requirements — the specific standard the plan needs to meet
- Special restrictions — peak-hour exclusions, school zone restrictions, event windows
Output formats
Plans deliver as:
- DWG drawings for authorities requiring CAD submission (most US DOTs)
- PDF report including drawings, method statement, sign list
- Authority-specific form sets where the authority publishes templates
Common pitfalls in outsourced traffic control work
Generic templates that miss state-specific requirements. California MUTCD differs from Texas TMUTCD, which differs from MUTCD federal. A plan that uses generic MUTCD where a state supplement applies gets returned. We build per-state templates and use them.
Missing pedestrian and cyclist provisions. Older traffic control work often defaults to vehicle-only thinking. Modern authorities require explicit pedestrian and cyclist accommodation. We include these as standard, not as add-ons.
No phase plan for moving works. A single-phase plan for a route build that moves along the corridor doesn’t reflect reality. We build phase plans where works are non-stationary.
Sign list mismatched to drawings. When the drawing shows signs that aren’t on the sign list, or vice versa, the authority returns the plan. We maintain consistency between drawings and sign lists through automated cross-check before submission.
Typical timelines
- Single-site short-duration — 1-2 weeks from project context delivery
- Linear route project with phasing — 3-6 weeks
- Complex multi-jurisdiction — 6-10 weeks
Authority approval cycles run on top — from a few days for routine works to several weeks for complex closures.
How we deliver
Traffic control plan work runs onshore-led for authority-specific requirements with offshore production support for drawing build-out and sign list assembly. Senior engineers handle authority interpretation and approval-cycle response.
Talk to us about a traffic control plan
Tell us the construction project, the authority, and the schedule. We’ll come back with scope, price, and timeline within two business days for typical projects.
Typical deliverables
- Traffic control drawings (lane closures, detours, pedestrian routes)
- Method statements for the build sequence
- Signage and signalling plans
- Authority-ready submission format
- Revisions through the approval cycle
- Multi-phase plans where works extend across stages
Who buys this
Construction PMs and project owners whose permit authority requires traffic management as a condition of approval.
Talk to us about delivery options
Tell us what you need delivered, what your timeline is, and what format the downstream team needs the output in. We'll come back with scope, price range, and proposed approach.