CadreOffers
The offer, signed and sealed. Your contract, from your templates. A signature you can stand behind, and the evidence that proves it.
Two halves of an offer. Writing it, and signing it.
- TemplatesA library per kind of role, titled sections, your letterhead, fields that fill themselves, and signature blocks placed inside the text.
- SigningConsent, identity, a fingerprint of the document (a short code taken from its exact wording), checked twice, a sealed PDF with a certificate of completion, and a history nobody can edit, including us.
Your contract, not a form. Templates, sections, letterhead, and fields that fill themselves.
Keep as many templates as you have kinds of role. Picking one copies it into the offer, so refining the template later never disturbs an offer already in flight.
- A template for each kind of role, copied when picked
- Titled sections and your letterhead, both baked into the signed copy
- Name, role, start date and company merge in from the record
- Your own fill-in fields per template: text, long text, date or a fixed set
- Signature blocks placed beside the clause, not stapled to the back
- A blank referenced field stops the send and names itself
The signing, done properly. Consent, then identity, then a signature they actually make.
Every step is recorded as it happens, into a history that cannot be edited or deleted afterwards: not by an administrator, not by our staff, and not by our own software.
- The disclosure they accepted, versioned and fingerprinted
- A one-time code to their email, verified before they see it
- The exact document’s fingerprint, checked at signing
- And checked again when you countersign
- A sealed PDF, with the whole timeline bound to it
The evidence, kept. Not a receipt: a record you could hand to a lawyer.
Sealed on execution
The executed document is rendered to PDF and cryptographically sealed with Mercleo’s signing certificate.
Certificate of completion
Bound to that same PDF: the document’s fingerprint, and every step in UTC (party, name, IP address, device, and how they proved who they were).
A history that can’t be rewritten
The record of what happened takes no edits and no deletions. There is no route around that for an administrator, for our staff, or for our own software.
Filed where it belongs
The signed contract lands in that person’s own document file, theirs to open from their first day onward.
Then they’re an employee. Without anybody re-typing the offer.
You countersign
Approving a signed offer applies your own signature blocks and closes the document. If it changed since it was signed, approval stops instead. That is the second and last signature: Cadre cannot pass the document to a second person on your side.
The employee record appears
Created from their application, with the start date carried across and the signed contract filed to their documents.
Onboarding starts on the day
When the start date arrives the invite goes out and the onboarding plan begins, without anyone having to remember.
Stop emailing the offer back and forth. The beta is open now.
No. Authoring, 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.