> 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.md).

# Event Templates

The **Event Templates** page stores reusable starting setups for future events. A template can hold the structure your team commonly prepares, such as event flowers, tasks, recipes, pricing, payment definitions, contract content, and proposal content.

For example, a wedding florist could keep a reusable template with a task plan, proposal sections, standard recipes, and a payment schedule. When a new event is created from that template, FlowerBuddy creates a separate event record with that starting content. Editing the saved template later does not update events that already used it.

The library separates reusable event setups from reusable recipes and reusable messages. Use the **Event Templates** tab for a whole event setup, **Recipe Templates** for individual floral designs, and **Email Templates** for prepared messages. The event template library below shows the available actions for each saved template.

<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-85ae461e020c1274059b369bb43bd301c5ea3302%2Fevent-templates-library.png?alt=media" alt="FlowerBuddy Event Templates library showing Event Templates, Recipe Templates, and Email Templates tabs, a populated template table with Template Name, Description, and Actions columns, and New Template above the list." width="550"><figcaption></figcaption></figure></div>

## Event template library

Use **New Template** to create reusable setup, or use a row's action controls to create an event from a template, edit the template, or delete it. The template name opens the same editor as **Edit Template**.

An event template is different from an ordinary event. It is not a client record, does not represent a booked status or payment history, and does not have event-specific contacts, timeline work, files, or production tabs. Its purpose is to supply a starting setup that can be reviewed for each new event.

[Create an event template](/reference/event-templates/create-an-event-template.md) explains the creation choices. [Create an event from a template](/reference/event-templates/create-an-event-from-template.md) explains how to use one for a new event. [Edit and delete event templates](/reference/event-templates/manage-event-templates.md) covers the row actions.

The other tabs have their own editors and choices. Open [Recipe Templates](/reference/event-templates/recipe-templates.md) to manage reusable floral designs, or [Email Templates](/reference/event-templates/email-templates.md) to prepare reusable messages and their variables.

## Event Template editor

Open a template name or select **Edit Template** to prepare the saved setup. The editor uses the Event Page layout, but its tabs and Details sections are narrowed to reusable content. Start with the [Event Template editor](/reference/event-templates/editor.md) to understand what belongs there.

Applying a template to an existing event is a separate action owned by [Event Page > Details](/reference/event-page/details.md). It gives you section-by-section **Add**, **Replace**, and **Keep existing** choices for that one event. It does not create a continuing connection to the saved template.

## In this section

* [Recipe Templates](/reference/event-templates/recipe-templates.md)
* [Email Templates](/reference/event-templates/email-templates.md)
* [Create an event template](/reference/event-templates/create-an-event-template.md)
* [Create an event from a template](/reference/event-templates/create-an-event-from-template.md)
* [Edit and delete event templates](/reference/event-templates/manage-event-templates.md)
* [Event Template editor](/reference/event-templates/editor.md)