Identify the reader and their question
Consider who needs the information. A team working directly on the task requires different detail from someone who only has to approve a decision. Write towards the next shared decision. If several groups are involved, a short common overview with linked detail may be enough instead of distributing the same long report everywhere.
Start with relevant changes since the previous update. Name an achieved result or changed condition rather than merely counting conversations. Five discussions tell the reader less than the fact that a delivery date is now confirmed or a technical question remains unresolved. Activity matters when it explains the state of the work.
Describe obstacles with the help required
For a problem, explain its actual effect and the next possible action. Delayed is too vague if nobody can tell which commitment is affected. Identify the missing decision or information and who needs to provide it. Separate established facts from assumptions so that a possibility is not passed on as a confirmed project position.
If no assistance is needed, the update does not have to invent a question. The next expected milestone and its prerequisite may be sufficient. Conversely, a necessary decision should not be hidden at the end of a long description. Make it visible where the reader can recognise and respond to it without searching through supporting detail.
Choose a dependable rhythm
Agree when routine updates are produced and which changes trigger an additional message. A critical development should not wait for the next weekly summary if others need to act. An unchanged position does not need new wording every day. Match the rhythm to actual developments instead of making reporting frequency an end in itself.
Keep the current position in a known location and link the supporting material. Avoid several independently maintained summaries with different dates. After a few rounds, check which information people use and which they consistently overlook. Remove ineffective repetition and retain the details that lead to coordinated action rather than merely demonstrating that a report has been written.
