Understand an event template

An event template saves you from starting again for each date. It prepares recurring choices: requested information, modules, teams and operating rules.

Before you start

The Event templates menu is available according to your permissions. Viewing and managing templates are separate permissions. Prepare templates on the web, preferably on a computer.

This guide covers event templates. Run sheet and checklist templates prepare operational content; they are separate resources.

What a template prepares

You can define requested fields, modules and visibility, proposed teams and participants, leads, event roles, and settings for the run sheet and other available modules.

You can associate a timeline with the template to prepare milestones around H0. Names and dates specific to each occasion are entered in the event.

What is inherited at creation

The event receives a copy of the template’s settings and roles. Proposed teams and participants provide a starting point. The creation steps depend on the template: some selections can be adjusted, while others are already prepared.

Documents attached to the template are inherited as links. Operational content is inherited when configured in the template. Always check the result in the new event.

Independent events

Editing the template prepares future events. It does not reconfigure events already created from it. Likewise, adjusting an event does not change its template.

This independence applies to the copied preparation. Shared resources, particularly linked documents, do not all become separate files: do not treat a template as a backup of your library.

Choose a useful scope

“Evening concert”, “Home fixture” or “Two-day exhibition” are possible formats. Create different templates when the teams or preparation genuinely differ, rather than one template per date.

Expected result

You have identified a reusable format. Create your template, then use it for a first event.