Nobody has a budget line called "time lost to reporting". That is precisely why it goes on for years: the cost is real, it is large, and it is invisible because it is distributed across people who each lose an hour here and two hours there.
Here is how to tell whether it is happening in your business. If three of these are true, you are losing a day a week somewhere.
1. Someone rebuilds the same report every period
Not runs it. Rebuilds it — exports the same three files, pastes them into the same workbook, fixes the same formatting, and checks the same totals.
The tell is that the person doing it can tell you exactly how long it takes, because they have done it enough times to know. Anything measured that precisely by a human is a process, and a process that a person executes by hand every month is a process that could execute itself.
2. Two systems give two answers and there is a "correct" one
Everyone in the business knows that the number in one place is the one to use and the number in the other place is "wrong" for a reason someone explained once.
That knowledge lives in people's heads. It is not written down, it is not enforced anywhere, and it is exactly the kind of thing that produces a bad decision the first time it is used by someone who was not in that conversation.
3. The month-end number arrives after it can change anything
If you find out a job lost money four weeks after it finished, that number is history rather than management information. The value of a figure decays fast: the same number is worth a great deal on the day and almost nothing a month later, because on the day you could still have done something.
This is the most expensive symptom on the list and the one least likely to be described as a reporting problem.
4. One workbook, one person
There is a file that the business genuinely depends on, and one person fully understands it. Everybody jokes about what happens if they leave.
The joke is the symptom. Key-person risk in a spreadsheet is the single most common serious data problem in businesses under two hundred people, and it is almost never on anyone's risk register.
5. People check the number before they trust it
Watch what happens when a report is shown in a meeting. If the response is "let me just verify that against..." — the report has already failed. Its job was to end that sentence.
Verification behaviour is the clearest possible signal that a reporting layer is not trusted, and an untrusted report costs more than no report, because you pay for it twice: once to produce and once to check.
What to do with this
Do not start by buying a tool. Start by counting.
For one week, ask everyone who touches a report to note the minutes. Not a study — a tally on a sticky note. At the end of the week, add it up and put a rough hourly cost against it.
Almost every business that does this is surprised by the total, and the total is what justifies fixing it. Without the number, "our reporting could be better" competes with everything else and always loses.
With the number, the conversation changes from a preference to a calculation — and the calculation is usually not close.