Contracts
Draft contracts with a rich-text editor, track parties and signatures, and move each contract cleanly through its lifecycle.
#The contracts list
Contracts are shown in a table with status tabs across the top: All, Draft, Active, Pending Signature, Signed, Executed, Cancelled, Expired. Summary cards above the table report Total, Active, Pending Signature, Expiring Soon, and Total Value.
Table columns: Contract name, Client, Status, Execution date, Value, Party count.
#Create a contract
Create Contract opens a modal with three tabs. You can save a contract with just the Details tab filled in and come back to add content and parties later.
Details tab
| Field | Type | Description |
|---|---|---|
| name* | text | The contract title — shown everywhere. |
| description | textarea | Short summary of the agreement. |
| clientId | combobox | The client the contract is with. |
| contractType | dropdown | Service Agreement, NDA, MSA, Vendor, Retainer, etc. |
| value | number | Total contract value in workspace currency. |
| startDate | date | When the contract becomes effective. |
| endDate | date | End of term. |
| renewalDate | date | Optional — date the contract auto-renews or needs attention. Drives the “Expiring Soon” summary. |
Parties tab
A signatory row per party — name, email, and (after sending) signature status. Use Add Party to add as many signers as you need.
Content tab
A full rich-text editor for the contract body (see Contract content below). You don’t need to fill it in before saving; draft shells are fine.
#The content editor
The contract body is built on BlockNote, a block-based rich-text editor. You get the tools you’d expect — headings, lists, tables, bold/italic, inline links, blockquotes — plus the ability to paste formatted content from Word or Google Docs and have it come through cleanly.
This Service Agreement ("Agreement") is entered into as of {{effective_date}} between {{client_name}} ("Client") and SynqHub Inc. ("Provider").
1. Services. Provider agrees to deliver the services described in Exhibit A, including discovery, design, implementation, and post-launch support.
2. Fees. Client shall pay Provider {{total_amount}} according to the milestone schedule set out in Exhibit B.
3. Term. This Agreement commences on the Effective Date and remains in effect until the Services are completed, unless terminated earlier per Section 8.
{{client_name}} or {{effective_date}} in your draft. They’re resolved when the contract is sent for signature.#Parties & signers
Every party you add on the Parties tab appears on the detail page with their current signature state: Pending, Requested, Signed, or Declined. The detail page gives you inline actions to request a signature, resend the request, or view what the signer received.
#Signatures
Click Request Signature next to a party to trigger a signature email. The party status moves to Awaiting. When they sign, the status flips to Signed and the signed timestamp is recorded.
#Status workflow
Contracts move through a deliberate set of states. You can trigger each transition from buttons on the detail page header:
- Draft — work in progress. Editable by anyone with access.
- Active — internal sign-off; ready to send out.
- Pending Signature — sent to one or more parties.
- Signed — all parties have signed.
- Executed — final state; all obligations kicked off.
- Cancelled — terminated before execution.
- Expired — end date passed without renewal.
Every transition lands in the Activity tab with who did it and when — your audit trail without extra work.