One file. Everyone on it.
Starting a request takes about a minute, and it replaces the eleven emails that used to be the job. Here is the whole sequence, from creation to a closed record.
- Multi-party by default, with sequencing you set
- Per-party privacy, enforced, not promised
- Review, rounds and supersession instead of overwrite
Starting one takes about a minute.
Name the request
One file for the matter, not one document per person. Everything that follows hangs off it.
Add your people
The applicant, the co-applicant, the guarantor, the witness, the notary, if the matter needs them, and what you need to know about each of them.
Upload the document to sign
Drop a signature zone for each signer and a field for each fact you need. Signature, initials, date signed, text, approve or decline, corporate seal.
Attach each person's checklist
Hers, and his. Documents to upload, forms to complete, facts to confirm. Each party sees only their own list.
Send
That is the whole job. Each person gets their own link and their own turn, in the order you set.
Review and close
Everything comes back to one screen. Approve each item, or send one back with a reason. Closing the file writes it into the client's profile.
Their own link, their own list, their own turn.
Privacy between parties on the same file is enforced at the data layer, not by asking people to be careful.
- The co-applicant cannot see the applicant's bank statement
- The witness cannot see either
- The order you set is the order that happens, no matter who opens their email first
- Each firm's records are sealed off from every other firm's at the database itself
One item reopens. Everything else stays.
Send an item back with a reason and only that item reopens. Everything the client already gave you stays exactly where it is. They correct one field, they do not start again.
- When the document itself has to change, that is a new round of the same file
- The earlier round, with its signatures and its dates, is preserved in full
- A signed instrument can only be superseded, on the record. Never quietly edited or deleted
Written into the document, not into a database row.
When the last party signs, the signature is written into the document itself. Open the PDF anywhere, forever, offline, and the marks are in the file. Not a row in a database that says the word signed.
- Signature, initials, date signed, text, approve or decline, and corporate seal zones
- Zone assignment per signer, so nobody signs in someone else's place
- The identity verification result travels on the signature, in the file
Run it once and it is obvious.
Book a twenty-minute walkthrough and we will build a real request with you, from creation to closed record.