> 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/proposal/scope-of-services.md).

# Scope of Services

**Scope of Services** is the proposal section that summarizes what the event includes for the client. It can present event recipes, recipe groups, quantities, selected prices, discounts, taxes, and the total that the event currently calculates. It is a client-facing view of event information, not a replacement for the internal **Recipes** tab.

In a proposal preview, Scope of Services shows the client's line items. This example includes bouquets with their quantities, prices, descriptions, and photos.

<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-2a10bb1a6e8cfc60238582fa40dbbedc6a0d99dd%2Fscope-of-services.png?alt=media" alt="FlowerBuddy proposal preview showing the Personals section with Bridal Bouquet and Bridesmaids Bouquet, including quantities, unit prices, totals, descriptions, and a bouquet photo." width="550"><figcaption></figcaption></figure></div>

## Add or open the section

1. Open the event and select **Proposal**.
2. Open **Section Settings** for **Scope of Services**, or add it above the section where you want it.
3. Review the section on the proposal canvas.

Scope of Services is a special section. It is part of the proposal's structure and cannot be removed or disabled through the ordinary section switch. Its content follows the event's included line items and their current values.

## Client view

The section can show a recipe or recipe group as a client-facing line. A group can represent several recipes while keeping the individual recipes available for production planning. The quantity and price shown depend on the event item and the proposal's display settings.

When the section has a populated event, review these areas:

* The order of recipes and recipe groups.
* The client-facing name and description.
* Quantity and optional-item choices.
* Recipe price and item detail visibility, when those settings are available.
* Section subtotals and the event total.
* Discounts, taxes, and applicable fees that the event currently includes.

The available item and price values come from the event. Change those underlying event values in the page that owns them, then return to Proposal and preview the result. Do not use a proposal style control to change a contract or payment setting.

## Check amendments

When the event has pricing or date changes held as amendments, the section can show the amended values after **Amendments Published** is turned on. If inline amendments are available in the rendered view, the proposal can show the original and amended information together. Review the section in **Preview Proposal** before sharing it.

## Preview line items and totals

The section is ready to review when its line items, quantities, and totals match what you intend to present. Select **Preview Proposal** and read the section as a client would. If an item is missing, check whether it is included in the event and whether its quantity is greater than zero. If a total is unexpected, review the event's pricing, taxes, discounts, and fees on their owning tabs.

The bottom of the section brings the line items together with the event's subtotal, discounts, taxes, and total.

<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-623e40fa722f7de13c83a745f381755083b2c835%2Fscope-of-services-totals.png?alt=media" alt="FlowerBuddy proposal preview with delivery and event labor line items followed by a populated subtotal, Autumn collection discount, FlowerBuddy Example Tax, and the event total." width="550"><figcaption></figcaption></figure></div>
