The Signature That Never Came Back
A 60-person insurance brokerage sends residential lease-guarantee agreements for signature. Volume is about 900 agreements per month, each with two signers: the tenant and a co-signer. The current process emails a flattened PDF and asks recipients to print, sign, scan, and return. Median turnaround is 9 days; 22% never return at all. The compliance officer requires: proof of who signed and when, tamper evidence, and retention of the completed agreement for 7 years. Two signers occasionally share one email address (spouses). The brokerage is on Acrobat Pro with an Adobe business subscription.
1. Diagnose why the print-sign-scan process is failing and map each compliance requirement to a capability.
Read the worked answer
The failure is friction plus no tracking. Print-sign-scan requires a printer, a scanner, and a round trip; every step is a drop-off point. There is also no visibility into whether a document was opened, so nobody knows to follow up.
Mapping the requirements:
- Proof of who signed and when → an e-signature service produces an audit trail (signer identity, email, IP, timestamp) attached to the completed document. A scanned image of a signature proves nothing about identity or time.
- Tamper evidence → the completed PDF is sealed with a digital certificate; any post-signature modification invalidates it. A flattened PDF emailed around has no such protection.
- 7-year retention → completed agreements must be archived with the audit trail intact, not just the signed page.
The fix is to send agreements through an e-signature workflow with defined signer roles and automatic reminders, not to keep improving the email-and-scan loop.
2. How should the shared-email-address case be handled, and what ordering should the two signers have?
Read the worked answer
Shared email is a real edge case. Most e-signature tools key a recipient to an email address; two recipients on one address can confuse routing and audit identity.
Options, in order of preference:
- Collect a distinct email per signer where possible (the co-signer often has one). This preserves clean identity evidence.
- Use a signing order so the tenant signs first, then the co-signer is invited - this serializes the flow and avoids two invitations landing in one inbox simultaneously.
- If a shared address is unavoidable, use distinct recipient names and require an authentication step (e.g., knowledge-based or access code) so the audit trail distinguishes the two signers.
On ordering: a sequential order (tenant, then co-signer) is preferable here because the co-signer's obligation typically depends on the tenant's acceptance, and it reduces the chance both parties sign a stale version. Parallel signing is faster but weaker for dependent obligations.