Most businesses do not have a reporting problem. They have too many reports and not enough trust in any of them.
The test is simple. Read a number out loud in a meeting. If somebody says they will double-check it, that report is decoration. The real decisions are being made somewhere else, on somebody's own spreadsheet.
Eight rules for reports people actually use.
01
Pick the few numbers that would change a decision
For each number on the report, ask what you would do differently if it doubled. If the answer is nothing, take it off. A report with six numbers people act on beats a dashboard with forty nobody reads.
02
Every number must be traceable to its source
You should be able to click a total and see the rows behind it. If a figure cannot be traced, it cannot be defended, and the first time someone challenges it in a meeting the whole report loses its authority.
03
Report the exceptions, not the whole list
Nobody reads a hundred rows. Show what is stuck, what is late, what is unusual. The job of a report is to point at the handful of things that need a human, not to prove the system was busy.
04
Build it on live data, never on exports
An export is a photograph of a moment that has already passed. The day someone forgets to run it, the report silently shows last week and looks exactly as convincing as it did before.
05
Make a job that stops running say so
Build it so a finished job switches itself off and writes down when. Otherwise silence looks the same as a breakdown, and people stop trusting the numbers long before anyone finds the fault.
06
Fail loudly, never quietly
One automation jammed for nine days without a single alert. The cause was a duplicate variable across two files. It was a two-line fix, but the nine days of silence were the actual damage.
07
Open the finished report and read it
Three problems in an automatic report once got past every technical check we had. We only found them by reading the report the way a customer would. A green tick is not proof; the document is the proof.
08
Give the report a meeting to live in
A report with no decision attached becomes wallpaper within a month. Same time, same people, same questions. The rhythm is what makes anyone act on it.
Silence is the most expensive failure
A report that crashes gets fixed on the same day. A report that stops arriving gets noticed weeks later, if at all.
We have taken on a report queue that had never delivered once and rebuilt it so it cannot jam again. The cause was one bad record blocking everything behind it. Nothing errored. Nothing alerted. Everyone assumed it was working, because nothing ever said otherwise.
Since being rebuilt, one of these systems has run fifty times on its own and worked every time. That number matters more than any chart on the report, because it is the thing that makes the chart believable.
Start with one number
Do not redesign everything. Pick the single number you wish you trusted, and trace it all the way back to where it comes from.
That one trace will show you every weak joint in the chain: the manual step, the export nobody re-runs, the two systems that disagree. Fix that chain, and the next number is far easier.
Six numbers you can defend beats forty you cannot.