LeaverProof
The offboarding checklist, sealed as proof. Turn a per-leaver offboarding checklist into a sealed PDF evidence record with a SHA-256 hash and a public verify URL: checklist, equipment, purge date, who did the work, client acknowledgement.
What it is
Turn a per-leaver offboarding checklist into a sealed PDF evidence record with a SHA-256 hash and a public verify URL: checklist, equipment, purge date, who did the work, client acknowledgement.
LeaverProof is an existing Infinihash product with its own site, sign-in and billing. The store lists it for completeness; details, documentation and support live at leaverproof.infinihash.com.
The problem
When a client employee leaves, the MSP learns about it late, works a long manual checklist from memory or a ticket, and keeps the proof in a separate spreadsheet: who the leaver was, their supervisor, who did the offboarding, what happened to the equipment, when the data gets purged. Unreturned equipment quietly bleeds money, and when the client asks what was done, there is no single record to hand them.
How it works
Start: add the client once, then one record per leaver (name, supervisor, last working day), or give the client an intake link so departures are reported the day they happen.
Work: mark each checklist section done, not applicable, or exception with a note; every save stamps who and when. Account for each equipment item as returned or not returned, with its value.
Seal: the record freezes into a PDF evidence pack with a SHA-256 and a public verify URL. The client acknowledges through a link, no account needed; corrections become new versions linked to the previous pack's hash.
What you get
- Fixed checklist: accounts disabled, mailbox disposition, OneDrive/files disposition, groups and OAuth removed, license reclaimed, equipment, purge date.
- Equipment accounting: returned or not returned with values; the per-client not-returned total is the same figure on the record, the pack and the client page.
- Client acknowledgement by link, no account: before sealing it prints on the pack; after sealing it is issued as a linked addendum and the pack does not change.
- A complete leaver record in under five minutes (measured in the acceptance suite).
- Purge queue: records whose purge date has arrived surface until they are marked purged.
- No-secrets guard: there is no field for credentials, and password-shaped text in a note triggers a warning that must be confirmed before sealing.
Questions
- What does the record cover?
- Accounts disabled, mailbox and file disposition, groups and OAuth removal, license reclaimed, equipment returned or not returned with its value, the data purge date, who did the work, and client acknowledgement.
- Can the client check a pack without an account?
- Yes. Compute the SHA-256 of the PDF and paste it on the verify page; it answers whether the hash exists, its position in the chain, and when it was recorded. Nothing else is disclosed.
- What if something on a sealed record is wrong?
- Sealed records cannot be edited. A correction starts a new version copied from the sealed one; sealing it links the new pack to the previous pack's SHA-256, and the original stays viewable and verifiable.
- How is it priced?
- $49/month flat per MSP account: not per client, not per leaver, not per seat. Clients and leaver records are unmetered.
What it does not do
- It does not deprovision accounts for you. The work happens in the client's systems; LeaverProof records what was done.
- It has no Microsoft 365, PSA, RMM or HR-system integrations in this version.
- It is not an HR system and it stores no credentials, ever.
Pricing
$49/month flat per MSP account: not per client, not per leaver, not per seat. Free during the beta; clients and leaver records are unmetered.
| Plan | Price |
|---|---|
| Standard | $49/month flat per MSP account |