Contracts and e-signatures

Templates with merge fields, sequential or parallel signing, renewal reminders, and an ESIGN/UETA audit certificate with document and signature hashes.

Sales → Contracts.

Drafting. Write the body once with merge fields — {ClientName}, {Date}, and any you define — and preview it with the fields resolved for a given client. Set an expiry and a renewal reminder so a contract does not quietly lapse.

Signing. Add signers (name, email, role) and choose the order: Sequential — one after another or Parallel — anyone, any order. Send for signature emails each signer their own Review and sign link from your connected mailbox. Sequentially, only the first signer is emailed; the moment they sign, the next one is emailed automatically, and so on. In parallel, everyone is emailed at once. Pressing it again re-sends to whoever has not signed. What the signer sees is described in What your customer sees: accepting a proposal and signing a contract.

A signature is the signer's typed name against their email, recorded with a timestamp; Record a signature lets you enter one taken on paper or in person, for the next signer in order unless you say otherwise.

Executed is the status once every signer has signed. The audit certificate lists each signature with its timestamp, the hash of the document as signed and the hash of each signature, which is what makes the record hold up under ESIGN and UETA: any later change to the text produces a different hash.

Renewals appear on the list with the renewal date, and the reminder raises a task ahead of it. A contract attached to a Proposals is executed automatically when the proposal is accepted.