Clarify a reply before acting
Separate what a teammate agreed to from what still needs an answer.
Clarify a reply before acting
Separate what a teammate agreed to from what still needs an answer.
Before you start: Open the correct conversation and have the original request and relevant document version available.
Steps
- Read the reply alongside the request it answers. Check the sender, message sequence and referenced version.
- Identify the kind of response. “Seen” acknowledges a message. “I can look later” describes availability. Feedback judges the material. Acceptance agrees to a particular responsibility or time.
- Write down what is clear and what remains unresolved. A short “yes” can answer one specific question, but may be ambiguous when the request contains several decisions.
- Compare feedback with the material. If someone reports a missing section that is present in the current version, check which version they read before changing the document.
- Ask one focused clarification in the same conversation. State the shared fact, the discrepancy and the question. For example: “The current agenda includes a recap. Were you reviewing the earlier version or this one?”
- Read the answer before acting. If availability or timing changes, update the plan with the people involved rather than continuing to treat the original request as accepted.
Expected result
You can describe the accepted scope and timing, the material reviewed and any remaining question. The next action follows the person’s actual response, not an assumption about what they meant.
Remember
Agreement to review a document does not automatically include editing it or carrying out the work it describes. A review of one version also does not automatically approve a later revision.
Continue learning
In this series: Work together in Chat — guide 4 of 6.
Turn what you learned into the way the team works.
Mark this lesson complete once the workflow exists in your workspace—not simply when you reach the bottom.