Short answer
A useful exit interview programme gives every leaver a voluntary route to share specific examples, explains confidentiality limits, separates urgent cases from research, codes answers consistently, and assigns each accepted theme an owner, action, measure, and review date. The interview itself is only one part of the method.
What an exit interview can and cannot do
An exit interview is a structured learning conversation with someone leaving an organisation. It can add context to workforce data, reveal recurring friction, and test whether an existing explanation fits the employee's experience. It cannot establish the single true cause of a departure, prove that a manager or policy caused turnover, or predict who will leave next.
Keep it separate from administrative offboarding. Returning equipment, confirming final pay, transferring access, and explaining benefits or references are tasks with defined owners. Mixing them into the learning conversation can consume the time and make candid feedback feel tied to an employment transaction.
Keep it separate from case handling too. An allegation about discrimination, harassment, retaliation, safety, fraud, or another serious concern may need a designated process. The US Equal Employment Opportunity Commission explains that retaliation can include adverse action because a person raised discrimination concerns. US OSHA guidance likewise states that employers must not retaliate against workers for reporting work-related injuries or illnesses. An exit interview is not a safe substitute for those routes.
In the UK, Acas guidance on responding to a resignation describes exit interviews as one way to understand why someone is leaving and address outstanding matters. It also says employers should be careful not to exclude or hold back the employee during notice. That supports a fair, practical process rather than treating every leaver as a risk.
Write the programme specification first
Complete this worksheet before drafting questions:
| Decision | What to record |
|---|---|
| Population | Which voluntary resignations, retirements, contract completions, internal moves, or employer-initiated exits are in scope |
| Purpose | The decisions the programme should inform, such as onboarding, scheduling, manager support, or job design |
| Invitation | Who sends it, through which accessible channel, and how the employee can accept, decline, or reschedule |
| Interviewer | Who can listen impartially and where an alternative interviewer is available |
| Timing | The offered windows before and after the last day, subject to local policy and worker access |
| Record | Whether notes or a recording are created, where they are held, and who can access them |
| Confidentiality | What can remain restricted, what may be aggregated, and what must be escalated |
| Routing | Named routes for safety, conduct, legal, payroll, benefits, and wellbeing matters |
| Analysis | The codebook, denominator, minimum reporting group, and review cadence |
| Action | Who accepts findings, owns changes, and reports what happened next |
Do not quietly narrow the eligible population to people who have a company laptop, a corporate email address, or a positive relationship with their manager. Record invitations, completions, and declines by relevant workforce group. Coverage is part of the evidence, because a theme based mainly on head-office respondents cannot represent a dispersed frontline workforce.
Participation should be voluntary. Make declining easy and free from pressure. If an employee wants to raise an outstanding employment matter, provide the appropriate route whether or not they join the interview.
Use an honest opening script
A short script gives every participant the same essential information:
Thank you for choosing to speak with us. The purpose is to learn from your experience and improve work for others. You may skip any question or stop. I will record only the notes we agree. I cannot promise that every point will remain with me: a safety, legal, conduct, or serious wellbeing concern may need a different route. Before we start, what questions do you have about access or follow-up?
Adapt the script to the organisation's actual policy. Do not say “anonymous” when the interviewer knows who is speaking. Do not promise that comments can never be identified in a very small team. Explain whether quotations will be used and seek explicit agreement before retaining one.
Choose the interviewer and channel around the employee
There is no universally candid channel. A live conversation allows follow-up. A written response gives the employee time and distance. A phone or video call may help after access to the workplace ends. Offer a realistic choice where possible.
The direct manager may be able to explain or fix a local issue, but may also be the subject the employee cannot discuss openly. Use an HR partner, a trained interviewer, a skip-level leader, or another suitable route when that conflict exists. The interviewer needs a discussion guide and escalation practice, not a script that forces every person through every question.
Avoid making one day the universal rule. Offer windows that fit notice periods, work patterns, final-pay processes, and local requirements. A short follow-up after departure can be useful when the employee wants it, but repeated contact after a decline is not respectful participation.
A complete exit interview question bank
Use these questions as a menu. Start broad, ask for examples, and stop when the employee has answered the purpose of the conversation.
Decision and expectations
- What led you to decide that leaving was the right step for you?
- Was there a particular moment or a longer pattern behind the decision?
- Which expectations about the role matched reality, and which did not?
- What, if anything, did you try to change before deciding?
Work and operating conditions
- What helped you do good work here?
- Which process, handover, tool, schedule, or decision made good work harder?
- Can you describe a recent example?
- Was that experience occasional, tied to a particular context, or persistent?
Manager, team, and voice
- What support from your manager or team was useful?
- Where did you need clearer priorities, feedback, recognition, or access to decisions?
- Did you have a workable route to raise concerns or ask for changes?
- Is there something you did not feel able to discuss while employed?
Development and movement
- Which skills or responsibilities were you able to develop?
- Were internal opportunities visible and realistic for you?
- Did onboarding or training prepare you for the work you were expected to do?
Close and permission
- What should the organisation preserve?
- What is one change you would ask a senior leader to examine?
- What have I misunderstood or failed to ask?
- Which parts of our notes may be retained or reported as a theme?
- Is any point better handled through another route, and may I help make that connection?
Useful follow-ups include “What happened next?”, “Who or what was affected?”, “What was different when it worked?”, and “What evidence would help us check that?” Avoid asking the employee to diagnose the whole organisation or name colleagues unnecessarily.
Route urgent matters before thematic analysis
Create a routing card for interviewers. It should name the current contact and next step for:
- immediate safety or safeguarding risk;
- discrimination, harassment, retaliation, or serious conduct concerns;
- unresolved pay, leave, benefits, or final-pay questions;
- data protection or access concerns;
- self-harm or acute wellbeing concerns;
- fraud, bribery, or regulatory issues.
The interviewer should record the minimum needed to make the handoff and explain it to the employee. Do not bury an urgent report in a quarterly theme deck. Do not investigate it within the interview unless the interviewer holds that role and has followed the relevant process.
Build a codebook before reading for patterns
Coding turns accounts into a reviewable dataset, but it also introduces judgement. Define codes in advance, allow a response to carry more than one code, and keep the employee's account separate from the analyst's interpretation.
| Field | Example |
|---|---|
| Workforce scope | UK customer operations employees with voluntary resignations |
| Theme code | Work allocation |
| Definition | Examples about how work is assigned or reprioritised |
| Include | Repeated urgent reassignment, unclear ownership, uneven allocation |
| Exclude | Pay concerns without a work-allocation example |
| Evidence note | Employee's agreed summary plus interviewer context |
| Confidence limit | Theme reflects respondents, not every eligible leaver |
Track the interview response rate as completed interviews divided by eligible invited leavers for the same period and population. Report who was missing. Do not calculate percentages for tiny groups if the result could expose a person's identity or invite unstable comparisons.
Compare exit themes with workforce events and other evidence, while keeping association separate from cause. A rise in scheduling comments after a rota change makes scheduling a hypothesis to investigate. It does not prove the rota caused every departure.
The CIPD turnover and retention factsheet recommends examining turnover by factors such as occupation, location, and tenure and warns that crude totals can hide where an issue sits. Apply that principle to interview coverage and themes as well as departure rates.
Fictional worked example
Northbridge Support is a fictional UK and US service business. In one quarter, it invites all 28 voluntary leavers in an agreed population and completes 17 interviews. Eleven do not participate, so the team labels the findings as respondent evidence rather than the view of all leavers.
Seven interviews include examples coded to “urgent work reassignment.” Five of those concern two teams that adopted a new triage rota. HR checks the code against the notes, removes one response that described an unrelated pay issue, and reports six relevant accounts. The pattern is associated with the rota, but the sample does not establish cause.
Operations chooses a bounded response: clarify escalation ownership in the two teams, test the revised handover for six weeks, and compare missed handoffs, overtime, and voluntary comments with the prior period. A named director owns the test. HR also sends one pay query and one conduct concern through separate routes rather than counting them as evidence for the rota hypothesis.
The decision log reads:
| Field | Entry |
|---|---|
| Observation | Six respondent accounts describe urgent reassignment in two teams |
| Coverage | 17 of 28 eligible invited leavers participated |
| Alternative explanations | Vacancy pressure, account mix, manager change |
| Action | Six-week handover and escalation test |
| Owner | Customer operations director |
| Measures | Missed handoffs, overtime, employee comments |
| Review decision | Continue, change, or stop the test based on the combined evidence |
Run a quarterly action review
An exit programme earns trust through visible follow-through. At each review:
- Reconcile eligible leavers, invitations, and completed interviews.
- Check whether participation is uneven by role, location, contract, shift, or tenure.
- Review urgent cases separately and confirm they reached the designated process.
- Recode a sample to test whether analysts apply definitions consistently.
- Compare themes with operational and workforce evidence.
- Select only actions with a clear owner, scope, measure, and review date.
- Tell employees what was learned and changed without exposing contributors.
- Record where evidence was insufficient and what would resolve the uncertainty.
For a programme designed around the realities of store and plant work, use the retail exit interview guide or manufacturing exit interview guide. For conversations before a resignation decision, compare stay interviews and exit interviews.
If a guided digital conversation would make the invitation more accessible across a defined population, review the Lontra product approach alongside your process requirements. Confirm the invitation route, leaver access after account closure, recording and access rules, escalation handoff, export needs, and integration with the organisation's existing offboarding workflow before launch.
The final test is simple: a participant should understand the purpose, choice, record, access, and escalation boundaries. A leader should be able to trace each action back to evidence without treating a departing employee's account as an individual score or a universal verdict.
