Contracts & eSignatures

Require a signature from each recipient, let clients sign by typing or drawing, and hold the contract until everyone who needs to sign has signed.

Signatures aren't a separate product in Foreman — they're a setting on the record. Turn on a signature for any recipient of a Client Agreement (proposal, contract, change order) or a Vendor Agreement, and that person has to sign before the record counts as accepted. Bid Requests carry the same per-recipient toggle, with a different meaning — see the note at the end.

Require a signature per recipient

  1. Open the record in the builder.
  2. In the side panel's Recipients section, add the people who'll receive it.
  3. Each recipient row has a Signature? toggle — switch it on for everyone who must sign.

Note

The toggle is per recipient, so you can require a signature from the homeowner but leave a cc'd partner as view-only.

What the recipient sees

When a client opens a record that requires their signature:

  1. A consent screen appears: they check I agree to use electronic records and signatures. and click Continue to Sign.
  2. They tap the highlighted Sign here field in the document.
  3. The Adopt Your Signature window opens. On the Type tab they type their name and pick a signature font; on the Draw tab they draw it with a finger or mouse (their name is still required). They check the agreement beneath the signature preview, then click Adopt and Sign.
  4. Back in the document, they click Complete Signing (Sign on a phone).

The signature, the date, and the signer's name are stamped onto the record and saved for your files.

The all-or-nothing gate

When more than one recipient is required to sign:

  1. A client agreement with required signatures shows Pending after sending. A vendor order starts as Sent and can move to Pending after a partial response.
  2. Each signature is recorded as recipients sign, but automatic acceptance waits for the last required signer.
  3. Only when every required recipient has signed does it flip to Accepted and commit to the budget.

This is the automatic signature workflow. A builder can separately use Mark Accepted on a client agreement to record acceptance obtained outside Foreman; that override does not create missing recipient signatures.

Decline

A recipient can click Decline instead of signing, then confirm with Decline Proposal for a client agreement or Decline Order for a vendor order. The response is recorded as declined. For vendor orders this is the recipient's response; it does not automatically change the whole order's status.

Note

A Bid Request signs a little differently: the vendor adopts their signature as part of submitting their quote, and it binds them to the prices they entered rather than to a contract you wrote. See Bid requests.

Don’t see this?

If the Signature? toggle isn't shown on a recipient, that record type doesn't support signing — only Client Agreements, Vendor Agreements and Bid Requests do.