Areas

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.

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 simply 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 just a list of spaces — they're a tagging mechanism that runs throughout the platform.

Activities on the schedule, tasks in project management, files, and advance responses can all be tagged to an area. When you tag something to an area, that data becomes filterable and rollable.

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.