Most retention conversations happen too late. By the time a manager notices someone is disengaged, the employee has already mentally moved on. A stay interview turns that around: you sit down with a current employee, ask what keeps them here and what might push them out, and you act on what you hear while there is still time to make a difference. The output is not a survey score. It is a list of concrete work items with an owner and a deadline.
What are stay interviews?
A stay interview is a structured, one-to-one conversation between a manager and a current employee focused on retention. You are not investigating a performance problem or assessing fit. You are asking someone who is already doing the job well what would make them stay longer and what would make them think about leaving. The answers typically surface workload issues, compensation gaps, career frustrations, or team dynamics that a manager can actually do something about.
Why the conversation needs to produce a work item
The difference between a stay interview that works and one that wastes everyone’s time is what happens after you leave the room. If the session produces vague notes that sit in a folder, the employee notices the gap between the conversation and the outcome, and trust erodes. If the session produces a specific action with a named owner and a date, it creates accountability. A compensation review routed to payroll, a workload adjustment agreed with the team lead, or a development plan signed off by HR are all outputs you can track and close.
How a real session translates into HR and payroll work
Consider a senior analyst who has been running two workstreams since a restructure six months ago. A stay interview surfaces the workload as the main retention risk, and a compensation gap as a secondary one. The manager agrees to reallocate one workstream, routes a market rate review to payroll with a four-week deadline, and copies the HR business partner on the follow-up. Three things are now in motion: a task for the manager, a validation task for payroll, and a calendar reminder for the follow-up. None of that exists without the conversation, and none of it survives the conversation without documentation.
How do stay interviews differ from exit interviews and surveys?
Exit interviews give you information after the decision is made. Employee engagement surveys give you trends across a population. Stay interviews give you an actionable case for a specific person who is still on the payroll. Each instrument serves a different purpose, and the mistake most HR teams make is treating engagement survey results as a substitute for individual retention action.
What surveys and exit interviews cannot do
When an engagement survey tells you that 30 percent of your workforce feels their contributions are not recognised, that is useful for designing a recognition programme, but it does not help you decide what to do for the analyst in finance who has been passed over for promotion twice and is showing early signs of quiet quitting. Surveys operate at the aggregate level; stay interviews operate at the case level. Exit interviews, meanwhile, are conducted after the employment relationship has already broken down. You learn what went wrong, but you cannot fix it for the person leaving. The most you can do is use the pattern to prevent the next departure.
When to use a stay interview instead of a survey
Stay interviews are one of the few tools in talent management that let you act on a retention risk before it becomes a departure. They make most sense when you have a specific risk in front of you: a high performer in a hard-to-fill role, someone who has flagged dissatisfaction informally, or a team member who has recently turned down a visible development opportunity. You do not need to wait for an annual survey cycle. If you have an early warning signal and a manager relationship strong enough to support an honest conversation, that is the right moment to act.
What data should stay interviews capture?
The session is only as useful as the record it produces. If the outcome stays in the manager’s head, it cannot be routed to HR or payroll, it cannot be audited, and it cannot be measured. You need a standard set of fields that any manager fills in after every session, regardless of how informal the conversation felt.
The fields that make a record actionable
At minimum you need the employee’s name and role, the date and the interviewer’s name, a short description of the main retention driver with a specific example, the agreed actions with the name of the person responsible for each one, a target date, and whether any action requires payroll involvement. That last field matters because pay-related requests need a different approval chain than a workload change or a coaching plan. Without it, pay requests sit in a manager’s action list until the window for that payroll cycle closes.
How to structure the conversation itself
A short script helps managers run consistent sessions without making the conversation feel like an interview. Open with a clear statement of purpose and confidentiality. Explain that you are asking because you want to address concerns while the person is still here, not after they have decided to leave. Then work through three or four core questions: what do you value most about working here, what would make you consider leaving, is there anything we could change that would make your job significantly better, and is there a role elsewhere in the organisation that interests you. Follow each question with a targeted probe based on what the person says. Close by summarising the actions you have agreed and confirming who owns each one.
Routing outcomes to the right owner
Once the record exists, the routing decision is straightforward. Manager-owned actions such as workload changes, schedule adjustments, and coaching conversations stay with the manager. HR-owned actions such as role redesign, title reviews, or internal mobility conversations go to the HR business partner. Payroll-owned actions such as market rate adjustments, contract changes, or deduction amendments go to payroll with the required lead time. The mistake to avoid is letting the manager decide all three without telling HR or payroll. A manager who promises a salary increase before payroll validates the budget creates a credibility problem that is much harder to fix than the original retention risk.
Compliance, access, and data protection
Stay interview records contain sensitive personal information. The same controls you apply to performance review documentation apply here: role-based access so only the relevant manager, HR business partner, and any required approvers can read the record, a defined retention period, and an audit log that shows who accessed or changed the record. Routing outcomes through your HR and payroll integration system rather than informal email chains reduces the risk of records getting lost or accessed inappropriately, and it creates the audit trail you need if a decision is later challenged.
How should teams pilot and measure stay interviews?
Running a pilot before a full rollout lets you find the operational gaps before they damage credibility with employees. A manager who runs a stay interview and then cannot deliver on the agreed actions because the routing process was not ready does more harm than no stay interview at all.
Designing a pilot that produces useful evidence
Choose a cohort of ten to fifteen employees where the retention risk is real and the managers involved are strong enough to run honest conversations. Keep the pilot to a defined period, typically one quarter, and agree upfront on what you are measuring. Process health metrics tell you whether the programme is running consistently: you want to see sessions completed within the planned window, records filled in within forty-eight hours, and action items assigned and not sitting open after the agreed deadline. Outcome metrics tell you whether it is working: staff turnover in the cohort, the proportion of pay-related requests that reach payroll before the relevant cycle closes, and qualitative feedback from participants after the first round of actions is completed.
What to check before you run the first session
Before any manager conducts a stay interview, confirm that the interviewer understands the confidentiality boundaries and can explain them clearly to the employee. Confirm that the record format is defined and accessible. Confirm that routing rules exist for each action category, and that payroll has a defined intake path for manager-initiated pay reviews. Confirm that access controls on records are in place. Running a session without these foundations in place is not a pilot; it is an improvisation, and employees will notice the difference.
How to use pilot results to decide whether to scale
At the end of the pilot period, report on both operational health and retention impact. If the action completion rate is above eighty percent and the attrition rate has held or improved, the case for scaling is straightforward. If action completion is low, investigate whether the problem is in the routing rules, the manager training, or the approval chains before you add more participants. Define your scale threshold before the pilot ends, not after. Post-hoc thresholds are always set to confirm whatever outcome you want to see.
What common pitfalls should teams avoid with stay interviews?
The programme breaks down in predictable places. Most of the failures are preventable if you address them before the first session rather than after the first complaint.
The most damaging mistake is a verbal commitment that cannot be kept
When a manager agrees in a stay interview to increase someone’s salary and then comes back three weeks later to say the budget was not approved, the employee is in a worse position than before the conversation. You have surfaced a compensation gap, created an expectation, and then failed to meet it. The way to prevent this is a simple rule enforced before any manager runs a session: no pay-related outcome may be communicated to an employee until payroll has confirmed the action is feasible and within budget. This is not a bureaucratic constraint. It is the difference between a stay interview that builds trust and one that destroys it.
Manager training needs to cover the boundaries, not just the questions
Most manager training for stay interviews focuses on how to ask the questions. That is the easy part. The harder part is knowing what you can and cannot commit to in the room. Managers need approved response templates for the most common topics: what to say when someone asks about a promotion that is not currently available, how to respond to a pay question without making a commitment, and how to handle a conversation that turns into a grievance. Short scenario-based training with a clear escalation matrix is more useful than a one-hour presentation on the theory of retention.
Documentation gaps block every downstream action
If the record is incomplete, none of the routing logic works. Payroll cannot validate a request with no details. HR cannot progress a role review with no context. The manager cannot be held accountable for an action that was never written down. The simplest safeguard is a required field structure that the system will not accept incomplete: if the action type, the owner, and the target date are all mandatory, a manager cannot submit a record that omits them.
What should HR and payroll teams do first?
Before you design a stay interview programme, spend half a day mapping how individual retention conversations currently work in your organisation. Find out who owns the follow-up when a manager informally raises a retention risk, where that information lands, how quickly pay-related requests reach payroll, and whether any of it is tracked or auditable. In most organisations, the inputs exist but the routing is informal, the ownership is unclear, and nothing is measurable. Fixing those three things gives you the operational foundation for a stay interview programme that produces results, rather than a layer of structured conversation on top of a process that cannot act on what it hears.