Published November 9, 2026.
A stay interview can build trust or damage it, depending on what happens after the conversation. When an employee raises a concern and hears nothing, the interview becomes evidence that speaking up is pointless. A short follow-up receipt closes that loop with a named owner, a promised change, and a review date. The receipt does not need to promise that every request will be granted. It needs to show that the concern was heard, recorded, and answered.
Write the concern in the employee's words
Start the receipt with a short summary of the concern using the employee's own language where possible. A paraphrase that changes the meaning can make the employee feel misunderstood all over again. Read the summary back during the interview and ask whether it is accurate. Record any correction before the employee leaves the room. The written concern is the reference point for every later update.
Separate a single incident from a pattern and a preference from a requirement. An employee who asks for a different shift may be describing a temporary conflict or a permanent need. The receipt should say which one the employee meant and what was not yet known. Do not label a concern as resolved just because a meeting was held. The label should describe the current state, not the effort spent.
Name the owner and the decision rule
Every follow-up item needs one owner, even when several people will contribute. The owner is the person who will come back to the employee with an answer or a status. Write the owner's name and the date the employee should expect an update. A team name or an inbox is not an owner. If the owner changes, update the receipt and tell the employee.
State the decision rule that will be used, such as a budget limit, a scheduling constraint, or a policy requirement. An employee who understands the rule can judge whether the answer is fair. If the manager does not know the rule, the first follow-up is to find it rather than to guess. Record the source of the rule and the person who confirmed it. A decision without a stated rule feels arbitrary even when it is correct.
Choose a change that can be observed
Translate the concern into one change the employee can see, such as a fixed schedule, a clearer handoff, or a weekly check-in. Avoid commitments that cannot be observed, such as feeling more supported or communicating better. Write what will be different, when it will start, and how the employee will know it happened. If the change is experimental, say how long it will run and when it will be reviewed. A small observable change is better than a broad promise.
When the answer is no, write the reason and the alternative that was offered. An employee may accept a no when the reason is clear and the alternative is real. Do not use a policy as a reason unless the policy actually applies. Record the employee's response to the alternative. A refusal can still be a respectful conversation when it is documented and explained.
Set a review date and keep it
Put the review date in both calendars before the interview ends. A date that exists only in the manager's memory will move when the week gets busy. The review should check whether the change happened, not whether the employee is happier. Ask what is working and what still needs adjustment. Record the answer in the same receipt.
If the change has not started by the review date, say so and give a new date with a reason. Do not quietly extend the deadline or wait for the employee to ask. A missed follow-up is worse than a slow one because it repeats the original silence. Escalate to the manager's own supervisor if the owner cannot meet the date. The receipt should show the new date and the escalation.
Protect privacy and trust
Keep the receipt in the approved employee record and limit access to the people who need it. Do not paste the concern into a public channel or a team dashboard. If the employee asks for confidentiality, explain what can and cannot be kept private. Record the limit at the time of the request rather than revealing it later. A promise of confidentiality that cannot be kept destroys trust when it breaks.
Do not use the stay interview as a performance warning or a surprise evaluation. Mixing the two makes future conversations feel unsafe. If a performance issue emerges, address it through the proper process and say so clearly. Keep the stay-interview notes focused on retention and work conditions. The employee should know which conversation is which.
Review the pattern across the team
At the end of the quarter, group the concerns by theme without naming individuals. A repeated theme in one team may point to a workload, scheduling, or management problem. Choose one team-level change and name the owner. Do not publish a theme that could identify a single employee in a small team. Use the pattern to improve the process, not to expose the person.
Ask the employees whether the follow-up improved the situation. A change that the manager believes is working may not be visible to the team. Record the answer and adjust the change if needed. Keep the receipt process short enough that managers will actually use it. The goal is a loop that closes, not a form that gets filed.