Your weekly report costs almost seven hours a week, and nobody has asked whether anyone reads it.
You know the one. Five department heads each write a status update every Friday. A coordinator collects the five updates, merges them into one document, fixes the formatting, and sends it to the leadership team. Then someone spots a wrong number, two managers fix their sections, and the whole thing goes out again.
Nobody designed this process. It grew. A leader asked for an update once, the update became a habit, and the habit became a rule. Today it runs on its own, like a meeting that outlived its purpose.
What one report really costs
Let’s put numbers on it. These figures are illustrative, so replace them with your own.
• Five managers, 45 minutes each: 3.75 hours
• One coordinator merging and formatting: 2 hours
• Corrections and resends: 1 hour
Total: 6.75 hours every week. Over 50 weeks, that is more than 330 hours, or about eight full working weeks spent on one document.
Most companies have several reports like this. Each one looks small on its own. Together they take a real share of the week, and nobody sees it because no one has ever added it up.
There is also a cost the arithmetic misses. Managers who write a report nobody reads learn that reporting is theater. They start writing what looks safe. The report gets longer and says less.
This is not a complaint about managers. They write the update because someone asked for it, and they do it carefully, which is exactly why it takes 45 minutes.
The question to ask before you buy anything
When people see seven hours of work, the first idea is usually a tool. Let AI collect the updates, merge them, and format the document. That would help.
It would also give you a faster version of a report that may not need to exist.
Ask this first: what decision did anyone make last month because of this report?
If leaders can name one, the report has earned its place. If the answers come slowly and vaguely, you have found work that can go away. A report nobody acts on is not communication. It is a weekly ritual with a deadline.
Three steps, in this order
1. Remove. Ask who reads the report and what they do with it. If the honest answer is “no one,” stop sending it. Tell people you are pausing it for a month, then watch who complains. In many companies, nobody does.
2. Simplify. If the report survives, ask what the reader actually needs. Often it is three numbers and two risks, not five pages. Shrink the template to match. Five managers who write five lines each need ten minutes, not forty-five.
3. Automate. Only now hand the leftover mechanical work to AI: collecting the updates, putting them in one format, and drafting a short summary for a person to check before it goes out.
What a short report looks like
A useful weekly update can fit on half a page. Three headings are usually enough: what changed this week, what is at risk, and what needs a decision from the reader. Everything else is detail that belongs in a folder, not in a leader’s inbox.
Ask managers to write to those three headings and the report shortens itself, because most weeks only a few items need real attention. A quiet week produces a short report, and that is a feature. A leader who receives two lines saying nothing has changed has learned something worth knowing.
What the numbers look like after
Run the same example again. Managers now spend 10 minutes each, about 50 minutes in total. The coordinator reviews an AI-assembled draft in 30 minutes instead of building the document from scratch in two hours. Corrections drop to 15 minutes because the simpler template leaves less room for mistakes.
That is about one and a half hours a week instead of almost seven. Over a year, roughly 250 hours come back.
Look at where the savings came from. More than half of the time saved comes from the simpler template, which arrived before any AI touched the report.
A drafted summary still needs a human eye. AI can merge five updates in seconds, but it cannot tell that one manager’s “on track” has quietly meant “late” for three weeks. Keep a person on the final read. In this example that check takes 15 minutes, and it is time well spent.
Why teams skip the first two steps
Buying is exciting and removing is uncomfortable. A new tool gets a launch email and a training session. Stopping a report gets you a few awkward questions.
There is a quieter reason too. Some reports exist because a former leader asked for one, and that leader moved on years ago. The report stayed behind, like a houseplant nobody remembers buying but everybody keeps watering.
Automating that report does not solve the problem. It just makes the watering faster.
When someone defends the report
Expect the objection: “Leadership might need it someday.” Fair enough. So test it instead of arguing about it.
Pause the report for four weeks. Tell the leadership team it is available on request, and keep the template ready. Then count how many requests arrive. If the count is zero, you have your answer. If the count is two, you have learned which two readers matter, and you can send the report to them alone.
Either result is cheaper than another year of Friday afternoons.
The same test works on other recurring work
Weekly reports are only the start. Run the same questions on meeting minutes nobody opens, monthly dashboards that get a quick glance, status decks rebuilt from scratch every cycle, and spreadsheets that one employee updates by hand because the system never quite fit.
Each one has a cost in hours, a reader who may or may not exist, and a smaller version waiting to be found. Most of the time, the smallest useful version takes a fraction of the effort.
AI earns its place at the end of that process, not the beginning. By then you know what the work is for, what a good version looks like, and how to tell when a draft is wrong. A tool is far more useful to someone who knows what they want from it.
Try it on one report this week
Pick one recurring report in your department. Write down how many people touch it, how many minutes each person spends, and how often it goes out. Then multiply.
Answer three questions. Who reads it? What did they decide because of it? What is the smallest version that would still support that decision?
You do not need a consultant for this. You need a calculator and a willingness to hear the answer. Seven hours written on a page is hard to argue with, which is usually the point.
If the report passes the test, keep it and simplify it. If it fails, you have just found seven free hours a week without buying anything.
Delete what nobody uses, simplify what remains, and automate only what is left. Most teams do it in the opposite order.
Which recurring report in your company takes far longer than it should, and who would actually notice if it stopped?
If you want to compare notes on a report like that, I’d be glad to hear your thoughts.
ADDITIONAL READING
• Your Company Isn’t Slow—Your Decisions Are Trapped in Manual Processes — https://jordanimutan.com/2025/12/19/your-company-isnt-slow/
• AI Was Supposed to Save Your Managers Time. It Didn’t. — https://jordanimutan.com/2026/09/03/ai-was-supposed-to-save-your-managers-time-it-didnt/
• Not Every Task Should Use AI. Here’s the Test We Use to Tell. — https://jordanimutan.com/2026/09/25/not-every-task-should-use-ai-heres-the-test-we-use-to-tell/
• The 20% of Any Job That’s Actually Worth Giving to AI — https://jordanimutan.com/2026/10/06/the-20-of-any-job-thats-actually-worth-giving-to-ai/
• The Real Reason Most AI Projects Stall Before They Start — https://jordanimutan.com/2026/09/11/the-real-reason-most-ai-projects-stall-before-they-start/
