Exit Interview Template
A structured exit interview, not a box-ticking chat on the last day. A themed question set that captures honest reasons for leaving, a fair process, and an exit-driver view that turns individual departures into patterns you can act on.
Reviewed by Pradeep Arora, Chief Strategy Officer
- A themed question set across the seven areas people actually leave over
- A process checklist that keeps the conversation neutral and confidential
- An exit-driver matrix that scores how strongly each driver shows up by team
- An action tracker that turns a recurring signal into an owned fix
What is inside
- A themed exit interview question set across the seven areas people actually leave over, with open questions that get past the polite answer to the real reason.
- A process checklist that keeps the conversation fair: a neutral interviewer, the right timing, explained confidentiality and documented notes, so the input is honest and usable.
- An exit-driver matrix that scores how strongly each driver shows up by team or quarter, so a run of individual departures becomes a pattern you can see.
- An action tracker that turns each recurring signal into an owned fix with a name and a date, so the exit interview changes something instead of closing a file.
Who it is for
Anyone who has to plan what people learn, and answer for whether it landed.
- L&D and training teams
- People managers and team leads
- Heads of function and department
- HR business partners
- Compliance and risk teams
- Onboarding and enablement teams
- Operations and delivery leads
- COOs and HR directors
How to use this template in 4 steps
- Pick your format. Download the PDF to share, the Word file to edit, or the Excel file to work in live. All three are free.
- Make it yours. Adapt the sections, fields and wording to your team, roles and process so it fits how you actually work.
- Put it to work. Fill it in, circulate it to stakeholders for sign-off, or roll it out to your team.
- Track and improve. Review it on a set cadence and refine it as your goals, roles and priorities change.
What is inside
- A themed exit interview question set across the seven areas people actually leave over, with open questions that get past the polite answer to the real reason.
- A process checklist that keeps the conversation fair: a neutral interviewer, the right timing, explained confidentiality and documented notes, so the input is honest and usable.
- An exit-driver matrix that scores how strongly each driver shows up by team or quarter, so a run of individual departures becomes a pattern you can see.
- An action tracker that turns each recurring signal into an owned fix with a name and a date, so the exit interview changes something instead of closing a file.
An exit interview is HR-owned and the notes are sensitive, so keep them confidential and share only aggregated themes, never a named individual's words, with the manager concerned. This is a starting structure to adapt, not legal advice. Follow your own offboarding policy, confidentiality rules and local employment law, and keep the tone neutral: the interview is a record and a learning tool, not a chance to settle scores.
The exit interview question set
The conversation is built one theme at a time. Each theme has a short set of open questions that invite the real story rather than a yes or no. Work through them in order, and let the leaver talk: the useful answer is usually the one after the first polite one.
| Theme | Questions |
|---|---|
| Reason for leaving | What finally made you decide to leave? When did you first start thinking about it, and what could have changed your mind? |
| Role and workload | Did the job match what you expected when you joined? Was the workload sustainable, and were your responsibilities clear? |
| Manager and support | Did you get the support, feedback and recognition you needed from your manager? What would have made that relationship work better? |
| Growth and development | Did you have a clear path to grow here? Was training and development available, and did it help you move forward? |
| Culture and team | How would you describe the team and the culture? Did you feel included, respected and safe to speak up? |
| Compensation and benefits | Was your pay and benefits fair for the work and the market? How much did compensation weigh in your decision to leave? |
| Would you recommend or return | Would you recommend us as a place to work, and why? Would you consider coming back, and what would have to be different? |
When growth comes up repeatedly, it is worth checking whether people had a real path, not just an intention to train them. A role-mapped development plan delivered in an LMS makes progress visible to the employee, so the answer to did you have a path to grow is yes while they are still here, not a regret on the way out.
Running a fair exit interview
The quality of the answers depends on the conditions of the conversation. Work through these before and after each interview. Tick items as you confirm them, it stays in this browser. The download has the same list.
- A neutral interviewer runs it, not the line managerBeforePeople will not be candid about a manager to that manager.
- Scheduled before the last day, not the final hourBeforeCatch them while still engaged and not in the offboarding rush.
- Confidentiality explained up frontBeforeSay how notes are used and that themes are shared, not names.
- Open questions asked, silence allowedDuringThe real reason usually follows the first polite answer.
- Notes documented objectively and stored centrallyAfterNeutral language, separated fact and view, in a shared record.
- Themes aggregated across departuresAfterOne exit is an anecdote; the pattern lives in the sum of them.
- An action owner assigned to each real signalAfterA recurring theme with no owner changes nothing.
The most common failure is the line manager running the interview of their own departing report. The leaver softens everything, the notes read fine, and the one thing you most needed to hear, that people are leaving because of the manager, is the one thing that never gets said.
Scoring the exit drivers
A single interview is a story. This matrix turns many into a signal by scoring how strongly each driver showed up, team by team or quarter by quarter. Score each row and the hot spots jump out: the driver and the team where people are leaving over the same thing. In Excel the totals calculate as you type.
| Team | Exits | Pay | Manager | Growth | Workload | Culture | Ready |
|---|---|---|---|---|---|---|---|
| Sales | 14 | 2 | 1 | 2 | 1 | 0 | 60% |
| Engineering | 9 | 1 | 1 | 2 | 1 | 0 | 50% |
| Customer support | 11 | 1 | 2 | 2 | 2 | 1 | 80% |
| Operations | 7 | 1 | 1 | 1 | 2 | 1 | 60% |
| Frontline / field | 18 | 2 | 1 | 2 | 2 | 1 | 80% |
| Coverage at required | 40% | 20% | 80% | 60% | 0% | 66% |
Read down the Growth column before anything else: it is strong across almost every team. When the same driver recurs org-wide rather than in one team, it is not a manager problem to fix in one place, it is a structural gap, and growth is the one most organisations can actually close.
From signal to action
The matrix shows where the heat is. This tracker is where it becomes work. For each theme that keeps recurring, record the signal, the action you will take and the owner who is accountable for it, then review it next cycle against the new exit data.
| Theme | Signal | Action | Owner |
|---|---|---|---|
| Growth and development | Growth scores strong across most teams; cited as reason by regretted leavers. | Build role-mapped development paths and make progress visible from month one. | L&D and HR |
| Manager and support | Support team exits cluster on manager and recognition. | Run first-time-manager and coaching training for the affected line; recheck next quarter. | L&D and dept head |
| Workload | Frontline and support flag unsustainable workload. | Review staffing and shift patterns against actual volume; set a workload ceiling. | Operations |
| Compensation and benefits | Pay strong for Sales and Frontline versus market. | Benchmark the affected bands and close the gap on the roles that are leaving. | HR and Finance |
| Culture and team | Low but present; watch for drift. | Add two culture questions to the engagement survey and track by team. | People team |
How to use it
- Have a neutral person run it
Schedule the interview with HR or someone outside the line, not the leaver's own manager. People will not be candid about a manager to that manager.
- Schedule it before the last day
Book the conversation while the person is still engaged, not in the rush of their final hour, and explain up front how the notes will be used.
- Work through the themes, not a yes-or-no form
Use the question set to cover reason for leaving, role, manager, growth, culture and pay, with open questions that invite the real story.
- Document the notes objectively
Record what was said in neutral language, separate fact from interpretation, and store it where it can be aggregated rather than in a personal folder.
- Score the exit drivers and aggregate
Rate how strongly each driver showed up, add it to the running matrix, and read across teams and quarters to see the pattern, not the anecdote.
- Assign an owner to every real signal
A recurring theme with no owner changes nothing. Log each pattern in the action tracker with a named owner and a date, and review it next cycle.
Growth is the exit driver you can most directly close, and when development reaches people where they work it actually lands. On Disprz, ROSHN reached 91 percent adoption with a 15 percent lift in proficiency, and frontline teams reach 45 percent-plus completion through short mobile modules in the local language. That is the difference between telling people there is a path and showing them one before they start looking elsewhere.
Common mistakes this template prevents
- The line manager interviewing their own departing report, so the one answer you most need is the one the leaver softens.
- Vague questions that collect a polite story nobody can act on, instead of open prompts that surface the real reason.
- Notes filed and forgotten, with no aggregation, so the same reasons for leaving recur quarter after quarter unnoticed.
- Treating every exit as a one-off, so a structural driver like a missing growth path is never seen as a pattern.
- A clear signal with no owner, so the exit interview closes a file and changes nothing.
Which format should you use?
| Format | Best for | What is inside | Editable | Size |
|---|---|---|---|---|
| Sharing and print | The full template, formatted to print or circulate | No | 57 KB | |
| Word | Editing the wording | Every section as editable text you can adapt | Yes | 87 KB |
| Excel | Filling it in live | The grid and fields set up as a working spreadsheet | Yes | 66 KB |
Questions people ask
What is an exit interview template?
Who should conduct an exit interview?
What questions should an exit interview include?
How do you use exit interview data?
Are exit interviews confidential?
Do I have to fill the form three times?
Growth is the driver you can actually fix. That is the part we run.
Bring your exit-driver patterns to a 30-minute working session. Lack of development is one of the most consistent reasons people leave, and it is the one you can close. We will show how Disprz maps skills to every role, builds a visible path from onboarding to advanced, and delivers it in short mobile modules, so growth stops being the reason on the exit form. ROSHN reached 91 percent adoption and a 15 percent lift in proficiency this way.