LeaverProof

What the record covers

• Accounts disabled, with the systems listed
• Mailbox and file disposition
• Groups and OAuth / app access removal
• License reclaimed
• Equipment returned or not returned, with its value
• Data purge date, surfaced until it is marked purged
• Who did the work, section by section, auto-stamped
• Client acknowledgement, through a link that needs no account

How it works

1. 1. Start the record

   Add the client once. For each leaver, start a record with a name, a supervisor and a last working day. Nothing else personal is collected, and there is no field anywhere for a password or credential.

2. 2. Work the fixed checklist

   Mark every section done, not applicable, or exception with a note. Add the equipment items and whether each came back. The client can report leavers themselves through an intake link, so a departure is recorded the day it happens.

3. 3. Seal it, and let the client acknowledge it

   Sealing freezes the record into a PDF with a SHA-256 and a public verify URL. Sealed records cannot be edited; a correction becomes a new version linked to the previous pack's hash. The client's supervisor or HR contact acknowledges through a link, before sealing (it prints on the pack) or after (it is issued as a linked addendum).

Why this exists

In a public Spiceworks discussion about offboarding process, MSP and helpdesk posters described running a 40-point per-leaver checklist tracked in a separate spreadsheet, and one helpdesk reported $30,000-$40,000/year in unreturned equipment. Those are the posters' own reported figures, quoted here as the reason this tool exists, not as a result it produces.

Pricing

Free during the beta: every account has the limits of the Standard plan. Billing opens soon.

One flat price per MSP account: not per client, not per leaver, not per seat. Full details

Questions

Does LeaverProof disable the accounts itself?

No. Records what was done. Does not deprovision accounts for you. There are no Microsoft 365, PSA, RMM or HR-system integrations in this version; the work happens in the client's systems and is recorded here.

What happens when something on a sealed record is wrong?

Sealed records cannot be edited. Start a correction: a new draft version copied from the sealed one. Sealing the correction links it to the previous pack's SHA-256, and the original stays viewable and verifiable.

Can I check a pack without an account?

Yes. Compute the SHA-256 of the PDF (for example with sha256sum) and paste it on the verify page. The page answers whether that hash exists, its position in the chain, and when it was recorded. Nothing else is disclosed.

Does the client need an account to acknowledge a record?

No. Send them the acknowledgement link from the record page. They see the record summary, type their name and role, and acknowledge. Their name, the time and their IP address are recorded.

Where do the equipment totals come from?

From the values you enter. The per-client total of not-returned equipment is your own entered figure, shown so you can see it in one place.

What about passwords a tech might paste into a note?

There is no field for credentials, and a scan warns before sealing when a note contains password-shaped text. Remove real secrets; the warning and any confirmation are recorded on the seal.