> 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/events/create-a-template-from-an-event.md).

# Create a template from an event

Create an event template when an existing event contains setup you want to reuse for future events. Choose this when the goal is reusable starting structure, not a second event with similar information.

## Save reusable setup

On the **Events** page, open the action menu for an event you can edit. Select **Create Template From Event**, enter a name in **Template Name**, and select **Create**. The new template saves reusable event setup while the source event remains unchanged.

The **Create New Template Event** dialog is where you enter the reusable template name before creating it.

<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-2bd2c6ff5651777b6cc0aad685e94439cb732f66%2F01-action-state.png?alt=media" alt="FlowerBuddy Create New Template Event dialog with the Template Name field filled in and the Create button ready to select." width="370"><figcaption></figcaption></figure></div>

## Use the new template

After you select **Create**, the dialog closes and the new template's Event Page opens. You can use the template when creating another event, while later edits to the template do not update events that already exist.

<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-1d1241fa2ef78517517129c119a9aee17466af0f%2F02-success-state.png?alt=media" alt="FlowerBuddy template created from an event, with the new reusable template page open after submission." width="550"><figcaption></figcaption></figure></div>

Creating a template does not duplicate the event, change its main status, sign its contract, or record a payment. Use the separate duplicate action when you need another event record instead.
