> 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/prepare-event-contract.md).

# Prepare event contract terms and signer requirements

The **Contract** section holds the terms that will be combined into the event's agreement. Prepare these terms and the signer information before sharing the Client Portal.

The Contract section shows whether contracts are enabled, the signer information settings, and whether terms have been added.

<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-545b2ab23f1ae74cc4e5a13a63581c8897afce29%2F02-contract-state.jpg?alt=media" alt="FlowerBuddy Details tab showing the Contract section with Enable, Preview, signer information, automatic signature authorization, and a warning that no contract has been added." width="550"><figcaption></figcaption></figure></div>

## Check contract availability

1. Open the event and select **Details**.
2. Expand **Contract**.
3. Turn on **Enable** if contracts are not enabled for this event.
4. Complete the displayed Automatic Signature Authorization step when FlowerBuddy requires it.

Enabling contracts allows clients to view and sign the terms you add. It does not publish the Client Portal or generate a signable document by itself.

The section shows an alert badge when contracts are disabled or the event has no contract terms.

## Add or import terms

Choose the starting point that fits the event:

* Select **Add Contract** to create terms specifically for this event.
* Select **Import** to copy one or more reusable contract templates from your Contract Library.

Imported terms become part of this event. Later edits to the reusable template do not automatically update the event.

When adding or editing a contract, give it a clear name and optional description. Build the agreement from sections:

1. Enter an optional **Heading** and the section **Body**.
2. Add sections where the agreement needs separate topics.
3. Drag sections into the order the client should read them.
4. Insert a contract variable when the text should use a current event or signer value.
5. Turn on **Require client initial** for a section that needs separate acknowledgement.
6. Save the contract.

Contract variables fill the preview or generated document with values such as the event name, date, number, or signer information. Review the rendered result instead of relying on the placeholder alone.

## Choose the signer information to collect

**Signer information** always includes the signer's name and email. Use **Configure settings** to request additional supported information for this event, such as a phone number, address, or company name.

Contract variables can make a signer field required automatically. For example, terms that include a signer address require that address during signing even when it was not selected manually.

In **Contact Info > Clients**, make one client the event signer. Confirm that person's email and any other required information before sharing the contract. Only one client can be the signer at a time.

## Preview the agreement

Select **Preview** to read the combined event contract in its current order. Check:

* that every required topic is present;
* that variables render the expected event and signer information;
* that required-initial sections are intentional; and
* that the signer named in **Contact Info** is the correct person.

Previewing does not create a document, send an email, publish the Client Portal, or sign the agreement.

Contract editing requires event edit access and an unlocked event. Generated documents can also protect terms and signer details while signing is in progress.