Contracts & Documents

Creating Contracts

Building contracts from templates, clauses, and payment terms.

A contract is written in the app, sent by email, and signed electronically. You can start from a template, pull in standard clauses, and set the payment terms on the same form.

The Contracts page

Open Contracts from the sidebar. Five stat cards sit at the top — Total Contracts, Expiring Soon, Pending Signatures, Signed Contracts and Total Templates — above three tabs: Contracts, Templates and Analytics, each showing its count.

Two quick filters narrow the list fast: Expiring Soon and Needs Action. There's also a search box and a status filter.

The status filter offers Completed and Cancelled, but a contract's status is only ever Draft, Sent, Viewed, Signed, Rejected or Expired. Those two filters match nothing. Voiding is tracked separately, as a flag rather than a status.

Writing one

The builder opens as a form.

Client and dates

Select Client is required and drawn from your leads. The wedding date fills itself in if that client has a wedding. Set when it was sent and when it's due to be signed by.

The contract body

Load from Template fills the body from a template, substituting the real client and wedding details as it goes.

The body is a rich text editor. View History shows previous versions, which is worth knowing about before you overwrite something.

The Clause Library

Clause Library opens a searchable collection of pre-written sections, filtered by All, Pricing, Cancellation, Liability, Venue, Caution, Timeline or Custom.

Each clause shows its category and, where relevant, a Required marker. Preview reads the full text; Insert drops it into the contract at the cursor.

Payment terms

A total, a deposit and its due date, and a schedule of milestones with their own dates and amounts. These appear on the client's copy as a payment table.

Your signature

If you sign first, there's a signature pad on the form. You can also sign after the client.

Variables

Contract text can carry placeholders that are filled in per client. The format is double braces around a lowercase name — {{client_name}}, {{wedding_date}}, {{venue_name}} — and the surest way to insert one correctly is the variable picker in the template editor rather than typing it.

This matters more than it looks. A mistyped placeholder is not flagged; it stays in the document as literal text, and if the contract is then signed, that text is in the signed agreement.

The available variables cover the client (name, email, phone), the wedding (date, time, venue, guest count, planner), your venue (name, address, phone, email, website), the contract itself (number, date, expiration) and the money (total, deposit, deposit due date, balance), plus a services summary.

Saving and sending

Publish finalizes the contract and emails it to the client. Saving without publishing keeps it as a draft you can edit freely.

Once sent, it also appears in the couple's Planning Hub if contracts are switched on there.

Tip: Build the payment schedule here rather than in the body text. Milestones set on the form render as a table on the client's copy and feed the reminders; the same dates typed into a paragraph do nothing.

Still stuck? A person reads every email.

If a guide and the app disagree, the app is right. Tell us and the guide gets fixed.

Email support