> 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/help-a-client-sign-an-event-contract.md).

# Help a client sign an event contract

The client signs an event contract from the Client Portal. You prepare the contract and designate the signer from the event, then guide the client through the identity details, email verification, required section initials, and final consent.

Before sharing the portal, [prepare the event contract terms and signer requirements](/reference/event-page/details/prepare-event-contract.md) and [publish the Client Portal](/reference/event-page/proposal/publish-and-client-portal.md). Confirm that the intended client is the event signer and that their email address is correct.

## Check the signer information

Ask the client to open the Client Portal and select **Contract**. If an unsigned document has already been generated, they can open **Documents** and select **Sign** for that document instead.

If FlowerBuddy needs to generate the contract, the client first sees **Document Signing Confirmation**. This dialog asks for:

* **First Name**
* **Last Name**
* **Email**

Depending on your contract signer settings or the variables used in the contract, the dialog can also ask for **Phone Number**, **Address**, or **Company Name**. The client should enter the information for the person who is designated as the event signer. The email must be the signer's email because FlowerBuddy sends the verification code to that address. If an unsigned document already exists, the client can open it from **Documents** and select **Sign** without entering these fields again.

The client selects **Sign Contract** after completing the displayed fields. FlowerBuddy then opens the current contract document for signing.

## Verify the client's email

FlowerBuddy uses a one-time code sent to the signer's email to verify signing. The client should:

1. Check the inbox for the message from your workspace.
2. Enter the code in **Signing code**.
3. Select **Resend code** if the message is not available after the displayed resend countdown.

The code verifies the email address attached to the signer. A code for a different address will not complete the signing process. If the client still cannot continue, check **Details > Contacts & Locations > Clients** and confirm that the intended signer and email are correct before sharing the portal again.

## Complete initials and consent

The contract can require separate acknowledgement for selected sections. Each required section shows an **Initial** checkbox beside its text. The client should read those sections and select every required **Initial** checkbox.

After the required initials are complete, the client selects the consent checkbox under **Electronic Signature**. The checkbox displays the consent text configured for the contract. The consent checkbox cannot be accepted until all required section initials are complete, and selecting it locks those initials for the signing attempt.

The **Sign Contract** button becomes available only when the client has entered the signing code, accepted every required initial, and accepted the electronic-signature consent.

## Recognize completion

After the client selects **Sign Contract** and the submission succeeds, the signing dialog shows **Contract signed** and the final signed PDF. The client can find the completed document in the portal's **Documents** tab.

On the event, open **Details > Files > Contracts** to confirm that the generated document is **Signed**. **Not Signed** means that the document is not complete yet. If the client leaves the dialog before finishing, they can return to the unsigned document and continue the signing process.

If the client needs a different signer or the contract terms need to change, resolve that from the event before asking the client to continue. Use [manage contract amendments](/reference/event-page/details/manage-contract-amendments.md) for pricing-related changes after a contract has been signed.