How to Automate the Weekly Team Update (2026): Five Sections, Written From Real Activity

Why the weekly update is the wrong thing to write by hand

The weekly team update is the same job every week: open six tabs, scroll the channels, remember what shipped, check the metrics, write it up. It takes thirty to sixty minutes and most of that time is gathering, not thinking. The thinking part, what to emphasize and what to flag, takes five minutes once the facts are in front of you. Automating the update means automating the gather-and-draft so you are left with only the five minutes that need a human.

Mio does this from inside Slack. It reads your actual project tracker, your channels, and your CRM, and writes a draft you edit. It does not post anything until you say so.

The five sections every weekly update needs

A weekly update that people actually read has a predictable shape. Five sections cover what a team and its leadership need to know, in the order they want to know it.

• Shipped: what landed this week. Merged PRs, closed issues, features that went live, deals that closed.
• In progress: what is moving and roughly where it stands, so no one has to ask for a status check.
• Metrics: the two or three numbers that matter for this team, with the direction of travel.
• Risks and blockers: what is stuck, what is slipping, and who is waiting on whom. This is the section leadership reads first.
• Next week: the short list of what the team is taking on, so priorities are visible before they become questions.

Resist the urge to add more. Five sections is enough to be complete and short enough to be read. The point of the update is that people finish it.

Where each section comes from

The reason this can be automated is that every section already exists as activity in a tool you use. Mio connects to those tools per user through managed OAuth, one click, no API keys, and pulls each section from the right source.

Set it up in three steps

You do not configure a pipeline. You ask for the update in plain language and tell Mio when to run it.

• Connect the sources. In Slack, connect your tracker, your code host, and your CRM to Mio with one click each through OAuth.
• Write the prompt once. Try @mio draft the weekly for #engineering: shipped, in progress, metrics, risks, next week, focus on what changed. Mio drafts it from the connected tools.
• Schedule it. Ask @mio run that weekly update every Friday at 9am and DM it to me first. It lands as a draft for you to review before anyone else sees it.

After the first run you will want to adjust the shape. Tell Mio keep risks at the top or drop the metrics section for this channel and it remembers for next time.

The editorial rules that still apply

Automating the draft does not mean automating the judgment. Mio gives you a complete, accurate draft built from real activity. You are still the editor. A few rules keep the update worth reading.

• Lead with what changed, not everything that happened. A list of every closed ticket is a log, not an update.
• Name the blocker and the owner. "Auth is behind" is noise. "Auth is behind, blocked on the SSO vendor, Dana is chasing" is signal.
• Cut the section that is empty this week rather than padding it.
• Decide what to emphasize and what to soften. That is the judgment the automation hands back to you.
• Read it before you send it. The draft is a starting point, not the final word.

What you get back

The trade is simple. Mio removes the half hour of gathering and assembling, and hands you a draft grounded in your own data. You spend five minutes adding judgment and hit send. The update goes out on time, every week, and you stop dreading Friday. That is the whole point: the busywork is handled, the calls are still yours.

FAQ