When reporting is being held together by workarounds
When a report is hard to produce, the problem is not always the report.
In small nonprofits and other small organisations, reporting is often where messy day-to-day processes finally become visible. Unclear ownership, inconsistent data entry, copied information, manual checks, and last-minute fixes can stay hidden for a while. Then someone needs a report they can trust, and all of it shows up at once.
So if reporting feels harder every month or quarter, that does not necessarily mean your team is bad at reporting. It often means the process underneath has been patched together over time.
This post will help you spot that pattern. Not so you can launch a big systems project, but so you can understand what kind of problem you are actually dealing with.
When reporting gets harder every cycle, it is usually not just about workload
This pattern is common in small organisations.
A report that used to feel manageable starts taking longer each month or quarter. More people need chasing. More checks creep in. More time gets spent comparing versions, double-checking figures, and making small corrections before anything can be shared with confidence.
On the surface, that can look like a capacity problem. Everyone is busy. Reporting takes time. Deadlines stack up.
Sometimes that is true. But when the same report gets slower, more stressful, and less reliable every cycle, there is usually something deeper going on.
The report is often just the point where process gaps become obvious.
A monthly board report might seem difficult because it needs careful review. But if producing it means pulling numbers from several spreadsheets, checking them against email updates, and manually rewriting figures before submission, the pressure is not really coming from the board report itself. The report is exposing how fragmented the underlying process has become.
That matters, because if the issue is structural, asking people to work faster or be more careful will only help for so long.
What reporting held together by workarounds looks like in practice
Workarounds do not usually look dramatic from the inside. They look normal, because people have adapted.
A spreadsheet gets created to fill a gap. Someone keeps a separate tracker because the main source is unreliable. A manager checks figures by hand because teams use different definitions. Updates are chased over email because there is no clear handoff point.
Over time, those small adjustments become the process.
Day to day, that often looks like:
- copying data from one place to another
- checking one spreadsheet against another
- asking people to resend the latest version
- cleaning up inconsistent formats before totals can be calculated
- manually reconciling figures that should already match
- holding reports until one person has done a final sense-check
One of the clearest warning signs is dependence on one person.
They know which file is the real one, which figures can be trusted, which numbers need adjusting, and which anomalies are actually normal. They may be doing excellent work. But if confidence in the report depends on their memory and personal logic, that is a workaround, not a stable process.
You might also notice quieter signs:
- conflicting numbers appearing in different reports
- confusion about which version is current
- repeated rework because data arrives in different formats
- late chasing for updates every reporting cycle
- a familiar last-minute cleanup ritual before anything goes out
A funder report that only one staff member knows how to compile is a good example. On paper, the process may look established because the report gets submitted. In reality, the key logic may live in that person’s spreadsheet and memory rather than in a shared process.
Why the real problem often starts upstream
Manual reporting problems usually start long before anyone opens the report template.
If data ownership is unclear, people record things differently. If teams collect similar information in different ways, totals do not line up. If information is copied across several places, errors and delays creep in. By the time reporting starts, the work is already compensating for upstream inconsistency.
That is why reporting pain is often a process problem in disguise.
In many small organisations, reporting requirements were added on top of existing work rather than built into how the work is recorded in the first place. A funder needs one format. The board needs another. A programme lead tracks progress in their own way. Finance keeps related information somewhere else. Each requirement makes sense on its own, but together they become hard to hold together.
A common example is the heroic monthly spreadsheet ritual.
Inside the organisation, it can feel normal. Everyone knows that at the end of the month there will be a push to gather updates, clean figures, compare notes, and get the report over the line. Because it happens regularly, it starts to feel like that is simply what reporting involves.
But often that ritual is covering up something more basic: unclear ownership earlier in the process. No one is fully sure who owns each input, where data should first be recorded, or which version should be treated as the main one. Reporting then becomes the place where those unresolved questions get sorted out by hand.
A programme update can make this very obvious. If different teams track the same information in different ways, conflicting totals are almost guaranteed. The last-minute scramble is not really a reporting issue. It is the result of inconsistent ways of working before the report even begins.
How to tell whether the issue is reporting or wider operations
It helps to separate reporting friction from a broader operating problem.
If a report is awkward because the template is clumsy or the format needs tidying, that may be a reporting-level issue.
But if the report is slow because data arrives late, definitions vary, or people record the same thing in different ways, the issue is probably wider than reporting.
A few simple questions can help:
- Where does the data first become messy?
- Who owns each input before it reaches the report?
- At what point does manual reconciliation start?
If the same confusion shows up before every reporting deadline, that is a strong sign the process is relying on hidden workarounds.
Another useful test is this: what would happen if the person who usually assembles the report was away for two weeks?
If the answer is that the report would be delayed, risky, or nearly impossible to produce confidently, then the real dependency is not just on a capable staff member. It is on undocumented judgment, manual fixes, and workarounds that nobody has properly surfaced.
That usually points to a wider operations problem.
The same is true when confidence in the numbers depends on memory rather than clarity. If people regularly say things like “use the figure from the other sheet,” “ignore that tab,” or “I know it looks wrong but that one is the correct version,” the process is doing too much hidden repair work.
A practical first step: map the reporting journey
Before changing tools, redesigning templates, or asking people to be more disciplined, map one report from start to finish.
Pick a report that comes up regularly, such as a monthly board pack or a funder report.
Then trace its journey.
Where does each number come from? Who provides it? Where is it first recorded? Where is it copied? Where do checks happen? Where do delays usually appear? Which steps rely on someone knowing what to fix rather than following a clear process?
This does not need to be a big exercise. A simple page with boxes and arrows is often enough.
The aim is to make the hidden work visible.
As you map it, mark:
- every manual handoff
- every place where data is entered more than once
- every step where definitions are unclear
- every decision point that depends on personal judgment
- every part of the process that only one person really understands
That will usually tell you more than jumping straight into a search for a better report format.
In many cases, the first useful fix is not in the report at all. It is clarifying one ownership point, removing one duplicate step, or agreeing one definition earlier in the process.
That is often enough to reduce stress quickly, because you are dealing with the workaround rather than just coping with it more efficiently.
If you want a simple way to assess this, you can use our simple reporting health-check checklist to see whether your reporting stress is mostly about workload, unclear process, or patched-together workarounds.
You might also find these useful:
Want to get started today? Use this quick checklist to see whether your reporting pain is really pointing to a wider operations issue.