Sending a PDF to one or more signers

When you have a PDF that needs signatures — a contract, an NDA, a vendor agreement, a permission slip — the Documents module sends it directly to the signers without leaving Turtini and without paying for a separate e-sign tool. Each signer gets their own personalized signing link.

How to send:

1. **Open Documents** → find the PDF you want signed.
2. **Click "Send for signature"** on the row. An inline form expands.
3. **Add each signer's name and email** — one row per signer. Click "+ Add another signer" for additional signers. Up to 10 per request.
4. **Pick the routing mode:**
- **All sign at once (parallel)** — every signer gets their email immediately. They sign in whatever order they like. Use for documents where the order doesn't matter (e.g. an NDA where each party is signing independently).
- **Sign in order (sequential)** — only the first signer is emailed initially. When they complete their signing, the platform notifies the next signer. Use for documents where one signer needs to review before another (e.g. employee → manager → HR).
5. **Add an optional note** — short message included in each signer's email. Helpful for context ("Please sign by Friday so we can submit to the city").
6. **Click "Send for signature."** The platform creates a signature request, generates per-signer tokens, and sends the emails.

What each signer receives:

A personalized email from `[email protected]` with:
- A greeting using their name
- Who is requesting the signature (your name + email)
- The document name
- Your optional note (if any)
- A prominent "Review and sign" button that opens their unique signing link

The signing link is unique per signer — they can sign without creating a Turtini account. The link doesn't expire on a fixed timeline, but you can revoke a signer's pending status from the document at any time (which invalidates the link).

What the document looks like during signing:

The document's status changes from "Draft" to "Out for signature" in the Documents list. Hovering over the status badge shows progress: "2 of 3 signed."

When every signer has signed, the platform:
- Stamps each signature image into the PDF at the correct location.
- Adds a Verified-by-Turtini audit page on the back with each signer's IP, user-agent, timestamp, and SHA-256 of their signature image.
- Updates the document status to "Signed."
- Emails the final signed PDF to every signer + you (the requester).

If a signer hasn't signed:

- Open the document row → check the signature request panel. You'll see who's signed and who's still pending.
- Click "Resend" on a pending signer to email them a fresh copy of the request.
- Click "Remove signer" to revoke their pending signature. (If you do this on a parallel request, others can still sign. If you do it on a sequential request and you remove the current signer, the request stalls — recommend removing the request entirely and starting over.)

If a signer declines:

The signing page has a "Decline" option that records the signer's decision and stops the request. You get an email letting you know who declined. The PDF stays in "Out for signature" status with that signer marked declined; you can either restart the request or treat it as final.

Legal validity:

Electronic signatures captured through this flow are valid under the U.S. ESIGN Act and most state UETA equivalents (49 states + DC). For certain document types (wills, divorce papers, real-estate-closing settlement statements in some jurisdictions), wet signatures or specialized e-sign platforms are required — check with your attorney if you're not sure. The audit packet on the final PDF is intended to support enforceability in routine commercial use.

What's not yet supported:

- **Positional signature fields.** Today every signer's signature goes on the last page in the audit block. Per-page positional signature fields (DocuSign-style anchor tags) are in development.
- **Initials on every page.** Treated the same as full signatures for now.
- **Standalone "send for review" (no signature).** Use the standard "Send" action for that — sends as an email attachment with no signature request.