> 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/amendments.md).

# Proposal amendments

An amendment records a qualifying change to an event after the agreed version has been established. It is separate from an event lock. Locking helps prevent accidental edits. An amendment keeps the changed value available for review and confirmation.

The event summary can show **Amended** while changed values wait for review, even when you are viewing another event tab. On **Proposal**, the **Amendments Published** switch controls whether the client can review those changes.

<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-b6d2e4796c3b911c735f3f34c9c3412be57ef025%2Fproposal-amendment-controls.png?alt=media" alt="FlowerBuddy Proposal tab on an amended event, with the Amended indicator in the event summary and separate Published and Amendments Published switches above the proposal design." width="550"><figcaption></figcaption></figure></div>

## Amendment state

An event can hold amended values for details such as an event date or pricing-related line-item information. The original and amended values can both matter while the change is waiting for confirmation. The main event status, such as **Booked**, does not by itself decide whether a change is an amendment.

For example, changing the quantity of a centerpiece or changing a price after the agreed version can create an amendment for the client to review. Use the event's normal editing controls to make the change, then inspect the Proposal view for the amendment state.

## Publish amendments for review

1. Open the event and select **Proposal**.
2. Review the amendment indicators and the changed values in **Scope of Services**.
3. Select **Amendments Published** when the updated proposal is ready for client review.
4. Select **Preview Proposal** and confirm that the amended information is presented as intended.

When amendments are published, the recipient-facing proposal can show the amended values and inline amendment information. The exact display depends on which event values changed and on the section's current settings.

The Proposal tab does not replace contract controls. If the recipient must review or sign a new contract document, use the contract controls under **Details** and follow the contract article for that action.

## Confirm amendments manually

Manual confirmation is a consequential event action that accepts an amendment without the client completing the electronic review flow. Follow [manually confirm event amendments](/reference/event-page/overview/manually-confirm-event-amendments.md) for the exact start step, warning, required acknowledgement and note, confirmation control, and result.

Do not confuse manual confirmation with turning on **Amendments Published**. Publishing makes the change available for client review. Confirmation accepts the change into the event.

## Review the amendment preview

The amendment is ready for review or confirmation when the Proposal preview shows the intended current and amended information, **Amendments Published** reflects the sharing decision, and the responsible person knows whether the client must review or the business will confirm manually. Contracts and payments remain under **Details**.