A team shares several updates, yet a blocked task still goes unnoticed. The messages describe effort without showing what changed or what decision is needed. An asynchronous update is information colleagues can read without being present at the same time. Keep it short, but give it a useful structure. The reader should understand the result, the next step and whether you need somebody to act.
Start with a visible change
Describe what has been completed since the previous update. For example, the draft instructions are ready for review and the example file is attached. That is more useful than saying that documentation is progressing. Link to the appropriate working material so the reader can check the result.
Separate a completed item from a partial one. If a section remains unfinished, say which part is missing. A status label should not make uncertain work appear ready to use.
Name the next useful step
Write the next action and its owner. Avoid listing everything that may happen later. A practical update could say that the reviewer will check two disputed points before the document is shared. That explains both the dependency and the direction of the work.
Use an agreed date where one exists. If timing is uncertain, explain what must be known before it can be confirmed. Do not invent a deadline just to make the update look complete.
Make a blocker answerable
Describe the missing decision or information and who can help. A request such as please confirm which product specification is approved gives a colleague something concrete to answer. A general phrase like waiting for feedback does not identify the problem.
Include enough context to avoid unnecessary back-and-forth. State which options are under consideration and where the evidence is stored. Do not place sensitive information in a channel that cannot appropriately handle it.
Agree how updates are read
Choose a shared location and a predictable review routine. Tell people how urgent matters should be raised separately; a routine update is not an emergency response method. Try the format on one piece of work and ask whether the recipient could act without another meeting. template.fyi offers editable formats as starting points for real tasks. Adapt a structure to your team, so the update supports follow-through rather than becoming another reporting obligation.