Good exit interview questions cover two things: why the person is leaving, and what they know that will leave with them. Ask 8 to 12 feedback questions about role, manager, growth and pay, then run a separate knowledge conversation about open work, unwritten workarounds, key contacts and the reasons behind past decisions.
Most exit interviews only do the first half. HR collects feedback, files it, and the person's real knowledge walks out on their last day. This guide gives you both halves: 55 questions you can copy, grouped by purpose, and a simple way to run them.
Why do exit interviews need two tracks?
The feedback track asks how the job felt. The knowledge track asks what the job knew. They need different people in the room and different timing.
| Feedback track | Knowledge track | |
|---|---|---|
| Goal | Learn why people leave, improve retention | Keep what the person knows working after they go |
| Led by | HR or a neutral person | Manager, successor or a teammate |
| When | Final week | Early in the notice period, over 2 to 3 sessions |
| Output | Aggregated themes for leadership | A handover document the team can use |
| Confidentiality | Reported in aggregate | Shared with the people who need it |
The stakes are real. Gallup estimates that replacing an employee costs between one-half and two times their annual salary (Gallup). A 2018 YouGov survey commissioned by Panopto found that respondents considered 42% of their job knowledge unique to them (Panopto press release). Treat that second figure as a self-reported order of magnitude, not a precise measure, but it matches what most managers feel when someone resigns.
Feedback track: 25 exit interview questions to ask
Why are you leaving?
- What made you start looking for a new role?
- Was there a specific moment when you decided to leave?
- What does your new role offer that this one did not?
- Could anything have changed your decision? When would it have needed to happen?
- Did you raise any of these concerns before? What happened?
The role and the work
- How closely did the job match what you were told when you joined?
- Which parts of your work felt most valuable? Which felt like waste?
- Did you have the tools, information and authority to do the job well?
- Was your workload sustainable? What made it heavier than it needed to be?
- What would you change about this role before we hire for it again?
Manager and team
- How would you describe your relationship with your manager?
- Did you get useful feedback, and often enough?
- Did you feel recognized for your work?
- How well did your team work with other teams?
- Is there anything about the team you would want leadership to know?
Growth and pay
- Did you see a path to grow here? What blocked it?
- Did you get the learning and development you expected?
- How did you feel about your pay and benefits compared with the market?
- Was pay the main reason you are leaving, one reason among several, or not a reason?
Culture and the organization
- How would you describe the culture to a friend considering a job here?
- Did you feel decisions were explained, or just announced?
- Did you feel safe raising problems?
- What should we keep doing exactly as it is?
- Would you consider coming back in future?
- Is there anything we did not ask that we should have?
Knowledge track: 30 questions about what the person knows
Run these with the manager or successor, ideally in two or three sessions of 30 to 45 minutes. Record the answers straight into a handover document.
Work in flight
- What is the real status of each thing you own, beyond what the tracker says?
- What have you promised someone, inside or outside the company, that is not written down?
- What is due, expiring or up for renewal in the next six months that only you track?
- If nothing changes after you leave, what breaks first, and when?
- Which tasks happen only once a quarter or once a year, so nobody else remembers them?
How the work actually gets done
- Walk me through your most frequent task from start to finish.
- Where do you deviate from the documented process, and why?
- Which shortcuts, scripts, spreadsheets or personal files does your work depend on?
- Where are the files, logins (via the password manager, never in the doc) and dashboards your successor needs?
- What do you check before you consider something finished?
- What goes wrong regularly, and what is your standard fix?
Decisions and their reasons
- Which decisions in your area would look strange to a newcomer but have good reasons behind them?
- What did we try that failed, so nobody should try it again without knowing the history?
- Which decisions are still open, and what would you recommend?
- What would you change straight away if you were staying?
- Which current arrangement is a temporary workaround that became permanent?
People and relationships
- Who do you work with most, and on what?
- Who actually approves things in practice, as opposed to on paper?
- Which customer, supplier or partner has preferences you only learn by getting them wrong?
- Which relationships need a personal introduction rather than an email?
- Who should your successor meet in their first week?
Risks and judgment
- What should your successor never change without asking first? Who should they ask?
- Which incident taught you the most, and what is the lesson in one sentence?
- What is the most common mistake a new person would make in this role?
- Where are we exposed if you are not here, for example audits, compliance dates or single points of failure?
- Which topics do only you understand well in this team?
For the successor
- What should your successor focus on in their first two weeks?
- What can safely wait?
- Which documents or past threads are worth reading first?
- If your successor could ask you one question in three months, what do you think it would be?
How to run the exit interview
- Start the knowledge track the week notice is given. Book two or three sessions with the manager or successor.
- Share the questions in advance. People give better answers when they have had time to think.
- Write answers into the handover document during the session. Do not rely on notes to be written up later.
- Run the feedback conversation in the final week, led by HR or someone outside the reporting line.
- Close the loop. Report feedback themes to leadership every quarter, and check with the successor after 30 days whether anything was missing.
Common mistakes
- Only asking why they left. You learn about retention but lose the job's knowledge.
- Asking for a summary. "Can you write up everything you do?" produces a thin document. Specific questions produce useful answers.
- Leaving it to the last day. By then there is no time to follow up.
- Mixing feedback and handover. People will not criticize their manager in a document the team will read.
How Reattend helps
Reattend is organizational memory software. Its desktop app remembers decisions, commitments and meeting notes as work happens, so less depends on what someone can recall in their final week. Exit interviews can be answered question by question in the desktop app and turned into a handoff document, and leaders can see the topics only one person holds and their open commitments. Use the questions above with or without it. If you want a ready-made form, start with our exit interview template.
Frequently asked questions
What are the best exit interview questions?
The best exit interview questions do two jobs. Ask about the reasons for leaving (role, manager, growth, pay, workload) and about the knowledge the person holds: open commitments, unwritten workarounds, key contacts, and decisions only they can explain. Most exit interviews only do the first job.
How many questions should an exit interview have?
Around 8 to 12 for the HR conversation, which fits in 30 to 45 minutes. The knowledge questions work better spread over two or three short sessions during the notice period, led by the manager or a teammate rather than HR.
Who should conduct the exit interview?
HR or a neutral person outside the reporting line should run the feedback part, so the person can speak freely about their manager. The person's manager or successor should run the knowledge part, because they know what to probe.
When should you hold an exit interview?
Hold the knowledge sessions early in the notice period, while there is time to follow up. Hold the feedback conversation in the last week, when the person is more likely to be candid.
Are exit interviews confidential?
They should be reported in aggregate. Tell the person who will see their answers before you start, and keep feedback about individuals separate from the knowledge handover, which is meant to be shared with the team.