> 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/build/availability-and-content.md).

# Build availability and content

Build availability depends on the event's booking state, workspace plan, event permissions, and whether you are viewing an event or an event template. When **Build** is available, it gathers the event's production work, hard-good quantities, recipe details, and progress controls.

When Build is available, its summary and recipe cards show the production picture you can review before opening individual instructions.

<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-aaa1a703e12ed5fe33d1057aa87f7cfe49df82b6%2Fevent-build.png?alt=media" alt="FlowerBuddy Event Page with the Build tab selected. The page shows completion and labor totals above a Hard Good Pull List and recipe cards with quantities, assignees, and locations." width="550"><figcaption></figcaption></figure></div>

## Open Build

1. Open the event.
2. Select **Build**.
3. Review the summary before opening a recipe.

The summary shows the event's completion percentage and labor totals. Below it, **Hard Good Pull List** groups the hard goods needed for the event. Recipe cards show quantities and, when available, assignees and locations.

## Availability

Build can be unavailable for an event that has not been booked when the workspace plan limits access before booking. When that condition applies, the **Build** tab is disabled and the page explains that it unlocks after the event is booked or that a plan upgrade provides earlier access.

An event template does not include a working **Build** tab. Open the event created from the template to review its production work. A locked **Build** tab is an access condition, not proof that the event has no recipes or hard goods.

## Review the page regions

* **Published**, **Expires**, and **Expiration Date** control the shared Build page.
* **Print** opens the Build PDF settings.
* **Build Tags** opens the tag options.
* **QR Code** creates a QR code for the shared Build page.
* **Copy Sharable Link** copies the shared page link.
* The completion and labor summary shows the current production picture.
* **Hard Good Pull List** shows the hard goods associated with the event.
* Recipe cards show the included production work.

The controls you can change depend on your event permissions. If a control is disabled, ask a workspace member with the needed event access instead of changing the event status or workspace plan just to open it.

## Review the Build information

Build is ready for review when the summary is visible, the expected hard goods are listed, and the recipe cards match the event's production plan. Use [recipe details and locations](/reference/event-page/build/recipe-details-and-locations.md) for the next review step.