OffersSigning
Evidence, not a receipt. Consent, then identity, then a fingerprint of the document (a short code taken from its exact wording) checked twice. A sealed copy with the whole timeline bound to it, in a history nobody can edit. Two signatures in all: theirs, then one from you.
Five steps, each one recorded. In that order, every time.
- ConsentThey accept the electronic-records disclosure before anything else. The version they saw and its fingerprint are stored, along with the fact a paper alternative was offered.
- IdentityA one-time code goes to the email the offer was addressed to. Only the hash of it is stored, it expires, and it can be used once.
- SignatureThey read the document and sign it. The fingerprint of what they saw is checked at that moment against what you sent.
- CountersignatureYou approve, your own blocks are applied, and the fingerprint is checked a second time. If the document moved, approval stops.
- SealThe executed document is rendered to PDF, sealed with the platform certificate, and bound to a certificate of completion carrying the whole timeline.
They consent first. To a disclosure you can produce later.
Before the document opens, the candidate accepts the electronic-records disclosure; the version they accepted is stored with its fingerprint, so “which disclosure did they see” is a lookup rather than an argument.
- The disclosure they accepted, kept by version
- And by fingerprint, so “which version” is never a guess
- Whether a paper alternative was offered: recorded, not assumed
- Their IP address and device at the moment they accepted
Then they prove it’s them. With a code you never store.
Nothing about it is stored as itself: not the code, which is hashed, and not a secret in the link, because there isn’t one.
- A one-time code, to the address the offer was sent to
- Kept only in scrambled form, never as the code itself
- It expires, and it is consumed on use
- The link itself carries no secret to leak
- They stay signed in through their own browser, not through a link they could pass on
And the document can’t drift. Checked at signing, and again at countersigning.
The contract is fingerprinted when you send it. If what is being signed is not what you sent, the process stops, rather than completing and leaving you to find out later.
- The document is fingerprinted when you send it
- The fingerprint is checked when they sign
- And checked again when you countersign
- A document that moved stops the process rather than passing quietly
- To change terms you send it back, which starts a fresh round
A history nobody can rewrite. Including us.
The log takes no edits
Not from an administrator, not from support, and not from our own software. Once a line is written it cannot be changed or removed, and there is no back door for us either.
Ten kinds of event
Disclosure accepted, code sent, code verified, document viewed, signed, declined, countersigned, executed, copy delivered, withdrawn. A decline is as much a record as a signature.
One offer in flight
An application can have exactly one live offer at a time. Sending a revised one clears the previous round first, so there is never a question of which document is the document.
The whole timeline, bound to the document
Every step with its party, how they proved who they were, when it happened in UTC, and the fingerprint of the document at that moment: sealed into the PDF as a certificate of completion.
Countersigned is hired. The record appears at that moment.
No. Authoring, identity, signing, sealing and the audit trail are all part of Cadre: there is no third-party signing bill and no second system to administer.
An email address. The code arrives there, the contract opens in a browser, and the signature is typed. No account, no app, no download.
Electronic-signature law turns on consent, attribution, integrity and retention rather than on ink. Cadre records each of them: the disclosure the candidate accepted, the code they verified, the fingerprint of the exact document they saw, and a sealed copy with the full timeline attached. If your sector has a stricter rule, check it against that list: this is the evidence, not the legal advice.
Not silently. The document is fingerprinted when you send it and checked again at signing and at countersigning, so a change stops the process rather than passing quietly. To alter terms you send the offer back with a note, which clears the previous round and starts a fresh one.
Declining is one of the ten recorded events, with the party and the time on it, and the offer moves to a terminal state. The record of the attempt does not disappear because the answer was no.
No, and if your policy requires two signatures from your organization, read this before you go further. An offer carries exactly two signatures: the candidate’s, then one from you. Cadre cannot pass the document on to a second person on your side, in order or otherwise. We would rather you knew now.
In that person’s own document file, from their first day onward; the employee record it attaches to is created at the same moment you countersign.