Have a retention conversation when there is something useful to discuss or review, not because you think you have detected a future resignation. Start from a request, a change in work or an outstanding commitment. Explain the reason for the meeting, choose someone able to help, and leave with a realistic next step that the employee can correct or question.
Choose a moment you can explain
You do not need an alert to ask how work is going. A role change, the end of onboarding or a promised development review can provide a clear reason for a conversation. Make these opportunities available consistently rather than selecting only people someone has labelled as likely to leave.
The CIPD's retention factsheet connects understanding why people leave with organisational responses such as fair treatment, flexibility and wellbeing. A conversation is one input to that work. It cannot establish a person's intentions or compensate for a change the employer repeatedly fails to make.
Use this proposed timing guide:
| Starting point | Useful response | Assumption to avoid |
|---|---|---|
| An employee asks for a discussion | Ask what support and conversation route would help | They are threatening to leave |
| An agreed action reaches its review date | Bring the original commitment and what actually happened | Silence means the issue is resolved |
| A role, workload or team arrangement changes | Explain the change and invite questions about its effects | Everyone experiences the change in the same way |
| Several people describe a work obstacle | Review the team condition and invite context through an appropriate channel | Each contributor has the same intention |
| Someone shares a rumour or an unexplained risk label | Check whether there is a legitimate, relevant work concern to address | A label is evidence about the employee |
Do not wait for a complete analytical record before responding to someone who asks for help. Equally, do not disguise a speculative investigation as a friendly check-in. A specific observation can be discussed honestly without claiming to know what it means.
Respond to work concerns without a “quiet quitting” label
Working agreed hours, declining optional projects or speaking less in a meeting does not establish disengagement or an intention to resign. A change may have several explanations, including workload, role expectations or a circumstance the employee does not need to disclose. Start with the relevant work observation and an open question rather than a claim about motivation.
For example: “We have two competing priorities for next week. Can we review what is realistic within your available time?” This proposed opening addresses the work without treating extra unpaid effort as the standard. If an agreed responsibility is not being met, clarify that expectation and the support available through the appropriate process. A retention conversation should not disguise a performance judgement or require someone to reveal private plans.
Pick the owner before writing the invitation
A useful conversation needs both a suitable relationship and a route to action. The person who knows the employee best may not have authority to resolve the concern. They may also be part of the concern.
Distinguish three roles:
- Conversation partner: someone the employee can reasonably speak with about this subject.
- Decision owner: the person who can approve or explain the requested change.
- Follow-up owner: the person responsible for bringing back an answer, including when the decision is delayed or negative.
One person may hold all three roles for a local scheduling clarification. A cross-team development opportunity may need more than one. Name the dependency rather than promising an outcome on someone else's behalf.
A retention discussion must not become a compulsory first step before a complaint or specialist route. Explain the relevant options and confidentiality boundaries. If the subject involves the manager, offer an appropriate alternative instead of automatically routing the account back to them.
Reopen the commitment, not a judgement about the person
Before the meeting, prepare a short record of what was agreed and what is known now. Separate the request, the promise and the interpretation. “We agreed to review project opportunities after onboarding” is different from “They expected an immediate promotion.”
A transparent opening might be: “We said we would revisit your development time after the launch. That review did not happen. I would like to understand what you need now and explain which options I can actually offer.”
This is a suggested script, not a customer quotation. It gives the employee something concrete to correct. They may say the original request no longer matters or identify a different issue. Do not make them repeat an old problem solely to complete your process.
For a broader question bank, use the stay interview guide. This page focuses on timing, ownership and recovery of an outstanding commitment.
Use a commitment review sheet
Acas guidance on problems raised by workers recommends taking concerns seriously, keeping a record, agreeing specific next steps and checking whether the problem is resolved. It also describes formal routes when informal discussion is not suitable or does not resolve the issue. Its procedural context is the UK; organisations elsewhere should use their applicable processes.
The following proposed worksheet helps a manager separate delivery from reassurance:
| Field | What to write |
|---|---|
| Original request | The employee's description, checked for accuracy |
| Previous commitment | What was actually promised, by whom and under which conditions |
| Current position | Completed, partly delivered, delayed, declined or no longer relevant |
| Remaining obstacle | The specific dependency or decision still open |
| Available options | What can happen now and what needs approval |
| Next response | Who will bring back which information, and when |
| Evidence of delivery | What both parties can check at the next review |
| Employee's view | Whether the action addressed the concern, including disagreement |
Keep access and detail proportionate to the purpose. A person who must approve training time may need the request and operational constraint, not every personal detail discussed. Explain what will be recorded and shared; do not promise absolute confidentiality that the process cannot provide.
A fictional example: the development time that disappeared
A customer-support specialist was offered time to shadow an implementation project after a busy launch. The launch ended, but urgent tickets continued to take priority. The manager has not returned with a decision.
At their review, the specialist explains that the request was about testing a different kind of work, not securing a promotion. The manager can release some time but cannot promise a place on another team's project. The implementation lead owns that decision.
They record two separate commitments: the manager will agree cover for a proposed session, and the implementation lead will confirm whether a suitable session is available. If no place is available, the manager will return with that answer and discuss another way to explore the work. They do not record “promotion promised” or “employee retained.”
At the next review, they check whether the session happened, whether it was relevant and what the specialist wants to do next. A completed session may still fail to address the concern. That finding changes the next action; it is not a reason to mark the person ungrateful or uncommitted.
Review the response separately from retention
Track whether the organisation did what it said it would do. Then ask whether the action helped with the stated work problem. These are different questions from whether the employee eventually stays.
For a programme review, useful fields include missed review dates, unresolved dependencies and concerns reopened after an action was marked complete. Interpret those records alongside changes in workforce composition and wider conditions. Do not claim a conversation prevented a resignation simply because someone remained employed afterward.
If the issue affects several teams, use the retention strategy guide to decide which organisational response needs testing. Avoid copying personal conversation notes into a broad team report.
Where preparation support fits
Lontra can support preparation for a defined employee conversation and give the manager a brief to review. Managers do not receive raw conversations. The tool does not decide who will leave, approve the requested change or replace an appropriate HR process. Explore how conversation preparation works.
The trial includes one campaign with up to 30 invitations for 60 days, with no card required. Start with a clearly explained work question and an owner who can respond. Explore a fictional team diagnostic to see how context can lead to a human-owned next step.
