A weekly handoff arrives after the agreed time twice. Before the next one-to-one, a manager writes, “You are not taking the handoff seriously.” The note sounds direct, but it combines an observable event with an explanation the manager has not checked.
A more useful starting point is to describe the event and prepare a question about it. In the fictional example below, a manager and colleague discuss a shared project update. The aim is to prepare an accurate conversation record: what happened, what remains unclear and what the people involved actually agree to do next.
Name the work event you want to discuss
Start with the part of the work that needs discussion. In this example, the shared project update was due at noon on two Fridays. The record shows that it arrived at 2:10 p.m. one week and 1:40 p.m. the next. Check those details against the source before using them in a conversation.
Also check the agreement itself. Was noon an agreed deadline, a suggestion in an old message or simply the time the manager expected? Those are different circumstances. If the expectation was never confirmed, the conversation needs to establish it rather than assume it was understood.
Keep the opening note specific: “I want to discuss the timing of the last two project updates.” That gives the colleague a recognizable subject. A label such as “unreliable” does not explain which event needs attention or what information the manager is seeking.
Keep the source and your interpretation in separate notes
A preparation note can have two short columns: what the record shows and what you need to understand. Put the agreed deadline and recorded arrival times in the first. Put questions about the handoff process in the second.
If another colleague reports an effect on their work, preserve that attribution. “The coordinator said the review started later” is different from an independently checked account of when the review began. Ask for clarification where it matters; do not turn a report into a measured impact by shortening the sentence.
Leave interpretations visibly tentative. The manager might wonder whether the update depends on information arriving from another team. That is a question to explore, not an explanation to insert into the record. The preparation note should make it possible to tell which statements came from a source and which originated as the manager's assumptions.
Ask for context without supplying an explanation
An open question can be straightforward: “Walk me through how you prepare the Friday update.” Listen for the sequence before asking about the two dates. The colleague may describe steps, dependencies or instructions that were absent from the manager's view.
Follow the account with a question about the missing detail. If the colleague mentions waiting for figures, ask when those figures were available on the relevant days. Avoid supplying the answer through a question such as, “Was the other team late again?” That introduces a conclusion the speaker has not yet given.
Record the explanation as the colleague's account. If a source needs checking afterward, identify that as an open step. Keep the discussion focused on the work rather than inviting guesses about motives or personal circumstances.
Distinguish a proposed next step from an agreement
The manager may propose an earlier check on missing information. Write it as a proposal until both people have discussed it. A suggestion to check at eleven is not yet an agreement that the colleague will always deliver at noon.
Clarify what the proposed action involves. Who checks the inputs? Where should a missing item be flagged? Which part of the update can proceed without it? Use the actual arrangements discussed, rather than filling the note with a tidy process that nobody agreed to follow.
Before moving on, restate the proposed next step and invite a correction. If a dependency requires another person's decision, name that dependency as unresolved. The note can accurately record a partial agreement. It does not need an invented deadline or commitment to appear complete, and a routine discussion should not silently become a performance or disciplinary decision.
Keep an accurate follow-up note
Write the follow-up through the organization's usual process. Include the work issue discussed, the relevant explanation, the action actually agreed and any source or decision still outstanding. Keep the record proportionate to the discussion and available only through the appropriate internal route.
Read it once from the colleague's perspective. Does it describe their account faithfully? Does it distinguish what they offered to do from what the manager suggested? Correct an inaccurate summary before it becomes the reference for the next meeting.
At the follow-up, compare the new information with the recorded agreement. Do not treat the existence of a note as proof that the action happened. The fictional preparation method here is an original editorial example, not a quotation from a product. Its purpose is practical: give the conversation a clear subject, leave room for context and retain an accurate account of the next step.
Review the Manager Conversation Toolkit and its listed format and scope.