Module Templates
How to build reusable form sections using content blocks, questions, and request tables
Module templates are the building blocks of advancing in BackOps. Each template defines a reusable form section — a named set of content, questions, and request tables — that can be assembled into advances and assigned to any number of collaborators across the event.
Building your module templates first is the foundation of the entire advancing workflow. Because every advance is assembled from these templates, time invested in building them well pays off every time they're reused.
Name and Label
Every module template has two text fields that serve different purposes.
The name is for internal use. It identifies the template within Event Settings and in the list you browse when building advance templates. The label is what collaborators actually see when they open their advance. These can be the same, but separating them is useful when you need multiple templates that appear identically to collaborators but are configured differently.
A common example: you might have two templates both labeled "Catering" to collaborators — one configured for artist needs and one for vendor needs — with internal names of "Artist Catering" and "Vendor Catering" so you can distinguish them in setup.
Block Types
Each module template is built from a sequence of blocks. Blocks can be reordered by dragging them into position, so you can arrange content, questions, and requests in whatever order makes sense for the collaborator filling it out.
Content Blocks
A content block is a rich text editor. It supports headings, bold, underline, colored text, and other formatting. Content blocks are used to provide instructions, context, or guidance before a collaborator fills something in — setting expectations for the section or explaining what's being asked.
Question Blocks
A question block presents the collaborator with a single input field. When adding a question block, you choose the response type from a dropdown. The available types are:
- Text
- Rich Text
- Number
- Date
- Date/Time
- Checkbox
- Link
- File Upload
- Multi File Upload
- Select
- Multi-Select
For Select and Multi-Select types, you define the options the collaborator will see.
Request Blocks
A request block creates a table where collaborators add one or more line items — for example, requesting golf carts, listing credentials needed, or specifying labor calls. Each row in the table is one request.
Request blocks come in two forms. Asset requests are tied to a defined asset type and flow into the event's procurement workflow when submitted — these are used for anything that needs to be ordered, sourced, or fulfilled. Non-asset requests are for general collection that needs to be tracked but doesn't require procurement, such as credentials or parking passes. Non-asset responses appear in the Advance Manager but do not enter the procurement pipeline.
When configuring a request block, you set a line item label using a variable-based builder. This label controls how each row displays in tables and exports throughout the platform. If a request has properties for type and quantity, for example, the label might be set to render as type — quantity — and that combined value appears everywhere that request is shown.
Approvals on Request Blocks
Request blocks can have one or both approval stages enabled. These flags determine whether a request needs to go through an approval step before it is considered fulfilled.
Advance approval covers the production-side review — typically the person coordinating that collaborator's advance confirming the request is operationally approved.
Resource approval covers the supply-side confirmation — typically the person or team actually responsible for providing the resource, confirming they can fulfill it.
You can enable one, both, or neither on any given request block, depending on the workflow that block requires.
Approval workflows are configured per request block here, and then reviewed during the advancing process. See Reviewing and Approvals for how these play out in practice.
Managing Module Templates
Module templates are managed in Event Settings. To get there, click the event name in the top-left corner of the event, then select Event Settings. Use the sidebar to navigate to Module Templates.
Open Event Settings
Click the event name in the top-left corner of the event and select Event Settings.
Go to Module Templates
Select Module Templates from the settings sidebar.
Create a new template
Click Add Module Template and give it a name, label, icon, and category.
Add and arrange blocks
With the template open, add content blocks, questions, and request blocks as needed. Drag blocks to reorder them.
Icons and Categories
Each module template has an icon chosen from a searchable preset library with hundreds of options. The icon appears alongside the template label in the advance form and in other parts of the platform.
Module categories group related templates together. They are primarily an organizational tool — as your template library grows, categories help you stay oriented. Categories are not yet heavily used as a filtering or navigation mechanism in the UI, so think of them as internal structure for now.