How to offboard a departing employee on Starch

Employee offboarding is the set of steps you run every time someone leaves — voluntary or not. Revoke access, retrieve equipment, document their work, close out payroll, notify the right people, and make sure nothing they owned falls into a gap. It sounds like a checklist, and it is, but the checklist has real consequences: a forgotten SaaS login is a security exposure, a missed final paycheck is a compliance violation, and undocumented processes walk out the door with the person.

What this looks like in practice varies. A ten-person team running on Google Workspace handles it differently than a company with a full HR stack, and a sudden termination hits differently than a planned two-week notice. The tasks are the same; the urgency and ownership differ.

On Starch, offboarding lives in one place instead of scattered across your email, calendar, and memory. You end up with a structured task list tracking every open item by owner and due date, a knowledge-capture workflow that pulls the departing employee's documentation into your team wiki before their last day, and automated follow-ups so nothing stalls because someone forgot to reply. The result: you close out each offboarding knowing access is revoked, equipment is tracked, final pay is logged, and institutional knowledge didn't leave with the person.