> 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.md). # Events An event brings together the floral designs, client information, pricing, proposal, payments, and preparation for one event. The **Events** page lets you see those events together, find the one you need, and keep track of where each stands. For example, you might be discussing flowers with one wedding client, preparing a proposal for another, and planning the build for a third. Your event list helps you keep those different stages of work in view. The list below shows event names, dates, prices, and statuses together. Filters above the list help you narrow it down.
FlowerBuddy Events page with the Active view selected and a search for an ampersand showing wedding events. The table lists event names, dates, prices, statuses, assignees, and tags beneath Tag, Assignee, and Workflow Status filters.
## Event list Each row represents one event. Its name helps you recognize the event, while its event number gives you another way to identify it. The date helps you plan ahead, and the price gives you a quick view of the current event price. Tags can help organize events with something in common, such as a venue or collection. Assignees show which workspace members are involved. Use [Search, filter, and sort events](/reference/events/find-filter-sort-and-review-events.md) to narrow the list, or [assign team members and tags](/reference/events/assign-team-members-and-tags.md) to organize rows. Select an event name to open its [Event Page](/reference/event-page.md), where you manage the full details. ## Event statuses An event's main status describes its broad stage or outcome: * **Inquiry:** A potential event you are discussing with a client. * **Proposal:** An event for which you are preparing or presenting an offer. * **Booked:** An event you have confirmed. * **Completed:** An event whose work is finished. * **Cancelled** or **Lost:** An event that will not go ahead with your business. * **Archived:** An event you have set aside from your current work. Use **Active** to see Inquiry, Proposal, and Booked events together. It is a filter, not a separate status you assign. To change an event's status, read [Change an event status from the Events page](/reference/events/change-event-status.md). A status helps organize your events. For the actual contract and payment records, open the event's **Details** tab. ## Workflow Status **Workflow Status** is a sub-status you can customize to add detail to the main event status. For example, "Inquiry: awaiting contact" and "Inquiry: meeting scheduled" distinguish two stages of an inquiry. "Lost: too expensive" can help record why an event did not go ahead. You choose the names that help your business. These examples are not built-in choices or a required sequence. Workflow Status is separate from the main event status, so changing one does not automatically change the other. You can also configure a task or task group to assign a Workflow Status when it is completed. This can connect finished work, such as a design review, to the progress you track for the event. ## Event templates and defaults An event template provides a reusable starting setup. If you create an event without choosing a template, FlowerBuddy uses the defaults in **Event Settings** instead. Start with [Create an event](/reference/events/create-an-event.md) or [create an event from a template](/reference/events/create-event-from-template.md). Later changes to a saved template or those defaults do not change events you already created. You can deliberately [apply a template to an existing event](/reference/event-page/details/apply-event-template.md) from **Details > Event Actions**. For example, you might first record an inquiry, then choose a template after learning more about the client's plans. You can also correct an event created with the wrong template, or with no template, without starting again. Applying a template lets you choose what to add, replace, or keep in each section. ## Open an event Use the Events page to find and compare events. Open the [Event Page](/reference/event-page.md) to plan the designs, manage the client information, and prepare the work for one event. ## In this section * [Create an event](/reference/events/create-an-event.md) * [Search, filter, and sort events](/reference/events/find-filter-sort-and-review-events.md) * [Change an event status from the Events page](/reference/events/change-event-status.md) * [Assign team members and tags from the Events page](/reference/events/assign-team-members-and-tags.md) * [Duplicate an event](/reference/events/duplicate-an-event.md) * [Delete an event](/reference/events/delete-an-event.md) * [Create an event from a template](/reference/events/create-event-from-template.md) * [Create a template from an event](/reference/events/create-a-template-from-an-event.md)