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

Stop writing the weekly update from memory on a Friday afternoon. Generate it from what actually happened.

Key Takeaways

• The weekly update is one of the highest-leverage documents in a company and one of the most painful to produce. Done well it keeps stakeholders aligned without a meeting; skipped, it gets replaced by status pings and surprise escalations.
• Most updates fail for one reason: they are written from memory, at the end of a long week, by someone who would rather be doing anything else.
• Every good weekly update answers the same five questions: what shipped, what is in progress, what moved, blockers, and upcoming priorities.
• The information for all five already exists in your project tracker, channels, deploy logs, and CRM. Writing the update is 30 to 60 minutes of pure retrieval, every week, per team.
• An AI coworker does the retrieval and assembly. You keep the editing. The update gets grounded in actual activity instead of Friday-afternoon recollection.

The rule

Every good weekly update answers five questions. What shipped, what is in progress, what moved, what is blocked, and what is next. Strip away the formatting debates and that is the entire document.

If your update covers those five things in under two minutes of reading time, it is doing its job. The hard part was never knowing the structure. It was assembling the content without it taking an hour.

Prerequisites. Connect the systems the update is built from: your project tracker (Linear) for shipped and in-progress work, the team Slack channels for decisions and context, deploy logs for what went out, and your CRM (HubSpot) if the update covers revenue. The update is only as accurate as the sources the AI coworker can read.

Step 1: Define the five sections

Lock the structure before automating it. Every good weekly update answers the same five questions.

1. What shipped. Completed work, with links to the source. Not "made progress on X", things that are done.
2. What is in progress. Active work and its current state, so readers know what to expect next week.
3. What moved. Items carried over from last week, with an honest note on why. This is the section most updates omit and the one leaders read most carefully.
4. Blockers. Anything stuck, with enough context that a stakeholder reading it can actually act.
5. Upcoming priorities. What the team is focused on next.

What good looks like: a reader two levels removed understands the team's week in under two minutes and knows what, if anything, needs them.

What goes wrong if you skip this: the AI returns a log of everything that happened. Without the five-section frame, you get activity, not an update, and nobody reads it twice.

Step 2: Generate the draft from real activity

The information for all five sections lives in your tools. Ask the AI coworker to assemble it.

@Mio draft the weekly update for #engineering. Read the channel
history, cross-reference closed and shipped issues in Linear and
recent deploys, check what is still open, and return a structured
digest with the five sections: what shipped, in progress, what
moved, blockers, and upcoming priorities. Link back to sources.

Mio reads the channel history, cross-references what closed and shipped in your connected tools, checks what is still open, and returns a structured digest covering all five sections, with links back to the source.

What good looks like: the draft is accurate enough that editing it takes under two minutes.

What goes wrong if you skip this: you keep writing from memory, which is a lossy source. The update reflects what the writer happened to notice, not what happened.

Try Mio free at app.mio.xyz and draft one team's update from real activity.

Step 3: Edit, then post in public

Automation handles retrieval. Judgment is still yours. Review the draft, cut what does not matter, and post it where people will see it.

@Mio post the edited #engineering weekly update in
#company-updates and DM me the draft first for approval.

What good looks like: the update lands in a shared channel, gets read, and quietly removes a status meeting from the calendar.

What goes wrong if you skip this: the draft posts unreviewed, or lands in an email thread where it gets archived unread.

Step 4: Put it on a schedule

The point of automating the assembly is that the update stops depending on anyone remembering to write it.

@Mio every Friday at 3pm, draft the weekly update for #engineering
from Linear, recent deploys, and the channel history, in the five
sections with source links, and DM it to me for review before I
post it.

What good looks like: the draft is in your DMs every Friday, and the only weekly work left is the two-minute edit.

What goes wrong if you skip this: on the busy weeks, the week that most needed an update, it gets skipped, and stakeholders fill the gap with pings.

The default works for most. Variations by team

The five-section frame holds across teams; the sources change.

• Sales-first teams swap Linear for HubSpot deal stages: what closed, what moved, what slipped, what is at risk, what is in focus.
• Support-first teams pull from the ticket queue: what was resolved, recurring issues, escalations, and trends.
• Cross-functional updates combine sources: shipped work from Linear, revenue from HubSpot, and decisions from the leadership channel.

Try Mio free at app.mio.xyz.

A few editorial rules that still apply

Automation handles the retrieval. These stay your job.

• Cut ruthlessly. A draft that includes everything is a log, not an update. Keep what changes a reader's decisions.
• Keep the "what moved" section honest. The fastest way to lose trust in an update is for slipped items to silently disappear.
• Post it in public. Updates in a shared channel build ambient awareness. Updates in email threads get archived unread.

Where teams get this wrong

• Automating a log. No five-section frame, no editing, and the update becomes noise people learn to ignore.
• Letting slipped items vanish. If "what moved" quietly drops, the update reads great and means nothing. Keep it honest.
• Burying it in email. A weekly update only builds alignment if people see it. Post in the channel.

What to automate next

Once a team's weekly writes itself, roll the same loop outward. Automate the company-wide digest by combining each team's update, and automate the morning brief so the day starts on the same grounded picture. Both run on the gather-summarize-deliver loop the weekly update already uses.

FAQ

Can AI write my weekly team update? Yes. An AI coworker that reads your project tracker, channels, deploy logs, and CRM can draft a structured update covering shipped, in progress, moved, blockers, and priorities, with source links. You edit and post. Mio does this in Slack.

What is the best tool to automate weekly updates? Look for one that reads across your real tools rather than asking you to paste in updates, returns the five-section structure, and runs on a schedule. Mio runs in Slack, connects to 3,000+ tools, and is free to start.

How long does an automated weekly update take? The draft generates in seconds. Editing it takes about two minutes, versus the 30 to 60 minutes of manual retrieval it replaces.

Should the update be written from memory or from tools? From tools. Memory is lossy and reflects only what the writer noticed. Generating from the actual record makes the update complete and trustworthy.

Why this works now

The five sections are not new and neither is the value of a good weekly update. What changed is that an AI coworker can now read across your tools, reconstruct the week from the actual record, and run on a schedule, which removes the 30 to 60 minutes of retrieval that made the update get skipped. The structure was always free. Now the assembly is too.

Mio is free to start. A Slack workspace admin can install it in about 30 seconds from app.mio.xyz. Point it at one team's channel and replace one weekly writing session. The full workflow is described on our AI weekly recap page.