Event templates

What a template stores

The latest model combines management of the former event types and program templates in one Event templates module. A template has a name, program, lineup, event duration and invitation or reminder timing rules. Recurrence belongs to an event or series, not to the template.

An organization has at least one active template and can choose a default. An empty template lets you prepare a single plan without a ready-made program. Access to its content and use still depends on your role; the selection list is not a way around material access restrictions.

Build a template from scratch

1. Open Event templates and choose to create one.
2. Give it a recognizable name and set the standard event duration.
3. Add songs, select their arrangements and keys, and add headings and notes.
4. Add the planned people with sections and roles or without these assignments.
5. Set reminder timing rules if the organization intends to use them.
6. Save and check the entire model; mark it as the default if needed.

Save a proven event as a model

You can save a well-prepared event as a template. In the new model this transfers the program, lineup, duration and reminder rules. Name the model for its purpose rather than just one concert's date.

Before saving, remove details that should not repeat: one-off notes, private instructions and people who are no longer relevant. A template is a starting point, so it should reduce routine work rather than require the same unnecessary items to be corrected each time.

An event receives an independent copy

Creating an event copies the template. Later changes to the model's name, duration, program or lineup do not change an existing event. This also applies to reminder rules in the new model: restoring the template's rules explicitly copies its current list.

The new lineup starts with its own statuses. A person's confirmation for a previous event is not consent to a new date. Saving a template alone sends no messages, and automatic reminders are initially disabled in a new event until deliberately activated.

Updating and deleting

Keep separate templates when their program or working arrangements really differ. Make small one-off adjustments in the event. Before changing the default model, check that people creating plans know what will be suggested for the next date.

Deleting a template archives it and preserves events created from it. The last active template cannot be deleted. If the action is blocked, prepare another active model and set the default as instructed by the form.