Sending and Signing BEOs & Contracts Electronically

Sending & Signing BEOs and Event Contracts Electronically: Document Generation, Approval Gateways, Multi-Signer Dispatch & Declined Document Recovery

Parent Hub: πŸŽ›οΈ EventKey Operations Hub

Category: πŸ–₯️ Manage Events & Lifecycle Execution

Target Roles: Event Sales Managers, Catering Directors, Conference Services Managers, Banquet Operations Managers, Systems Administrators

Last Updated:

Executive Overview

In EventKey, the integrated Electronic BEO & Contract Signing engine enables sales and catering teams to generate, dispatch, track, and digitally execute both Banquet Event Orders (BEOs) and formal event contracts directly from the Event Record. Eliminating manual printing, scanning, and external PDF attachments, the platform routes secure, time-stamped signature links to designated signers, tracks individual signer progress, manages client revision requests or declines, and archives executed copies automatically onto the reservation folio. While BEOs require internal approval prior to dispatch, both BEO Contracts and Event Contracts follow the exact same unified sending, tracking, and resending workflows once generated.

Operational Prerequisites & Document Guardrails

Before generating or dispatching electronic documents from the Contracts tab, verify that the following platform prerequisites and document-specific rules are satisfied:

  1. Event Status Requirement: The Event Record must be in Tentative (or Confirmed) status to generate and send BEOs or contracts, unless Allow Doc Generation On Prospect is enabled under Event Administration > Advanced setup > Application Configuration.

  2. Sender Email Authentication: The property's outbound email address must be entered and verified under Application Configuration > Email From (Verify) before digital signature invitations can be transmitted.

  3. BEO-Specific Guardrail β€” Mandatory Approval Status (Approved Only):

    ⚠️ Strict BEO Approval Gatekeeper:

    Only BEOs in Approved status can be generated into a BEO Contract and sent to clients for review and signature. When clicking Generate BEO Contract, the selection modal displays only BEO versions that have been internally approved under Actions > Print BEO. BEOs remaining in Draft or Pending Review status are excluded from client dispatch. (Note: Standard Event Contracts do not require a separate approval status step prior to generation).

  4. Property Contract Templates: While EventKey dynamically merges reservation data (event dates, spaces, rates, and contact blocks), formal legal contract templates must be uploaded and configured by property administration under Events Setup > Event Contracts.

Step 1: Generating the Document (BEO Contract vs. Event Contract)

Depending on whether you are dispatching an operational Banquet Event Order or a legal Event Contract, select the appropriate generation button on the Contracts tab (Home > Event Management > Select Event Record > Contracts tab):

Document Type

Generation Button

Configuration & Staging Steps

Banquet Event Order (BEO)

Generate BEO Contract

  1. Click the blue Generate BEO Contract button.


  1. In the Generate BEO Contracts modal, check the box next to the Approved BEO version (e.g., BEO Version 1.pdf).


  1. Click the blue Generate button.


  1. The BEO is staged in the Contracts grid in Not Signed status, and its status in BEO Versions updates to Distributed.

Standard Event Contract

Generate Contracts

  1. Click the blue Generate Contracts button.


  1. In the Generate Contracts modal, check the box next to the desired property contract template (e.g., Trade Show Contract).


  1. Click the Contract Due Date calendar icon to select the signature deadline (e.g., December 1, 2026).


  1. Click the blue Generate button. The contract is staged in the Contracts grid in Not Signed status.

πŸ“· VISUAL CALLOUT:

Contracts Tab: Document Generation Controls

(Left) The Generate BEO Contracts modal displaying Approved BEO versions ready for selection; (Right) The Generate Contracts modal showing property contract templates (Trade Show) and the Contract Due Date calendar picker (December 1, 2026) alongside the blue Generate button.


Image 11-16-26 at 12.45β€―PM.png
Generate BEO Approved Versions
Generate Contracts.png
Generate Contract Templates

Step 2: Unified Electronic Dispatch Workflow (BEOs & Contracts)

Once generated and staged in Not Signed status, both BEO Contracts and Event Contracts use the exact same sending workflow:

Step

Action

Platform Guidance & Operational Details

  1. Open Email Configuration

Locate the staged document row in the Contracts table (e.g., Grinch Who Stole Christmas_BEO or Trade Show) and click its blue Send Contracts button.

Launches the Send Contracts email composition modal.

  1. Assign Signers

Click Signer1 (or Signer2 / Signer3 for BEOs) and select the recipient contact from the dropdown (e.g., John Smith β€” Guest, PRIMARY_CONTACT).

  • BEO Contracts: Support up to three signers (Signer1, Signer2, Signer3).


  • Event Contracts: Support the designated contract signer.

  1. Add CC/BCC & Subject

Optionally select internal team members or stakeholders under CC or BCC. Enter a descriptive email Subject line (e.g., Event BEO or Event Contract).

CC/BCC recipients receive a copy of the email notification for visibility but cannot execute signatures.

  1. Compose Body & Insert Link

Enter your message in the Body rich text editor. Click the Review and Sign Button icon on the right side of the editor toolbar to insert the mandatory $$review_and_sign_btn$$ token.

Mandatory Link Token: The $$review_and_sign_btn$$ placeholder renders the interactive blue Review & Sign button in the recipient's email.

  1. Send Document

Verify all recipient addresses and message details, then click the blue Send button in the lower-right corner.

Dispatches secure, time-stamped signing links to all designated signers and returns to the Event Record.

πŸ“· VISUAL CALLOUT:

Send Contracts Email Configuration Modal (Using BEO Contract)

Email dispatch window showing Signer selection (John Smith β€” Guest, PRIMARY_CONTACT), Subject (Event Contract), formatted message body, and the required $$review_and_sign_btn$$ token inserted above the blue Send button.

Send Contract Email Configuration

Client Experience: Reviewing, Signing, or Declining Documents

When the email arrives in the client's inbox, clicking the blue Review & Sign button launches the secure Online Signature web portal:

  • Navigating & Reviewing: The left sidebar displays page thumbnails (Page: 1, Page: 2, Page: 3), enabling the signer to inspect all event schedules, room arrangements, amenities, rates, and legal terms.

  • Signing & Confirming:

    1. Scroll to the bottom of the final page and click inside the blue Signature block (or Click to Sign button).

    2. In the Add Signature modal, use a mouse or touchscreen to draw a signature (or select Upload Picture / type signature if enabled in Application Configuration) and click Save.

    3. Click the blue Confirm button at the bottom of the document.

    4. The portal displays "The document was signed successfully" with a View Document button, sends an email alert ("Signing completed by a signer"), and automatically updates the PMS status to Signed once all signers complete the flow.

πŸ“· VISUAL CALLOUT:

Executing Your Contract as a Client (Video uses a BEO Contract)

Executing Your Contract as a Client
  • Declining & Requesting Revisions for BEO Contracts:

    • If a client identifies an error or requests modifications, they can click the red Decline button next to Confirm at the bottom of the signature portal.

    • The portal displays: "The document is declined. Revision Requested." and transitions the document status in EventKey to Declined.

πŸ“· VISUAL CALLOUT:

Declining Your BEO Contract as a Client

Declining Your BEO Contract as a Client

Tracking Signers, Resending Reminders & Handling Declined Documents

In the Contracts tab of the Event Record, operators use the same tracking and recovery workflows for both BEOs and Event Contracts:

1. Monitoring Signer Progress & Using "Send Again"

  • Click the + (expand) icon to the left of the BEO or Contract name to view individual signer rows.

  • The expanded table details each Signer name, Type (BEO_FORM or EVENT_FORM), Last Requested on date, and individual Signed on status (Not Signed or Signed).

  • Resending to Unresponsive Signers: If a signer has not yet responded or misplaced the email, click the blue Send Again link directly beneath the Last Requested on date on that signer's row to re-trigger the signature invitation email immediately.

πŸ“· VISUAL CALLOUT:

Expanded Multi-Signer Tracking & Delete Contract Confirmation

(Left) Expanded Contracts grid showing individual signer statuses, Not Signed badges, and the clickable Send Again links; (Right) The Delete Contract confirmation modal required before issuing a revised BEO or Contract.


Image 11-16-26 at 1.55β€―PM.png
Expanded Contract Grid
Image 11-16-26 at 1.56β€―PM.png
Delete Contract Confirmation Modal

2. Recovering from a Declined Document (Declined Status Workflow)

When a client declines a BEO or Contract in the online portal, the row transitions to Declined status and cannot be re-sent as-is. To issue a revised document for signature:

Step

Action

Platform Guidance & Operational Details

  1. Delete Declined Document

On the Contracts tab, locate the declined row, click the red Delete Contract button, and click Delete in the confirmation modal.

Permanently removes the declined document package from the Contracts tab without altering underlying event data.

  1. Update Event & Re-Generate

Apply the requested changes to the Event Record.


  • For BEOs: Click Actions > Print BEO > Create New BEO, generate the revised version, and update its status from Draft to Approved in the BEO Versions modal.


  • For Contracts: Proceed directly to re-generation once event fields are updated.

Ensures the document reflects the latest negotiated terms and satisfies BEO approval rules.

  1. Re-Stage & Send

On the Contracts tab, click Generate BEO Contract (selecting the newly Approved BEO) or Generate Contracts (selecting the contract template), then click Send Contracts to end the Sent Contract modal and dispatch fresh signature links.

Restarts the electronic signature cycle with updated document terms.

πŸ“· VISUAL CALLOUT:

Recovering from a Declined Document (Declined Status Workflow)

Recovering from a Declined Document (Declined Status Workflow)

Downloading & Archiving Executed Documents

  • Master Document Download: Once all designated signers complete their signatures, the master row status updates to Signed. Click the blue Download button on the main row to save the complete, signed PDF with embedded timestamps and signature blocks.

  • Individual Signer Form Download: Expanding the row (+) provides a Download Form link under the Signed on column for auditing individual signer certificates.

  • Email Notification Receipt: Internal event coordinators automatically receive a confirmation email ("Signing completed by a signer") containing a direct View Document button whenever a signer completes their signature.