Closing a property purchase: you, your spouse, your solicitor and the seller's solicitor all need to sign the same set of documents. Done sequentially, it takes a week. Done in parallel with the right flow, it takes hours.
Sequential vs parallel routing
Sequential routing sends the document to signer one, then signer two once signer one is done, and so on. Used when later signers need to see earlier signatures or comments first. Common for legal sign-offs.
Parallel routing sends to all signers at once. Each signs in their own time; the document is finalised when everyone's done. Common for confirmations from independent parties.
Setting up in Flint
Upload the PDF to Flint's signing tool. Drag signature fields onto the page for each signer. Add each signer's email and choose sequence (numbered) or parallel.
Optionally add CC recipients who receive a copy of the final document but don't sign. Useful for compliance teams and counterparties' assistants.
Common pitfalls
Don't put two signers' fields too close together — they get confused about which line is theirs. Label each signature field with the signer's name or role.
If one signer needs to add information (dates, names, addresses) before passing on, use text fields for them and signature fields for everyone else. Place dependencies first in the sequence.
Deadlines help. Set a sign-by date on each step. If a signer misses it, Flint reminds them automatically and you can re-send.
Tracking and audit
Each signer's action is logged separately: email opened, document viewed, signature applied, with IP and timestamp. The final document carries a certificate of completion summarising the whole chain.
For regulated industries (legal, healthcare, finance), keep the certificate of completion with the signed PDF — it's the evidence record.
FAQ
Can I mix sequential and parallel in one request?
Yes — for example, two signers in parallel, then a witness, then a final approver. Flint supports mixed routing.
What's the maximum number of signers?
There's no hard limit. Real-world contracts with 10+ signers work fine; the UX is the limiting factor, not the technology.
What if one signer needs to delegate?
Most tools allow a signer to delegate to a colleague with a documented audit trail. The new signer becomes part of the record.
Can signers see who else has signed?
Configurable. In sequential mode, later signers usually see earlier ones; in parallel, you can hide co-signer identities for privacy.
Multi-party signing is a routing decision before it's a signing decision. Plan the flow in Flint and the rest follows.