Sending a document for e-signature
How signature requests work — illustrations, disclosures, LIRD, risk profile assessments.
Signature requests in VerifiedAdvisorsHub are tamper-evident: every original document is hashed when the request is created, and the hash is recorded on the signed copy too. You can prove later that the document a client signed was the document you sent.
Where signature requests live
- Insurance illustrations — uploaded PDFs, sent from a client’s Insurance page.
- Advisor disclosure — auto-generated from your disclosure template, sent from a client’s Disclosure page.
- LIRD (Life Insurance Replacement) — three-step wizard on the LIRD page.
- Risk profile — created when you complete a client’s risk profile assessment.
What the client sees
The client gets an email with a magic link. Clicking it lands them on a sign page where they can review the document and sign their fields. After they sign, you get a counter-sign notification (where applicable). Once everyone has signed, both of you get the sealed PDF in your respective Documents tabs.
Voiding a request
If you sent the wrong document or the client never responds, void the request from the request list. The link stops working immediately and the client (if they click the link) sees a friendly “link revoked” page.
Where the signed PDFs are stored
Sealed signed PDFs live in Cloudflare R2 storage. We never expose the storage URL directly — every download goes through an auth-gated route that re-mints a presigned link. This means a leaked URL doesn’t grant indefinite access.