Introduction to BackOps
What BackOps is, the problem it solves for live event teams, and how the docs are organized so you can find the part of the platform you need.
BackOps is the back-of-house operating system for live events: one connected place to plan, staff, schedule, advance and resource every show your company runs.
Most live event teams run operations on a patchwork of spreadsheets, email threads, shared drives and group chats. Every link between the crew sheet, the schedule and the budget is kept in step by a person, and every one of those links breaks the moment something changes. Point tools for crew or gear help inside their own module, then hand everything else off by export or retyping.
Why BackOps
BackOps keeps the records of an operation connected. Crew, collaborators, areas, the schedule, tasks, advances, files and resources are linked records inside one event, so a change made in one place is the change everyone sees. The structure on top of those records is yours to configure: event types, custom attributes, templates and statuses are set to how your company already works, so you do not rebuild your process to fit the tool.
The result is less time spent running the operations of each event, a team that stays in sync instead of hunting for the latest version, and a process that runs the same way on the twentieth event as on the first.
How the docs are organized
The sidebar follows the shape of the product:
- Start Here: what BackOps is, how it fits together, and a first walk through setting up an organization and an event.
- Types, Attributes & Roles: the shared pattern for classifying events, crew, collaborators, locations and resources.
- Your Organization: the organization itself, licensing and billing, departments, locations and integrations.
- Events: creating events, event types, templates and areas.
- People: collaborators, crew and the organization's databases of both.
- Planning: the schedule, run of show and project management.
- Advancing: collecting structured information from collaborators.
- Resourcing: inventory, procurement, orders and coverage.
- Documents & Content: files, Dynamic Docs and content.
- Communications: event email and notifications.
- Working with Data: the shared table views and spreadsheet import.
- Reference: permissions and the changelog.
If you are new, read how BackOps fits together next, then follow the Getting Started pages in order.