The same policy that routes approvals decides how signing happens
Signing isn't a separate tool bolted on after approvals clear. It's the same policy, deciding: below a value threshold your org sets, signing happens natively in-app. At or above it, the policy requires a third party instead. No manual handoff, no second system to configure.
How the threshold works
Set a value threshold on a policy, with its currency. A contract below it signs natively — an eligible signer records a "sign" decision, audit-logged the same way an approval decision is, once every approval step ahead of it has cleared. A contract at or above the threshold is routed to require third-party signing instead. Configure no threshold at all, and everything signs natively.
Fails closed, on purpose
If a contract's value can't be confirmed against the threshold — no value recorded yet, or a currency that doesn't match the threshold's own — the engine doesn't guess in the permissive direction. It requires third-party signing. Getting this wrong should mean more scrutiny, never less.
Type it, draw it, or adopt a style — a signer's real choice
For a contract that signs natively, a signer isn't limited to typing their name. Three methods, all recorded with the same consent checkbox and freshly-retyped name every time — reusing a saved signature never skips that step.
Typed
Type your full legal name fresh, every time — never pre-filled from a prior signature — alongside the consent checkbox. The original method, still there.
Drawn
Sign with a mouse, trackpad, or touchscreen on a real signature pad. The drawing is trimmed to its own bounding box and stored as the actual image you drew — not reconstructed or approximated afterward.
Adopted
Pick a script style and your typed name renders in it — Dancing Script, Great Vibes, Sacramento, or Pacifico, four real typeface choices, not a generic "cursive" filter.
A saved signature, yours across every contract
Save a drawn or adopted signature to your own account — up to ten — and reuse it on any contract you sign, in any organization you belong to. It follows the person, not the org membership, since it's your handwriting or style preference either way.
A real viewer, not just a record that signing happened
A "View signature" link on the contract's workflow panel opens the actual captured signature — the drawn image or the styled name — alongside the signer's typed name, method, and consent timestamp. Anyone who can see the contract can verify what was actually signed, not just that a checkbox was checked somewhere.
Who signs first is your choice
For a contract the other side also signs, an organization admin chooses the signing order from five options, on an approval policy or on a single record. Whatever the order, nothing is signed until every internal approval has cleared.
Five signing orders
Both - Either Order, Both - External First, Both - Internal First (the default), External Only and Internal Only.
Locked once the counterparty is invited
The order can be changed until the counterparty has been invited. After that it is fixed for that record.
Retract, or amend
Until both parties have signed, the sender can retract a signing, which takes the documents back; earlier approvals stay. Once a signing is complete it is locked for good, and a later change is made as an amendment, which is a new signing.
The blanks are set before signing opens
Fields to fill are the blanks in a contract's Word or PDF documents, such as a name, a date or an address, that the other party completes before they sign.
A checklist before you route
When you route a record that has fields you can still shape, a checklist lists them first, so you can set each one required or optional and confirm or dismiss suggestions. Continue and route sends it; Cancel does not. A record with no such fields routes exactly as before.
Fixed when the signing opens
Which fields exist, who fills each one in and whether each is required or optional are fixed when the signing opens, which can be before anyone has signed. After that you can only dismiss a suggestion nobody confirmed. Your own values stay editable until your side signs, and retracting the signing unlocks the definitions until the next signing opens.
Know the signing method before you commit
The same dry-run evaluation that tells you who would have to approve a hypothetical contract also tells you which signing method it would require — before the contract exists, no document and no workflow started.See dry-run evaluation on the DoA engine page →
What this actually is
This isn't a document-preparation or signature-capture product on its own — it's routing intelligence. Who has to sign, and whether that needs to go through a stronger third-party channel, decided by the same policy that governs approvals, not a separate configuration to maintain.
The DoA engine
The policy that decides who signs is the same one that decides who approves.
Contract records
The value on the record is what the threshold actually checks against.
No separate line item for signing
Signature routing is part of the base price on every tier. See the published figures.