How do I run a useful employee exit interview?

Run a useful employee exit interview by explaining the purpose and privacy boundaries, asking about specific work experiences and recording what the person actually says without turning it into a verdict. Check important factual gaps through an appropriate process. Finish with a small number of supported actions and owners, rather than a folder of feedback nobody uses.

The employee has decided to leave. This is a poor moment to win an argument about whether they ought to feel disappointed. I would use the conversation to understand the work from their position, including what they think you have misunderstood.

Decide what the conversation is for

Choose a practical purpose: understanding a mismatch between the advertised role and actual work, identifying a process that repeatedly caused difficulty, or learning what helped the person do a good job. Keep the purpose narrow enough to act on.

Acas's exit-interview discussion describes feedback as a way to understand departures and improve future arrangements. Its wider resignation guidance concerns the United Kingdom; use the feedback principle without importing its legal instructions into a U.S. employment process.

An exit interview is not the whole departure process. Final pay, benefits, property return, records and handover have their own requirements. Handle those through the actual appropriate process rather than making them bargaining chips for a favorable conversation.

Nor is the interview a substitute for responding properly to a serious complaint. If an allegation needs an investigation, safety response or other formal action, involve the responsible people. A line in a retention spreadsheet is not a completed response.

Make the invitation and boundaries honest

Explain who is conducting the conversation, what you want to learn, how notes will be used and who may receive the information. Agree an appropriate format and timing under your policy and applicable requirements.

Do not promise anonymity in a conversation where you know the speaker. Even a summary without a name can identify someone in a small team. Explain the actual confidentiality limits instead of offering reassurance the organization cannot honor.

Consider whether the interviewer can hear difficult feedback without defending their own decisions. If the direct manager is central to the concern, another appropriate person may provide a better route. That choice still needs clear handling of records and follow-up.

Give the person a way to decline a question or explain a concern about the process. Do not treat silence as satisfaction or pressure someone to disclose private details unrelated to the work. The quality of feedback cannot be improved by pretending it was freely given when it was not.

Ask about events before asking for a score

Begin with a neutral invitation to describe the role as it was actually experienced. Let the employee identify what mattered. A question that already names the suspected bad manager or inadequate pay can lead the answer toward the interviewer's theory.

Useful original prompts might include:

• Which parts of the job were different from what you expected when you joined?
• Describe a recent week when the work was especially difficult to organize.
• What happened when you needed a decision, information or support?
• Which arrangement helped you do the work well and should be kept?
• If one part of the role could be changed for the next person, what would you examine first?

These are illustrative prompts. Adapt them to the agreed purpose. Follow an answer with a request for relevant circumstances, not a demand that the employee prove every feeling to your satisfaction.

Separate what happened, how the person understood it and the consequence they describe. An explanation can be sincere without establishing every causal link. Equally, a missing timestamp does not make the person's experience irrelevant.

Listen without promising an outcome you cannot deliver

Check your understanding in ordinary language. If the person says the schedule was impossible, ask which part and what made it difficult. Do not immediately offer a counterexample from a different employee.

Record specific requests as requests. A manager may be able to review a process but not promise a pay change, a new role or a particular investigation outcome. Say what the actual next step is and who owns it.

If the conversation becomes an effort to persuade the employee to stay, acknowledge that it is a different discussion. A retention proposal can exist, but it should not quietly replace the stated purpose of hearing feedback.

Keep notes factual and proportionate. Distinguish a direct account, an interpretation and something the person heard from somebody else. Ask before recording and follow the applicable permission and record-handling process.

Work through an original feedback record

Consider a wholly fictional employer with three departing employees invited to give feedback. Two participate and the third does not respond. These are original teaching accounts, not actual employees, interviews or findings about a real workplace.

Participant A mentions both pay and schedule changes. Participant B mentions pay and development opportunities. The record therefore contains two pay mentions, one schedule mention and one development mention across two people.

That is four topic mentions, not four respondents or four separate departures. A person can identify several concerns. Turning the topics into mutually exclusive slices would require inventing a main reason the participants did not necessarily supply.

Pay appears in both participating accounts. That does not establish the third leaver's reason, a view shared by the whole workforce or proof that a higher wage would have prevented either departure.

Keep the coverage visible: two accounts from three invited leavers. A neat summary that omits the missing response can make the evidence look more complete than it is.

Separate publication from the employee's awareness

Participant A describes a shift change as arriving the night before work. In this fictional record, the system history shows the change was published at 4 p.m. on June 5, 2027, for a 9 a.m. start on June 6.

Publication preceded the shift by seventeen hours: eight hours to midnight plus nine more to the start. The employee says they first saw it at 10 p.m., eleven hours before work.

Those statements describe different events. The system can establish publication time under the supplied assumptions. The 10 p.m. awareness time remains the employee's account; it is not independently established merely because it appears in the interview notes.

Scroll across to compare the original record's claims. No legal scheduling-notice conclusion is supplied.

Calling A wrong because the change was technically posted earlier would miss the delivery question. Calling the system record eleven hours' notice would also mislabel the evidence.

The useful next inquiry concerns how changes reach employees, what lead time is feasible, which exceptions occur and how conflicts are handled. Relevant legal or contractual scheduling requirements need their own actual review; this seventeen-hour calculation does not determine compliance.

Fund the conversation and analysis

For an original bounded work plan, the interviewer has two paid hours available at an all-in $50 hourly employment cost. Preparation takes twenty minutes, two interviews take thirty minutes each, analysis takes twenty-five minutes and an internal action handoff takes fifteen.

The total is 120 minutes, costing $100. Each employee participates for thirty paid minutes before leaving, at an all-in $30 hourly employment cost. Their combined hour costs another $30.

The complete defined interview-and-analysis task therefore costs $130. All those hours are available without displacing accepted work. No other paid provider, recording service or survey fee is required in this limited example.

If the third person later accepts, another thirty-minute interview plus fifteen minutes of notes would require forty-five more interviewer minutes, costing $37.50. Thirty participant minutes add $15, for another $52.50.

That expansion would need additional approved time and funding; it does not fit inside the original two interviewer hours. The full expanded task would cost $182.50. Further investigation or implementation remains a separate scope, not work made free by calling the feedback collected.

Turn feedback into a bounded next action

For the scheduling concern, assign an appropriate owner to inspect the current change-notification process and its actual constraints. Define what would be examined, what evidence is needed and when a proposed change will return for decision.

A chosen forty-eight-hour internal planning target, for example, would be a proposal to assess, not a legal standard or a promise that every exceptional change can meet it. Check customer demands, staffing, permissions and the treatment of genuine emergencies before announcing it as solved.

Separate that operational proposal from the pay and development questions. One convenient scheduling fix should not swallow the other topics because it is the easiest to approve.

If a change is adopted later, observe what actually happens and record other relevant changes. A later decline in departures cannot automatically be credited to two exit conversations. The growth-measure guide helps keep an operating explanation beside a count.

Protect the record and close the follow-through

Keep identifiable notes accessible only through the appropriate process. A broad management summary can often describe the issue and needed action without reproducing unnecessary personal detail. Check whether a small-group description still identifies the speaker.

Where a serious concern requires escalation, preserve its meaning and send it through the authorized route. Do not soften it into a generic culture issue to make the summary easier to read. Equally, do not circulate an unverified allegation as an established finding.

Track each action to a decision, completion or an explicit unresolved condition. Thanking the employee and closing the form completes a conversation; it does not establish that the underlying work arrangement improved.

The first-employee guide considers the role and resources a business can support. Use feedback to examine that actual arrangement, not merely to recruit a replacement into the same unexplained difficulty.

Keep a small exit-interview record

1. Purpose, participant choice and honest privacy boundaries.
2. Specific work experiences and the person's own explanation.
3. Supporting records, contradictions and unanswered questions.
4. Participation coverage and overlapping topics.
5. Paid time, analysis and any separately approved follow-up.
6. Action owner, decision date and evidence of what changed.