A grant reporting dashboard that connects money, milestones and evidence quality

A grant dashboard should expose decisions and exceptions, not decorate a status meeting. Build it from controlled source records and give every figure a definition, owner, date and route to evidence.

What to take away

A grant dashboard should expose decisions and exceptions rather than decorate a status meeting.
Give every figure a definition, owner, date and route to evidence from controlled source records.
Define green, amber and red with numeric or observable criteria, and never average red exceptions into a favourable score.
Separate outputs, observed outcomes and evaluated impacts, because monitoring change does not establish that an intervention caused it.
Test dashboard failure with known edge cases and preserve the last valid value when a source file is late.

Define the audience

List the decisions expected from the project owner, finance lead, board and funder. They may need different views. Keep personal data and commercially sensitive supplier information out of broad circulation when an aggregate answers the question.

Use the funder's required report as a constraint. A dashboard can support formal reporting but does not replace the authorised form or evidence.

Create an indicator dictionary

For each tile, state the formula, unit, population, exclusions, baseline, target, source, refresh date and owner. Record status thresholds. Put the definition beside the dashboard or one click away.

Freeze the dictionary during a reporting period. If a definition changes, label the break and recalculate earlier figures only when the method and reason are preserved.

Build five sections

The first section shows approved budget, commitments, paid cost, proposed eligible expenditure, grant receipts and forecast. The second shows milestone status and delayed dependencies. The third shows core outputs and outcomes against baseline and target. The fourth shows open risks, changes and funder decisions. The fifth shows evidence gaps and overdue actions.

The Cabinet Office Model Grant Funding Agreement illustrates central government provisions for monitoring, financial reporting and performance measures. The live agreement determines the recipient's mandatory fields.

Connect source records

Use project IDs shared by the ledger, work plan and evidence register. Automate imports only after manual definitions are sound. Reconcile totals and test a sample back to invoices, bank records or accepted outputs.

Show last refresh time and data completeness. Never present a stale tile as current. Preserve the source extract used for an issued report so later system changes do not rewrite history.

Make status meaningful

Define green, amber and red with numeric or observable criteria. For example, amber might mean a milestone forecast outside internal tolerance but still within the agreement date. Red might mean the contractual date is threatened or approval is required.

Do not average red exceptions into a favourable overall score. Display the highest material risk and its owner.

Separate change from impact

Outcome movement belongs on the dashboard, but causality needs more evidence. The Quality in Policy Impact Evaluation guidance explains that monitoring change does not establish that an intervention caused it.

Label outputs, observed outcomes and evaluated impacts separately. Where no strong comparison exists, use contribution language and record alternative explanations.

Protect information

Apply access controls, secure sharing and retention rules. Consult the ICO guidance hub where personal data is processed. Avoid exporting identifiable rows into presentation files.

Test dashboard failure

Choose several known edge cases before launch: a credit note, delayed supplier, duplicated participant, missing baseline and approved budget change. Confirm that each produces the right calculation and visible exception. Test access with an ordinary user account as well as the administrator.

Document what happens when a source file is late or malformed. The dashboard should preserve the last valid value, mark it stale and alert its owner rather than quietly replacing it with zero. Reconcile automated totals after any formula, field or data-source change.

Keep a manual recovery route for a reporting deadline, including the authorised source extracts and calculation instructions. Do not let dependence on one dashboard remove the underlying audit trail.

Review before release

Have owners certify their figures, finance reconcile money and an independent reviewer test calculations. Store the released dashboard, date, reviewer and corrections.

Remove a tile when it no longer informs a decision or obligation. This draft contains no live internal links and remains on hold for data, finance and agreement review.

Before you act

List the decisions expected from each audience.
Create an indicator dictionary with formula, unit, source and owner.
Connect source records using shared project IDs.
Define green, amber and red with numeric criteria.
Test edge cases such as credit notes and missing baselines.
Have owners certify figures and an independent reviewer test calculations.

Common questions

What should a grant dashboard show instead of decorating a status meeting?

It should expose decisions and exceptions. Build it from controlled source records and give every figure a definition, owner, date and route to evidence. The dashboard supports formal reporting but does not replace the authorised form or evidence.

How should status colours be defined and used?

What should happen when a source file is late or malformed?

The dashboard should preserve the last valid value, mark it stale and alert its owner rather than quietly replacing it with zero. Reconcile automated totals after any formula, field or data-source change. Keep a manual recovery route for a reporting deadline.