Introduction

Dynamic Docs is how BackOps turns event data into the documents your team and external stakeholders actually need.

Every event generates a category of work that lives entirely outside most systems: day sheets assembled in Word, call sheets compiled in Sheets, COM reports built from scratch, patch sheets rebuilt every show. These documents are essential. They're how information moves from the people managing the event to the people executing it, but creating and maintaining them is manual, repetitive, and entirely disconnected from the data they're supposed to reflect.

The problem isn't that teams lack information. It's that getting that information into a usable format, for the right people, at the right time, requires leaving the platform entirely. And when data changes (a schedule shifts, a request gets approved, a crew member swaps), every document built outside the system is stale before it's sent.

Why Dynamic Docs Matters

In the current model, document assembly is pure overhead. Someone pulls data from the platform, pastes it into a template, formats it, and distributes it. The next day, or after the next update, that process starts over. The more complex the event, the more documents are involved, and the more time that cycle consumes.

BackOps addresses this by keeping documents inside the platform and connecting them directly to live event data. When a document is built with Dynamic Docs, it doesn't capture what was true when it was created. It reflects what's true every time it's opened. There's no export, no reformatting, and no version to manage.

This also changes how documents scale. A team running 50 shows doesn't need to rebuild the same day sheet layout 50 times. A single document with the right variables renders accurately for any collaborator, any date, and any area, without duplication.

How Dynamic Docs Works

Documents are built in a full-page editor inside the event. The primary building block is the Query Block, a live data table that pulls from event entities: crew, activities, advances, requests, tasks, procurement resources, files, and more. You choose what to query, which fields to display, and what filters to apply. The table queries live data on every load.

Variables are what turn a single document into a reusable layout. You define a named parameter (a Collaborator, an Area, a Date) and bind your Query Block filters to it. When someone opens the document, they pick a value from the configuration bar at the top of the page, and every block that references that variable re-renders against the new context.

Finished documents can be shared directly with collaborators and crew members inside BackOps, or distributed outside the platform via public links, token-based URLs that require no account and work for anyone who receives them.