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

# Manage contract amendments

An amendment is a pricing-related or event-date change made after a contract is signed. FlowerBuddy compares the current event with the contracted version so the changed agreement can be reviewed separately from the original one.

An event being **Booked** does not create this comparison by itself. The signed contract is the starting point.

## Amendment indicators

Changes that can create amendments include:

* adding or removing recipes, other costs, taxes, or discounts;
* changing included quantities or prices;
* changing which line items a percentage cost, tax, or discount applies to; and
* changing the event date.

When the event has pending changes, its status area shows **Amended**. Select it to open the amendment action. Changed fields can also show their contracted values beside the current values.

Contracted values can remain visible beside the current values on pricing rows while an amendment is pending.

<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-932e872e33eed1f9128b948e015d5abbd7171280%2F05-populated-contracted-tax-discount.jpg?alt=media" alt="FlowerBuddy Taxes, Discounts, &#x26; Fees view showing tax and discount rows marked Added with reset icons, illustrating amendment indicators rather than old and new values side by side." width="550"><figcaption></figcaption></figure></div>

## Review what changed

Before asking the client to approve an amendment, compare the amendment summary with the agreement. Review each changed item, the event subtotal and total, and the event date when applicable.

Correct an unintended change before publishing. When a changed field shows a reset icon beside its contracted value, select that icon to restore the contracted value.

## Publish amendments for client approval

1. Open the event's **Proposal** tab.
2. Turn on **Amendments Published**.
3. Review the amendment summary and any other warnings.
4. Confirm that **Amendments Published** remains on.
5. Share the Client Portal only after confirming the intended signer and recipient.

Publishing makes the changes available for the client to review and sign. It does not approve the changes for the client.

After the signer completes the amended agreement, the confirmed values become the contracted basis for later changes. New differences are then compared with that updated agreement.

## Confirm amendments manually

Use manual confirmation only when the client has agreed outside FlowerBuddy and you intend to record that agreement without client e-signature.

1. Select the event's **Amended** status area.
2. Select **Manually Confirm Amendments**.
3. Compare every item in the amendment summary.
4. Read the warning and turn on **I understand and want to continue**.
5. Enter the required **Notes (visible to clients)** explaining the agreement.
6. Select **Manually Confirm Amendments**.

Manual confirmation cannot be undone. It bypasses client review and e-signature, creates an unsigned document that clients can view and download, and makes the confirmed values the basis for later amendments.

Do not use manual confirmation merely to clear an amendment warning. First verify that the client has accepted the changes and that the visible notes accurately describe that agreement.