Docs

Creating Advance Templates from Module Templates

How to package module templates into a reusable advance template in BackOps, with default due dates, required modules, task tracking, and task review per module.

An advance template is a named, ordered set of module templates that you assign as a package. Instead of adding modules one at a time each time you create an advance for a collaborator, you build the template once and start every similar advance from it.

What an Advance Template Stores

An advance template has a name and an ordered list of module templates. Each module template can appear once per advance template, and each entry carries its own settings:

  • Order: where the module appears in the advance. Drag modules to reorder them.
  • Due date: the default deadline for completing the module.
  • Required: marks the module as one the collaborator is expected to complete.
  • Task tracking: whether the module creates and updates tasks as collaborators answer and reviewers review.
  • Task review: whether answers in a tracked module wait for a reviewer before their tasks count as done. With it off, an answer moves its task straight to Done.

These settings are copied onto each advance created from the template. The reviewer for a module belongs to the live advance, not to the template.

Managing Advance Templates

Advance templates live in Event settings, under Advances, next to the module templates they draw from.

Open Event settings

Select the event name in the top-left corner of the event, then Event settings.

Go to Advances

Select Advances in the settings sidebar.

Create a template

Add a template and give it a name. If your organization keeps a library of advance templates, you can add one from the organization instead, and the module templates it uses come with it.

Add modules

Add module templates and set each one's due date, required flag, task tracking, and task review.

Order the modules

Drag modules into the order collaborators should see them.

Task tracking needs the event's advance task status mapping, set in Project Management settings. Creating an advance from a template with a tracked module fails until the mapping exists. See Task Tracking.

Templates as Starting Points

When you create an advance from a template, the template's modules are copied onto that collaborator's advance. Later changes to the advance, such as adding a module, never touch the template or any other advance built from it, and later changes to the template do not reach advances already created from it.

Build the common structure once as a template, then add what a particular collaborator needs on their advance. See Assigning Advances for what can be changed after assignment.

Reusing Templates Across Events

Advance templates belong to the event they are created in. Two things carry them further:

  • Event templates can include advance templates and module templates, so an event created from a template starts with them.
  • Your organization's advance template library holds standard templates that any event can copy and adapt. See Organization Advance Templates.