Skip to content

Offboarding checklist approval: turn the last step into a recorded decision

Why an offboarding checklist needs an approver of record: revoking access is a decision two reviewers and Legal make, not a box someone ticks alone.

Updated · 6 min read

In short

  • Most offboarding checklists end with a box someone ticks, not a decision anyone signed off on - the line that actually matters is revoking the departing person's access.
  • DueReason's access-or-account-action template treats offboarding's access line as a revoke measure: two reviewers, then Legal, each with a written reason.
  • The request records the subject, the grounds and the facts behind them, and produces a record you can still show later, not a checked row in a shared sheet.
  • DueReason does not remove access itself - it records the decision and issues the signed grant; disabling accounts still happens in your own identity tooling.

A typical offboarding checklist has a line for "revoke access" sitting next to "collect laptop" and "final paycheck" - same formatting, same single checkbox, no sign-off step that distinguishes a decision anyone could be asked about later from a task someone remembered to do. The access line is the one with consequences if it is wrong: done too early and a still-working employee is locked out; done too late, or to the wrong account, and a departed person keeps access they should not have.

Offboarding's access line is a revoke action

DueReason's access-or-account-action template has a revoke measure built for exactly this: two reviewers from the account-reviewers group, then a separate approval from Legal, each required to give a written reason. Running offboarding's access step through this template instead of a spreadsheet checkbox means the same request records who is affected, why, and who signed off - the rest of the checklist (equipment, final pay, exit interview) can stay wherever it already lives.

Why a checklist alone has no approver of record

A checked box answers "was this done," not "who decided it should be done, and on what grounds." Anyone with edit access to the sheet can tick it, un-tick it, or tick it for someone else, and nothing distinguishes the person who actually reviewed the departure from whoever happened to update the row. If a departure is later questioned - a disputed termination, a access-timing complaint - a checklist has no record of who approved the access change or why, only that a box is checked.

The grounds, the facts, and the record

A revoke request carries the subject (the account or person), the stated grounds and supporting facts - room enough for the actual reason (role elimination, policy breach, resignation effective date), not a one-word checklist label. Once the two reviewers and Legal have answered, the request can produce a signed, verifiable record, and it can also produce a record - JSON or CSV - while it is still pending, so a question mid-process does not need anyone to reconstruct who has answered so far from memory.

What is still on your own tooling

DueReason does not connect to an HR system or identity provider and does not deprovision anything on its own. The revoke request and its signed grant are the record and the gate - someone still disables the account, removes the badge or revokes the credentials using whatever systems already do that in your organization. The checklist's other lines, and the act of carrying each one out, stay exactly where they are; only the access decision itself moves into a workflow with reviewers and a record.

Questions

Is offboarding always a "revoke" measure, never a restriction or suspension?
Usually revoke, since a departing person's access is meant to end, but a temporary leave or a paused contractor can use restrict or suspend instead - that path needs one reviewer rather than two reviewers plus Legal.
Who has to be in the reviewer and Legal groups for this to work?
Whoever your organization assigns to the account-reviewers and legal groups when setting up the template - DueReason does not pick reviewers on its own, and the same two-reviewers-plus-Legal structure applies to every revoke request, not just offboarding.
Does approving the request actually disable accounts or revoke system access?
No. It issues a signed grant once the reviewers and Legal have answered. Someone still carries out the actual deprovisioning in your identity provider or the relevant systems - DueReason has no connector that does this automatically.

Turn your offboarding checklist into a workflow

Create an account, install the access-or-account-action template, and give the access line in offboarding the reviewers and record it never had on a shared checklist.

Create your account

Sources

This guide explains the regulation as we read it; it is not legal advice. Check the official text and your national law, which may add obligations.

Start with DueReason

Create a free account, try it live, or talk to us about your workflow.

Get product updates