E-signatures
Electronic signing consent
A single line above the submit button asks the signer to agree that signing electronically counts. It is the least visually interesting part of the flow and one of the more useful things kept afterwards.

What it says
I agree to sign electronically, and that my electronic signature is as binding as a handwritten one. It sits in the bar fixed to the bottom of the signing view, beside the running status line and the Finish signing button, so it is never scrolled past or hidden behind a fold. It is unticked when the page loads and stays that way until the signer deliberately ticks it.
It cannot be skipped
Pressing Finish signing without it shows the reason rather than silently failing. That check is repeated when the submission reaches the server, which refuses it outright if the consent flag is not present. A consent gate that only exists in the browser is not a gate, so it exists in both places, and the server one is the one that counts.
The wording is versioned
The consent carries a version string, set on the deployment rather than per envelope. It is included in the challenge payload before signing and again with the document, so the version the signer was shown is the version that travels with the submission. When the wording changes, older signatures keep the version they actually agreed to instead of retroactively appearing to have agreed to something new.
What is stored per signer
Three things go onto that recipient's row at the moment of submission: the timestamp when consent was accepted, the version string, and, separately, the hash of the document as it stood at that instant. The consent version also lands in the metadata of the signed event in the audit trail, so it appears in two independent places rather than one.
Where it shows up afterwards
The certificate of completion gives each signer their own block, and one of its rows reads Consent accepted, followed by the exact timestamp in UTC and the version in brackets. That is the line worth pointing at if anybody ever asks whether the person understood they were signing rather than filling in a form, because it names the moment and the wording together.
How it works, in three steps
Step 1
The signer opens the document
The consent line is already in the bottom bar, unticked, next to the status telling them what is still outstanding.
Step 2
They tick it before finishing
Pressing Finish signing without it names the missing consent rather than failing quietly.
Step 3
It is recorded with the signature
Timestamp and version go onto the record and onto the certificate, alongside the hash of the document at that moment.
Limits worth knowing
- The wording is fixed. You cannot substitute your own consent text per envelope or per signer.
- There is no opt out. A signer who will not tick it cannot complete the signing.
- The version comes from the deployment, so every envelope signed on a given day carries the same one.
- Consent is recorded at submission. There is no separate earlier step for it.
Questions people ask
Can I change the consent wording for my industry?
No. It is one fixed sentence for every envelope. Anything specific to your situation belongs in the document itself, which is what the signer is actually signing.
What happens if a signer refuses to tick it?
They cannot finish. The honest path for them is the Decline button, which records a refusal with an optional reason rather than leaving the request hanging.
Is the consent shown before they see the document?
The version is carried from the challenge onwards, but the tick itself lives with the document, so they read what they are signing before agreeing to sign it electronically.
Where can I see it later?
On the certificate of completion, in that signer's block, as a timestamp with the version in brackets.
Make your own signing flow
The button opens the generator with this use case already described. Change the wording to match yours, generate, then edit anything you like.
Send a document for signingRelated pages
Certificate of completion
The signed document shows the marks. The certificate shows how they got there. It is a separate PDF built from the event log the moment everyone has finished, and it is the file worth keeping alongside the contract.
The date signed field
Ask a person to type today's date and a certain number of them will type last Tuesday, or their birthday, or nothing. The date on an executed agreement is a fact about when it happened, so it is not something a signer should be typing at all.
E signature consent forms
A consent form is the one document where refusing has to be as easy as agreeing, and where the record of who agreed matters more than the mark on the page. That changes which settings are worth the extra friction.
More finished work of this kind is on the e-signature examples hub.