Ask an agency PM what Friday looks like and you'll get the same answer with different tools in it.

Open the board — ClickUp, Asana, Jira, whichever. Notice it's wrong. Half the tasks say "In progress" for work that shipped Tuesday. The one that's actually blocked still says green. Ask three people in Slack what really happened. Wait. Piece it together. Write it up so it reads right to the client. Rewrite it once because it sounded like an excuse.

Two hours. Every week. Per client.

Why the update takes two hours

The update itself is ten minutes of writing. The other hour and fifty is finding out what to write, and that's the part nobody talks about.

The board is a copy. Every decision on a client project gets made somewhere else first — in the Slack channel, on the Tuesday call, in a reply-all with the client. The board only knows what someone typed into it afterwards, and by Friday most of the week's decisions never got typed. So the board is a starting point you have to correct, not a source you can trust.

The people who know are busy. The designer who finished the homepage on Tuesday is on a different client now. The developer who's blocked on the API told his lead in a DM, not the channel. Getting the truth means interrupting five people for a sentence each.

The client is reading for a reason. A client update isn't a status report. It's the document that decides whether the client feels the retainer is worth it this month. So it gets rewritten — for tone, for what to lead with, for how to say "the launch moved" without it sounding like your fault.

A 2020 survey found over a third of organisations spend more than 24 hours a month collecting project status (Wudpecker). For an agency PM with four clients, that's Friday, all of it.

The template that works

If you're going to write it by hand, write it in this shape. It's the one clients actually read.

Subject: [Client] — week of [date]

What shipped this week. Two to four lines. Specific: "Homepage design approved and handed to dev." Not "progress on homepage."

What's in motion. What's being worked on now and when it lands. Dates, not "soon."

What we need from you. The one thing the client owes you — an approval, a decision, an asset — with a date. This is the line that gets read first.

What changed. Anything that moved: a date, a scope, a priority. Say it plainly and say why. "Launch moved from the 14th to the 21st — legal's copy review came back Thursday with changes." Clients forgive a moved date. They don't forgive finding out about it later.

Next week. Three lines.

Keep it under two hundred words. If it's longer, the client skims it and the important line — what you need from them — gets missed.

The version you don't write from memory

Here's the thing about that template: every section is a fact about what happened, and every fact was said out loud somewhere before you went looking for it. "Homepage approved" was a Slack message. "Legal's review came back Thursday" was a sentence on a call. "Launch moved to the 21st" was decided in a thread.

The two hours is the cost of the board not having heard any of it.

Fluorine is a project board that does. Its engine, Flo, reads the client's Slack channel, the call transcripts, the repo and forwarded email, and when something said there disagrees with the board, it proposes the change — with the sentence quoted — and your PM confirms. Nothing moves without them.

Then the update writes itself from the record. Fluorine's summary view takes any date range and produces what changed, grouped by project: what shipped, what moved, who confirmed each change, and the line that caused it. Copy it, add the two sentences of tone, send.

Every line traceable. When the client replies "who decided the 21st?", the date on the board links to the moment on the call. That's not a feature — it's the dispute you don't have to have.

Flo never writes to the client's Slack, never posts, never sends anything. Here's exactly what it reads and never does.

What this changes on Friday

The board is right on Friday morning because it was corrected on Tuesday, when the thing was said.

Nobody gets interrupted. The designer who moved on already told the record what she finished.

"What changed" has evidence attached. The moved date isn't your word against the client's memory; it's the clip.

The update takes ten minutes — the ten it was always supposed to take.

Try it on one client

Connect that client's Slack channel and the weekly call recording. Run two weeks as normal. Then open the summary on Friday and compare it to what you'd have written by hand.

If it caught things you'd have had to ask about, that's the two hours. If the board was already right — it happens, rarely — you have a well-run project and the evidence to prove it to the client.

Fluorine is free right now. Try it.

FAQs

Can the client see the board? Not yet — there's no guest access today. The update you send them is generated from the board; they don't log in. Client access is on the list.

Does it work if the client uses a different tool? Flo reads the conversation, not the client's tracker. If the decisions happen in your Slack channel and on your calls, it hears them regardless of what the client uses internally.

What if the call isn't recorded? Then there's no transcript, and Flo only hears what's in Slack and email. Most agencies that try this turn on cloud recording for client calls the second week.

Is the summary sent automatically? No. It's generated when you open it, and you send it. Flo never sends anything on your behalf. There's also a daily brief to a Slack channel you choose, if you want the internal version every morning.

References

Wudpecker. (2024). 15 Project Management Trends in 2024. https://www.wudpecker.io/blog/15-project-management-trends-in-2024