How to Create a Traffic Control Plan for Special Events

Written by: Paul Foster, Founder, CEO, OnePlan

Key Takeaways

• A traffic control plan (TCP) is a scaled diagram required by permitting authorities to manage vehicle and pedestrian movement around special events that affect public roadways.
• Every TCP must address eight core elements including event boundaries, the four MUTCD TTC areas, traffic control devices, personnel, ADA pedestrian routing, emergency access, detour routes, and stakeholder notification.
• Accurate TCP diagrams are drawn to scale on current maps and include all four TTC areas plus device placement, ADA paths, emergency corridors, and personnel positions to avoid rejection.
• Common mistakes such as undefined closure limits, missing taper calculations, incomplete pedestrian routes, or non-compliant diagrams cause permit delays and revisions.
• OnePlan provides a browser-based platform that lets event teams create accurate, to-scale TCPs with auto-generated device counts — book a demo today to streamline your next permit submission.

Eight Essentials Every Traffic Control Plan Must Cover

A complete TCP covers eight core elements. Each one has a clear objective, specific inputs, and decisions that influence whether a reviewer approves or rejects the submission.

1. Event boundary and roadway context. Define the exact begin and end points of every closure using street names, posted speed limits, lane widths, and intersection geometry. Undefined limits are among the most common reasons TCPs are rejected, because reviewers cannot confirm what is open or closed. With the limits documented, you can decide which roads close fully and which remain partially open.
2. The four MUTCD Temporary Traffic Control (TTC) areas. Every TTC zone must address advance warning, transition, activity, and termination areas in sequence. MoDOT guidance illustrates this four-area structure as the foundation of any compliant TTC plan. Roadway classification and speed determine device type and spacing in each area, so gather those inputs before you start drawing.
3. Traffic control devices. List every sign, cone, barrel, barricade, arrow board, and channelizing device by type, quantity, and placement. Use MUTCD Part 6 device standards as your reference. Decide where you need retroreflective devices and where illuminated devices are required for night operations.
4. Traffic control personnel. Identify flaggers, law enforcement officers, and event marshals by position and shift. Base this on your staffing plan and post assignments. Decide where a flagger is sufficient and where a uniformed officer is required at an intersection.
5. ADA-compliant pedestrian routing. Show the full detour path with surface type, curb ramps, and night visibility. Use the existing sidewalk network and accessible route standards as inputs. Decide whether to install temporary ramps or redirect crossings to existing accessible locations.
6. Emergency access corridors. Mark dedicated lanes or routes for fire, EMS, and law enforcement that remain clear throughout the event. Confirm these with fire department and EMS access requirements. Decide whether emergency access passes through the event footprint or around it.
7. Detour routing. Detour routes must be evaluated for pavement condition, capacity, and geometrics, and state routes should be used where available. Use the alternative road network and turn restrictions as inputs. Decide whether one detour loop works for all traffic or whether different origins need separate routes.
8. Stakeholder notification. Document which agencies have been notified: city traffic engineering, police, fire, EMS, transit authority, and neighboring businesses. Special event TCPs typically require coordination with local law enforcement, fire and EMS agencies, and transit authorities, with approval timelines set by municipal permitting processes. Use an agency contact list and submission deadlines to decide whether you need a pre-event coordination meeting.

Practical takeaway: A TCP that addresses all eight elements gives reviewers what they need to approve on first submission. Missing any one of them, especially ADA routing or emergency access, almost always triggers a rejection.

Five Core Components of Temporary Traffic Control

The MUTCD defines four sequential TTC areas for every temporary traffic control zone: advance warning, transition, activity, and termination. A fifth, cross-cutting category, devices and personnel, operates across all four areas. Here is how each one works in a special event context.

1. Advance warning area. Drivers first learn that conditions ahead have changed in this area. Place signs, flashing beacons, or changeable message signs upstream of the event footprint. On urban streets at 40 mph or more, MoDOT guidance calls for 350 feet between advance warning signs, and on rural highways the first sign is typically placed 1,500 feet or more from the activity area. For a street festival in a city grid (illustrative example for an urban jurisdiction, so verify with your local authority), three sequential warning signs at 350-foot intervals provide a common starting point.
2. Transition area. Traffic shifts from its normal path into the modified path in this area. Tapers, which can be merging, shifting, or shoulder, guide drivers using cones or channelizing devices. Merging tapers must be at least length L, calculated as WS/60 for speeds at or below 40 mph, where W is the offset width and S is the speed limit. Shifting tapers require at least 0.5 L, and shoulder tapers require at least 0.33 L.
3. Activity area. The activity area contains three sub-zones: the work space (closed to road users), the traffic space (where road users are routed), and the buffer space (lateral and longitudinal separation between the two). For a road race finish line, the work space is the finish chute, the traffic space is the redirected lane, and the buffer is the separation between them. Longitudinal buffer lengths range from 115 feet at 20 mph to 730 feet at 70 mph, so posted speed directly affects how much space you must reserve.
4. Termination area. Traffic returns to its normal path after passing the event in this area. It typically includes a downstream taper and an END ROAD WORK sign. Many special event TCPs overlook the termination area, yet reviewers expect it for a complete, compliant submission.
5. Devices and personnel. Signs, cones, barrels, barricades, arrow boards, and flaggers operate across all four areas. Device selection depends on roadway speed, event duration, and time of day. When your event runs after dark, that time-of-day factor triggers a dedicated set of requirements: retroreflective performance, arrow board brightness, lighting placement, and increased inspection frequency are all required considerations for night visibility.

Practical takeaway: Reviewers check that all four areas appear on the diagram and that device spacing matches the posted speed. Plans that skip the termination area or use incorrect taper lengths almost always come back for revision.

Step-by-Step: Drawing a Permit-Ready TCP Diagram

A permit-ready TCP diagram is drawn to scale on a current aerial or street map base. The following steps produce a diagram that satisfies most permitting authorities. Requirements vary by jurisdiction, so confirm details with your local DOT or city traffic engineering office.

1. Obtain a current aerial or satellite image of the event area at a scale that shows individual lanes and intersections clearly.
2. Establish a scale bar and north arrow on the diagram.
3. Mark the event boundary with exact street addresses or GPS coordinates at begin and end points.
4. Draw each of the four TTC areas in sequence using standard MUTCD symbology.
5. Place every traffic control device to scale, labeled by type and MUTCD sign code where applicable.
6. Show the ADA-compliant pedestrian detour as a continuous, unbroken path with accessible crossing points marked.
7. Mark emergency access corridors in a distinct color or line weight.
8. Show the detour route for displaced vehicle traffic with directional arrows.
9. Identify all flagger and officer positions by symbol and shift.
10. Add a legend that defines every symbol used on the diagram.
11. Include a title block with event name, date, submitting organization, and plan version.
12. Confirm the diagram is print-ready at the size required by the permitting authority, commonly 11×17 inches or larger.

Practical takeaway: A 12-item diagram checklist, covering scale bar, north arrow, event boundary, four TTC areas, devices, ADA route, emergency access, detour, personnel positions, legend, and title block, covers the elements most reviewers check first. OnePlan’s drag-and-drop platform keeps every checklist item present and to scale on a live map base, so your exported file is ready for submission.

Start your first TCP in OnePlan free, or book a 15-minute demo to see how the checklist comes to life on screen.

Traffic Control Plan Software Options Compared

TCP diagrams are produced using a range of tools. At one end, planners use PowerPoint, Excel, Canva, Photoshop, Google Maps, or internal static, top-view screenshots and plan files. These tools are not to scale, so accurate device placement and taper length calculations are impossible. At the other end, CAD and AutoCAD deliver precision but require specialist training and significant cost.

OnePlan sits between these two extremes. It is a browser-based platform where anyone can drag and drop MUTCD-compliant traffic control objects, such as cones, signs, barriers, arrow boards, and flagger positions, onto a live satellite or street map that stays accurately to scale at any zoom level. Every object placed on the map feeds an auto-generated Bill of Quantities, so the device count for procurement matches the diagram exactly. Plans export as high-resolution, print-ready maps suitable for permit submissions.

Stadium, a UK security and traffic management firm, used OnePlan to plan Coventry Moves, an event with over 400 individual road closures across 7 procession routes and 110 stakeholders. Creating eight traffic management maps dropped from a full day in CAD to about two hours in OnePlan.

At the North Texas Tribute Jam, organizer Evelin Costa found that sharing detailed plans for roadblocks, crowd control, and traffic management in OnePlan meant getting the necessary approvals from the City of Lewisville’s Health and Safety Department quickly and without headaches.

OnePlan has powered more than 200,000 events in 150 countries, from local road races to Formula 1 circuits. It runs in a browser, requires no software installation, and avoids the learning curve of CAD tools, while your first event is free.

See how OnePlan simplifies TCP creation by booking a 15-minute demo at oneplan.io.

Practical takeaway: Effective TCP software produces a to-scale diagram, generates a device count automatically, and exports a print-ready file without relying on a CAD specialist or repeated site visits to verify measurements.

Common Mistakes That Get Traffic Control Plans Rejected

Most TCP rejections stem from missing logic, clarity, or proof that the plan can be built and maintained safely, not from a single device error. These issues usually show up as gaps in how closures, access, and protection connect on the diagram, which is why the following mistakes appear so often.

• Undefined begin and end points. Prevention: include exact street addresses or GPS coordinates at every closure limit.
• Incomplete sign sequences. Prevention: list every sign in order with its MUTCD code, placement distance, and mounting height.
• Missing taper and buffer details. Prevention: calculate taper length using the MUTCD formula and document the basis in the plan notes.
• Ignored access points. Prevention: account for every driveway, ramp, and side street within the TTC zone and show how each is handled.
• Non-continuous pedestrian routing. Prevention: trace the ADA pedestrian detour from end to end on the diagram. Gaps in the path are a common rejection trigger.
• No emergency access corridor. Prevention: mark a dedicated emergency route and confirm it with fire and EMS before submission.
• Absent inspection and change-control process. Prevention: field changes that alter footprint, access, or protection strategy require re-approval, a change log entry, crew briefing, and re-inspection before work resumes.
• Missing PE seal where required. Prevention: submitting without a required Professional Engineer seal results in automatic rejection. Confirm whether your jurisdiction requires PE certification before submission.
• Diagrams not to scale. Prevention: use a platform that places objects on a live map base rather than a static image, so device spacing reflects real-world distances.

Practical takeaway: Run the 12-item diagram checklist from the earlier section against every submission draft. If any item is missing, the plan is not ready to submit.

Local Jurisdiction Requirements Checklist

TCP requirements vary significantly by state, county, city, and roadway classification. The guidance in this article reflects general MUTCD principles, and your local authority may impose additional or different requirements. Before submitting, verify the following with your local DOT, city traffic engineering office, or permitting authority:

• Submission deadline, because some jurisdictions require 30 or more days’ notice and others process standard applications within 10 business days
• Whether a PE seal is required for your roadway classification and event type
• Required diagram format and print size
• Whether multi-agency sign-off is needed, such as city traffic engineering plus state DOT for events crossing jurisdictions
• Specific ADA pedestrian routing standards beyond MUTCD minimums
• Whether a pre-event coordination meeting with police, fire, and EMS is mandatory
• Post-event traffic dispersal plan requirements

Practical takeaway: Treat the MUTCD as the floor, not the ceiling. Local jurisdictions routinely add requirements on top of federal standards, and a plan that meets MUTCD but misses a local rule will still be rejected.

How to Measure TCP Process Success

A well-executed TCP process produces measurable improvements beyond permit approval. The indicators below signal that your process is working.

• Fewer revision cycles. First-submission approval, or approval with minor comments only, shows that the plan addressed reviewer requirements completely.
• Faster approvals. Shorter review timelines reflect a diagram that is clear, complete, and to scale, which reduces the back-and-forth that delays permits.
• Reduced site visits. When measurements are validated on a to-scale map before anyone goes to the site, the number of physical verification trips drops. The Beirut Marathon cut roughly 20 pre-event site visits per year down to two by planning remotely on accurate maps.
• Stronger stakeholder alignment. When police, fire, EMS, and city traffic engineering all review the same live plan rather than separate static files, conflicts surface earlier and are resolved before submission rather than on event day.
• Accurate device procurement. An auto-generated Bill of Quantities that matches the diagram means the right number of cones, signs, and barriers arrives on site, with no shortfalls and no surplus.

Practical takeaway: Track revision cycles and approval timelines across events. A downward trend in both provides the clearest signal that your TCP process is improving.

Frequently Asked Questions

How far in advance should I submit a traffic control plan for a special event permit?

Submission deadlines vary by jurisdiction. Some cities require a TCP at least 30 days before the event, and others ask for 60 or 90 days for large-scale events with significant road closures. A small community 5K in a single municipality may have a shorter window than a multi-stage road race crossing several jurisdictions. Contact your local city traffic engineering office or DOT as early as possible, ideally three to six months out for complex events, to confirm the exact deadline and whether a pre-submission meeting is required.

Who needs to be involved in creating a traffic control plan?

The core team typically includes the event organizer or race director, a traffic management professional, and representatives from the local police department, fire department, and EMS. For events on state highways, the relevant state DOT district office must also be involved. Transit authorities need notification if bus routes are affected. For large events, a pre-submission coordination meeting with all agencies is common and sometimes mandatory. Bringing these stakeholders into the planning process early reduces surprises during permit review.

Does a traffic control plan need to be drawn by a Professional Engineer?

Requirements depend on jurisdiction, roadway classification, event duration, and traffic volume. Some states and cities require a PE seal on any TCP affecting a state highway or arterial road. Others accept plans prepared by a certified flagger supervisor or traffic control technician for lower-volume local streets. Always confirm PE requirements with your permitting authority before investing time in a diagram, because submitting without a required PE seal results in automatic rejection.

What is the difference between a traffic control plan and an event site plan?

A traffic control plan focuses specifically on how vehicle and pedestrian movement is managed on public roadways adjacent to or through the event footprint, including closures, detours, signage, devices, and personnel. An event site plan covers the internal layout of the event itself, such as stage placement, vendor positions, crowd areas, fencing, toilets, parking, and ingress and egress routes. Most permit packages require both. OnePlan handles both in a single platform, so the road closure diagram and the internal site layout share the same to-scale map base and can be exported separately for the relevant reviewing agencies.

Can I reuse a traffic control plan from a previous year’s event?

A previous year’s TCP is a useful starting point, but it should not be submitted unchanged. Road conditions, construction, signal timing, and jurisdiction requirements can all change year to year. Review the plan against current street geometry, update device placements to reflect any changes, confirm that ADA routing is still continuous, and recheck submission requirements with the permitting authority. In OnePlan, you can duplicate a previous event plan and update it on a current satellite map base, so the geometry reflects what is actually on the ground today rather than what was there last year.

Conclusion

A permit-ready traffic control plan covers the four MUTCD TTC areas, all required devices and personnel, a continuous ADA pedestrian route, a clear emergency access corridor, a documented detour, and stakeholder notification, all drawn to scale on a current map base. Plans built in PowerPoint, Canva, or on static screenshots cannot meet that standard because nothing in them reflects real-world distances. CAD can meet it, but it requires specialist skills that most event teams do not have.

OnePlan gives race directors, festival producers, and local government events teams a drag-and-drop platform that produces accurate, to-scale, print-ready TCP diagrams and an auto-generated Bill of Quantities. The time savings Stadium achieved, and the approval speed the North Texas Tribute Jam experienced, show what happens when TCP diagrams are built on accurate, to-scale maps from the start. The same platform that supports community road races and Formula 1 circuits gives your team the tools to create permit-ready TCPs without specialist CAD training.

Start your first TCP free at oneplan.io, or book a demo to see the platform in action.