Published November 8, 2026.
A weekly retention pulse is a short, repeatable conversation and a small set of signals, not an annual survey. It gives a manager a chance to hear a problem while it is still fixable. The pulse should be light enough to survive a busy week and specific enough to produce an action. It works best when the team knows what is recorded and what is not.
Choose a few signals that change
Pick signals that can move week to week: unplanned absence, a drop in completed work, a missed one-on-one, a sudden change in communication, and a request for a schedule change. Do not use a single engagement score as the pulse. A score is too slow and too abstract to guide a Monday conversation. Record the signal, the date, and the source. Keep the note factual and short. A manager should be able to see the pattern without reading a file of impressions. If a signal is sensitive, store it in the approved system rather than a personal notebook. Review the list each quarter and remove any signal that has never led to a useful conversation. A pulse that collects data for its own sake becomes a reporting burden. The point is to notice a change and ask about it.
Ask three questions in the one-on-one
Use the same three questions each week: what is going well, what is getting in the way, and what would make next week better. The questions are simple enough to answer honestly and specific enough to produce a next step. Do not turn the conversation into a performance review. The pulse is a check, not a verdict.
Listen for a change from the previous week. A person who usually says the work is fine and suddenly says it is overwhelming may be signalling a workload problem. A person who stops mentioning a project may have lost confidence in it. Record the change and follow up in the next conversation.
End the conversation with one action and an owner. The action may belong to the manager, the employee, or both. Write it down and check it next week. A pulse without a follow-up teaches the team that speaking up changes nothing.
Separate workload from fit
A retention risk is not always a bad fit. A strong employee can be exhausted by a temporary load, a broken tool, or an unclear priority. Ask which one is true before assuming the person wants to leave. A transfer, a schedule change, or a short break may solve a problem that a new hire would not.
Use the pulse to spot a workload spike early. If one person is covering two queues for a third week, the risk is in the schedule, not the person's commitment. The manager should fix the coverage before the next pulse. A conversation that only asks how the employee feels without changing the load becomes hollow.
Record the difference between a temporary and a persistent issue. A persistent problem needs a plan with a date. A temporary problem needs a check-in and an end point. The distinction helps the manager choose the right response.
Make the pulse safe to answer honestly
Explain what is recorded and who can see it before the first pulse. A manager who promises confidentiality but writes notes in a shared file breaks trust. Keep the notes factual and limited to what is needed for the action. If the employee asks not to record something, respect that unless there is a safety or legal duty to document it.
Do not use the pulse as evidence in a performance case without telling the employee. The conversation is meant to surface problems early, and using it later as a surprise changes the meaning. If a performance issue emerges, move to the formal process and say so. The pulse should not become a trap. Ask the team once a quarter whether the pulse feels useful. If people say it is a checkbox, change the questions or the cadence. A tool that people do not trust will produce safe answers and no useful signal.
Review the team pattern monthly
Once a month, look at the signals across the team rather than one person at a time. A cluster of schedule requests may point to a shift design problem. A cluster of missed one-on-ones may point to a manager who is overloaded. The pattern is often more actionable than an individual case. Share the pattern with the team in a short note and name the change the manager will make. Do not share individual notes. The team should see that the pulse leads to something visible, such as a changed meeting time or a new backup for a queue. Choose one change and measure it for a month. If the change does not help, say so and try another. A retention pulse is a learning loop, not a compliance exercise.
Close the loop when someone leaves
When someone leaves, review the last few pulse notes with the person's permission and the HR process. Look for a signal that was missed or a concern that was raised and not addressed. Do not use the review to blame the manager or the employee. Use it to improve the questions and the response.
Ask the departing employee what would have made the job easier. Record the answer in the exit record, not in the pulse file. Share the themes with the team after the person has left. A team that hears only the exit interview summary may miss the practical fix. Update the pulse questions if the exit feedback points to a gap. A question about workload may need a follow-up about tools or decision authority. The pulse should evolve with the team, not stay frozen at its first version.