Manage your venues
Before you start Venues live in your org tree. You'll need permission to create nodes in your organization to add or edit them.
01 Why venues exist — the scan origin
Every scan needs a precise point to sit on — the coordinates all the distance-based signals (traffic radius, airspace, lightning proximity, nearby hospitals) measure from. A venue is that point, saved and reusable. Instead of re-typing an address each time you run a show at the same place, you define the venue once and every event there inherits its exact origin.
02 Add a venue
Open Venues and add one. A venue carries:
- Address — geocoded server-side into latitude/longitude, which become the scan origin.
- Capacity — the venue's headcount, used for crowd context.
- Name — how it shows up when you pick it while creating an event.
You can browse your venues as a table or a calendar of what's scheduled where.
03 Bulk-upload from a CSV
Loading a whole circuit or a promoter's building list? Use the CSV upload on the Venues page — name, address, and capacity per row. Each address is geocoded on import, so a hundred buildings become a hundred ready-to-use scan origins in one pass.
04 Use a venue when you create an event or tour
When you create an event — or a tour stop — pick the venue instead of typing a location, and the event starts life with the venue's exact origin, so the map and every radius-based signal are anchored correctly from the first scan. Because venues are org-tree nodes, per-venue scan-cadence defaults also flow down to the events held there.
Tips
- Set up venues before a busy season so event creation is a one-click pick, not an address re-type.
- A good street address geocodes to a good origin — check the coordinates on the map if a venue's signals look off-center.
- Capacity feeds crowd context — keep it accurate for multi-room or expandable buildings.