How Undersign works
Everything in Undersign sits on one simple model. Once you see the chain, the rest of the documentation stops being a list of features and becomes a set of moving parts in the same flow.
The model in one chain
Follow a document from upload to a signed, verifiable record. Each stage links to its own page.
-
PDF
You upload a file, a contract, form, or agreement. Undersign stores a secure copy and treats it as the source of truth. See Documents.
-
Template
The uploaded document becomes a reusable template with fixed positions for signatures and data. See Templates.
-
Signature request
When you send, Undersign creates a request that pairs the template with its signers and tracks the whole run. See Signature requests.
-
Signer
Each recipient has a role, an identity, and the fields they're allowed to complete. See Signers.
-
Signing
Signers complete their assigned fields: signature, initials, dates, text, checkboxes. The mode (email or in-person) only changes how the signer reaches the document. See Signing modes.
-
Completed document
Once every signer has acted, the document is sealed as complete and everyone receives a final copy.
-
Audit trail + certificate
Every action was already being logged; on completion, a tamper-evident audit trail and a completion certificate accompany the document as proof. See Audit trail and Completion certificates.
Sender and signer are separate world
You (the sender) build templates, choose signers, and manage requests from the dashboard. Signers may never create an account; they receive a link, review, and sign. This separation is why Undersign works for both internal teams and external parties with no onboarding.