Introduction
Scheduling is a core part of BackOps. Nearly every aspect of event planning is tied to when things happen, and schedules are how that timing is organized, communicated, and executed.
Events often involve hundreds of moving pieces, and when everything is forced into a single spreadsheet or master timeline, schedules quickly become overwhelming. BackOps approaches scheduling differently, with the goal of making complex schedules clear, filterable, and consumable for everyone involved.
Activities: The Building Blocks of Schedules
Section titled “Activities: The Building Blocks of Schedules”In BackOps, schedules are made up of activities.
An activity represents something that happens at a specific time during an event. Activities can range from high-level moments to detailed operational actions, depending on how deeply you choose to plan.
Examples of activities include:
- Doors opening
- General sessions
- Load-in or load-out windows
- Rehearsals
- Sound checks
- Meals
- Meetings
Activities are created once, then surfaced across different calendars based on who and what is associated with them.
A Multi-Calendar Approach
Section titled “A Multi-Calendar Approach”BackOps uses a multi-calendar model to help break large schedules into manageable views.
Rather than forcing everything into a single timeline, activities can appear on multiple calendars at the same time, depending on how they are tagged.
You can view schedules by:
- Area – what’s happening in a specific space
- Collaborator – what a specific group is involved in
- Event – the overall event-wide schedule
- Personal – activities relevant to you individually
These calendars are not exclusive. A single activity can appear on several calendars at once.
Associating Areas and Collaborators
Section titled “Associating Areas and Collaborators”Activities become powerful through association, using familiar calendar concepts.
When you create an activity, you can:
- Add one or more areas as the location, which places the activity on those area calendars
- Add collaborators as organizers, attendees, or optional attendees, which places the activity on those collaborator calendars
- Add specific people, which places the activity on their personal calendars
This mirrors how traditional calendars work, while extending those concepts to support event-scale collaboration.
Because activities are associated rather than duplicated, a single activity automatically reaches the right audiences without creating multiple schedule entries.
As a result:
- Teams can focus only on what’s relevant to them
- Complex schedules become easier to understand
- Collaborators see the information they need without unnecessary noise
The Event Calendar and Global Activities
Section titled “The Event Calendar and Global Activities”In addition to area- and collaborator-based views, BackOps includes an event calendar.
Some activities are relevant to everyone and form the backbone of the event schedule. These are created as global activities.
Examples of global activities include:
- Doors opening
- Key sessions
- Major program moments
- Event start and end times
Global activities appear prominently on the event calendar and provide context for all other scheduling decisions. They can still be tagged with areas and collaborators, but marking them as global makes them easier to identify and plan around.
Two Levels of Scheduling
Section titled “Two Levels of Scheduling”BackOps approaches scheduling at two distinct levels:
1. High-Level Scheduling
Section titled “1. High-Level Scheduling”At the top level, activities are placed on calendars much like a traditional calendar system. This provides a clear overview of what happens when across the event.
This level is ideal for:
- Understanding the flow of the event
- Coordinating between teams
- Communicating key moments
2. Detailed Run of Show
Section titled “2. Detailed Run of Show”Each activity can be taken one step deeper using a run of show.
A run of show allows you to break an activity down into minute-by-minute or cue-by-cue detail. This is especially valuable for:
- Scripted sessions
- Performances
- Keynotes
- Highly technical moments
Rather than forcing this detail into the main schedule, BackOps keeps it nested within the activity itself. This keeps high-level schedules readable while still supporting deep operational planning.
Filtering Without Losing Context
Section titled “Filtering Without Losing Context”One of the biggest challenges in event scheduling is balancing detail with clarity.
BackOps solves this by allowing you to:
- Filter schedules by area or collaborator
- Zoom in on specific parts of the event
- Maintain visibility into how everything rolls up at the event level
You can focus on a single space, team, or moment without losing sight of how it fits into the overall event timeline.
Schedules as a Coordination Tool
Section titled “Schedules as a Coordination Tool”At their core, schedules in BackOps are about coordination.
By combining flexible activities, multiple calendar views, and optional deep run-of-show detail, BackOps turns scheduling from a chaotic spreadsheet into a shared, structured system that teams can actually use.
Schedules become easier to understand, easier to communicate, and easier to execute—no matter the size or complexity of the event.