Use cases · People & HR

Employee offboarding and access removal

When someone leaves, build one offboarding checklist from the systems they used, track every access removal and equipment return, and give IT and HR a clear record that nothing was missed.

Where it starts

The trigger.

A leaving date is confirmed in the HR system.

How it runs today

  • Access is removed from the systems someone remembers, not all of them.
  • Shared accounts and licences stay active after people leave.
  • Nobody can show a complete record of what was removed and when.

The workflow

Four bounded steps.

Each step has an owner and a stop rule.

  1. 01 / List

    Pull the systems, groups, licences and equipment linked to the person.

  2. 02 / Plan

    Create a dated checklist with an owner for each removal and handover.

  3. 03 / Track

    Record each completed step and remind owners about overdue ones.

  4. 04 / Confirm

    HR and IT review the completed checklist and sign it off.

Where people stay in control

Approval points.

  • IT owners remove access themselves or approve each automated removal.
  • Handover of files and accounts is agreed with the manager before removal.

How we would measure it

Against a baseline.

Measured before and after, on the same work.

Accounts still active after the leaving date.

Time from leaving date to completed checklist.

Licences recovered after departures.

Related

Go deeper.

More use cases

Other places to start.

All use cases

An illustrative workflow pattern, not a result from a specific customer.

Bring the messy version

One workflow.
A better way to run it.

Show us the tools, the handoffs, and the part that keeps slowing your team down.

Explore with AI

What would you like help with?

Get the main points in plain language.

Continue with

Includes this page title and canonical URL. The prompt is copied before the provider opens; supported providers also receive it through the URL.