Make a weekly team update worth reading

A weekly team update has a different job from a client progress report. Colleagues need to coordinate across projects: avoid booking the same specialist twice, reuse work that already exists and notice when a changed priority affects their own plans. Build the update around those connections rather than asking everyone to list their achievements.

Show where next week's work intersects

Identify handoffs between people or teams. A designer waiting for approved wording and an editor waiting for a product answer may be part of the same dependency, even if their tasks sit in different project lists. Describe that connection so the group can resolve the sequence before both people lose a day.

Include availability only where it affects coordination. A planned absence, a training day or a period reserved for a deadline can change when colleagues should request a review. State the coverage arrangement and relevant working window; do not disclose personal reasons for absence or turn the update into a public attendance record.

Imagine a small team preparing both a customer newsletter and a partner presentation. Both require the same product expert, who is available only on Tuesday. The update can bring the two requests together and propose one coordinated review. Two separate reports saying ‘waiting for product input’ would not reveal the opportunity to combine the work. This is an illustrative scenario, not a report of a client project.

Broadcast changes that other projects may miss

Highlight decisions with consequences beyond the meeting in which they were made. A revised service name, a postponed launch or a newly approved description may affect several drafts. Link to the maintained decision and explain who should check their work. Do not assume that everyone reads every project's notes.

Make priority changes explicit. If an urgent release now takes precedence over a planned article, name the work being deferred as well as the new focus. Otherwise colleagues may continue treating both as equally committed. An internal update is a place to expose that conflict, not quietly ask everyone to absorb it.

Share reusable work with a clear boundary. A newly checked explanation, an approved diagram or a useful interview may save another colleague from starting again. Say what it covers and whether it can be reused as it stands. A draft intended for one audience should not spread through the organisation as approved universal wording.

Remove information that belongs elsewhere

Keep individual task detail in the project records and private performance feedback in the appropriate conversation. The team update is neither a timesheet nor a leaderboard. A quiet week may require only a few coordination notes; a week with several interlocking deadlines may need a fuller explanation. Let the relationships between the work determine the length.

Review the update by asking what it helped someone do differently. Did a colleague avoid duplicating research, arrange cover in time or notice a conflicting demand before accepting it? Those outcomes are more useful than counting acknowledgements. If the message changes no coordination decisions, shorten it or change what it contains.