The Friday update gets written on Friday at 4:40, which is why it reads the way it does. Three things that happened today, because today is what you can remember. A number copied off a dashboard with no last-week number next to it. And "all on track" at the bottom, because the one thing that isn't on track would take a paragraph you don't have at 4:40.
The person reading it is a client, an investor or your own team, and they skim it for one thing: what does this mean for me. Did the thing I asked about move. Is anything about to land on my desk.
A reporting team in Murage does the assembling. It reads the week, puts the figures next to last week's, and hands you a draft under 300 words with what shipped, what moved, what is stuck and what you need. You read it and send it.
What it reads
You need Murage with an AI engine (Fuigo, your existing Claude or ChatGPT plan, or an API key), and either your tools connected or the week's notes pasted into a project. The project is the simplest version: one called "Weekly update", with the task list export, the numbers sheet and whatever you jotted down during the week dropped in as you go. If your task tool and your spreadsheet are in the connected-apps catalog, connect them through Flux Router or your own connected-apps key and skip the pasting.
Paste last week's update in as well, and the one before it if you have it. One good example does more than any description of the format, because the format is mostly things you'd never think to say out loud, like the client's name going in the first line and yours not going in at all. The team keeps the shape, the headings, the length and the sign-off you already use.
Every Friday at 3, draft the weekly update: what shipped, what moved, what is stuck, and what we need. Keep it under 300 words. Send nothing.
Your Chief of Staff proposes a routine for Friday at 3 and shows a Confirm card. Nothing is scheduled until you press it. The routine gets its own conversation, so every Friday's draft sits in one thread and you can scroll back to the week a client is asking about. Three bots share the work. An Analyst gathers what happened: finished, started, sat still. Numbers adds the figures and the change from last week, which is the part people skip when they write it by hand. Copy writes it short and plain, in the format your example set.
The draft is four short sections. (This one is an example; yours carries your own week.) Shipped: the three things that went out. Moved: revenue against last week, support tickets against last week. Stuck: one blocker, with a name next to it. Asks: the two things you need from whoever is reading.
The Stuck line
The blocker is the reason we'd bother with any of this. Written by hand at 4:40, the blocker gets softened or dropped because explaining it is awkward. Written by the team from the week's notes, it is just there, with the owner, and you decide whether to soften it.
Usually you shouldn't.
Friday at 3, then Friday at 3:20
Murage runs on your computer, so it needs to be open at 3 or within the 12 hours after; a late run still happens when it comes back. Read the draft, change the numbers you know better than the export does, cut what the reader doesn't need, approve. Sending waits for you. New bots start on Ask, and a message to your whole client list is yours to press.
If the draft gets the shape wrong, say what's wrong in a sentence that can be reused. "Shipped should be bullets and Moved should be a table" teaches more than "fix the format", and the bot keeps it as a lesson for next Friday. Once you have two or three good ones, /learn can write the format down as a skill. Teach a skill is on by default, and the skill only goes live after you enable it.
If the update is three lines to one person, type it. This earns its keep when the same update goes to several people who weren't in the room, or when you have stopped sending it because assembling it takes the hour you don't have on Friday. The weekly report use case has the whole job, and the Back-Office Crew in the library turns the week's operational mess into a prioritized action list with follow-ups, which feeds the same update.
Download Murage and drop last Friday's update into a project tonight. Then read what comes back at 3 on Friday.