Introduction

Advancing is how BackOps collects, organizes, and operationalizes the information needed to actually run an event.

The term advancing originates in the music industry, where teams advance artists by gathering technical, logistical, and hospitality requirements ahead of a show. In BackOps, the concept is expanded and generalized so it works for any type of event.

At its core, advancing answers a simple question:

What information do we need from the people we're working with in order to execute this event successfully?

Why Advancing Matters

In most event workflows, advancing is manual, inconsistent, hard to reuse, and difficult to summarize. Even when teams use custom forms or spreadsheets, the result is often a pile of disconnected data that still has to be translated into action.

BackOps is designed to solve this end-to-end. Advancing is not just about collecting information — it's about turning that information into usable, actionable planning data.

How Advancing Is Structured

Advancing in BackOps is built in three layers, which gives teams both consistency and flexibility.

Module templates are the foundational building blocks. Each module template defines a single form section — a combination of instructional content, questions, and request tables — that captures a specific category of information. A "Catering" module, a "Technical Requirements" module, and a "Credentials" module are all examples. Module templates are reusable: build them once, and use them wherever they're needed.

Advance templates are curated packages of module templates. An advance template assembles several module templates into a ready-to-assign structure, with settings for due dates, which modules are required, and whether each module should drive task tracking. A "Standard Artist Advance" might combine technical, hospitality, and logistics modules with their typical due dates pre-configured.

Advances are what collaborators actually receive. An advance is created for a specific collaborator and seeded from an advance template (or built from scratch). It can be scoped to an area, an activity, or both — and it can still be adjusted after assignment if that collaborator's situation requires it.

This structure means you invest in building module templates and advance templates once, and then applying them is fast and consistent across every collaborator.