The Reporting Factory Has No Customers.

Somewhere in your organisation, a report is being produced because a person who left four years ago once asked for it.

The report has survived two reorganisations, three directors and a migration to a collaboration platform nobody enjoys. Its template is protected with the seriousness normally reserved for constitutional law.

Every Thursday, people collect numbers. On Friday, they chase the missing numbers. On Monday, somebody adjusts the colours, updates the date and moves one sentence from “issues” to “risks” because issues sound worse.

Then the report is sent.

Nobody knows what happens next.

The factory works

This is the strange part. The reporting process may be very well managed.

There is a template, a deadline, a distribution list, a naming convention and a folder structure. Contributors know which cells they own. The coordinator knows whom to chase. The final deck looks calm, aligned and expensive.

The factory works.

It is the customer who has disappeared.

Ask who reads the report and you will hear a list of offices. Ask which decision those offices make from it and the answer becomes less precise. Ask what changed because of last month's report and somebody will suggest that reporting is important for “visibility.”

Visibility is useful. It is also the word organisations use when they cannot identify a decision.

Reporting is work

Reports do not appear by administrative weather.

People gather the data, repair it, reconcile definitions, explain anomalies, request corrections, rewrite blunt language, prepare graphics and sit through coordination meetings. A twenty-page management report may contain hundreds of hours of hidden work.

That cost is rarely measured because the report itself is treated as free. Everyone contributes a little, so nobody sees the full bill.

The opportunity cost is worse. The people best able to explain what is happening are often the same people spending Friday afternoon converting what is happening into the approved format.

During an active operation, this becomes absurd. The closer a person is to the work, the more reporting requests arrive. Each requester wants only three lines. Twenty requesters later, the person doing the work has become a small news agency.

The numbers can all be true

A reporting factory does not need to invent data in order to mislead.

A fleet may show 92 per cent availability while the unavailable eight per cent contains the only vehicles with the equipment required for tomorrow's task.

A warehouse may report that every dispatch left on time while the receiving team waits because “on time” was measured at the wrong end of the journey.

A broadcasting system may show healthy subsystems while the audience hears silence. Each component produced a correct status. Nobody measured the experience at the output.

These are not false numbers. They are numbers without a customer, a question or enough context.

Information is not improved merely by arranging more of it in rows.

Why reports never die

Creating a report is easy. Retiring one feels dangerous.

The person who stops it may later be asked why management was not informed. Nobody is punished for sending an unnecessary report. People are punished for failing to send the one report that, in hindsight, somebody says they needed.

So organisations accumulate reporting requirements like old cables in a drawer. Each one might be useful. Removing any particular one feels reckless. Together, they become a knot.

There is also status in reporting. Receiving a report proves that a unit matters. Being copied creates the appearance of oversight. Asking for a new dashboard looks more managerial than reading the old one carefully.

The result is a system optimised for the production of evidence that management was informed.

Whether management understood is a different question.

Give every report a customer

A useful report needs a named customer, not a distribution list.

That customer must be able to answer four basic questions:

• What decision will this information support?
• How quickly must that decision be made?
• Which exceptions require attention?
• What would we lose if the report stopped?

If nobody can answer, stop the report for one cycle.

Do not organise a six-month review programme. Do not establish a task force for the strategic modernisation of reporting. Simply do not send it once.

If somebody notices, good. You have found the customer. Ask what that person actually needed.

If nobody notices, you have found something else.

Shorter is not automatically better

The answer is not to replace a thirty-page report with a one-page report containing the same confusion in a smaller font.

Some subjects are complex. Some records must be complete. A technical investigation, a financial statement and a legal submission cannot be reduced to three cheerful bullets because a senior reader has limited patience.

The useful distinction is between the record and the decision interface.

Keep the evidence. Keep the detailed analysis. But tell the decision-maker what changed, why it matters, what is uncertain and what must happen next.

That may require four lines. It may require four pages. The length is secondary. The purpose is not.

Close the factory door occasionally

Every recurring report should carry an expiry date.

At that date, somebody must choose to renew it, change it or stop it. Not producing the report should be a legitimate option, not an act of rebellion.

The test is simple:

What decision did the report change?

What action did it trigger?

What did the reader understand afterward that was not understood before?

If the answers are unclear, the report may still be beautifully produced.

But a factory without customers is not a reporting system.

It is a tradition with deadlines.