Should you automate the weekly client report?
Pulling the numbers, yes. Saying what they mean, no. How to tell which part of a weekly client report to hand to software.
Sunnyworks ·
Short answer: automate the assembly, not the explanation.
A weekly client report is two jobs in one. The first is collecting the numbers and putting them in the same layout as last week. The second is telling the client what the numbers mean, especially when they are bad. Software can build the draft. The explanation is yours.
Run it through three tests
Volume. Count all the reports, not one. Minutes per report, times the number of clients, is the real figure. For example, 45 minutes for each of five clients is nearly four hours every week. One short report for one client may not be worth the effort. Five of them probably are.
Variability. Put your last four reports for one client side by side. The sections, charts and order that never change are the part to hand over. The sentences you write fresh each week are not. The more of the page that is identical, the more software can do.
System access. For every number in the report, name where it comes from. A dashboard, an export file or a spreadsheet can be reached by software. A number you get by asking a colleague, or by reading it off a screen that offers no export, cannot be reached yet. The report will only be as reliable as its weakest source.
What to keep with a person
The “so what” lines. The explanation when a number goes down. The choice of what to leave out for a particular client. And the last read before the report goes out, because a wrong number sent to a client costs more than a late report. A sensible setup lets software build the draft while a person checks it and sends it, at least at first.
A free first step, under an hour
Take your most recent report for one client and do three things:
Next to every number, write where it came from.
Mark each section “same as last week” or “written fresh”.
Look in the settings of each source for an export or a scheduled report.
Those marks are what anyone building this would ask you first. If a number has no source you can name, start there.
What it looks like on a real-sized week
Example only. The week below is made up, for a four-person social media agency. It is not a client. Five tasks were typed into the Task Check, and parts of the answer are quoted here as it came back.
What was typed: “Building the weekly report for each of five clients: copying follower, click and sales numbers from each platform into a slide template, about 45 minutes per client.”
Why it fits: “Volume is high: five reports every week at about 45 minutes each. Variability is low, because the same numbers go into the same template each time. The numbers live in platform dashboards, which software can usually reach.”
First step: “Write down the exact steps for one client's report, listing each number, where it comes from and which slide it goes on. This should take under an hour.”
Keep with a person: “This needs judgment about the client, the context and the relationship, and none of that is in a dashboard. The way it is explained affects trust, so a person should own it.”
What it could not tell: “The list does not say how many different platforms feed the reports or whether each one allows its numbers to be exported, which affects how much of the reporting can be automated.”
The last line is the system access test at work. The Task Check could not say how much of the report can be automated until it knew whether each source allows an export. In the same answer it ranked the Friday email of finished reports second, and said the short comment on each report fits only as a first draft that a person reviews.
You can run your own week through the Task Check. It is free, and it takes a plain list of what one person does.
Where to go next
Or start free with the Task Check.
If you want this built for you, it is one workflow under the Automation & Implementation Build.