Advance Templates
How to build reusable advance packages by assembling module templates with configured settings
Advance templates let you pre-assemble a collection of module templates into a ready-to-assign package. Instead of adding modules one at a time each time you create an advance for a collaborator, you build the template once and use it as a starting point whenever that advance structure is needed.
What an Advance Template Stores
An advance template has a name and an ordered list of module templates. For each module in the template, you configure:
- Order — the position this module appears in the advance (drag-and-drop in the UI)
- Due date — the default deadline for completing this module
- Required — whether this module must be completed; incomplete required modules are flagged to the collaborator
- Task tracking — whether this module should drive automatic task creation and status updates
These settings travel with the template when it's used to create an advance, and can still be adjusted per collaborator after assignment.
Event Scope
Advance templates are scoped to the event they're created in. They are not shared across your organization's events directly — but they can be included in event templates, which lets you clone an entire event setup (including advance templates) when creating new events from a template.
Managing Advance Templates
Advance templates are managed in Event Settings alongside module templates and asset types. Click the event name in the top-left corner of the event, select Event Settings, then navigate to Advance Templates in the settings sidebar.
Open Event Settings
Click the event name in the top-left corner and select Event Settings.
Go to Advance Templates
Select Advance Templates from the settings sidebar.
Create a new template
Click Add Advance Template and give it a name.
Add modules
Add module templates to the advance template. For each module, set the due date, required flag, and whether task tracking is enabled.
Order the modules
Drag modules into the order collaborators should encounter them.
Templates as Starting Points
When you use an advance template to create an advance for a collaborator, the template's module list is copied into that collaborator's advance as a starting point. From there, you can add additional modules, remove modules that don't apply, adjust due dates, and change any per-module settings — without affecting the original template or any other advances built from it.
This means templates work well even when different collaborators of the same type need slightly different configurations. Build the common structure as a template, then customize each collaborator's advance individually after assigning it.