Outsourced EmploymentPowered by StealthAgents

Research note

How often do offboarding checklists record a completed access removal sign-off?

A local method for measuring how often offboarding checklists record a completed access removal sign-off, with separate checks for the owner, the evidence, and the reviewer.

Published

Research note illustration for How often do offboarding checklists record a completed access removal sign-off?
Table of contents

Question and scope

The question covers employees who left the organization during the review window and had at least one system account. It includes voluntary departures, involuntary departures, and end-of-contract cases. It excludes transfers between teams where the person stayed employed. The review covers one employer, one window, and the systems that the checklist names.

A case enters the sample when the offboarding record shows a last working day and a checklist. If the checklist exists only as a message thread, the case enters as an informal process. Record the source of the checklist and the date it was opened. A checklist completed after the last day should be marked as late.

The stop point is a second-person sign-off with evidence for each system, not a checked box. A box with no confirmation does not show that the account was removed. The sign-off may include a screenshot, a ticket number, or a system report. Report cases with a checklist but no sign-off separately.

Definitions and evidence standard

Define a complete sign-off before reviewing any case. It should name the reviewer, the date, the systems reviewed, and at least one piece of evidence per system. A note that says all access removed does not meet the standard. Record the definition with the case so a later reader applies the same rule.

Use the system admin record, the ticket, and the checklist as the primary evidence. A memory of the exit interview can add context but cannot replace a dated confirmation. If only a verbal report exists, mark the case as unverified rather than assigning a date. Report the share of unverified cases with the result.

Separate the removal date from the sign-off date. An account can be closed on the last day while the review happens a week later. Measure both dates so a slow review does not look like a slow removal. The two numbers answer different questions about the process.

Sampling and measurement

Freeze the list of departures before reviewing any of them. Include more than one manager, more than one role, and more than one month. Record the export date and the filter used. Do not remove a case because the checklist is incomplete, since the gaps are part of the finding.

If the list is large, take a random sample and record the selection method. Keep the full count beside the sample so a reader can see the coverage. A replaced case should be reported as a deviation. The sample should be large enough to compare at least two teams.

Measure the number of cases, the share with a completed sign-off, the median and longest time from the last day to the sign-off, and the share with no sign-off at all. Add the number with no named owner and the number with no evidence. Report the counts by manager and system group. A single percentage hides which system drives the gap.

Findings and interpretation

Present the distribution before suggesting a cause. A cluster of missing sign-offs under one manager may mean the checklist was never routed to a reviewer. A cluster in one system may mean the owner left the team. Read the cases behind the largest cluster before naming a reason.

Compare the result with the routing method. A checklist that assigns a reviewer at the start may produce a faster sign-off than one that waits for the manager to choose. Record the method and the first person who saw the checklist. The comparison can show whether the delay is in the removal or the review.

Check whether late sign-offs still caught an open account and whether it was closed the same day. A late review that found a live account is different from a review that confirmed a clean closure. Record the date of any follow-up and the owner. The quality of the delay matters alongside its length.

Limitations

The review measures the presence of a sign-off, not whether every hidden account was found. A complete checklist can still miss a tool that no one listed. The result describes the documentation trail, not the full access surface. Report it beside a separate access review so a reader does not overread the number.

The checklist may change during the window, and an older case may follow a version that was appropriate at the time. Record the checklist version rather than applying the current rule retroactively. A case that missed an old standard may not be a current defect. Keep the version note with the case file.

A departure that never received a checklist is invisible to this method. The count may understate the problem if some teams skip the process. Pair the review with a count of departures with no checklist. The answer can reveal a gap the sign-off record cannot show.

Practical next step

Create one offboarding checklist with a fixed field for each system, the owner, and the evidence. Send it to the reviewer before the last day so the review is scheduled. A single form makes the sign-off measurable. Keep it short enough that a manager will complete it.

Set a target for the sign-off and name the person who confirms it. A short target such as two business days after the last day gives the reviewer a clear deadline. Record the date the target was met or missed. Tell the employee's manager who to ask if the review stalls.

Test the process for one month and compare the sign-off rate with the baseline. Keep the change if it improves the rate without delaying the departure. If the form or the reminder causes errors, fix that step. The goal is a closed account, not more paperwork.

Sources

References supplied with this research note.

Article source directory
SourcePublisherContext
U.S. Department of Labor, Recordkeepingdol.govPrimary reference supplied with this article.
National Institute of Standards and Technology, Privacy Frameworknist.govPrimary reference supplied with this article.
U.S. Equal Employment Opportunity Commission, Recordkeeping Requirementseeoc.govPrimary reference supplied with this article.