How Advancing Works

Once you understand the three-layer structure of advancing — module templates, advance templates, and collaborator advances — it helps to see how those layers connect to the rest of the event workflow. This page covers the full picture: what collaborators do, how production teams review it, and how advancing connects to tasks, procurement, and day sheets.

Flexible Information Collection

Because advances are assembled from module templates, you can build different advance structures for different types of collaborators without rebuilding anything from scratch.

Examples include:

• Advancing speakers on presentation needs
• Advancing artists on technical and hospitality requirements
• Advancing vendors on services, equipment, or staffing
• Advancing venues on capacities, access, and infrastructure

Advancing is just as useful for corporate events, conferences, and internal projects as it is for concerts or festivals.

Internal and External Advancing

Advancing is not limited to external collaborators. You can use the same structured process internally to plan room setups, equipment needs, office or production spaces, and session-level requirements. This keeps internal planning decisions in the same system as external requests, rather than scattered across side channels.

Associating Advances with the Event

An advance can be associated with an area, activity, or both — but only one of each. This scoping is not just organizational — it makes the advance data accessible and editable in the operational contexts where people need it.

When an advance is scoped to an area, the advance information appears on that area's page and can be edited there directly. The same is true for activities: scoped advances appear on the activity view and can be updated in place. Both surfaces also include the advance data in their day sheet exports.

This changes the day-to-day workflow meaningfully. Previously, updating an advance required navigating to the collaborator record — regardless of which area or activity that advance was for. If ten collaborators were advancing the same stage, updating each one meant ten separate trips to ten separate collaborator pages. Now, all advances scoped to a given area or activity are surfaced together in that context and can be edited without leaving it.

For example, if a band's backline advance is scoped to the Mainstage area and their specific performance activity, the production team can pull up and update exact requirements from either the area view or the schedule, wherever they happen to be working.

Turning Information Into Action

Once information is collected, BackOps helps you roll it up and make sense of it across several contexts.

The Advance Manager is the event-level view that aggregates all advance responses by module type. If a "Catering" module was used across 30 different advances, Advance Manager shows all 30 responses together in one table, making it practical to review large volumes of information without clicking through individual collaborators.

You can also review and update advance data by collaborator, by activity, and by area. Each context surfaces only the advances scoped to it, so working from an area or activity gives you a focused view of exactly what is relevant to that space or moment without the noise of the full event.

Approvals, Negotiation, and Alignment

Advancing is a collaborative process, and not every request can be fulfilled as-is. BackOps supports a two-stage approval workflow for requests: an operational approval from the production side, and a fulfillment confirmation from the supply side.

This creates a shared record of what has been asked for, what has been approved, and what has been confirmed as deliverable — without chasing those conversations across emails and side channels.

Task Tracking

When task tracking is enabled on a module, BackOps automatically generates tasks for every question and request in that module. Those tasks update their status as collaborators respond and reviewers review — moving from Not Started through Needs Review and into Done without anyone manually creating or updating them.

This gives the production team a live, task-based view of the entire advancing process that mirrors exactly where things stand.

Closing the Loop

Advancing does not end with data collection. Once requirements are finalized, the same structured data that powered the planning process can be used to generate summaries and day sheets, share finalized information back with collaborators, and ensure everyone is aligned on what has been approved and planned.

Instead of re-summarizing information in emails or documents, teams work from a single source of truth that everyone involved can reference.

Advancing as a Foundation

Advancing is the first step toward procurement and execution. Asset requests submitted through advances flow directly into the procurement workflow. Day sheet exports pull from scoped advance data. Task tracking mirrors advance progress in the project management view.

By centralizing information collection, approvals, and roll-ups, BackOps turns advancing into a repeatable, scalable workflow that supports everything that comes next.