E-Sign turns a form into a signed document. Instead of just collecting a drawn signature in a field, you send the signer a private link, show them the full agreement, capture their signature in a dedicated signing ceremony, and keep a hashed PDF plus a complete audit trail of who signed what and when.
E-Sign is a Pro feature. The signature field and the E-Sign module are different things: the field captures a squiggle inside a normal submission, while E-Sign produces a standalone executed document you can hand to a client or a court.
How it works
- Write a document template. Templates live under Tiger Forms → Documents. Merge tags pull answers straight out of the submission, so one template serves every customer.
- Attach it to a form. When the form is submitted, the document is generated from the template with that submission’s values baked in.
- Invite the signers. Each signer receives their own signed link. Nothing is public: the link carries a purpose-scoped token, so a link issued for signing cannot be replayed to download the finished PDF.
- They sign. The ceremony page shows the agreement in full, records that it was opened, and captures the signature.
- It is executed. Once the last signer has signed, the PDF is finalised, hashed and stored, and everyone gets a copy.
Multiple signers
Signers are sequential. Each holds a position, and the next person is only invited once the one before them has signed — which is what you want for a countersigned agreement. A signer cannot jump the queue by guessing a URL: their token is only valid when it is their turn.
If someone is slow, automatic reminders chase them on a schedule you set, and stop as soon as they sign.
The audit trail
Every meaningful event is recorded and never edited afterwards — the log is append-only. It captures when the document was sent, when each signer opened it, and when each signature was applied, together with the finished document’s hash. Because the hash is stored alongside the record, you can prove later that the PDF you are holding is byte-for-byte the one that was signed.
Holding a booking until the waiver is signed
If you also run Tiger Booking, E-Sign can gate a booking on its waiver. The appointment is still created — you never lose the lead, and the customer is not left staring at an error — but it opens as pending and is only promoted to confirmed once every signer has signed.
The gate is deliberately narrow. It blocks the move into a confirmed state and nothing else: cancelling, rescheduling and completing are always allowed, because a gate that traps a booking in limbo is worse than no gate at all. If the front desk tries to confirm too early they are told exactly why, so they can re-send the document instead of filing a support ticket.
Data protection
A personal-data export includes who was asked to sign and what happened to each request. An erasure request is handled differently from ordinary submissions: an executed agreement is anonymised rather than deleted, because the record of a signed contract is exactly the kind of thing the “legal claims” exemption exists for. The identifying details go; the fact that a document was executed, and its hash, remain.
Troubleshooting
The signer says their link does not work.
Signing links are single-purpose and expire. The most common cause is that it is not that person’s turn yet — signers are invited in order. Open the document in the admin and check which position is currently pending. Re-sending the invitation issues a fresh link.
The document never reaches the signer.
This is nearly always mail delivery rather than E-Sign. Open Tiger Forms → Settings → Mail and read the Delivery check panel — it inspects SPF, DKIM, DMARC and sender alignment for the address you send from and tells you which one is failing. A From address on a free mailbox such as Gmail is rejected outright by most providers; use an address on your own domain.
The booking stayed pending after the waiver was signed.
The booking is promoted when the last signer signs, not the first. If several people are on the document, check whether any position is still outstanding. If the booking was created after the signature was collected, it is promoted on the next status change rather than retroactively.