E-signature
E-signature built into the portal
Signing in Common Ridge is part of the product, not an integration. Subscription agreements, side letters and tax forms are signed where the investor already is, and the signed file carries its own evidence.
How a signature is captured
The signer must be signed in and confirm a one-time code sent to their email. They accept a versioned ESIGN and UETA disclosure, adopt a signature by typing, drawing or uploading, and apply each field with an explicit act. On a phone, signing advances field to field with zoom and a review summary.
Evidence
Every step is written to a hash-chained event log: created, sent, viewed, consent accepted, code verified, field completed, signed, declined, voided, completed. At completion the system flattens the fields, appends a Certificate of Completion, embeds the document hash and applies a digital signature to the PDF.
- Certificate lists each signer, timestamps, IP address, user agent and authentication methods
- The original, the flattened unsigned copy and the final signed copy are all retained
- A public verify page recomputes the document hash and the event chain from the envelope ID without exposing personal data
Workflow
Sequential or parallel signing, countersignature by the fund, reminders, expiry, decline with a reason, void, and bulk send in batches. If the fund accepts a smaller amount than requested, a short acceptance addendum is signed instead of editing the original.
See it with your own fund structure
Book a walkthrough, or start a trial and explore a workspace yourself.