Written by: Paul Foster, Founder, CEO, OnePlan
Key Takeaways
- Street fair permit maps are often rejected for missing scale, emergency access lanes, vendor numbering, or ADA routes, which triggers costly revision cycles.
- A single, live, to-scale map keeps fire, police, and public works reviewers aligned on one accurate layout and reduces approval delays.
- Following a six-step workflow that covers checklists, scale, infrastructure, crowd and ADA routes, exports, and uploads produces permit-ready maps.
- Using a GIS-based platform preserves real-world dimensions, creates a Bill of Quantities, and exports print-ready files that meet municipal portal requirements.
- Book a demo with OnePlan to streamline your next street fair permit submission and keep every stakeholder working from the same plan.
Why Accurate Permit Maps Matter for Approvals
Municipal reviewers compare permit maps against a checklist. If a map lacks a north arrow, omits fire-lane widths, or places vendor stalls without numbering, the application is returned for revision. Each revision cycle can cost days or even weeks and may push an event past its submission deadline.
A single, live, to-scale map prevents many of these issues at the source. When fire, police, and public works all view the same plan, they avoid conflicting versions and last-minute surprises on event day. Digital permitting workflows that centralize all reviewers on one application have been shown to cut approval time significantly, and the same principle applies to the maps those applications include.
Who Benefits Most from This Street Fair Map Guide
This guide serves community-events coordinators, special events coordinators, and public works managers who must submit an approvable street fair permit map. It applies whether you plan a one-off block party or a recurring annual fair. Requirements vary by municipality, so cross-reference every step with your local permitting portal before submission.
Step 1: Gather Required Map Elements from the City Checklist
Start by downloading the specific checklist from your city’s permitting office before you open any planning tool. Most portals list required map elements alongside the application form. For example, Portland’s Bureau of Transportation requires a traffic control plan or workspace diagram for temporary street use permits involving sidewalk or travel lane closures. That rule is city specific, and your city may have a similar requirement.
Most checklists include a north arrow, a scale bar, street names and block boundaries, emergency vehicle access lanes with widths labeled, vendor or booth numbering, ADA-accessible routes, entry and exit points, and the name and date of the event. Collect all of these requirements before you start drawing your map.
Step 2: Set the Correct Scale and North Arrow on a Live Map Base
Technical reviews often fail because maps are not drawn to scale. A shape dropped onto a screenshot in PowerPoint or Excel has no real-world dimension, so a reviewer cannot verify that a fire lane is 20 feet wide if the drawing has no scale.
Planning on a live satellite or street map base solves this problem. In OnePlan, the canvas is a zoomable satellite or street map built on leading GIS technology, so every object placed on it stays accurately to scale as you zoom. The north arrow follows the map orientation. Set your map view to the street closure area, zoom to the block level, and your scale is correct before you place a single object.
Step 3: Place Infrastructure, Vendor Stalls, and Emergency Lanes to Scale
With the map base set, drag and drop infrastructure onto the street in the positions you plan to use on event day. Place tents, stages, food and beverage stalls, crowd barriers, fencing, portable toilets, generators, and signage in their actual locations. Each object should reflect its real-world footprint, so a 10×10-foot vendor tent should occupy 10×10 feet on the map.
Label vendor stalls sequentially so everyone can reference the same booth by number. Number each booth so the permit reviewer, fire marshal, and event-day staff all speak the same language. Mark emergency vehicle access lanes and label their widths. Use OnePlan’s area and perimeter calculator to confirm that access lanes meet the minimum width your city requires. Verify that figure with your local fire department, because it varies by jurisdiction.
Before moving to crowd-flow planning, confirm that your map includes every element municipal reviewers expect to see. Use this checklist to make sure nothing is missing:
- North arrow visible and correctly oriented
- Scale bar or scale notation included
- All street names and block boundaries labeled
- Emergency vehicle access lanes drawn and widths labeled
- Vendor stalls placed to scale and numbered sequentially
- Entry and exit points marked
- Portable toilets and first-aid stations located
- Generators and power sources positioned
- Crowd barriers and fencing drawn to scale
- Event name, date, and organizer contact on the map face
Step 4: Add Crowd-Flow and ADA Routes
Crowd flow and ADA accessibility routes often go missing from first-draft maps, and reviewers frequently reject maps for this reason. Draw pedestrian flow paths as directional routes on the map that show how attendees move from entry points through the fair and back out. Identify any pinch points where crowd density could build.
Mark ADA-accessible routes separately and show a continuous, unobstructed path from accessible parking or transit stops through the event footprint to key amenities. Confirm that vendor stalls and infrastructure do not block this route. OnePlan’s crowd capacity calculator lets you outline any standing area and instantly see its capacity, which supports defensible spacing decisions for both general crowd areas and accessible zones.
Step 5: Generate the Bill of Quantities and Export Print-Ready Files
A complete map in OnePlan automatically feeds into the Bill of Quantities. Every object placed on the map appears in a structured inventory that you can export to Excel or CSV. You see how many linear feet of crowd barriers, how many vendor tents, and how many portable toilets you need, so procurement and contractor coordination flow directly from the map without re-keying data.
For the permit submission, export a high-resolution PNG at print-ready size. OnePlan exports up to A0, which covers the needs of any municipal review. Include a legend on the exported file. Most portals accept PDF or high-resolution image files, so check your city’s accepted formats before exporting and convert the file type if needed.
Step 6: Upload to the City Portal with Supporting Documents
Most municipal portals require the site map along with supporting documents such as proof of insurance, a noise permit application, a vendor list, and sometimes a separate traffic control plan. Madison, Wisconsin, for example, requires a site map and, if applicable, a route map to be attached at the time of online submission for street use permits. Submitting without them creates an incomplete application.
Upload your exported map file, attach all required supporting documents, and save a copy of the submission confirmation. If the portal allows it, share a live view-only link to your OnePlan map with the reviewing departments so they can zoom in on any element without waiting for a revised PDF.
Because submission portals and lead times vary significantly by city, the examples below show how requirements can differ and help you gauge the range you may encounter.
Example City Portals (Illustrative Only)
Lead times and submission requirements vary widely across U.S. cities, so a process that works in one city may not match another. The table below shows illustrative examples of portal contacts and typical lead times for four cities, giving you a starting point to understand the range of requirements you may see. Deadlines, file formats, and contact details change frequently, so always verify current requirements directly with the relevant city portal before submitting.
| City | Portal / Contact (Illustrative) | Typical Lead Time (Illustrative) | Notes (Illustrative) |
|---|---|---|---|
| New York City, NY | NYC Mayor’s Office of Citywide Event Coordination (CECM) | 60–90 days before event | Verify current requirements at nyc.gov, large events may require additional agency sign-offs |
| San Francisco, CA | SF Entertainment Commission / SF Film Commission | 45–60 days before event | Verify at sf.gov, street closures require SFMTA coordination |
| Columbus, OH | Columbus Special Events Office | 30–60 days before event | Verify at columbus.gov, site map required with application |
| Portland, OR | PBOT Temporary Street Use Permitting | Varies by closure type | Traffic control plan must use PBOT basemap tool, non-compliant submissions rejected |
Common Challenges and Troubleshooting
Inaccurate layouts. If a reviewer flags that vendor stalls overlap a fire lane or that the map does not match the street’s actual geometry, the cause is usually a non-scaled drawing. Rebuilding on a live map base fixes this because objects placed in OnePlan reflect real-world dimensions, so a 20-foot fire lane measures 20 feet on the map.
Missing fire-lane widths. Reviewers need labeled dimensions, not just a visible gap between objects. Use OnePlan’s area and perimeter calculator to measure the lane width, then add a text label directly on the map before exporting.
Version-control issues. When maps travel by email as static files, different departments often review different versions. OnePlan’s real-time collaboration keeps every stakeholder on the same live plan. Share a password-protected view-only link so fire, police, and public works always see the current version without anyone resending files.
Wrong file format on upload. Some portals accept only PDF, while others require a specific image resolution. Export from OnePlan at the resolution the portal specifies, then convert to PDF if needed before uploading.
Measuring Success with Your New Map Workflow
A well-executed permit map workflow produces measurable results that you can track over time. After your first submission using a to-scale map, monitor these indicators to see how your process improves:
- Fewer re-submission cycles per application
- Reduced back-and-forth emails with reviewing departments
- Fewer on-site visits needed to verify dimensions
- Faster approval turnaround from submission to sign-off
- Accurate Bill of Quantities that reduces over-ordering of barriers and fencing
Eagle Mountain City, a local government customer, cut event planning time by 70% from 8–10 hours down to a few hours per event after moving to OnePlan. The city built one comprehensive, to-scale map shared across fire, police, and facilities departments instead of creating separate maps for each. OnePlan has powered 200,000 events in 150 countries, from community street fairs to the Olympics.
Frequently Asked Questions
How far in advance should I submit a street fair permit map?
Lead times vary significantly by city and event size. Smaller cities may process applications in two to three weeks, while major cities like New York often require 60 to 90 days. Check your local portal for the current deadline and build in extra time for at least one revision cycle. Submitting a complete, to-scale map with all required elements on the first attempt gives you the best chance to avoid delays.
What scale should a street fair permit map use?
Most municipal guidelines do not prescribe a single scale ratio, but they do require that the map be drawn to scale and include a scale bar or notation. A common working scale for a single city block is 1 inch equals 20 feet, while larger events that cover multiple blocks may need a smaller scale to fit on a standard page. When you plan on a live map base in OnePlan, scale follows the map’s geo-accuracy, and the area calculator confirms real-world dimensions before you export.
Which departments typically review a street fair permit map?
In many U.S. cities, the reviewing departments include the fire marshal or fire department, the police department, public works or transportation, and the parks department if the event uses park land. Some cities route applications through a single special events office that coordinates all departmental reviews internally. Sharing one live plan with all reviewers, rather than sending separate PDFs, keeps everyone on the same version and speeds up the process.
What is the minimum width for an emergency vehicle access lane on a street fair map?
Local fire codes set minimum fire-lane widths, and those requirements vary by jurisdiction. Many U.S. cities require 20 feet of unobstructed width, but that figure is not universal. Confirm the required width with your local fire marshal before finalizing the map. Once you confirm it, use OnePlan’s area and perimeter calculator to measure the lane on the map and label the dimension clearly before exporting.
Can I reuse the same permit map for a recurring annual street fair?
Yes, and reusing a base map can save significant time for recurring events. In OnePlan, you can duplicate a previous event’s plan, update the date and any layout changes, and export a fresh set of permit documents without rebuilding the plan. This approach works especially well when the street layout stays the same year to year but vendor assignments or infrastructure positions shift slightly.
Plan Your Next Street Fair the Easy Way
Static maps created in PowerPoint, Excel, or Canva often cause permit rejections and wasted revision cycles. A single, accurate, to-scale map built on a live street or satellite base gives every reviewer the same layout, the correct dimensions, and the documentation they need to approve your event.
OnePlan is the drag-and-drop platform that keeps every element to scale on a live map base, auto-generates the Bill of Quantities, and exports high-resolution, print-ready files for any municipal portal. Your first event is free and can deliver the same kind of time savings Eagle Mountain City achieved.