Written by: Paul Foster, Founder, CEO, OnePlan
Key Takeaways
- Street fair traffic control plans must include a to-scale site map, sequenced detour routes, ADA-accessible paths, emergency access lanes, and a complete signage manifest to meet most U.S. municipal requirements.
- Most jurisdictions follow MUTCD Part 6 standards, with the 11th Edition now in effect and states required to adopt it by January 18, 2026.
- Submission timelines range from 45–60 days for small cities to 90–120 days for large cities, with additional coordination needed for state highway closures.
- Common rejection triggers include generic templates, inadequate ADA provisions, incomplete sign sequencing, and missing emergency access details on the map.
- OnePlan provides a browser-based platform to build accurate, to-scale TCP maps and auto-generate permit documents. Book a demo today to see how it streamlines your next submission.
Core Requirements Every Municipality Expects
Most U.S. municipalities align their TCP review criteria with the MUTCD Part 6 framework, which defines four zones in every temporary traffic control area: the advance warning area, the transition area, the activity area, and the termination area. The 11th Edition of the MUTCD, effective January 18, 2024, is now the federal standard, and states had until January 18, 2026 to adopt it. Any TCP submitted after that date should reference 11th Edition provisions.
Across jurisdictions, a submission-ready street fair TCP is expected to include the following five core elements:
- To-scale site map. A geo-accurate plan shows the event footprint, street closures, vendor placement, stages, and all temporary infrastructure. Generic screenshots are a leading rejection trigger. The map must reflect actual lane widths, kerb lines, driveways, and nearby intersections.
- Detour routes. Clearly marked alternative routes for vehicles displaced by the closure, with advance warning signage sequenced from the first device to the last, per MUTCD Section 6C.03.
- ADA-accessible routes. Continuous, unobstructed accessible paths connect admission, stages, restrooms, food areas, first aid, and exits on firm, stable surfaces. Temporary status does not exempt events from ADA duties under Title II or Title III.
- Emergency access lanes. Unobstructed lanes of sufficient width for fire apparatus and EMS vehicles run throughout the event footprint, with rescue routes clearly drawn on the site map.
- Signage manifest (Bill of Quantities). A complete inventory lists every traffic control device, including signs, cones, barricades, and delineators, with quantities, placement locations, and MUTCD compliance references.
Some jurisdictions, including Nashville, require a licensed engineer’s stamp for closures exceeding seven continuous days, while shorter events may qualify for pre-approved templates. Confirm the stamping requirement with your local transportation department before drafting.
Submission Timelines by City Size
Once you understand what your TCP must include, the next step is planning when to submit it. Permit review windows vary significantly by jurisdiction size, street classification, and the number of agencies involved. Community festivals and parades typically require 3–6 weeks of advance processing, while large-scale public events such as marathons can require 6–12 weeks. The table below provides illustrative ranges. Confirm the exact deadline with your local permitting office, as requirements vary by region.
| Municipality Size | Typical TCP Submission Lead Time | California Example (Illustrative) |
|---|---|---|
| Small city / town (under 50,000 residents) | 45–60 days before event | Many smaller California cities publish 45-day minimums for street fair closures on local streets |
| Medium city (50,000–300,000 residents) | 60–90 days before event | Mid-size California cities with multi-department review (public works, fire, police) commonly require 60–90 days |
| Large city (300,000+ residents) | 90–120 days before event | Los Angeles recommends submitting parade permit applications at least 40 days in advance but must act on any application received at least 5 days prior (waivable), with approval or denial typically within 15 days of a complete application, and arterial closures involving Caltrans add further review time |
City transportation departments recommend treating the minimum notice period as a deadline rather than a target and submitting earlier to allow buffer time for corrections. In California, any closure affecting a state highway requires Caltrans encroachment permit coordination on top of the municipal timeline, so plan for the longer window.
Step-by-Step Workflow to Build Your TCP
This five-step workflow walks you through the full permit-submission process for a street fair TCP. Each step includes a checklist and, where applicable, California-specific notes. Requirements vary by jurisdiction, so verify details with your local authority.
- Build the to-scale site map.
- Open a live satellite or street map base and place the event footprint accurately.
- Mark all street closures, vendor stalls, stages, tents, portable restrooms, and temporary infrastructure to scale.
- Confirm actual lane widths, kerb lines, driveways, bus stops, and fire hydrant locations against the map.
- California note: Many California cities require the site map as a PDF at a specified scale for arterial closures. Confirm the required scale with your city’s public works department.
- Identify all displaced vehicle movements and map alternative routes.
- Sequence advance warning signs from the first device to the last per MUTCD 11th Edition Part 6.
- Confirm detour routes avoid school zones during peak hours, typically 7:00–9:00 AM and 2:30–4:00 PM.
- California note: Closures affecting state routes require a Caltrans-approved detour plan in addition to the municipal TCP.
- Draw a continuous accessible path connecting entry, stages, restrooms, food and beverage, first aid, and exits.
- Confirm surfaces are firm, stable, and slip-resistant, with a maximum running slope of 8.33% (1:12) and cross slope of 2.08% (1:48).
- Ensure barricades do not block curb ramps and that accessible parking spaces connect directly to the accessible route.
- California note: California’s Unruh Civil Rights Act applies alongside federal ADA requirements. Some California cities require a separate ADA access narrative in the permit packet.
- Mark unobstructed emergency lanes on the site map with minimum clear widths sufficient for fire apparatus. Check your local fire department’s requirement, commonly 20 feet minimum in many U.S. jurisdictions.
- Confirm emergency lanes remain unobstructed by vendor stalls, stages, or crowd barriers throughout the event.
- Include EMS staging locations and the nearest hospital route on the plan.
- California note: California Fire Code Section 503 governs fire apparatus access roads. Confirm the applicable local amendment with your city’s fire marshal.
- List every traffic control device, including road closed signs, detour signs, cones, barricades, delineators, and ADA wayfinding signs.
- Record quantities, placement locations, and MUTCD device codes for each item.
- Cross-reference the manifest against the site map to confirm every device shown on the map appears in the inventory.
- California note: California’s MUTCD (CA MUTCD) supplements the federal standard. Confirm which edition your city references before finalizing sign specifications.
Creating Compliant Maps Without CAD or PowerPoint
The most common reason a TCP map fails review is that it is not to scale. A screenshot dropped into PowerPoint with shapes drawn on top does not reflect actual lane widths, and reviewers notice that immediately. CAD solves the accuracy problem but requires specialist training most events teams do not have. Work that takes a full day for eight maps in CAD takes about two hours in OnePlan, according to Sam Wilson, National Operations Manager at Stadium, who used OnePlan to plan Coventry Moves, an event with over 400 road closures across seven procession routes and 110 stakeholders.
With OnePlan, you can place barriers, tents, and more inside its integrated, live planning tool OnePlan’s planning canvas uses a live, zoomable satellite or street map built on leading GIS technology. Every object placed on it, including road closed signs, crowd barriers, cones, tents, ADA route markers, and emergency lane boundaries, stays accurately to scale as you zoom. There is nothing to download, no engineering background required, and no blank canvas to start from.
Beach event planning example inside OnePlan: the base layer is a zoomable satellite or street map, and everything placed on it (tents, stages, crowd barriers, toilets, vehicles, staff, signage, routes) stays accurately to scale as you zoom - Open the event location on the live satellite map base.
- Drag and drop to-scale traffic control objects, such as barricades, cones, signage, fencing, and ADA route markers, from a library of thousands of event-specific objects.
- Use the area and perimeter calculator to confirm emergency lane widths and vendor placement dimensions instantly.
- Export a high-resolution PNG map, up to A0 and print-ready, for the permit packet.
- Export the auto-generated Bill of Quantities as a CSV. Every object placed on the map becomes a line item in the inventory, with quantities calculated automatically.
The North Texas Tribute Jam’s organizer reported that sharing detailed plans for roadblocks, crowd control, and traffic management in OnePlan led to quick approvals from the City of Lewisville’s Health and Safety Department. That outcome, with faster approvals and fewer revision cycles, starts with a map that reviewers can trust on first read.
Festival planning example inside OnePlan: the base layer is a zoomable satellite or street map, and everything placed on it (tents, stages, crowd barriers, toilets, vehicles, staff, signage, routes) stays accurately to scale as you zoom Common Rejection Reasons and Practical Fixes
The table below covers frequent TCP rejection triggers reported by permitting authorities across U.S. jurisdictions, along with the recommended correction for each. Specific standards vary by state and municipality, so confirm requirements with your local authority.
Rejection Trigger Recommended Fix Generic template used instead of a site-specific layout, so the plan does not reflect actual lane widths, kerb lines, driveways, or nearby intersections Build the map on a live satellite base that shows real-world geometry, and confirm lane widths and kerb lines against the map before submission Inadequate pedestrian and ADA provisions, with pedestrians directed onto live roadways, accessible routes blocked by barricades, or curb ramps obstructed Draw a continuous ADA-compliant accessible route on the site map, confirm barricades do not cross curb ramps, and add ADA wayfinding signage to the manifest Incomplete sign sequencing, with advance warning signs not shown in correct MUTCD order from first device to last Map every sign in sequence on the site plan and cross-reference against MUTCD 11th Edition Part 6 device placement requirements for the applicable speed limit Missing or vague emergency access provisions, where emergency lanes are not shown on the map or described only in text without drawings Draw emergency lanes explicitly on the site map with clear width dimensions and confirm with the local fire marshal that the width meets the applicable fire code requirement Inaccurate site measurements, where the plan assumes a lane width or road width that differs from the actual kerb-to-kerb distance Use a to-scale map base and measure distances within the platform before placing any objects. Even a 5% measurement error can cause a multi-month delay. Equipment Rental Manifest Checklist for TCPs
The signage manifest submitted with a street fair TCP must account for every traffic control device on site. The checklist below covers the standard categories. Quantities depend on the specific event layout. Use OnePlan’s auto-generated Bill of Quantities to produce exact counts from the site map rather than estimating by hand.
- Signage: Road Closed signs, Detour signs, Street Closed to Thru Traffic signs, No Parking signs, ADA accessible route signs, directional wayfinding signs
- Barricades: Type III barricades for road closures, Type II barricades for pedestrian channelization, water-filled plastic barriers for vehicle impact protection
- Channelizing devices: Traffic cones, 28-inch minimum for most street-level applications, delineator posts, tubular markers
- ADA devices: Detectable warning surfaces at temporary curb ramps, accessible route surface panels for grass or gravel crossings, ADA parking space markers and van-accessible signage
- Lighting and visibility: Retroreflective sheeting on all devices, flashing warning lights for nighttime or low-visibility conditions, arrow boards for lane transitions
- Support equipment: Sign stands, sandbag ballast, barricade lights, traffic control personnel vests and flags
How to Measure Success for Your Street Fair TCP
A well-built street fair TCP produces measurable outcomes before, during, and after the event. The most immediate benefit is fewer revision cycles. When your plan is accurate and complete on first submission, you avoid the third or fourth round of corrections that can cost you the permit window entirely.
That faster approval path creates a second advantage. Your operations team gains more lead time to confirm equipment rentals and brief traffic control personnel before rates increase or availability tightens. A to-scale map that reviewers and contractors can trust then reduces site visits. When the plan accurately reflects real-world geometry, there is less need to drive out and verify measurements in person.
The Eagle Mountain City events team cut planning time from 8–10 hours down to a few hours per event by moving to a single, to-scale collaborative plan. That same approach makes TCP submissions cleaner and faster for any local government events team.
Frequently Asked Questions
How far in advance should I submit a street fair traffic control plan?
The minimum lead time depends on your city’s size and the streets involved. Small cities typically require 45–60 days. Medium cities commonly require 60–90 days. Large cities with multi-agency review can require 90–120 days or more.
Treat the published minimum as a hard deadline, not a target. Submitting earlier gives you time to address revision requests without losing the permit window. In California, closures affecting state routes require Caltrans coordination on top of the municipal timeline, so add additional buffer for those situations. Always confirm the exact deadline with your local permitting office, as requirements vary by jurisdiction.
Who needs to review and approve a street fair TCP?
Most U.S. municipalities route TCP submissions through at least three departments. Public works or transportation engineering reviews the traffic control plan itself. The fire department or fire marshal checks emergency access lane widths and apparatus routing. The police department handles traffic control personnel coordination and road closure authorization.
Larger cities may also involve transit agencies if bus routes are affected, and state DOT review is required for any closure touching a state-maintained road. Identify all reviewing agencies before you submit and confirm whether each requires a separate application form or can be addressed within a single permit packet.
Can I create a compliant TCP map without CAD software?
Yes. The requirement is that the map be to scale and accurately reflect real-world geometry, not that it be produced in any specific software. OnePlan’s browser-based platform uses a live satellite or street map base built on leading GIS technology, so every object placed on it stays accurately to scale at any zoom level.
You can drag and drop traffic control objects, measure lane widths and emergency lane clearances using the built-in area calculator, and export a high-resolution, print-ready map for the permit packet, all without CAD or engineering training.
What is the most common reason a street fair TCP gets rejected?
The most frequent rejection trigger is a site map that does not reflect actual site conditions, such as using a generic template or a screenshot that assumes lane widths and road geometry rather than measuring them. Reviewers also commonly flag missing or inadequate ADA-accessible route provisions, incomplete sign sequencing, and emergency access lanes that are described in text but not drawn on the map.
The fix for most of these issues is the same. Build the plan on a to-scale map base that reflects real-world measurements, and cross-reference every element on the map against the signage manifest before submission.
Does the MUTCD 11th Edition apply to my street fair TCP?
The MUTCD 11th Edition became effective January 18, 2024, and states had until January 18, 2026 to adopt it. For most U.S. jurisdictions, any TCP submitted after that date should reference 11th Edition provisions.
Some states maintain their own MUTCD supplement. California, for example, publishes the CA MUTCD, and your TCP must comply with whichever version your local authority references. Confirm the applicable edition with your city’s transportation engineering department before finalizing sign specifications and device placement distances.
Ready to Submit Your Next Street-Fair TCP?
A permit-ready street fair traffic control plan requires a to-scale site map, sequenced detour routes, a continuous ADA-accessible path, clearly drawn emergency lanes, and a complete signage manifest. All of this must be assembled and submitted within a jurisdiction-specific window that can be as short as 45 days or as long as 120. Piecing that together across disconnected tools wastes time and invites the revision cycles that cost permit windows.
OnePlan gives city events coordinators, festival organizers, and public-works staff a single browser-based platform to build accurate, to-scale TCP maps on live satellite imagery, produce auto-generated Bills of Quantities, and export print-ready permit documents in hours, not days. From a small community street fair to a large multi-route closure, the same drag-and-drop tools work at every scale, and your first event is free.