> 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/forms/form-submissions/create-an-event-from-a-submission.md).

# Create an event from a form submission

Create an event from a submission when the response should become an event but was not already configured to create one automatically.

## Start event creation

1. Open **Forms > Form Submissions**.
2. Find the response you want to use.
3. Select **Create event from form submission** in its row actions.
4. In the **Create New Event** dialog, review **Event Name**, **Template Name (Optional)**, and **Event Date**.
5. Leave **Archive form submission** selected when the response should move to **Archived** after the event is created. Clear it when the response should remain in **Active**.
6. Select **Create**.

FlowerBuddy uses the response's contact and event-date information when it can. It adds text, number, and choice questions and answers to the event's internal notes. Recipe Quantity answers can update matching recipes supplied by the selected template. A template provides reusable event setup. Leaving the template unset creates the event without that template's starting content.

**Timeline Item** answers create named scheduled activities, and **Timeline Items** answers create one activity for each row. Answered places from these questions and from **Location** or **Locations** are added to the event's separate [Locations list](/reference/event-page/details/manage-event-locations.md). Location notes preserve the question's context or the recipient's notes. A single Location field configured with **Use as primary location** sets that place as primary when answered.

Event creation uses the questions saved with that submission. Editing the form later does not reinterpret an older response using the new question definitions. Review the created event's timeline, locations, and primary designation before planning from them.

The form response and event remain separate records. General answer fields do not automatically fill a recipe's **Proposal Notes** or **Florist Notes**. Review the linked submission when you need the complete original response.

After creation, the new event opens on its Event Page and the submission becomes linked to that event. The response remains available for review in **Archived** or **Active**, based on **Archive form submission**.

## Choose the right path

Use the automatic path in [Configure form details and event creation](/reference/forms/form-editor/form-details/configure-form-details.md) when every response should start an event. That path creates and links the event without this dialog. Use the manual path when the team should review a response before deciding whether to create an event.

When testing a form, check its **Create Event** choice first. A public response sends a florist notification, can send a client confirmation when a primary email is collected, and can start an event through the form's settings.