> For the complete documentation index, see [llms.txt](https://help.getweddingos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.getweddingos.com/sales/contracts.md).

# Contracts

In WeddingOS, your contract is part of the proposal. Clients read and sign both in a single step. There is no separate contract workflow.

***

## Where your contract text lives

Contract text is stored per package in **Settings > Packages**. Each package has its own contract, so your Full Planning agreement can be different from your Day-Of agreement.

To edit: go to Settings > Packages, click the package, and scroll to the **Contract Text** section. The editor supports basic formatting.

***

## Template variables

Your contract text can include variables that WeddingOS fills in automatically when the proposal is sent:

| Variable           | What it inserts                         |
| ------------------ | --------------------------------------- |
| `{{CLIENT_NAME}}`  | Primary client's full name              |
| `{{FIANCE_NAME}}`  | Partner's full name                     |
| `{{EVENT_NAME}}`   | Event name (e.g. "Smith/Jones Wedding") |
| `{{WEDDING_DATE}}` | Wedding date                            |
| `{{VENUE}}`        | Venue name                              |
| `{{TOTAL_PRICE}}`  | Total contract value                    |
| `{{PACKAGE_NAME}}` | Package name                            |
| `{{COMPANY_NAME}}` | Your business name                      |
| `{{PLANNER_NAME}}` | Assigned planner's name                 |

The full list of available variables is shown in the panel next to the contract editor in Settings > Packages.

***

## How signing works

When you send a proposal, WeddingOS takes a snapshot of the contract text at that moment and saves it to the proposal record. Edits to your package contract later do not affect proposals that have already been sent.

The client receives a link to a page showing:

1. Package name and inclusions
2. Total investment and payment schedule
3. Full contract text

They type their name and click Sign. That name, the timestamp, and their IP address are recorded. A signed PDF is generated and saved to their Google Drive folder.

***

## After signing

The proposal status card on the client's profile shows **Signed** with a link to the signed PDF in Drive. Open that link to download it if you need to send the client a copy.

***

## If you don't use WeddingOS proposals

If you sign contracts outside of WeddingOS, the contract section won't appear on the client's profile. Everything else (payments, checklists, vendors, timeline) still works normally. See [Converting a Lead to Booked](/sales/converting-lead-to-booked.md) for how to book clients who signed offline.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.getweddingos.com/sales/contracts.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.