Ten Reports Nobody Reads: A 90-Minute Audit to Clear Your Team's Paperwork

There is a particular kind of organisational debt that never appears on a balance sheet. It accrues every time someone builds a report for a meeting that was later cancelled, keeps a log because an auditor once asked for it, or circulates a weekly pack that three people open and none of them act on. The debt is paid in Friday afternoons.

This article takes a position: most UK operations, facilities and compliance teams are carrying more recurring reporting than they can justify, and the fastest route to reclaiming capacity is a single, disciplined review rather than a slow cultural campaign. Ninety minutes, done properly, is enough to start.

The method: three questions, one score

The audit runs in three blocks. Spend thirty minutes listing every recurring report, return or log your team produces, however small. Include the ones produced for other departments on your behalf, because those consume your hours just the same.

Spend forty minutes scoring each item against three questions:

1. Who actually reads it? Named individuals, not departments. If the honest answer is "it goes on the shared drive", score it low.
2. What decision does it inform? A budget call, a staffing change, a risk escalation, a statutory return. If no decision follows, score it low.
3. What happens if it stops? If the answer is genuinely "nothing", score it low.

Score each question from one to three. Anything totalling four or below goes on the retirement list; five to seven goes to review with a proposed change of frequency or format; eight and above survives untouched.

Spend the final twenty minutes agreeing decisions with whoever owns the consequence. Not the format, not the ambition, just the decision: keep, change or stop, with a name against each.

Ten culprits worth examining first

1. The weekly KPI pack. Often a forty-slide deck built for a monthly audience. Replacement: a one-page exception summary, with the full pack available on request.

2. The duplicated compliance log. Fire checks, water temperatures or equipment inspections recorded in both a spreadsheet and a building management system. Replacement: one system of record, with the other switched to read-only.

3. Minutes nobody opens. Detailed narrative minutes of routine meetings. Replacement: decisions and actions only, circulated within a day.

4. The status email with fourteen recipients. Replacement: a short update in an existing channel, or nothing at all where the work is already visible.

5. The recycled board slide. The same three figures restated each month because the pack has a fixed template. Replacement: annual review of the template itself.

6. Parallel absence and holiday trackers. Two spreadsheets maintained by two managers with slightly different totals. Replacement: the HR system, once, with access granted properly.

7. The quarterly supplier scorecard. Produced diligently, discussed never. Replacement: an annual review, or a conversation when performance slips.

8. The narrative timesheet. Free-text justification of hours already recorded. Replacement: exception reporting only, where a variance needs explaining.

9. The duplicated risk assessment. Site-level RAMS copied into a regional summary that repeats the content verbatim. Replacement: a single register with a reference, not a transcription.

10. The all-staff newsletter. Frequently maintained by one person, competing with an intranet nobody has been shown how to use. Replacement: fix the intranet, or reduce the newsletter to a monthly note with a clear call to action.

A worked example

Consider a facilities team of nine in a two-site operation. The audit surfaced twenty-three recurring reports. Six scored four or below, including the weekly KPI pack, two duplicated compliance logs and a monthly contractor narrative. Combined effort was estimated at five hours a week, or roughly 240 hours a year once preparation, checking and circulation were counted.

Four of the six were retired outright, one moved to quarterly, and one was replaced by a single exception summary of two paragraphs. The estimated saving was 190 hours, reallocated to a backlog of overdue planned maintenance. The team did not become less accountable; the record simply stopped being written twice.

Retiring a report without inviting it back

The failure mode is familiar: a report is stopped in March and quietly reinstated in July because someone asked a question in a meeting and the only available answer was that report. Three precautions prevent it.

First, announce the retirement in writing to the recipients, stating what will now happen instead and where the underlying data still lives. Second, name an owner for the replacement, even if the replacement is a five-minute conversation. Third, record the decision in the same place you record other operational changes, with a review date twelve months out.

Where a report exists to satisfy a contractual, statutory or audit obligation, check the retention requirement before you stop producing it, and confirm with the relevant body where the requirement is unclear. Retiring something an auditor expects is a different decision from retiring an internal convenience, and the two should not be conflated.

What to do on Monday

Book the ninety minutes, invite the two people who prepare the most reports, and bring a list rather than a proposal. The aim of the first session is not to win an argument about reporting culture. It is to leave the room with three items marked stop and a date by which they will have stopped.