For IT and HR teams handling departures

The exit interview happened. The GitHub access didn't get revoked.

Offlist turns offboarding into one checklist that covers access, equipment, and paperwork — split across IT and HR, tracked until every box is actually checked.

Try the live demo → Get in touch
Dana Whitfield — Departing Sep 12Day 0
THE RISK

Access doesn't close itself

Offboarding is split across IT, HR, and whoever manages a given tool — and nobody owns the whole list. So most of it happens from memory.

Slack
still active
GitHub
still active
AWS console
still active
Company email
still active
VPN
still active

Access left open after departure is one of the most common findings in internal security reviews — and it's entirely preventable with a checklist someone actually finishes.

HOW IT WORKS

A departure has a shape. Offlist follows it.

Every departure moves through the same days, whether it's planned or immediate.

DAY 0
Departure logged, checklist auto-created for IT + HR
DAY 0
Access revoked across every connected system
DAY 1–3
Equipment collected, final pay and benefits processed
DAY 3–5
Knowledge transfer confirmed with the team
CLOSED
Every item checked — departure archived
WITHOUT IT VS. WITH IT

What actually changes

🟠 Without Offlist

  • IT finds out about a departure the morning of, or after
  • Access is revoked "as remembered," not as a list
  • Equipment return depends on someone following up manually
  • No record of what was actually done for a former employee

🟢 With Offlist

  • A checklist is created the moment a departure is logged
  • Every system to revoke is listed — nothing relies on memory
  • IT and HR see the same list, split by who owns what
  • A timestamped record exists for every completed departure

See a departure close out

The live demo lets you check off real items across a few sample departures — your test data stays in your browser.

Try the live demo →