> 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-page.md). # Event Page The Event Page brings together everything you are planning for one event: the client, floral designs, prices, proposal, contract, payments, and preparation. Open an event from the [Events](/reference/events.md) page to work on it. For a wedding, you might start with the date and the couple's details, develop bouquets and centerpieces, and present those designs in a proposal. As the plans are agreed, the same event holds the information you need to purchase materials and prepare the arrangements. The page below shows a wedding's summary above its tabs, with the planned arrangements on the **Recipes** tab.
FlowerBuddy Event Page for Amelia and Noah Garden Wedding. The summary shows the event name, date, cost, price, estimated profit, and Inquiry status above the event tabs. The Recipes tab shows populated floral arrangements and their quantities and prices.
## Event information in one place The [event summary](/reference/event-page/overview.md) keeps the event's name, date, status, and key figures visible above the tabs. Cost is what you expect to spend; price is what you charge the client. Estimated profit helps you compare the two, based on the costs you have entered. The main status, such as **Inquiry**, **Proposal**, or **Booked**, shows the event's broad stage. An optional **Workflow Status** adds detail you define for your business, such as "Inquiry: meeting scheduled." ## Event Page tabs Each tab brings together a different part of the event: * [Details](/reference/event-page/details.md): The date, contacts, notes, Event Flowers, timeline, files, contract, payments, and event settings. Event Flowers is the flower palette you plan to use across the designs. The timeline holds activities such as delivery and setup, with their times and locations. * [Tasks](/reference/event-page/tasks.md): Work to complete for this event, organized into individual tasks and task groups. The separate [Tasks](/reference/tasks.md) page brings work from multiple events together. * [Recipes](/reference/event-page/recipes.md): Your floral designs and other costs, including quantities, ingredients, and prices. * [Taxes, Discounts, & Fees](/reference/event-page/taxes-discounts-fees.md): Event taxes, discounts, and applicable fees that contribute to the totals. * [Proposal](/reference/event-page/proposal.md): The presentation you prepare for the client, including the designs, images, and prices you choose to show. * [Order](/reference/event-page/order.md): The flower and hard-good quantities needed for purchasing. * [Build](/reference/event-page/build.md): Recipes, materials, and instructions for making the designs and tracking their completion. * [History](/reference/event-page/history.md): A record of changes to the event, available to workspace owners. If your workspace uses QuickBooks with Accounting Review enabled, you may also see [Accounting](/reference/event-page/accounting.md) for reviewing payments and revenue. It is intended for businesses using accrual accounting. Feature access and event status can affect which tabs you can open. ## Recipes across planning and production A recipe describes how to make a floral design: the flowers, hard goods, and quantities it needs, along with labor and other details used to plan its cost and price. For example, a centerpiece recipe can describe one arrangement, while its quantity tells you how many to make. Those recipes support several parts of the event. **Proposal** presents the designs to your client, **Order** helps you work out what to purchase, and **Build** helps your team make the arrangements. Keeping the recipes current helps those preparations reflect what you intend to provide. The agreement and payments are managed on **Details**. A payment schedule sets out amounts due and their dates; payment records show money received. ## Locks and amendments Locking an event helps prevent accidental edits. Proposal and Booked events are locked by default, while Inquiry events start unlocked. You can [unlock an event](/reference/event-page/overview/lock-or-unlock-event.md) when you intend to make changes. After a contract is signed, pricing-related changes can create amendments. For example, adding centerpieces or changing a quantity can be tracked against what was agreed. You can publish amendments for the client to review and sign, or confirm them manually. Once confirmed, the updated agreement becomes the basis for later changes. See [Manage contract amendments](/reference/event-page/details/manage-contract-amendments.md) for the choices and their effects. ## In this section * [Event summary](/reference/event-page/overview.md) * [Details](/reference/event-page/details.md) * [Tasks](/reference/event-page/tasks.md) * [Recipes](/reference/event-page/recipes.md) * [Taxes, Discounts, & Fees](/reference/event-page/taxes-discounts-fees.md) * [Proposal](/reference/event-page/proposal.md) * [Accounting](/reference/event-page/accounting.md) * [Order](/reference/event-page/order.md) * [Build](/reference/event-page/build.md) * [History](/reference/event-page/history.md)