The reporting workflow that stopped eating Mondays

Where the morning actually goes

The work is not analysis. It is opening six tabs, copying figures into a template, fixing the chart that broke when someone renamed a campaign, writing two lines of commentary, exporting, renaming the file, and sending it. Then doing the whole thing again for the next client.

Nobody schedules that morning. It just happens, every week, and it is invisible on any plan because it never appears as a project. It shows up as a team that is somehow always busy on a Monday.

Ask what the report is for before you automate it

The first question is not which tool. It is what decision this report supports. Most recurring reports answer that badly, because they grew by accretion: someone asked for a metric two years ago, it was never taken out, and now it is nine pages nobody reads past the summary.

Automating that just produces nine pages faster. So before building anything I go through the report with whoever actually reads it and cut every number that has never once changed a decision. The document usually gets shorter, and the build gets simpler as a result.

The three parts worth automating

Collection is the obvious one. Numbers are pulled from where they already live, on a schedule, rather than by hand at the moment they are needed.

Assembly is the part that actually costs the morning. The template fills itself, the charts regenerate, the client name and the period are right, and the file lands where it belongs under the name it should have.

Distribution is small but worth doing. The report reaches whoever needs it on the day that was agreed, without anyone having to remember to send it.

The part that should stay human

The commentary. A generated paragraph about what changed is the fastest way to make a client stop trusting the entire document, because it reads like nobody looked at it.

So the workflow assembles everything and then stops, leaving the account lead a draft with the numbers already correct and an empty box for the two lines only they can write. That is a ten minute job instead of a morning, and it is the ten minutes the client is actually paying for.

Handover is the build, not the afterthought

A workflow only one person understands is a liability with a nice interface. When that person leaves it becomes a black box nobody dares touch, and eventually someone quietly goes back to doing it by hand.

So documentation is part of the job rather than a favour at the end: what each step does, what breaks it, how to add a client, and who to call. I would rather hand over something a team can change without me than something that keeps me on a retainer for the wrong reason.