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.
Require a signature per recipient
- Open the record in the builder.
- In the side panel's Recipients section, add the people who'll receive it.
- Each recipient row has a Signature? toggle — switch it on for everyone who must sign.
Note
What the recipient sees
When a client opens a record that requires their signature:
- A consent screen appears: they check I agree to use electronic records and signatures and click Continue to Sign.
- They tap the highlighted Sign here field in the document.
- In the signing window they either Type their name (and pick a signature font) or Draw it with their finger or mouse.
- They click Complete Signing.
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:
- The record moves to Pending (awaiting signatures) as soon as it's sent.
- Each signature lands as recipients sign — but the record stays Pending until the last required signer signs.
- Only when every required recipient has signed does it flip to Accepted and commit to the budget.
This means a partially-signed contract is never treated as accepted — you always have every signature before it counts.
Decline
A recipient can click Decline instead of signing. You're notified, and the record moves to Declined.
Don’t see this?