> For the complete documentation index, see [llms.txt](https://help.flowerbuddy.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.flowerbuddy.co/reference/event-templates/editor/tasks.md).

# Prepare reusable tasks in a template

The template **Tasks** tab stores work that a new event should start with. A task can use a group, an assignee or Event role, a status, a date relative to the event, or a completion dependency. Use this tab when the same preparation sequence belongs on many events.

The populated example below shows two tasks in **To Do** with dates relative to the event. The other lanes remain available for a template whose starting work is already **In Progress** or **Complete**.

<div data-with-frame="true"><figure><img src="https://2616748322-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUtdSEPutB4SrRwwUMOIx%2Fuploads%2Fgit-blob-760d30ef233d27d0aec98d92c93365cfe8ce4fe0%2Fevent-template-editor-tasks.png?alt=media" alt="FlowerBuddy Event Template Tasks tab showing Schedule Final Design Consult and Order Flowers in the To Do lane, each with a relative event date, alongside empty In Progress and Complete lanes and Add Task and Add Group controls." width="550"><figcaption></figcaption></figure></div>

## Add reusable work

Select **Add Task** to create a task in the template. Select **Add Group** when several tasks should be reviewed together. Give each task a name that remains useful on a future event, such as reviewing final design details or ordering flowers.

Use **Assignee** or an **Event Role** when the responsibility should be part of the starting setup. A role is useful when different people may fill that responsibility on different events. Review the assignee after creating a real event so the role or member matches the event team.

## Choose dates and dependencies

Template tasks can use dates relative to the event, such as **Event - 45 days** or **Event - 21 days**. [Set a task due date and completion dependency](/reference/tasks/set-task-due-date.md) explains the shared date rules. **Specific date** is not available in a template; choose a relative rule that can be calculated for the new event.

Use a completion dependency when one reusable task should wait for another task or group. Keep the dependency structure understandable because it will be copied into each event that uses the template.

## Choose a starting status

Use **To Do**, **In Progress**, or **Complete** to represent the intended starting state. Do not mark work complete merely because it is part of the template. The task status applies to the task, not to the event's main status.

The template task structure can be added or replaced when applying a template to an existing event. See [Apply an event template](/reference/event-page/details/apply-event-template.md) for that choice.