Employee Offboarding Checklist, Process, Template, and Documents to Collect

The employee offboarding checklist

Copy this and cut what does not apply. A three-person office does not need the access matrix a regulated company needs, and a contractor does not trigger the benefits steps at all. What matters is the phase order: each phase exists to unblock the next, and the last-day items are grouped deliberately because that is the point of no return.

PHASE 1. NOTICE AND CONFIRMATION (day 0 to day 1)
Get the departure in writing: a resignation letter, or a written confirmation of termination with the last working day stated. · Agree the actual last working day and whether the person works it or is paid through it. · Notify the small number of people who need to know before it is announced: the manager, HR, payroll, IT. · Check the file for anything that changes the process (an employment agreement with notice terms, an immigration sponsorship, a company loan, an equity vesting date, an open investigation).

PHASE 2. PAYROLL, BENEFITS, AND STATUTORY DEADLINES (start immediately)
Tell payroll the termination date so the final paycheck can be calculated on time. Do not let this wait for the last day, because in several states it is already too late by then. · Calculate accrued but unused vacation or PTO if your state or your policy requires payout. · Notify the health plan of the qualifying event so the COBRA election notice goes out on schedule. · Stop future payroll deductions, expense advances, and benefit contributions. · Note where the final W-2 will be sent, which is often not the address you have on file.

PHASE 3. WORK HANDOVER AND KNOWLEDGE TRANSFER (the notice period)
List everything the person currently owns: live projects, recurring tasks, client and vendor relationships, approvals they are the only signer on, systems only they administer. · Assign each item to a named person, not to a team. · Have the departing employee write down the things that exist only in their head: where files live, which supplier to call, why a process is the way it is. · Redirect or reassign shared responsibilities: shared inbox rules, on-call rotations, calendar invites they own, bank or system administrator rights.

PHASE 4. LAST DAY: ACCESS AND PROPERTY
Disable system access at the agreed time, coordinated with the manager so it happens neither early nor late. · Collect laptop, phone, monitors, keys, badges, access cards, corporate card, and anything else issued at onboarding. · Transfer ownership of files, documents, and shared drives before the account is closed, not after. · Set up email forwarding or an auto-response so client mail is not lost. · Run the exit interview if you are doing one. · Return personal belongings and confirm the last paycheck arrangements in writing.

PHASE 5. AFTER THE LAST DAY: CLOSE THE FILE
Confirm the final paycheck was issued on the statutory deadline and that any expense reimbursements were settled. · Confirm the COBRA election notice was actually sent, and keep proof. · Remove the person from directories, org charts, distribution lists, the website, and anywhere else their name is published. · Update headcount and, if you are backfilling, start from the job description the role actually needs now rather than the one you wrote three years ago. · File the personnel records under your retention schedule and diary the date they can be destroyed.

One rule holds the whole sequence together: nothing on the last-day list is optional and none of it improves by being postponed. Every item on that list gets harder the moment the person is no longer reachable, and the two with legal deadlines attached do not care that the week was busy.

The offboarding documents and deadlines that carry legal weight

Most of an offboarding checklist is good practice you can adapt. A few items are not, because a statute or a regulation sets the clock. These are the ones worth knowing precisely, and they are the reason offboarding cannot be left to whoever is free on Friday.

Final paycheck: the deadline is set by your state, not by your payroll cycle. There is no single federal rule that says a final paycheck is due on a particular day. The Fair Labor Standards Act requires that wages earned are paid, and the timing is then set state by state. That timing genuinely varies: some states simply say the next regular payday, while others require payment immediately or within a short fixed window, and several draw a distinction between an employee who was discharged and one who resigned. California is the clearest illustration and a useful worst case to plan around. Under California Labor Code section 201, an employee who is discharged must be paid all wages, including accrued vacation, immediately at the time of termination. Under section 202, an employee who quits without giving at least 72 hours notice must be paid within 72 hours of quitting, while an employee who gives 72 hours notice is due their wages on their last day. Four states (Alabama, Florida, Georgia, and Mississippi) have no state-specific final paycheck statute at all, so the federal baseline applies. Because the spread is that wide, the only safe process is to look up the rule for the state where the work was actually performed and build your notification step around the tightest deadline you face. For a multi-state workforce, that means the employee's work state, not your headquarters.

COBRA: two clocks, and the first one is yours. COBRA continuation coverage applies to private-sector group health plans at employers with at least 20 employees on more than 50 percent of typical business days in the previous calendar year. When a qualifying event such as termination or a reduction in hours occurs, the employer must notify the plan administrator within 30 days. The plan administrator then has 14 days after receiving that notice to provide the election notice to the qualified beneficiaries. The departing employee and covered dependents then have 60 days to elect coverage, counted from the date coverage ends or the date the election notice is provided, whichever is later. Coverage runs up to 18 months for termination or reduced hours, extends to a total of up to 36 months where a second qualifying event applies, and can reach 29 months under the disability extension. The plan may charge up to 102 percent of the cost to the plan. The failure mode here is simple and common: HR knows the person left, but nobody sent the plan the notice, and the 30 days ran out while everyone assumed someone else had done it.

Form I-9: keep it longer than you think, then destroy it on schedule. Federal regulations require you to retain a Form I-9 for each person you hire for three years after the date of hire, or one year after the date employment ends, whichever is later. Work the arithmetic through and it means something practical: for anyone who worked less than two years, you keep the form for three years from their start date; for anyone who worked longer, you keep it for one year after they leave. You may retain I-9s on paper, on microfilm or microfiche, or electronically, and you only need to keep the pages that you and the employee actually wrote on. The reason to get this right in both directions is that I-9s are inspectable, and a file that has been purged too early is as much of a problem as one that was never completed.

Form W-2 and the rest of the records. The final W-2 goes to the employee by the normal January 31 deadline for the year in which they were paid, which is why capturing a forwarding address at offboarding matters more than it looks. Beyond that, personnel records, payroll records, benefits records, and I-9s all sit under different retention periods, and they are not all the same length. The practical move is to write your retention schedule once, apply it at the point the file is closed, and diary the destruction date rather than keeping everything forever by default.

None of the above is legal advice, and employment law is one of the areas where the state you are in genuinely changes the answer. Confirm your own state's final pay rule with the state labor agency, and route anything unusual (a disputed termination, an immigration sponsorship, an employee on protected leave) to counsel rather than to a checklist.

• Written confirmation of the departure and the agreed last working day
• Payroll notified early enough to meet the state final paycheck deadline
• Health plan notified of the qualifying event within the COBRA window
• Accrued PTO calculated and paid where the state or your policy requires it
• Forwarding address captured for the final W-2 and any later correspondence
• Company property returned and logged against the list issued at onboarding
• Personnel records filed under a written retention schedule with a destruction date

Access revocation and equipment: the part that goes wrong quietly

Every other item on the offboarding checklist announces itself when you get it wrong. An unpaid final paycheck generates a phone call. A missing laptop generates an invoice. Access left open generates nothing at all, which is exactly why it is the item most often left half-finished.

The federal security control catalog treats this as a distinct requirement rather than a nice-to-have. NIST SP 800-53 Rev 5 control PS-4, Personnel Termination, states that upon termination of individual employment an organization should disable system access within an organization-defined time period, terminate or revoke any authenticators and credentials associated with the individual, conduct exit interviews that include a discussion of defined information security topics, retrieve all security-related organizational system-related property, and retain access to organizational information and systems formerly controlled by the terminated individual. Read that last item again, because it is the one people miss: you are not just closing the door, you are making sure the organization keeps what was behind it.

In practice the difficulty is not the primary account, it is everything that hangs off it. Single sign-on makes the first ninety percent easy and hides the last ten. The accounts that survive an offboarding are the ones that were never in the identity provider: a tool someone signed up for with a company card, a shared login in a password manager, a personal API key wired into an automation, an admin seat on a vendor portal, a phone number registered for a multi-factor prompt, a forwarding rule quietly copying mail elsewhere. The way to find those is to keep the list current at onboarding rather than to reconstruct it under pressure on someone's last afternoon.

The timing matters as much as the completeness. Revoke too early and you have told the person they are fired before their manager has, which is a genuinely bad way to find out. Revoke too late and you have an account with live credentials belonging to someone who no longer works for you. The workable answer is to agree the exact revocation time with the manager during phase 1, put it on the calendar, and treat it as a scheduled event rather than a task somebody gets to. Our IT offboarding checklist goes through the full account and device list, including the SaaS accounts that never touch your identity provider.

Equipment follows the same principle in reverse. The reason to log what was issued at onboarding is so that the return list writes itself, rather than being assembled from memory. A remote employee adds a shipping step and a deadline, and it is worth agreeing both in writing before the last day rather than exchanging increasingly awkward emails a fortnight later.

The exit interview and the handover nobody documents

An exit interview is worth running for one reason: it is the only moment in the employment relationship where the person has nothing to lose by telling you the truth. That value evaporates if the conversation is a form, if the departing employee's own manager runs it, or if nothing visible ever happens as a result. Have someone neutral run it, ask open questions, take notes, and aggregate the answers across departures rather than acting on any single one.

Questions that actually produce information: what made you start looking, what would have kept you, what does the person taking over need to know that is not written down anywhere, what part of the job was different from what you expected when you were hired, and what should we stop doing. Notice that the third one is not a culture question at all. It is the most commercially useful thing you will get out of the meeting.

That points at the real gap in most offboarding. The paperwork gets done because it has deadlines. The knowledge transfer does not, because it has none, so it quietly becomes the successor's problem three weeks later when a renewal passes or a client asks about something nobody can explain. If you want that part to actually happen, treat it like the compliance items: name the receiving person, write the list of what has to be handed over during the notice period, and check it off. Anything genuinely repeatable belongs in a written standard operating procedure rather than in an exit interview note, because a procedure survives the next departure too. A resignation is the worst possible moment to start documenting a process, which is the argument for doing it while nobody is leaving.

How the checklist changes for a resignation, a termination, or a layoff

The five phases hold in all three cases. What moves is the timing, the documentation, and how much of the notice period you actually get.

Voluntary resignation. You usually get a notice period, which makes this the easiest version: handover and knowledge transfer have somewhere to happen, and access revocation lands on a known date. Get the resignation in writing even when it was given verbally, because the distinction between resigning and being dismissed matters later for unemployment claims and for anything disputed. Watch the state rule on final pay, since several states set a different deadline depending on whether notice was given.

Involuntary termination. There is generally no notice period, so phases 3, 4 and 5 compress into a single day and phase 2 becomes urgent rather than merely scheduled. Coordination is what makes this go cleanly: the manager, HR, and IT should agree the sequence in advance, down to the hour, so the conversation happens before access is cut and not after. Documentation carries more weight here, so the reasons and the process should already be recorded, ideally against whatever standard your employee handbook sets out and consistent with the record built through your performance review process. Have the final pay position worked out before the meeting, not after it.

Layoff or reduction in force. Everything above applies, plus a set of obligations that only arise at scale, including federal and state advance-notice requirements that can be triggered by larger reductions and have their own thresholds and timelines. This is the case least suited to a checklist and most in need of counsel before anything is communicated. What the checklist still does for you is the operational part: the same handover, access, property, and records steps, run many times over, on a schedule, without anyone being missed.

One thing does not change across the three. However the person is leaving, the offboarding experience is watched closely by everyone who is staying, and it is a reasonably good predictor of how they will describe you afterward.

Running offboarding without it eating the week

Look at what the checklist above actually consists of. A small number of real decisions (who takes over what, what the final pay position is, how and when the departure is communicated) and a long tail of coordination: telling five functions the same date, chasing the manager for the handover list, confirming the plan administrator actually received the qualifying-event notice, collecting a laptop from a remote employee, checking that the accrued PTO calculation came back, remembering in eleven months that a retention period expires. The decisions are the work. The coordination is what makes a single departure consume a week of someone's attention.

That coordination layer is what Officeagent runs. It turns the checklist into tracked tasks with one named owner and a due date rather than a document someone means to work through, drafts and sends the notifications to payroll, benefits, and IT from your standard list, chases the items that have not come back so the handover list and the equipment return do not stall on a reply, files the resignation letter, the acknowledgment, and the exit interview notes against the personnel record where the next person will look, and puts the dated items (the final pay deadline, the COBRA notification, the records destruction date) on the calendar when the process starts rather than when they become a problem. Every message it drafts waits for a human approval before it goes, which is the control you want on anything that touches somebody's last paycheck.

To be clear about what this is and is not: Officeagent is not an HRIS and it does not run your payroll, calculate your final paycheck, or file anything with a state agency. Those belong in your payroll and benefits systems, and the legal calls belong with your advisers. What it does is make sure the twenty small handoffs around them actually happen on time, which is the part that fails in practice. If your onboarding and offboarding are two halves of the same policy, the same machinery runs both: build the sequence once from your employee onboarding checklist, reverse it here, and stop rebuilding it from memory every time someone resigns.