Published October 27, 2026.
Map who covers which conversations
List every recurring one-on-one by employee, manager, cadence, and topic. Mark the ones that must continue during an absence: new hires in their first 90 days, employees on a performance plan, anyone with an open accommodation or scheduling issue, and roles with a single point of failure.
Assign a named coverage person for each. The coverage person should be senior enough to answer routine questions but not so senior that the meeting becomes a skip-level review. Tell the employee in advance who will meet them and why the change is temporary.
Write a coverage note per team
The departing manager leaves a one-page note: current priorities, open commitments made to each employee, known friction, pending decisions, and the boundary of what the coverage person may approve. Update it before the absence, not on the first morning.
Keep the note factual and free of performance speculation. The coverage person needs to know what was promised and what is unresolved, not who is suspected of planning to leave. Store it where the coverage person and the returning manager can both reach it.
Use a short interim agenda
A 15-minute interim meeting needs only four questions: what is blocking your work, what did you expect to hear from the manager, what has changed since the last conversation, and what should I pass along. The coverage person records answers and routes decisions rather than improvising them.
Do not turn the interim meeting into a status report on every project. The purpose is continuity of the relationship and early detection of unresolved friction. Project status already has another forum; losing the human check-in is the risk this control addresses.
Escalate anything that crosses a boundary
The coverage note should list decisions that must wait: pay changes, formal performance action, schedule exceptions, and commitments about role changes. When an employee raises one, the coverage person acknowledges the question, records it, and gives a date when the responsible owner will respond.
An escalation packet includes the employee's question in their own words, the relevant dates, what has already been tried, and the decision required. Send it to the accountable owner the same day. Silence is not a holding answer, and a vague promise damages trust more than a clear delay.
Do not batch six weeks into one meeting
A common failure is to skip all interim conversations and schedule a long catch-up when the manager returns. The catch-up becomes a project review, and the small signals that would have surfaced in week two are already stale.
Keep the cadence even when the content is thin. A ten-minute call that ends with nothing to escalate is still evidence that someone is paying attention. It also gives the returning manager a record of what changed during the absence.
Return ownership with a summary
On return, the manager reads the coverage notes and meets the employee within the first week. The meeting should confirm what was decided, what remains open, and which commitments from before the absence still stand. Correct any promise the coverage person could not make.
Record the return handoff in the same system as the regular one-on-one. A short summary is enough: decisions confirmed, open items, and the next date. This closes the loop and prevents the employee from having to repeat their concerns to a third person.
Audit skipped meetings
Track scheduled versus completed one-on-ones by team, not by individual manager ranking. A team with repeated cancellations is a coverage problem even if the manager has a good reason. Review the pattern at the operations meeting and assign a backup before the next absence.
Use completion data alongside early-tenure exit reasons. If new hires in a team with skipped check-ins leave more often, the finding is a prompt for a closer look, not proof that the meeting caused the exit. Keep the interpretation modest and test the next cycle.