> 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/share-and-track-event-contract.md).

# Share and track an event contract

Clients access an event contract through the Client Portal. Prepare the terms on **Details**, share the portal from **Proposal**, and track the generated document in **Details > Files**.

After a contract is generated, the event's Files section separates contract documents from ordinary attachments.

<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-5865682e02146bbde05ca6ea334ce8061b8d8423%2F01-files-overview.png?alt=media" alt="FlowerBuddy Details tab showing the Files section with a Contracts area containing a generated booking document and an Attachments area below it." width="550"><figcaption></figcaption></figure></div>

## Confirm that the contract is ready

Before sharing the Client Portal:

1. Open **Details > Contract**.
2. Confirm that **Enable** is on and the Automatic Signature Authorization notice is current.
3. Confirm that at least one contract is listed.
4. Select **Preview** and review the complete agreement.
5. Open **Details > Contact Info** and confirm that the intended client has the **Signer** label and a correct email address.
6. Review the payment schedule, especially any amount due relative to **Contract Signing**.

## Share the signing access

1. Open the event's **Proposal** tab.
2. Review the proposal and any publication warnings.
3. Publish the Client Portal when it is not already published.
4. Copy its link for an approved message, or use the available email action only after confirming the recipient.

Sharing the Client Portal does not sign the contract for the client. The signer opens **Contract** in the portal and starts the signing process there.

If you use a FlowerBuddy send action, it sends an external message. Check the recipient and the agreement before confirming it.

## Generated contract documents

Editable contract terms and generated documents are different records. The terms exist in **Details > Contract** before signing begins. FlowerBuddy generates the event contract document after the signer enters the contract process.

Open **Details > Files > Contracts** to track it:

* **Not Signed** means one or more required signing steps remain.
* **Signed** means the agreement has completed its signing requirements.

Open an unsigned document to understand what is pending. If it was generated for the wrong signer or outdated terms, delete the unsigned document before making the protected changes and generating a replacement.

When the document is signed, open or download the PDF from **Files**. A signed document establishes the contracted values that FlowerBuddy uses when it identifies later amendments.

## Resolve a missing contract

If the Client Portal does not offer contract signing, check that:

* contracts are enabled for the event;
* the automatic signature authorization is active;
* contract terms are present;
* one client is the signer;
* the required signer fields can be completed; and
* the Client Portal is published and available.

Resolve the displayed warning at its source. Do not create repeated signing documents while an existing unsigned document is still active.