When Reporting Depends Too Much on One Person

The board pack goes out. The funder update is submitted. The monthly numbers appear on time.

From the outside, reporting can look steady enough.

But inside the organisation, everyone knows there is one person who really holds it together. They know which exports to pull, which spreadsheet tabs still matter, where the latest figures sit, what needs checking before anything is shared, and which numbers usually need a manual adjustment.

When that person is away, overloaded, or leaves, confidence drops quickly.

If you are a CEO or Executive Director, this can create a low-level unease. Reporting is getting done, but it does not feel especially robust. The concern is usually not the person. It is how much the organisation relies on what they remember.

This is common in small nonprofits and small organisations. It is not usually a staffing failure, and it is not a sign that someone is not trying hard enough. More often, it points to a reporting setup that has become too dependent on staff memory and manual work.

It can look fine until that person is unavailable

This pattern often stays hidden because the reports do get produced.

Leadership sees the final report, not always the copying, checking, reconciling, and remembering behind it.

The strain tends to show up when the usual person is on leave, tied up with year-end work, pulled into another priority, or simply not available to explain the steps. A report that seemed routine suddenly becomes difficult to reproduce.

A board pack may be delayed because nobody else knows the sequence, where the source data sits, or which version of the numbers is final. A funder report may stall because only one staff member knows which spreadsheets need to be combined and which figures need adjusting before submission.

Often leadership feels the risk before they have a clear name for it. It can show up as hesitation around deadlines, uncertainty when someone asks where a figure came from, or a sense that reporting is less reliable than it looks.

What this usually looks like day to day

Inside a small organisation, this dependency can feel normal because it has built up gradually.

One trusted person has learned the work over time. They know which system export is useful and which one is misleading. They know how the spreadsheets link together. They know which numbers need a manual sense-check because the source data is inconsistent or incomplete.

That knowledge is valuable. But it also means the organisation may be leaning on one person more than it realises.

You might hear things like:

• “Ask Sam, she knows how that report works.”
• “We can do it, but only if James is back by Thursday.”
• “That figure is right, but I need to check how it was adjusted last month.”
• “There is a spreadsheet for that somewhere.”

A programme manager may export data each month, clean it manually, and fix known issues from memory before sharing results. The report works, but it is not easy for someone else to repeat. Questions like “Where did this figure come from?” or “Could someone else produce this by Friday?” become harder to answer than they should be.

Over time, delays, version confusion, and last-minute checking can start to feel routine. People stop treating them as warning signs and start treating them as part of reporting.

The issue is not the person. It is where the reporting knowledge lives

When reporting depends heavily on one person, the main problem is usually not that they are too controlling or not sharing enough.

The deeper issue is that reporting reliability sits in their memory, judgement, and manual workarounds rather than in a process the organisation can understand and repeat.

In other words, the setup is not very portable.

A capable member of staff can hide this fragility for a long time. They remember the extra checks. They know which columns to ignore. They can spot when a total looks wrong. They know that one spreadsheet is updated monthly but another is not. Because they can keep it moving, the organisation may not fully see the weakness until they are unavailable.

Naming that clearly helps avoid blame.

The person keeping reporting running is often doing exactly what the organisation has needed. They are compensating for inherited spreadsheets, unclear ownership, scattered data, and reporting steps that were never properly written down. The risk sits in the setup, not in the fact that one person has been helpful enough to keep it going.

This is closely related to a wider pattern of key person dependency. If that sounds familiar, this guide on How to spot key person dependency before it causes problems gives some practical signs to look for.

How to tell whether this is workload or a fragile setup

Small teams are busy. Not every delay points to a structural problem.

But some signs suggest the issue is bigger than capacity.

If another sensible person could not reproduce the report without a long handover, it is probably not just a workload issue.

If key checks, source definitions, adjustment rules, or spreadsheet logic are mostly known by one person, the setup is carrying hidden risk.

If reporting slows down or confidence drops every time that person is unavailable, the organisation is relying on concentrated knowledge rather than a stable process.

A few simple questions can help:

• Could someone else explain where each headline number comes from?
• Could someone else produce the report next week without sitting beside the usual person?
• Are the important checks written down anywhere?
• Do people know which file is current, which source is trusted, and who signs off the final version?

If the answer to most of these is “not really,” you are probably looking at a fragile reporting setup rather than a temporary squeeze on time.

In some cases, the reporting pressure is really a sign of upstream workflow problems. If the difficulty starts before anyone even begins compiling the report, Why reporting problems are often really workflow problems may help you pinpoint what to inspect.

A sensible first step: map the report before changing anything

You do not need to begin with a full reporting overhaul.

A better first step is to pick one important recurring report and map how it is actually produced.

This could be a monthly board report, a funder return, a programme dashboard, or a finance summary. Start at the beginning and write down the path from source data to final version.

Keep it simple:

• where the data comes from
• which exports get pulled
• what is copied or combined
• what gets checked or adjusted
• where definitions are unclear
• who reviews it
• how the final version is approved

The point is not to create a perfect process document. It is to make the hidden work visible.

That often includes chasing missing data, manually updating figures, reconciling conflicting versions, re-entering information, translating one format into another, or relying on “just ask X” at key points.

Once you can see the full path, the weak spots are usually easier to spot as well. You may notice that one adjustment only exists in someone’s head. Or that one spreadsheet drives the final numbers but nobody is quite sure how it was built. Or that a report depends on a manual clean-up step that never made it into any shared process.

That is a stronger place to start from than jumping straight to a new tool, a new role, or a broad reporting redesign.

This is common, and it is worth checking early

This comes up often in small organisations because reporting usually grows in response to real needs, not neat design.

That does not mean the team has done anything wrong. It usually means the process evolved under pressure and was never made easy to hand over.

If you are noticing that dependency now, that is useful. It gives you a chance to reduce the risk while the report is still being produced, rather than later when deadlines are tighter and options are fewer.

If you want a practical next step, Affordable Automation for Non-Profits (includes a 4-minute diagnostic) includes a short diagnostic that can help you see whether the issue is mainly reporting, workflow, or reliance on staff memory.