Stay Interview Scripts Managers Will Actually Use

A useful stay interview script asks three questions: what makes you stay, what might make you leave, and what one change would improve your week. Keep it to 20 minutes, aggregate themes instead of storing individual quotes, and commit to one visible fix per quarter.

#Why do stay interviews beat exit data alone?

Exit interviews explain who already left. Stay interviews explain what is still working, and what is quietly breaking, while employees still have optionality. In practice, the value is not the transcript. It is pattern detection across teams.

Conversation	Timing	Best use	Main risk
Stay interview	Before someone decides to leave	Find fixable retention friction	Feels like surveillance
Engagement survey	Broad periodic pulse	Quantify themes	Too shallow for root cause
Exit interview	After resignation	Confirm patterns	Too late to retain

#What is the three-question stay interview script?

Use this script:

1. What makes you stay? Listen for anchors: manager, mission, flexibility, growth, team trust.
2. What would make you consider leaving? Probe once for clarity. Do not debate or defend.
3. What one change would improve your week? Force prioritization. "Everything" is not an actionable answer.

Close with: "We are aggregating themes, not putting individual quotes in performance files. We will share what we heard and what action we are taking."

#How should managers be trained?

Train managers for 30 minutes:

• Walk through the script and timing.
• Role-play a defensive manager response and practice pausing.
• Show the aggregation template: theme, frequency band, suggested owner.
• Explicitly forbid forwarding raw notes into calibration, PIPs, or performance files.

That last rule matters. SHRM's stay interview guidance emphasizes retention conversations, not performance evidence. Once employees believe the notes can be used against them, the program stops producing useful signal.

#How do you aggregate themes without surveillance?

Use buckets leadership can act on:

• Compensation and leveling clarity
• Manager quality and feedback cadence
• Workload and prioritization
• Career path and promotion velocity
• Tools, process, and cross-functional friction
• Flexibility and location policy fit

For each bucket, report frequency and severity, not names. Pair this with workforce survey action plans and onboarding buddy programs so listening becomes an operating loop, not a one-off HR exercise.

#What breaks stay interview programs?

Scripts grow to 12 questions. Notes land in performance files. Leaders do not act. Rating season overlaps with "safe space" interviews. HR tries to run every conversation and cannot scale.

Fix those with a one-page script, manager-owned conversations, a written no-performance-file rule, and a quarterly "you said / we did" update.

#Operational checklist

• One-page script published in manager resource hub
• Manager enablement recorded
• Aggregation template with theme buckets and severity bands
• Written rule: stay interview content not used in performance documentation
• Quarterly leadership review with one committed action
• Close-the-loop communication template

#Restored practitioner detail

Exit interviews explain who already left. Stay interviews explain what still works—and what is quietly breaking—for people who remain. Most programs fail for predictable reasons: scripts run long, managers treat answers as performance evidence, or leadership never acts on themes. Employees learn the exercise is theater and stop telling the truth.

Growing SMBs do not need enterprise retention analytics to run stay interviews well. They need a one-page script managers can execute in twenty minutes, a clear rule about where notes go, and a quarterly commitment to fix one org-wide friction point surfaced by aggregated themes. Stay interviews are listening infrastructure—not surveillance, not a substitute for compensation benchmarks, and not a replacement for fixing broken managers.

#Why stay interviews beat exit data alone

Exit interviews arrive after the decision. By then, counteroffers are often too late and root causes are filtered through politeness. Stay interviews capture pull factors while employees still have optionality: what keeps them engaged, what would make them look externally, and what single change would improve their week.

The goal is pattern detection across teams, not individual dossiers. HR and executives care about themes—unclear promotion paths, calendar overload, broken handoffs between functions—not verbatim quotes tied to names in performance files. When managers understand that distinction, candor rises.

Tip. Position stay interviews as "how we improve the job," not "how we evaluate you." If employees fear ratings consequences, you will hear safe answers.

#The three-question script

Keep the script on one page. Three questions, twenty minutes, no improvisation spiral.

1. What makes you stay? Listen for specific anchors: manager, mission, flexibility, growth, team trust—not generic "the people."
2. What would make you consider leaving? This is the risk question. Probe once for clarity; do not debate or defend the company in the room.
3. What one change would improve your week? Force prioritization. "Everything" is not an answer; help them name the highest-leverage fix.

Close with gratitude and a reminder: themes roll up anonymously; this is not a performance review. Managers note themes and severity, not transcript length.

#Train managers in thirty minutes

HR does not need to attend every conversation. Run a single enablement session:

• Walk through the script and timing (fifteen minutes listen, five minutes notes).
• Role-play one defensive manager who argues with answers—train pause, not rebuttal.
• Show the aggregation template: theme, frequency band (one person / several / widespread), suggested owner.
• Explicitly forbid forwarding raw notes to calibration, PIPs, or skip-level "gotcha" files.

Managers who already run decent 1:1s can add stay interviews quarterly without a new meeting culture. Schedule them outside performance-rating windows so psychological safety stays intact.

#Aggregate themes—not individual surveillance

After conversations complete, managers submit theme summaries to HR ops—not employee-attributed quotes. Use buckets that leadership can act on:

• Compensation and leveling clarity
• Manager quality and feedback cadence
• Workload and prioritization
• Career path and promotion velocity
• Tools, process, and cross-functional friction
• Flexibility and location policy fit

Leadership reviews themes in a thirty-minute quarterly forum. Pick one org-wide fix with a named owner and a publish date. Communicate what you heard and what you are changing—even when the fix is "not this quarter" with rationale. Silence trains employees that stay interviews are discardable.

Break trust once—using stay interview content in a PIP, sharing identifiable quotes with executives, or ignoring repeated themes—and the program dies faster than any engagement survey recovery plan.

#Connect stay interviews to broader retention ops

Stay interviews complement—they do not replace—workforce survey action plans and manager enablement. Surveys give breadth; stay interviews give depth on high-impact roles and flight risks you already suspect.

Pair with onboarding buddy programs on the front end: buddies surface early friction; stay interviews confirm whether fixes stuck at six and twelve months. If onboarding scores high but stay themes show mid-tenure stagnation, the constraint is likely leveling or manager variance—not welcome-week logistics.

For critical roles, consider stay interviews at ninety days post-hire and annually thereafter—same script, same aggregation rules. Frequency is less important than consistency and closed-loop action.

#What breaks stay interview programs

Scripts grow to twelve questions. Managers run out of time; employees fatigue. Fix: three questions maximum; optional follow-up only with HR coaching.

Notes land in performance files. Legal and cultural risk follow. Fix: store aggregated themes in an HR ops repository with retention policy; prohibit individual quote storage in talent systems.

No leadership action. Employees stop participating. Fix: one visible org fix per quarter, communicated company-wide.

Rating season overlap. Employees hedge answers. Fix: schedule stay interviews mid-cycle, away from calibration and merit conversations.

Only HR runs them. Scale fails. Fix: manager-owned conversations with HR-designed guardrails.

#Operational checklist

• One-page script published in manager resource hub
• Enablement session recorded for new managers
• Aggregation template with theme buckets and severity bands
• Written rule: stay interview content not used in performance documentation
• Quarterly leadership forum on themes with one committed action item
• Communication template for "you said / we did" close-the-loop posts

#What to do this week

1. Draft the three-question script and limit it to one printed page.
2. Identify ten managers to pilot quarterly stay interviews on high-impact teams.
3. Build the theme aggregation template—no employee names in leadership readouts.
4. Schedule the first quarterly theme review before the next pilot cycle ends.
5. Publish where notes may and may not be stored—performance systems are out of bounds.

Stay interviews are cheap signal if you treat them as operational listening with closed-loop fixes. They are expensive noise if they become retention surveillance. Keep the script short, aggregate honestly, and fix one real problem per quarter—employees will notice, and the next conversation gets easier.

#Related guides

• Workforce Survey Action Plans That Close the Loop
• Onboarding Buddy Programs That Actually Stick