Use Rules, Auto-Generation, and Pitch Assignments

Add placement rules, run generated layouts, and review pitch assignments before the plan becomes operational.

Article guidance

Rules and generated layouts help reduce manual placement work. They do not replace venue judgement. Treat them as a planning assistant that still needs a human review before export.

Rule types

Exclusion rules keep two participant types or items a minimum distance apart.
Proximity rules place participants near infrastructure or useful locations.
Capacity rules limit how many participants of a type can be placed in a zone.
AI or natural language rules can guide generated layouts where the feature is configured, but they still need review.

Run generated layout

Build the base layout: Add the background, zones, infrastructure, and important boundaries first.
Add rules: Create active placement rules in the site plan tools.
Open auto-generation: Choose which participants to include.
Choose placement priority: Use options such as space efficiency, grouping, or pedestrian flow where available.
Generate and review: Inspect the result, then move participants manually where needed.
Recover or cancel when needed: If the page refreshes during generation, SmartGig resumes status updates. If the run no longer makes sense, cancel it and start again.

Pitch assignments

Placed participants can have pitch or location references. Use these carefully because they may appear in operational reports, arrival details, exports, or participant-facing information.

When a participant's planning answers change after placement, SmartGig flags the saved layout for review so planners can check whether the current pitch still matches the latest application detail.

Generation recovery

Queued or running generation has a saved status record.
The builder can resume status updates after a refresh.
If the live stream drops, SmartGig falls back to polling the generation status.
AI-assisted adjustments are rechecked for overlaps, boundary issues, infrastructure clashes, and active rule violations before the run is marked ready for review.
Cancelled runs stay in the run history with a clear cancelled state.