Docs

Setting Up Areas for Your Event's Stages, Rooms and Zones

How to define the stages, rooms and zones of your event as areas in BackOps, and why tying activities, advances, files and resources to areas matters.

Areas represent the physical and sometimes logical spaces that make up your event. They're one of the most useful organizational tools in BackOps, and they become more valuable as your event takes shape.

To add one, open the Areas group in the event sidebar, choose Manage Areas, and create the area with a name. Each area then appears in the sidebar under Areas.

What to Create as an Area

An area is any space within your event that you need to track things about. You don't have to be exhaustive upfront. Add the ones you know, and come back to create more as the event develops.

Common examples include:

  • Stages (Main Stage, Second Stage, Acoustic Stage)
  • Breakout rooms and session spaces
  • General session rooms
  • Registration and check-in areas
  • Artist and speaker green rooms
  • Back-of-house zones
  • Catering and hospitality spaces
  • Conference rooms
  • Outdoor zones or fields

The right areas for your event depend on what you're producing. A corporate conference might have breakout rooms and a general session space. A festival might have multiple stages, a production village, and a hospitality compound. Both are valid. Areas don't have a predefined shape.

Structure

Areas in BackOps use a flat structure. There's no nesting or hierarchy. You create a list of the spaces that matter to your event.

This keeps things simple and searchable, and it's flexible enough to represent everything from a single-room event to a large, multi-zone festival site.

Why Areas Matter

Areas aren't only a list of spaces. They're a way of tying work to a place that runs throughout the platform.

Activities on the schedule, advances, files, and resources and procurement can all be tied to an area. Each area has its own page with Dashboard, Schedule, Advance, Resources and Files tabs, and you can give people access to just the areas they work in.

This matters in practice. A stage manager who only needs information about their stage doesn't want to wade through everything happening at the rest of the event. A venue coordinator asking for floor plans for a specific room doesn't need to see every file in the system.

Think of areas as a way to group and surface the right information for the right people. The more consistently you tie activities, advances and files to areas, the more useful each area's page becomes later in the process.

Next: Project Management

Learn how to get your task list set up and start tracking what needs to get done.