Reporting Problem: Fix Data, Workflow, Measures or Tool?

A reporting problem can look like a dashboard problem even when the real issue starts much earlier.

The figures may be difficult to trust because teams use different definitions. The report may be late because data collection and handoffs are unclear. The measures may not answer the decision the reader needs to make. Or the tool may really be unable to support the agreed work.

Before rebuilding a report or buying software, decide which layer needs attention first: the measures, the workflow, the data, or the tool.

The four layers behind a reporting problem

Layer	Typical symptom	Question to answer
Measures	The report is full but does not support a useful decision or explain change.	What does the audience need to understand or decide, and what evidence would support that?
Workflow	Staff chase inputs, deadlines slip, and responsibilities change each cycle.	Who collects, checks, approves and owns each stage—and what happens when information is missing?
Data	Numbers disagree, definitions vary, records are incomplete, or cross-checking is routine.	What is the definition, source of truth, collection rule, owner and quality check for each important item?
Tool	The agreed workflow and data rules are clear, but the system cannot capture, combine or present what is required.	Which important requirement cannot the current setup meet, even after reasonable setup changes?

These layers affect each other. You do not need to force the problem into one box. Look for the earliest layer where a practical change would prevent extra work later.

Start with the decision, not the dashboard

Choose one important report and one real audience. Ask what that person needs to understand, decide, explain, or improve. A useful report may need fewer measures than the current one.

What decision should this report support?
Which outcome, activity, risk or commitment matters?
What comparison or context prevents the number being misread?
How current must the information be?
What level of confidence is appropriate?
Which information is truly needed, and which is collected because it always has been?

If the audience and decision are unclear, do not start with data cleanup or software. Make the reporting purpose clear first. Impact Measurement 101 provides a practical starting point.

Trace one important number backwards

Take one figure that matters and follow it from the final report back to the moment it was first recorded.

Where does the number appear in the final output?
Who checks and approves it?
What calculation, grouping or interpretation is applied?
Which file or system holds the official record?
Who records the original information, when and against what definition?
What happens when the information is late, incomplete or unusual?

This check often shows that reporting has become a job of comparing numbers. Staff compare sources, translate definitions and fill gaps left earlier in the process.

How to decide which layer to fix first

Fix the measures first when

The report does not answer a clear decision or learning question.
Teams collect many indicators but cannot explain what matters.
Different audiences need different levels of detail.
The organisation is treating available data as if it were automatically useful evidence.

Fix the workflow first when

Most effort goes into chasing, reminding and clarifying.
Collection and approval owners are unclear.
The process changes depending on who prepares the report.
Exceptions and late inputs have no agreed route.

Fix the data first when

Definitions vary across teams, periods or systems.
Several sources look official.
Missing or duplicate records seriously affect confidence.
The same figure must be corrected repeatedly.

Fix the tool first when

The decision, measures, workflow, definitions and owners are agreed.
The current system still cannot meet a necessary capture, permission, integration or reporting requirement.
The manual effort is caused by a verified system limit rather than by inconsistent work.
The replacement or configuration benefit is greater than its ongoing complexity and maintenance.

A practical order for improving reporting

Make the audience and decision clear.
Choose the minimum useful measures.
Agree definitions and ownership.
Map collection, checking, approval and exceptions.
Remove unnecessary capture and repeated cross-checking.
Configure or connect the systems that support the agreed process.
Build the report or dashboard.
Review whether people use it and whether the update process is sustainable.

Starting at step six can create a polished output with the same unreliable inputs and hidden work underneath it.

Browse the Nonprofit Reporting, Evidence and Impact Operations hub for the full reporting pathway.

Test whether outside support is a good fit

Review Simple and Engaging’s services if the problem keeps coming back and one team cannot solve it alone. If you are still unsure what kind of problem you have, take the diagnostic first. You can also ask for a free personal review of your result.

Discuss the problem Still diagnosing? Take the health check

When reporting support becomes worthwhile

Outside support can be a good fit when reporting affects funder or board confidence, several teams own different parts of the workflow, definitions and systems need alignment, deadlines leave little room for trial and error, or the person holding the current process cannot also redesign it.

The right first engagement should make the reporting decision clear, trace the work and evidence, find the main layer, and define the right level of support. It should not assume that a new dashboard or tool is the answer.