Site Plans 11 June 2026

Build a Site Plan

Create an event layout with a map, image, or plain background and place participants, zones, labels, and infrastructure.

All articles

The site plan builder is a full-screen workspace for turning event data into a usable layout. The goal is not to draw a perfect-looking map. The goal is to create a current, readable plan that planners, suppliers, participants, and event-day teams can trust.

Build the plan

01

Open the event site plan

Use Site Plans or the event Site Plan module.

02

Choose a background

Use Map when geography matters, Image when you have a plan or floor drawing, or Plain for measured layouts that do not need map detail.

03

Set scale and grid

Use the setup guide to set planning profile, boundary, grid, snap, labels, and uploaded-image scale where needed.

04

Place participants

Drag unplaced participants onto the plan, then set location references, pitch details, and notes from the selected participant panel.

05

Add infrastructure and zones

Mark entrances, queue lanes, power, water, waste, welfare, stages, access routes, fire lanes, no-parking corridors, emergency exits, and other operational points.

06

Record supplier details

Add circuit capacity, cable routes, wastewater or grease-waste markers, scanner counts, gate capacity, and access notes where they are needed for handover.

07

Use search and layers

Search participants, references, infrastructure, zones, and issues. Use layer presets for planning, supplier, check-in, emergency-services, accessibility, or public-facing views.

08

Review planning notes

Use Planner review for map reports, move requests, assigned follow-up, and object notes that need action before sign-off.

09

Save and check health

Save the plan, then review blockers, warnings, revision state, and sign-off requirements in the workflow panel.

Background choices

  • Map works well when roads, entrances, access routes, and site boundaries matter.
  • Image works well when you already have a site drawing, floorplan, or exported map image.
  • Plain works well for measured layouts that do not need map detail.

When the builder warns you

  • A save conflict means another tab or user saved a newer revision. Reload latest before continuing unless you deliberately need to save a draft copy.
  • A blocker is a hard issue such as invalid geometry, overlaps, boundary problems, infrastructure clashes, or placement in a no-go area.
  • A warning is a planning risk such as unplaced participants, missing boundaries, overloaded power, service conflicts, missing access routes, or unanswered placement data.
  • Use the remediation hint to decide whether to move, resize, redraw, remove, or deliberately accept the warning.

Before approval or publish

  • Check that late participant changes and changed application answers have been reviewed.
  • Confirm supplier needs such as power, water, waste, access, gate flow, and emergency routes.
  • Resolve blockers before publishing and record a deliberate decision for warnings that remain.
  • Complete layout, access and safety, utilities, published output, and manager sign-off where required.
  • Publish only when the saved revision is the official layout the wider team should use.

Use Fit Canvas after changing background or boundaries so the layout is easy to inspect before placing people.

Site planning

Need site plans that use real event data?

SmartGig Site Plan helps organisers place traders, infrastructure, zones and public map details using current event information.

Related articles