How to send a document for signature — signing order, reminders and proof

Signing a PDF you received takes a minute. Getting a contract signed by someone else is a different problem: it involves another person's inbox, their attention and their calendar, and it is where most agreements quietly stall.

Here's what actually moves a document from "sent" to "executed".

Place the fields before you send

The single biggest cause of a stalled signature is a document that arrives without telling the recipient what to do. "Please find attached" plus a 6-page PDF is a task, not a request.

Place the fields first — signature, initials, date, free text, checkboxes — directly on the pages where they belong, colour-coded per recipient. The signer then opens a document that shows them exactly where to act. The work moves from their side to yours, which is where it belongs if you want the deal closed.

Sequential or parallel?

Two routing models, and picking wrong slows things down.

Parallel — everyone gets the link at once and signs whenever. Right for an NDA between two equals, or a document where nobody's signature depends on another's.

Sequential — signer 2 only receives their link once signer 1 has finished. Right when order carries meaning: a manager approving before the client countersigns, or a witness who has to sign after the principal.

Sequential feels slower and often isn't, because it removes the "wait, has finance approved this yet?" round trip.

Don't make them create an account

If signing requires the other party to register, a meaningful share simply won't. They're doing you a favour by signing; making them set a password first is a strange way to say thanks.

A private tokenised link — long, unguessable, tied to one recipient — is both easier and perfectly defensible. The token is the authentication, the same model bank payment links use. What matters legally is the evidence recorded at the moment of signing, not whether the signer picked a password beforehand.

Reminders are most of the win

People do not ignore contracts on purpose. They open the email in a meeting, mean to come back to it, and don't.

A reminder cadence of roughly 3, 7 and 14 days recovers a large share of documents that would otherwise die in an inbox. It's polite, it's automatic, and it stops you personally chasing someone you'd rather stay on good terms with.

Two rules: stop reminding once they've signed, and let them decline. A decline with a reason is far more useful than silence — you learn the deal is dead, or what needs renegotiating.

The proof you keep afterwards

When a document completes, the useful artefact isn't the signed PDF alone. It's the signed PDF plus a certificate of completion recording:

• every signer, with the email address the link was sent to
• the exact timestamp of each signature
• the IP address and browser used
• a cryptographic fingerprint (SHA-256) of the final document

The fingerprint is what makes tampering detectable: change one character afterwards and the hash no longer matches. That's the difference between "we have a signed copy" and "we can prove what was signed".

Store both together. A signed PDF with no audit record is much weaker evidence than people assume — see what's legally binding.

What to do when something changes

Don't edit a signed document. Ever. Once a counterparty holds a signed copy, altering the file destroys the very thing that made it trustworthy.

Void it instead — with a visible watermark on the original and a notification to everyone who signed — and issue a corrected version. It feels heavier than quietly fixing a typo. It's also the only version that survives scrutiny.

Where Eurobillr fits

Eurobillr handles the whole flow: upload any PDF (or send an AI-drafted contract straight in), drag fields onto the real document colour-coded per recipient, choose sequential or parallel routing, and send. Signers use a private link with no account, and can draw, type, upload or reuse a saved signature. A nightly job nudges pending signers on a 3/7/14-day cadence. Everyone receives the sealed PDFs plus a Certificate of Completion with a SHA-256 fingerprint, and voiding applies a watermark and notifies every party.

More at the e-signature overview.