Event site plan software that knows what it is placing.
A site plan is not just boxes on a map. It is traders, stages, power, entrances, toilets, first aid, access routes, quiet zones, retained vehicles, generators, pitch frontage, emergency routes, and the small details that become very large details on site.
SmartGig connects the plan to live event data, so layouts are built from the actual requirements instead of a PDF and a hopeful shrug.
Build plans from live trader, vehicle and event data
Use participant and event information from SmartGig while you build the layout, so the map reflects what people have applied for and what the event needs.
- Place traders using pitch sizes, categories, power needs, frontage, quiet-zone requests, vehicle requirements, generators, and special notes.
- Map stages, gates, infrastructure, welfare, emergency access, supplier points, zones, annotations, and operational layers.
- Flag placed participants when application answers change, because stale planning data has a habit of waiting until the worst possible moment.
Spot pitch, access and layout issues before publishing
Good site planning means spotting clashes before traders, suppliers, crew, or the public discover them with their feet.
- Review boundaries, exclusions, capacity, proximity, power, utilities, emergency routes, weather-risk areas, noise-sensitive zones, frontage access, and retained-vehicle access.
- Use saved plan health, warnings, blockers, review notes, threaded follow-up, object history, and published-snapshot checks.
- Keep active-editor presence and version-aware saves around the plan, so teamwork does not quietly overwrite teamwork.
Share, reuse and export plans for crews and stakeholders
When the plan is approved, SmartGig freezes the official snapshot and turns it into useful handover material.
- Publish staff viewers, participant portal locations, attendee maps, accessibility maps, supplier packs, operations packs, emergency-services packs, and visual PDFs.
- Export CSV, GeoJSON, KML, reports, schedules, utility loads, object data, and snapshot bundles from the plan.
- Save proven layouts as templates so next year starts from something better than a blank map and a memory.