How long does a stay-interview action take to reach the employee?

Published November 9, 2026.

A stay interview is only as useful as the action that follows it. A manager can leave the conversation feeling that it went well while the employee waits weeks for a change that never arrives. This review sets out a bounded way to measure how long a stay-interview action takes to reach the employee. It does not estimate a national follow-through rate or claim that one delay caused one resignation. The protocol separates a status update from a completed change so the result is honest.

Question and scope

This review asks how long a stay-interview action takes to reach the employee after the concern is recorded. The unit is one concern raised in a stay interview, followed from the recorded date to the first visible action or the decision that no action will be taken. The study measures the time to a status update, the time to a completed change, and the employee's response. It does not judge whether the requested change was reasonable or whether the manager was fair.

Set the scope to one employer, one team, and one stay-interview format. Record the interview guide, the follow-up rule, and the manager's decision authority at the start. If the format or the authority changes during the window, keep the original definition for concerns already raised and analyze the later cohort separately. A new approval rule can look like faster follow-through when it is only a different gate.

Exclude concerns that were withdrawn by the employee before any action. Include concerns where the answer was no, because a clear no is still a follow-up. Test the definition on two recent interviews before collecting the full sample. Record the test result and the boundary cases.

Definitions that make the measure reproducible

Define the concern date as the day the manager recorded it in the follow-up receipt, not the day the interview was scheduled. Define a status update as a message that tells the employee what is happening and when to expect the next update. Define a completed change as the observable action the manager committed to, such as a schedule change or a new check-in. Define the employee response as the employee's recorded view of whether the change happened.

A status update is not a completed change, even when it is prompt. A completed change without a status update can still leave the employee in the dark during the wait. Report the two measures separately. Do not combine them into a single follow-up score.

Record the concern category, the requested change, the owner, and the decision rule. A scheduling concern and a pay concern have different approval paths. Add whether the employee asked for confidentiality. Privacy limits can change what can be shared and with whom.

Evidence standard and data dictionary

For each concern, capture the interview date, the recorded date, the owner, the promised date, and the decision. Add the first status update time, the completed change time, and the employee response time. Record the number of messages between the interview and the action. Keep the receipt and the messages with the record.

Record whether the concern was a single incident, a pattern, or a preference. A pattern may need a team-level change, while a preference may need a personal arrangement. Add whether the employee asked for the conversation to remain private. A second reviewer should be able to rebuild the path from the concern to the action.

Record the manager's span of control and the number of open follow-ups at the time. A manager with many open items may be slower for reasons of capacity rather than intent. Add whether the manager had a named backup. These fields help separate a process problem from a workload problem.

Sampling and collection

Draw the sample from the stay-interview log, not from a list of employees who stayed. The log should include concerns that were resolved, refused, or still open. Record the export date, the filters, and the number of concerns excluded. If the team is small, describe each concern instead of computing a rate.

Collect the receipt as it existed at the time, not after a later cleanup. If a date was edited later, record the edit and analyze the original delay separately. Do not infer a follow-up from a calendar event that has no message. Note the collection date separately from the concern date.

Record whether the employee was still employed at the end of the window. An employee who left may have a different follow-up experience than one who stayed. Report the leavers separately so their timelines do not distort the result. Do not use the stay interview as a substitute for an exit interview.

Analysis and reporting

Report the number of concerns, the median time to a status update, and the median time to a completed change. Show the counts by concern category, owner, and decision. Present the share that received a status update within the promised time. Use the same denominator for every rate and show concerns with incomplete records.

Inspect the slowest concerns and describe which stage dominated without naming the employee. A wait before the owner decision may point to an approval problem, while a wait after the decision may point to a scheduling problem. Compare the result with the manager's open follow-up count. Report the refused concerns separately so their timelines do not distort the completed cases.

A useful additional view is the share of employees who said the change was visible. A manager can record a change as complete while the employee sees no difference. Show the manager completion and the employee confirmation side by side. That comparison is the most useful test of follow-through.

Limits of the evidence

The record cannot show whether the employee would have stayed without the change. It can show only what was raised, what was promised, and what happened. A fast follow-up is not proof of good management, and a slow one is not proof of neglect. The protocol also cannot capture a change that was made informally and never recorded.

A small team may have too few concerns to support a stable time. Describe the cases and the specific delays instead of ranking managers. If one manager owns most of the concerns, report that concentration. A general rate would hide a single workload problem.

An employee may not report a concern because of past follow-through failures. The sample is therefore biased toward people who still trust the process. Record the participation and describe the limitation. Do not present the result as the full picture of employee concerns.

Give the result to the manager and the HR owner and ask for one observable change. The change might be a named backup, a decision deadline, a status template, or a monthly follow-up review. Record the owner, the effective date, and the measure that will show whether the change worked. Repeat the protocol with the same definitions for the next cohort.

If status updates improve but completed changes do not, the bottleneck may be approval or capacity. If completed changes improve but employee confirmation does not, the change may not be visible enough. Report the stages together before declaring a success. Close the review when the owner accepts the finding and the next cohort is scheduled.

Ask the last five employees whether they knew what happened after the interview. A clear answer is a direct test of the loop. Fix the step where the message stopped. The next measurement should show whether the same silence recurred.

Record whether the employee was told the decision rule before the interview ended. A person who understands the constraint is less likely to read a delay as indifference. Add the rule and the promised update date to the receipt. That small step makes the later conversation easier for both sides.

Ask the manager which follow-up was easiest to close and which one required another owner. The answer often reveals an approval path that is not written down. Record the path and the owner. A clear path is more useful than a reminder to follow up faster.

Data Sources and Methodology

The review uses public employment guidance to bound the definitions and to keep the recommended record fields within common legal and administrative practice. The sources below are used as context, not as a claim that any one employer follows them in the same way. Each measure in this protocol is defined from the employer's own records, then compared with these public references where the reference is relevant. The citations are listed with the specific topic they support so a reader can check the boundary without searching the whole site.

The method is deliberately descriptive. It does not pool employers or estimate a national rate. A reader who repeats the protocol should use the same definitions, the same observation window, and the same sampling rule, then report the counts beside the shares. Keep that report with the study record so a later reviewer can repeat the comparison.

Sources

Society for Human Resource Management, stay interview resources - accessed November 9, 2026.
U.S. Bureau of Labor Statistics, job openings and labor turnover - accessed November 9, 2026.
U.S. Department of Labor, employment law guidance - accessed November 9, 2026.
U.S. Equal Employment Opportunity Commission, recordkeeping - accessed November 9, 2026.

Question and scope

Definitions that make the measure reproducible

Evidence standard and data dictionary

Sampling and collection

Analysis and reporting

Limits of the evidence

Data Sources and Methodology

Sources

Related Research