Why Reporting Problems Are Often Really Workflow Problems

If reporting always becomes a scramble at month-end, before a board meeting, or just ahead of a funder deadline, it is easy to assume the report itself is the problem.

Often, it is not.

In many small nonprofits, the stress only becomes visible when someone has to pull everything together. But the real issue often started earlier: in how information is recorded, where it is stored, who updates it, and what happens when a step depends on somebody remembering to follow up. That’s why it helps to start with simple metrics that are easy to track consistently.

That distinction matters. If the problem sits upstream, tidying the spreadsheet or redesigning the template will only help so much.

The pain shows up in reporting, but it often starts in the workflow

A report is where everything finally meets.

It is the point where someone has to gather updates, compare figures, check whether numbers match, chase missing context, and turn scattered information into something useful for leadership, the board, or a funder. When that feels painful every time, it is understandable to focus on the report.

Sometimes the report does need work. But often it is simply the place where weak ways of working become visible.

This is a common pattern in small organisations. Staff are usually doing their best. The issue is rarely effort or intent. But if reporting depends on chasing people, cleaning spreadsheets, or checking numbers by hand every cycle, that usually points to an upstream workflow issue.

The pressure may land at the end of the month. The cause has often been building throughout it.

If that sounds familiar, the signs that reporting is being held together by workarounds can help you work out whether the issue sits in the report itself or in the work feeding into it.

What this often looks like in practice

In practice, this is less a reporting failure and more a reconstruction exercise.

A board report runs late not because nobody can format a report, but because programme updates are spread across spreadsheets, emails, forms, Slack messages, and phone follow-ups. By the time one person assembles the final version, they are not just reporting. They are chasing, checking, interpreting, and filling gaps.

A funder report becomes stressful because frontline staff record the same activity in different ways. One person uses one definition, another uses a slightly different one, and someone else records it later from memory. The person preparing the report then has to clean and reinterpret everything before the numbers can be submitted.

Leadership loses confidence in a KPI report because the figures change from one version to the next. That is not always a spreadsheet design problem. Often, source information is entered at different times, by different people, with no clear ownership or shared process.

When this is happening, reporting depends too much on knowing who to ask, what they probably meant, and which version is most likely to be right.

That is usually a workflow problem showing up through reporting.

What may be going wrong before reporting even begins

The core issue is often simple: the report is trying to combine inputs that were never set up to fit together cleanly.

Information may be captured inconsistently. The same activity might be recorded in different places, in different formats, or with different meanings attached. Even if everyone is acting reasonably, the result is unreliable because the workflow is not clear enough to produce consistent inputs.

Ownership may also be unclear. It is not always obvious who updates what, when it should happen, or what counts as complete. That creates delays, duplication, and gaps long before anyone starts compiling the report.

Then there are handoffs. One person finishes their part, but the next step depends on someone noticing an email, remembering to update a sheet, or knowing that something mentioned in conversation needs to be written down. Important context ends up living in staff memory instead of in the workflow itself.

By the time reporting starts, the underlying issues are already there.

The spreadsheet often gets blamed because that is where the strain becomes visible. But in many cases it is only revealing the weakness in the process underneath.

Why leaders often ask for better reports when the real issue is elsewhere

From a leadership point of view, the request usually sounds reasonable: can we get the report faster, make it clearer, and feel more confident in the numbers?

But inside the team, that request may be landing on top of a workflow that is already patchy.

People may be entering the same information into case notes, spreadsheets, funder trackers, and internal summaries. They may be translating one person’s notes into another person’s format. They may be manually updating figures because the original source was never set up to support reporting clearly.

So when leaders ask for a better report, staff often respond by working around the workflow rather than fixing it. They add checking steps, build another version of the spreadsheet, keep a side document with explanations, or rely on the person who knows how it works.

That can keep things moving for a while. But it also makes reporting slower, more fragile, and harder to trust.

If the workflow underneath is causing the problem, improving the report format alone will not change much. The same issues are likely to return next month, even in a cleaner template.

How to tell whether this is a reporting issue or a workflow issue

A true reporting issue is usually about format, structure, or presentation.

For example, the report may include too much detail, not enough explanation, or the wrong layout for the board or leadership team. Those are real reporting issues.

But if the difficulty starts with gathering the information in the first place, you are probably looking at a workflow issue.

It is more likely a workflow issue if:

• the report depends on chasing people for updates every cycle
• someone has to interpret missing context from emails, notes, or memory
• different versions of the same information need to be compared by hand
• numbers are entered at different times with no clear cut-off or ownership
• the same reporting problem returns even after the spreadsheet has been tidied

A useful test is this: when a figure looks wrong, can someone easily trace where it came from and how it was recorded?

If not, the issue is probably not just the report at the end. It is that the source information is incomplete, late, inconsistent, or hard to follow back.

Start by mapping one report backwards

Before redesigning the template, adding another spreadsheet, or asking people to be more careful, start with one recurring report and map it backwards.

Look at where each number comes from, who records it, when it gets updated, where it is stored, and what has to happen before it appears in the report. Focus on the parts that regularly cause friction.

As you do that, look for:

• duplicate entry in more than one place
• unclear ownership for updates or checks
• missing definitions for what counts and what does not
• handoffs that depend on memory or informal follow-up
• steps where someone is manually patching things together every month

This kind of review can quickly show whether you have a reporting problem, a workflow problem, or a bit of both.

Use Reporting Problem: Fix the Data, Workflow, Measures, or Tool First? to decide which reporting layer to investigate before changing tools or rebuilding the output. If the pressure is most visible around funding deadlines, this practical grant reporting guide explains how to collect evidence during delivery instead of rebuilding it later.