Offboarding Checklist & Asset-Return Tracker
Build an internal tool that turns a known last day into a complete, role-by-role offboarding checklist, tracks every company asset back through the door, and won't mark anyone "fully offboarded" until a human confirms it.
A login-protected tracker where recording a departure auto-generates a tailored offboarding checklist and asset-return list, notifies each owner with deadlines tied to the last day, and requires HR sign-off (with exceptions logged) before anyone is closed out - fully audited and exportable to CSV.
Before you start
- A free Vercel account
- A free Supabase account
- A free Resend account
- Claude Code installed on a Linux machine
- A list (or spreadsheet) of who currently leaves and what they hand back
The problem this kills
Someone resigns. The last day is two weeks out. HR runs offboarding off memory and a half-remembered email thread: did IT revoke access? Did the laptop come back? Who told payroll? Did facilities collect the badge? Every departure is a scramble, and every scramble leaves something behind - an active login, an unreturned phone, a final-pay deduction nobody flagged.
Then an auditor (or a security incident, or a lawyer) asks "show me that this person was fully offboarded," and you have nothing but a sticky note and good intentions.
This tool replaces the scramble with a system: record the departure once, and the right checklist and asset list appear automatically, with deadlines, owners, reminders, and a hard stop that won't let you call it "done" until a person confirms it really is.
What you'll build
A small, login-protected web app for your HR, IT, manager, and facilities teams:
- Record a departure - employee, last day, manager, and whether it's voluntary or involuntary (which changes the timing).
- Auto-generate the plan - the tool builds a role-by-role checklist (HR, IT, manager, facilities, payroll) and an asset-return list (laptop, phone, badge, cards, keys) from templates you define.
- Notify the owners - each task and asset gets an owner and a deadline pinned to the last day; Resend emails them and chases overdue items.
- Track returns and tasks - everyone updates their own items; you watch the whole exit on one screen.
- Gate the close-out - HR reviews and approves the plan up front, and "fully offboarded" requires a human confirming every asset is back and every task is closed, with any exceptions written down.
- Flag the loose ends - unreturned assets surface for payroll/deduction follow-up per your policy, and access-revocation steps stay visible until done.
- Export the truth - a clean CSV of offboarding status and outstanding items, anytime.
What's inside the Implementation Plan
A start-to-finish runbook you paste into Claude Code (the AI coding agent). It builds the whole thing with you, step by step - no prior coding needed.
It opens by interviewing you about your business. Before a single line is written, the plan makes the agent ask how offboarding works at your company today - who owns which steps, what systems hold your asset list, how you name people and devices, your voluntary-vs-involuntary timing rules, and the messy exceptions (the contractor with no laptop, the remote hire shipping a device back, the involuntary exit that has to happen same-day). Then it reads a short tailored spec back to you for a thumbs-up. You get a tool shaped to your actual process - not a generic template.
Inside you'll find: a definition of done, account setup, the discovery interview, the data model, the build broken into copy-paste steps (each ends with a ready-to-paste prompt), a verification checklist, and the no-API CSV fallback so you can ship today even without connecting to your HR or device-management system.
The governance it includes (this is the point)
This isn't a toy. The plan bakes in the controls that make an internal tool trustworthy:
- Login so only your team can use it.
- Row-level security so people only see their own organization's data.
- A complete audit trail - who did what, and when, on every task and asset.
- A hard human-in-the-loop gate - the tool drafts the plan and the close-out, but a person approves the plan up front and a person must confirm every asset returned and every task closed before anyone is marked fully offboarded. Exceptions are logged, never silently skipped.
- Duplicate guards - the same employee and last day can only open one offboarding case, so nobody gets processed twice.
Who it's for
HR coordinators, IT admins, and people managers who run offboarding from memory and miss a step (or an asset) every single time someone leaves - and anyone who's ever been asked to prove a departure was handled cleanly and couldn't.
You've got this. Paste the first prompt and let the agent interview you.