Most weekly briefs are assembled by hand from chat threads, tickets and spreadsheets, and are out of date by the time they are sent. The work is mostly collecting and summarizing, which can be drafted automatically, while deciding what matters stays with the manager. These four steps fix the format, connect the sources and keep a person as the sender.

Step 1 — Agree the format

Goal: Decide what leadership actually needs each week.

  1. Ask the readers what they use the brief for and what they skip.
  2. Fix a short structure: progress, risks, blockers and decisions needed.
  3. Group by project or team, with a named owner for each.
  4. Keep it to what fits on one screen.

You finish with: A one-screen brief template with owners per section.

Step 2 — Connect approved sources

Goal: Let the draft read from the tools where work happens.

  1. List the sources allowed: project boards, ticket systems and shared trackers.
  2. Give read-only access to those sources only.
  3. Exclude private channels and personal messages.
  4. Agree how owners mark items as blocked or needing a decision.

You finish with: Read-only connections to an approved list of sources.

Step 3 — Draft and flag

Goal: Produce a useful first draft on schedule.

  1. Collect changes since the last brief from each source.
  2. Summarize progress, risks and blockers per project, with links back to the source.
  3. Pull out items that need a decision, with the owner named.
  4. Deliver the draft to the manager ahead of the send time.

You finish with: A linked draft brief with decisions flagged.

Step 4 — Review, send and improve

Goal: Keep a person accountable and the brief useful.

  1. The manager edits and sends the brief; it is never sent automatically.
  2. Track preparation time against the starting point.
  3. Ask readers each month what to add or drop.
  4. Fix sources that keep producing missing or stale updates.

You finish with: A brief sent by a person each week, with less time spent preparing it.

Common pitfalls

  • Reading from private channels or personal messages.
  • Sending the brief automatically without a person reviewing it.
  • A brief so long that decisions get lost.
  • Owners not updating their tools, so the draft repeats stale status.

See it as a workflow

Operations

The weekly status brief

Gather updates from approved tools, draft the brief, and flag the items that need a decision.

See the workflow

More guides like this

Related answers

Read as Markdown Connect your tools