Written by: Paul Foster, Founder, CEO, OnePlan
Key Takeaways
- Municipal festival site maps must be georeferenced, dimensionally accurate, and include boundaries, utilities, infrastructure, crowd areas, and emergency access to satisfy every reviewing department.
- A repeatable 7-step workflow, from defining boundaries and marking utilities to placing infrastructure and planning egress, removes last-minute revisions and failed inspections.
- Real-time collaboration on a single live plan prevents version chaos and keeps fire, police, public works, and vendors working from the same document.
- Accurate to-scale placement enables precise Bill of Quantities exports, procurement accuracy, and faster permit approvals across jurisdictions.
- OnePlan provides the purpose-built platform that makes this workflow accessible to any city events team, so see how OnePlan streamlines permit-ready festival mapping.
What Municipal Festival Site Mapping Means in Practice
Municipal festival site mapping creates a to-scale, operational layout of a city-managed event space that satisfies the documentation requirements of every reviewing department: fire, police, public works, parks and recreation, and licensing. A permit-ready site map is not a sketch or a screenshot. It is a georeferenced, dimensionally accurate plan that shows boundaries, utilities, infrastructure, crowd areas, emergency access, and vendor placement, all in one document that every stakeholder can read and act on.
Most city events teams still build these maps in PowerPoint, Excel, Canva, Photoshop, Google Maps, or internal static, top-view screenshots and plan files. None of those tools are to scale, none support real-time collaboration, and none generate the quantities and exports that permit reviewers expect. Teams then face repeated site visits, siloed department plans, and approval delays that cost time and money.
7-Step Municipal Festival Site Mapping Workflow
Step 1: Define Site Boundaries and Street Closures
Begin by establishing the legal footprint of your event. Draw the outer perimeter of the event area on a georeferenced map base, then overlay every street closure, parking restriction, and access point that requires a permit.
Most city permitting offices review this information before any other element. Asheville, NC, for example, requires that parking closures be clearly identified on the event site plan, and site plans for events requesting street closures often include the location and number of affected meters or parking spaces. Requirements vary by jurisdiction, so confirm expectations with your local permitting office.
Key decisions at this step include whether the perimeter requires fencing or barricades, how many access gates are needed, and which streets require formal closure notifications. These decisions directly inform your notification obligations. In Asheville, NC, events involving road closures require documented notification to impacted addresses, a process that depends on having an accurate boundary map first.
Once your boundary and closures are finalized, ensure the map includes a north directional arrow and surrounding street names with one-way indicators. These elements are standard requirements for permit submission and help reviewers understand orientation at a glance.
Step 2: Mark Underground Utilities
Identify what sits underground before placing any infrastructure. Utility conflicts are one of the most common causes of last-minute site plan revisions because they remain invisible until something goes wrong.
Municipalities often prohibit staking, spiking, or digging on public property for event site elements because of risks to underground utilities including hydro, gas, and irrigation lines, and they require the use of non-penetrating weights instead. This prohibition means you must know exactly where utilities run before deciding where to anchor tents, run cable matting, or position generators, since each of these may involve ground contact or weight distribution that conflicts with underground lines.
To identify these constraints early, contact your local utility notification service (811 in the United States) before finalizing any infrastructure placement. Overlay the utility data on your site map so that every department reviewing the plan can see clearance zones. This step also informs your electrical plan, since site plans can include electrical layouts for vendors and stages that specify power requirements for each location.
Step 3: Place Infrastructure with Accurate Quantities
With boundaries confirmed and utilities marked, place every physical element of the event. Include stages, tents, vendor booths, generators, portable restrooms, fencing, crowd barriers, signage, and vehicles. Every object must be dimensionally accurate and positioned to scale.
Permitting requirements often specify that site plans must show the location and dimensions of physical equipment including stages, vendors, booths, tents, signs, barricades, portable toilets, and vehicles. Santa Clara requires an Event Diagram detailing the size, dimensions, and location of all event setups, including power locations, tents, and staging. Requirements vary by jurisdiction, so verify details with your local authority.
Accurate placement at this step also drives procurement. When every object on the map is to scale, you can generate an exact inventory, including how many feet of crowd barrier, how many portable restroom units, and how many tent segments you need. That inventory becomes your order list and your budget baseline. This approach removes the guesswork that causes over-ordering or costly last-minute additions.
Industry best practice calls for approximately one toilet per 75–100 attendees at day events, with at least 5% of total units being ADA-compliant and distributed across all major zones including entrances, stages, and exits. ADA-compliant units must sit on firm, stable surfaces with sufficient maneuvering clearance. Always confirm local ADA and accessibility requirements with the relevant authority.
Step 4: Plan Crowd Flow and Emergency Egress
Crowd flow and emergency egress are the elements most likely to trigger a revision request from fire or police reviewers and the elements most likely to cause harm if they are wrong.
Festival disasters frequently originate from flawed venue layouts that funnel crowds into choke points, blind corners, dead-ends, or pinch points, generating dangerous compressive forces once density exceeds safe thresholds. The 2010 Love Parade in Duisburg, Germany, is the most cited example. Twenty-one people died and more than 500 were injured when a single tunnel entrance and exit route created a fatal bottleneck.
Walk through your site map during the design phase to identify and remove pinch points before construction. Emergency access lanes at least 4–6 feet wide must be incorporated into festival site plans and kept clear at all times to allow ambulances, fire, and police vehicles to reach any point on the grounds. Tampa specifically requires 20-foot-wide fire lane clearances in all areas along with the location of all fire hydrants.
Use OnePlan’s arrival calculator and exit calculator to estimate queue lengths, exit capacity, and flow rates before committing to a layout. These free tools use exit width, crowd size, and flow rate to surface potential bottlenecks at the planning stage, not on event day.
ADA-compliant accessible routes must connect parking to entrances, activity areas, restrooms, and exits. Any gate, opening, or passage along an accessible route at a temporary event must maintain a minimum clear width of 32 inches, with double gates recommended at high-traffic points to support two-way movement. Always verify ADA requirements with the relevant local authority.
Step 5: Create Stakeholder-Specific Versions
Build a single master plan, then present information clearly for each reviewer. Fire departments need fire lanes, hydrant locations, and extinguisher placement. Police need access points, crowd control positions, and command post locations. Vendors need their assigned booth locations and power connections. Public works needs utility overlays and road closure details.
Site plans often include locations and specifications for command posts for Emergency Medical Services, police, and security, as well as transportation pickup and dropoff locations. Site plans also often include a legend and detailed specifications for structures such as tents, canopies, booths, platforms, generators, propane tanks, food vendors, stages, and bleachers. Requirements vary by jurisdiction.
The practical approach is to build one comprehensive plan and export targeted versions for each audience. This approach eliminates the version fragmentation that occurs when each department maintains its own separate file. Eagle Mountain City Events Manager Dawn Hancock described the shift directly: “Gone are the days of creating separate layouts for fire, police, facilities, and other departments. Now I can create a single, all-encompassing layout.”
Step 6: Export Maps and Documents for Permits
Permit-ready exports must be professional, legible, and dimensionally accurate so reviewers can print, annotate, and file them. A screenshot does not meet this standard.
San Francisco Department of Building Inspection requires building project plans for full permits to be drawn to scale on paper at least 11×17 inches. Site-permit plans must be prepared by licensed engineers or architects.
Your permit package typically includes the site map, a Bill of Quantities for infrastructure, an electrical plan, a traffic and road closure map, and any specialty plans such as alcohol service areas, pyrotechnics zones, and waste management. The Town of Caledon requires event site maps for alcohol permits to be submitted at least 30 days prior to the event.
Festival organizers should begin the full permitting process, including site assessments and multi-agency coordination meetings, 6–12 months in advance to allow time for plan revisions and avoid last-minute denials. Starting with an accurate, exportable digital plan makes that timeline realistic.
Step 7: Measure Success and Improve Next Year
After the event, document what changed between the submitted plan and the actual site setup. Note any infrastructure that moved, any egress routes that were modified on the day, and any feedback from fire, police, or public works reviewers. Save the final as-built plan as the starting point for next year.
Recurring events gain major efficiency from reusable templates. When your base map, boundary, and standard infrastructure are already placed, annual planning time drops from days to hours. Eagle Mountain City reduced planning time by 70%, from 8–10 hours down to a few hours per event, and reported a 5x return on investment by building on a reusable plan each year.
Track approval cycle time, number of revision requests, and inter-department feedback as year-over-year metrics. These numbers make the case for continued investment in accurate site mapping tools and give your team a clear picture of where the workflow can improve.
Now that you understand the seven-step workflow, use the following checklist to confirm that your site map includes the elements municipal permitting departments typically require.
Municipal Permitting Checklist
The following elements appear consistently across city permitting requirements. This checklist is illustrative, so always verify requirements with your local permitting authority, as standards vary by jurisdiction.
- Site boundaries: Perimeter drawn to scale with dimensions, north arrow, surrounding street names, and one-way indicators
- Street closures and parking: Closed streets identified, number of parking meters or spaces reserved, road closure notification documentation
- Underground utilities: Utility clearance zones marked, no-dig areas identified, contact with local utility notification service confirmed
- Infrastructure placement: Stages, tents, vendor booths, generators, signage, and vehicles shown with dimensions
- Fire lanes: Minimum 20-foot-wide fire lanes marked in all areas (verify local requirement), fire hydrant locations shown
- Electrical plan: Amp and volt requirements specified per vendor and stage location
- Portable restrooms: Quantity and locations shown, minimum 5% ADA-compliant units (see Step 3 for placement details)
- Emergency access routes: Primary, secondary, and emergency vehicle access points marked, minimum lane widths confirmed with local authority
- Crowd areas and egress: Crowd zones outlined, multiple exit pathways shown, accessible routes connecting parking, entrances, activity areas, restrooms, and exits
- Command posts: EMS, police, and security command post locations identified
- Food and beverage: Vendor locations, alcohol service areas with fencing type, and food vendor notification documentation
- Waste and sanitation: Waste collection bin locations by type, wastewater disposal sites, portable toilet locations
- First aid and medical: First aid station locations marked on map
- Legend: All symbols defined, structure specifications listed
- Bill of Quantities: Exportable inventory of all infrastructure items with quantities
Common Challenges: Version Control and Multi-Department Coordination
The most persistent problem in municipal festival site mapping is not drawing the map, it is keeping everyone on the same version of it. When fire, police, public works, parks, and vendors each receive a static PDF by email, version control collapses within days. Someone updates the stage position, resends the file to three departments, and forgets to notify the fourth. On event day, the fire marshal may work from a plan that no longer matches the site.
The practical fix is a single source of truth, one live plan that all departments can view, with a defined process for who has edit access and how changes are communicated. Real-time collaboration tools remove the emailed-file cycle entirely. When a reviewer requests a change, it is made once in the live plan and immediately visible to everyone with access, with no resending, no version numbering, and no confusion about which file is current.
Siloed planning is the related problem. Disconnected systems across emergency response teams and limited spatial context during incidents cause responders to lack instant awareness of layouts, access points, and surroundings at event sites. The solution is to build the master plan collaboratively from the start, with each department contributing to the same map rather than maintaining a parallel version.
The North Texas Tribute Jam demonstrated what this looks like in practice. “Working with the City of Lewisville’s Health and Safety Department was much simpler thanks to OnePlan. Being able to share detailed plans for roadblocks, crowd control, and traffic management meant we got the necessary approvals quickly and without headaches.” The event saved 110 hours of planning time as a direct result.
See how OnePlan’s real-time collaboration keeps every department on the same plan.
Tools Comparison: Manual Methods, GIS/CAD, and Purpose-Built Event-Mapping Platforms
Municipal events teams typically choose between three approaches, and each option carries specific trade-offs.
| Dimension | Manual tools (PowerPoint, Google Maps, PDFs) | GIS/CAD software | Purpose-built event-mapping platforms (e.g., OnePlan) |
|---|---|---|---|
| To-scale accuracy | No, layouts are guesswork and objects do not reflect real dimensions | Yes, precise and georeferenced | Yes, every object stays to scale on a live satellite or street map |
| Ease of use | Familiar but limited, with no event-specific objects | Steep learning curve that requires specialist training | Drag-and-drop interface usable in seconds with no engineering background |
| Real-time collaboration | No, static files are emailed back and forth | Limited, typically single-user or requires specialist handoff | Yes, multiple users edit the same live plan simultaneously |
| Permit-ready exports | Screenshots only, not print-ready at scale | Yes, but requires a specialist to produce | Yes, high-resolution maps up to A0, plus Bill of Quantities CSV |
| Event-specific objects and calculators | None | None purpose-built for events | Thousands of event objects, plus crowd capacity, arrival, and exit calculators |
| Cost and accessibility | Low cost but produces inaccurate results | High cost that requires licensed software and trained staff | First event free, with paid plans from approximately $75/month per seat |
| Municipal fit | Poor, with siloed plans, version chaos, and failed permit reviews | Moderate, accurate but inaccessible to most events staff | Strong, built for cross-department coordination and permit exports |
OnePlan sits in the practical middle. It is as easy to pick up as a non-specialist tool, as accurate as engineering software, and purpose-built for the event site planning workflow. Its drag-and-drop object library, auto-generated Bill of Quantities, and real-time collaboration make it a tool that city events teams, fire marshals, and police liaisons can all use without anyone needing a CAD license.
The City of Greater Dandenong made this transition directly. Before OnePlan, the team created site plans using Microsoft Word or PDFs with added symbols, which featured outdated maps, non-scale layouts, and imprecise emergency location markings. After switching, the team reported saving time and money through accurate site plans, fewer site visits, improved contractor coordination, and better emergency services collaboration. “For our New Year’s Eve fireworks, we needed to set a safe exclusion zone, and OnePlan’s measuring tool was invaluable. It saved us from making numerous site visits or using inaccurate maps.”
Frequently Asked Questions
How far in advance should a municipal events team start the site mapping process?
For recurring annual festivals, start building or updating the site map 6–12 months before the event date. This timeline gives enough time to complete the permitting cycle, incorporate feedback from fire, police, and public works, and make layout revisions without rushing. For one-off events, the schedule depends on local permit lead times, which can range from a few weeks to several months. Starting with a reusable base map from a previous year significantly compresses this timeline.
How do we give different departments access to the plan without sending multiple files?
The most effective approach is a single live plan shared via a secure link, with role-based permissions that determine who can edit and who can view. Fire, police, vendors, and public works then see the same up-to-date plan without anyone managing multiple file versions. When a change is made, it becomes immediately visible to everyone with access.
What level of accuracy do permit reviewers actually expect from a festival site map?
Most city permitting offices require maps that are drawn to scale and include dimensions for all structures and clearance zones. The San Francisco Fire Department, for example, states that plans must be accurate and drawn to scale but do not need to be prepared by a design or engineering professional. The practical standard is that a reviewer should be able to measure distances on the map and trust that they reflect real-world dimensions. This requirement rules out screenshots and non-scaled sketches but does not require CAD-level engineering drawings.
Can OnePlan be used for a one-off community event, or is it only for recurring festivals?
OnePlan supports both one-off and recurring events. Your first event is free, up to 25 objects, with no payment details required. For a one-off event that needs more objects or features, you can pay month-to-month for just the period you need and stop afterward. There is no requirement to commit to an annual plan. Recurring events gain the most value because the base map, boundaries, and standard infrastructure carry over each year, but the platform remains fully accessible for single events.
How does OnePlan integrate with existing city GIS data?
OnePlan is built on leading GIS mapping technology powered by Esri, which means its map base is geo-accurate and aligned with the same spatial standards that city GIS teams use. You can import existing site plans, aerial images, drone photos, or CAD-derived files by converting them to PNG format first, then scaling them onto the map as a base layer and planning on top. Your existing GIS assets then become the foundation of a live, buildable plan rather than a static file in a folder.
Ready to Build Permit-Ready Festival Maps Faster?
Municipal festival site mapping does not have to involve repeated site visits, siloed department plans, or last-minute permit revisions. A clear, to-scale workflow, from boundary definition to permit export, keeps every department aligned and every reviewer confident in what they are approving.
OnePlan is the purpose-built platform that makes this workflow accessible to any city events team, regardless of technical background. Drag-and-drop infrastructure placement, an auto-generated Bill of Quantities, real-time collaboration, and high-resolution permit exports replace the manual methods and expensive engineering software that slow teams down.
The results speak for themselves. Eagle Mountain City’s 70% time savings, the North Texas Tribute Jam’s planning efficiency, and the City of Greater Dandenong’s elimination of inaccurate maps all demonstrate what becomes possible when municipal teams move from static files to a single source of truth.