Menu
Home Features How it works Solutions Pricing Live demo Contact Try it free
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.

Dana Whitfield — Departing Sep 12Day 0
BUILT FOR
IT Teams HR & People Ops Startups Agencies & MSPs Remote-first companies Healthcare & Finance
3
checklist categories, one view
0
logins needed to see status
∞
departures tracked, no per-seat limit on templates
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.

Did IT actually revoke their AWS access?
Who has the laptop right now?
Did HR process the final paycheck?
Is there a record of what we actually did?
Who's supposed to run the exit interview?
Wait — they still have Slack access?
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
QUESTIONS

Everything worth knowing before you start

What is Offlist?

Offlist is a shared checklist tool that makes sure every step of an employee's offboarding — access revocation, equipment return, HR paperwork — actually gets done and gets recorded.

Who is it built for?

IT teams and HR/People Ops teams who currently split offboarding across email, memory, and separate spreadsheets — plus agencies and MSPs who manage offboarding for multiple client organizations.

Can I try it before talking to anyone?

Yes — the live demo is open to everyone, no account needed. Test it with sample departures right now.

Why do I need to contact you instead of just signing up?

We set up every paid workspace personally so your checklist templates and team roles are configured correctly from day one, rather than leaving you to figure it out alone. It takes one short conversation.

Can I customize the checklist items?

Yes. Templates are fully editable — add, remove, or reorder items per category, and every new departure picks up your current template.

Does it integrate with our other tools?

Offlist is currently a standalone checklist and audit trail. Direct integrations with identity providers and ticketing tools are on our roadmap — ask us about your specific stack.

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 →