> 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/recipes/add-recipe-notes-and-build-information.md).

# Add recipe notes and Build information

[Recipes](/reference/event-page/recipes.md) have two note fields. **Proposal Notes** explain a design to the client. **Florist Notes** help you and your team make it. Both can be included in Build instructions, but only Proposal Notes can appear in a proposal.

## Add Proposal Notes

1. Open the event and select **Recipes**.
2. Expand the recipe, then expand **Inspiration Photos & Notes**.
3. Enter client-facing information in **Proposal Notes (can optionally be added to your proposals)**.

Use Proposal Notes for information that can help a client understand the design, such as its overall shape, color direction, or important included elements. On the **Proposal** tab, the Scope of Services **Notes** setting determines whether Proposal Notes appear to the client.

Do not use Proposal Notes for private pricing reasoning or internal substitutions when the client should not receive them.

## Add Florist Notes

Enter instructions for you and your team in **Florist Notes (for your eyes only)**. For example, describe how to assemble the arrangement or which substitution to use if a flower is unavailable. "For your eyes only" means for florists rather than clients, not just the person who wrote the note.

The two fields appear together under **Inspiration Photos & Notes**. In this example, Proposal Notes describe the bouquet's appearance, while Florist Notes give the floral team details to remember when making 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-b0bdb08ab2e3c42018f8e8c0e4151bca2dced7b1%2Frecipe-notes.png?alt=media" alt="Expanded Inspiration Photos &#x26; Notes section of a Bridal Bouquet recipe, with populated Proposal Notes describing the bouquet and Florist Notes giving the floral team design preferences and flowers to avoid. Each note field has a pencil icon for editing." width="550"><figcaption></figcaption></figure></div>

The shared digital **Build** page displays both note fields for the people preparing the designs. In **Build PDF Settings**, **Show Recipe Notes** includes both fields in the PDF too.

## Prepare the rest of the Build information

Build can use more than notes. Complete the recipe information that workers need:

* Add inspiration images that accurately show the intended direction.
* Confirm the recipe and item quantities.
* Add the correct flowers and hard goods.
* Set direct-labor estimates when they help production planning.
* Use recipe groups when one client-facing offering contains several designs that must be built separately.

Changes made on **Build**, such as progress and completion information, serve production tracking. They do not replace the core recipe definition on **Recipes**.

## Review before sharing or printing

**Build PDF Settings** can include recipe images, flower and hard-good images, both recipe note fields, prices, and a QR code for digital instructions. Before generating a PDF, review those choices from the recipient's perspective. Before sharing the digital Build page, review both note fields because the page displays them without the PDF's **Show Recipe Notes** switch.

Check that the notes, images, quantities, and item lists reflect the current design, especially after applying a template or changing the event through an amendment.