Nurse Exit Interview Analysis: Coding Reasons Into Usable Data

The exit interview that says "pay" and means something else

A resignation lands on a Tuesday. The nurse manager of a 28-bed med-surg unit sits down with the departing RN for the exit interview, writes three lines of notes, and files them in the HR folder. The reason on the form reads "better opportunity." The previous month's form from the same unit said "pay." The month before that, "schedule." Six weeks later the Director of Nursing asks a fair question in the Monday meeting: why are people leaving that unit, and can we do anything about it?

Nobody can answer. The conversations were honest, but the notes sit in a folder where they cannot be counted, so the pattern stays invisible until the cluster is already a staffing problem.

The fix is not a longer interview or a fancier survey. It is a consistent way of writing down the reason so that twelve departures become twelve rows with comparable codes. This guide to nurse exit interview analysis lays out a simple reason-coding scheme, the rules that keep it consistent between managers, and how to read the counts by unit and period so the preventable drivers surface early.

Why most exit interview notes never become data

Free-text notes fail for ordinary reasons. Two managers describe the same situation in different words. One records the nurse's first stated reason and the other records the one that took twenty minutes to emerge. The form has a single "reason for leaving" field, so a nurse who named workload, a new manager, and a pay gap gets reduced to whichever the interviewer typed first.

Exit conversations also happen after the decision is made, and nurses are often diplomatic on the way out. "Pay" is the easy answer to give and to write down, and it can stand in for feeling undervalued or for chronic short staffing. Published survey work points the same way. The American Nurses Foundation and McKinsey surveyed more than 7,000 nurses in 2023 and found about 39% said they were likely to leave their position within six months. The top reasons in that survey were not feeling valued, insufficient staffing, and inadequate compensation. Those three can overlap, which is why a single free-text field struggles to separate them.

The stakes for getting the picture right are financial as well as operational. The 2026 NSI National Health Care Retention & RN Staffing Report puts national RN turnover at 17.6% for calendar year 2025, and the cost to replace one bedside RN at $60,090 in that same 2026 report. A unit that cannot say why its nurses leave cannot decide where a retention dollar should go first.

Nurse exit interview analysis starts with a reason-code scheme

Coding means mapping what the nurse said onto a short, fixed list of reasons, so that every departure is recorded the same way. The list should be short enough that managers actually use it and specific enough that a count means something. Eight to twelve codes, grouped into a handful of families, is a workable range for a single facility.

A starting scheme might look like this:

• Compensation: base pay compared with the market, differentials, overtime or incentive pay, benefits.
• Workload and staffing: assignments, short shifts, frequent floating, missed breaks, mandatory overtime.
• Schedule: shift pattern, weekend rotation, self-scheduling flexibility, request approval.
• Leadership and recognition: the direct manager relationship, feeling valued, voice in decisions.
• Growth and role: advancement, education support, clinical ladder, specialty change.
• Life events and external: relocation, family, return to school, retirement.
• Health or career exit: leaving the profession, injury, burnout stated outright.
• Other, with a required note: used rarely, and reviewed every quarter to see whether a new code is needed.

Take the codes from your own facility's language rather than a borrowed template that does not match how your nurses talk.

Coding rules that keep managers consistent

A scheme only produces usable counts if different people apply it the same way. Four rules do most of the work.

Record a primary reason and up to two contributing reasons. The primary reason is the one that, in the nurse's own framing, tipped the decision. Contributing reasons are the others they raised. Primaries give a clean ranking; contributing reasons show how often workload sits underneath a stated pay complaint.

Code what was said, not what you infer. If the nurse says "the money wasn't there," the code is compensation. If you suspect the real issue was the manager, note the suspicion in the comment field and leave the code alone. Inference is where one manager's bias becomes the unit's data.

Use the same prompt for every interview. A short, fixed set of open questions, asked in the same order, gives you comparable material. Ask what led to the decision, what would have changed it, and what one thing you would fix for the nurses who stay. The second question is the one that separates preventable departures from the rest.

Have someone other than the unit manager review the coding. Where the unit manager is part of the story, a second reader from HR or the nursing office keeps the codes honest. Do this on a sample if you cannot do it for every record.

Keep each record free of patient information. Reason coding needs only the nurse's decision, the unit, and the dates.

Reading the counts by unit and period

Once each departure carries a unit, a date, a primary code, and any contributing codes, the useful questions become simple counts.

Here is a worked example with invented round numbers, shown only to illustrate the method. Suppose a med-surg unit records 12 departures over a rolling twelve months. Coding gives 5 primary reasons of workload and staffing, 3 compensation, 2 leadership and recognition, 1 life event, and 1 schedule. Looking only at the primary column, workload leads. Adding the contributing reasons, compensation appears on 7 of the 12 records. That tells you something the ranking alone hides: pay is not the most common tipping point on this unit, but it is present in more than half the departures, so a pay fix alone would probably not hold anyone who is leaving over workload.

Three ways to read the same data:

• By unit. Compare each unit's top two primary codes. A reason that dominates one unit and barely registers on the others points to a local cause, usually workload, leadership, or schedule. A reason that shows up everywhere points to something structural, often compensation.
• By period. Count by quarter or rolling six months rather than waiting for a year-end tally. A reason that moves from one departure to four in two quarters is the early signal the free-text folder never gave you.
• Against your turnover rate. Pair the reason counts with your unit-level turnover so a loud reason on a stable unit does not draw attention away from a quiet one on a unit that is losing people. The guide to turnover rate by unit and role covers how to build that denominator.

Small units mean small counts. Treat them as a prompt for a conversation with the manager and the staff, and avoid reading too much into a single quarter.

Separating preventable departures from the rest

The reason code tells you why a nurse left. A second flag tells you whether the facility could reasonably have changed the outcome. Mark each departure as preventable, partly preventable, or not preventable, using the nurse's answer to "what would have changed your decision."

Retirement, a spouse's relocation, and a return to school are usually not preventable. Departures over workload, recognition, schedule flexibility, or a pay gap you could have closed often are. Marking everything "not preventable" is as unhelpful as marking everything preventable.

This flag also connects to the broader classification of departures. If your records do not already separate resignations from terminations and other exits, voluntary vs. involuntary turnover explains how to draw that line so that your nurse exit interview analysis only covers the departures it can actually explain.

When compensation appears as a repeated primary or contributing code, compare your pay bands with public wage data before you decide what to do. BLS Occupational Employment and Wage Statistics publishes RN wages by state and metro area, and the piece on nurse wage gaps and flight risk shows how to turn that comparison into a ranked list of roles at risk. A pay complaint in an exit interview is worth checking against the market before it becomes a budget request.

Turning the counts into action

Counts matter only if they change what the unit does. After each quarter, take the top preventable driver for each unit and write down one specific action, an owner, and a date. Revisit the same code the following quarter to see whether it has moved. An action log for retention interventions gives that follow-through a home, so the exit-interview findings do not die in a slide deck.

If you want the scheme built rather than drawn from scratch, the Nurse Exit Interview Analysis & Reason-Coding Workbook lets you code each nurse departure's exit-interview reason, then surface the top preventable drivers by unit and period. It runs as a spreadsheet you fill in yourself, with no PHI, no EHR connection, and no scheduling takeover. Any spreadsheet you maintain can do the job, as long as the codes are fixed and the review step is real.

For the wider set of turnover measurement guides, including rates, costs, and benchmarks, the nurse turnover resource hub is the place to start. Exit interviews are the input where nurses tell you, in their own words, what they would change. Coding those words is how you make sure someone counts them.