Blog / exit interviews

Separate the Exit Interview From the Last-Day Checklist

Two workstreams, two owners: how to schedule exit conversations, keep separation logistics auditable, and review departures without relitigating them.

Published:

Editorial illustration for Separate the Exit Interview From the Last-Day Checklist
In this article

Published October 27, 2026.

Two workstreams, two owners

An exit interview and a last-day checklist answer different questions. The interview asks why the person decided to leave and what the organization should change. The checklist asks whether equipment, access, knowledge, and payroll were handled correctly. Combining them produces a rushed conversation and an incomplete handoff.

Name a neutral interviewer for the conversation and the people operations coordinator for the checklist. The interviewer should not be the departing employee's direct manager when the exit involves conflict with that manager. Both owners work from the same departure date but keep separate records.

Schedule the interview before the last week

Aim for seven to ten days before the final day. The employee still has enough context to describe the decision, but the conversation is not competing with farewells and asset return. Offer two time slots and a written alternative if the employee prefers to submit answers.

Do not require the interview as a condition of final pay, a reference, or an orderly departure. A voluntary conversation produces more usable information than a coerced one. If the employee declines, record the decline and move on to the checklist rather than pressing for a reason.

Write questions that do not relitigate the separation

Ask when the employee first considered leaving, what changed after that point, what they told their manager, and what would have kept them. Follow with a question about the work itself: which parts were sustainable and which were not. Keep the language neutral and avoid asking the employee to defend the decision.

Leave legal claims, harassment allegations, and accommodation disputes out of the general interview script. If the employee raises one, stop the standard questions, explain the separate reporting route, and record only that a referral was made. The exit interview is not an investigation.

Record the handoff inventory

The checklist should list every item that must move: open client work, recurring reports, passwords held outside the password manager, physical keys, equipment, and pending approvals. For each item, record the receiving person, the transfer method, and the date completed.

A document dump is not a handoff. Require the receiver to confirm that they can perform the task once with the departing employee present. Mark the item complete only after that confirmation. Items without a named receiver stay open and appear on the manager's weekly review.

Keep access removal on its own evidence trail

Access removal needs its own timestamped record because it is both a security control and a common audit question. List each system, the account type, the removal date, and the person who confirmed it. Shared accounts should be rotated or retired rather than passed to a successor.

Do not let the last-day checklist close while an access item is pending. A closed checklist with an open account is worse than an open checklist, because it hides the risk. Route exceptions to the security owner with the system name and the reason for delay.

Protect confidentiality and references

Store interview notes separately from the personnel file when local policy allows, with access limited to the retention lead and the HR owner. Remove names before sharing themes with operational leaders. Small teams need extra care because a single detail can identify the speaker.

Decide the reference policy before anyone asks. State who provides references, what they may confirm, and how requests are routed. Managers who improvise informal references create inconsistent commitments and can expose the organization to claims of unequal treatment.

Review exits in aggregate, not in the moment

Hold the individual notes until the quarter closes, then review them as a set. Count reasons by role, tenure band, manager group, and schedule pattern. Read the narratives behind the largest group before assigning a cause, and keep the original codes so another reviewer can check the classification.

The output is a short list of changes with owners and dates, not a verdict about any one manager. Follow up at the next quarter to see whether the same reason appears again. A retention program earns credibility when departing employees can see that earlier feedback changed a process.

Sources reviewed