Make the purpose
easy to recognize.
A writing sequence for a message, decision note, or handoff. Adapt it to the actual work and the team’s existing arrangements.
Name the function
Decide whether you are sharing information, asking a question, proposing a change, or recording a decision. State that function near the beginning.
A message can contain several functions, but give each its own recognizable place. Do not let a request disappear inside background material.
Attach the necessary context
Include the source, earlier decision, or short explanation needed to understand the topic. Keep the reference specific enough to find again.
Separate the source from your interpretation. A proposed next step should not look as though it was already contained in the material you are citing.
Keep uncertainty visible
Identify what is known, what is proposed, and what still needs confirmation. This makes disagreement easier to direct toward the actual open point.
If the team changes the question, update the note so it describes the current discussion rather than an earlier plan that no longer applies.
Make the next responsibility explicit
For a handoff, describe what is complete and what is being passed on. Include the material the next person needs rather than forwarding a thread without explanation.
Use the team’s real decision and responsibility arrangements. This resource does not assign authority or prescribe who may approve a change.
Read for a later return
Imagine finding the message after the immediate conversation has faded. Check whether the purpose, source, status, and next step remain understandable.
Keep a lasting decision where the team expects to find it. A useful conversation and a durable record can be connected without being treated as the same thing.