How do you build a useful grant dashboard?

Build a grant dashboard by choosing a decision, defining the measures and showing the period, coverage and source behind each view. Add a map when location helps answer the question. Keep counts, rates and geographic meaning distinct, and provide a readable table so people can check the results without relying on the graphic alone.

By Sopact Academy · Reviewed September 12, 2026. This lesson combines cited public guidance with practical workflow recommendations. Figures and teaching scenarios are illustrative unless explicitly identified as a published case.

Choose the question before the chart

A program team may need to identify overdue reports. A portfolio lead may need to compare funding coverage across places. A board may need a concise view of progress and uncertainty. These are different tasks and should not all be squeezed into the same crowded screen.

Write the question at the top of the specification. Choose the few measures that help answer it, then identify the detail a reader may need to inspect. A decorative map is not useful if the question is simply which three reports need follow-up.

Build from defined measures

For every indicator, record the numerator, denominator where relevant, period, included records and source. Use the same definitions as the reporting workflow. A dashboard should not introduce a second definition of “completed” or “active” without explanation.

Show when the data was refreshed and which period it describes. “Updated today” may mean an older report was imported today, not that the underlying outcomes were measured today.

Worked example: a count and a rate tell different stories

Use this fictional example. Area A has 60 reported employment outcomes among 100 people with known status; Area B has 36 among 60. Both have a 60% rate among known results, even though their counts differ.

A chart of counts would show Area A higher. A chart of rates would show equal values. Neither alone describes the full picture, and neither establishes that location caused the result.

For only two areas, a labeled comparison is easier to read than a map. Keep the geographic view for questions where the spatial pattern adds useful information.

Define what a location means

An organization’s headquarters, a service site and a participant’s residence are different geographies. A grant to an organization based in one city may serve people across several regions.

Choose the geography that fits the question and label it clearly. Date location changes and retain the location applicable to the observation period; today’s address must not silently replace a historical service location. Do not present headquarters as service reach. If the evidence supports only headquarters, state that limit.

For grants serving multiple places, choose and document an allocation rule. A grant counted in every served region can make regional counts exceed the portfolio’s distinct grant total. That can be legitimate if clearly described, but it must not look like a deduplicated total.

Choose a map that matches the measure

The ONS guidance on choropleth maps recommends standardized rates rather than absolute values for shaded-area maps. It also advises against using a map for only a few areas. Apply those principles when deciding whether geography adds value.

For a map, specify the boundary version, measure, legend, classification and missing-data treatment. Keep categories consistent when readers compare periods, or explain changes that affect the colors.

Do not treat an unshaded region as zero unless the data actually establishes zero. It may mean no record, insufficient coverage, suppressed information or a place outside the scope. Give these states clear labels.

Handle small groups and sensitive locations

Decide what detail each audience needs. Public maps may require broader geographic aggregation and rules for small groups. Do not expose precise participant locations merely because they are available in an internal record.

Agree suppression and access rules with the responsible data owner. Check combinations of filters as well as the default view: a broad dashboard can reveal a very small group after several selections.

When values are withheld, explain the display state without revealing the hidden value through another total, tooltip or download. Review the whole experience, not only the map layer.

Use filters that preserve context

Show the selected program, period, population and geography near the results. Make it easy to reset filters. A screenshot of a chart should not lose the information needed to interpret it.

When a filter changes the denominator, update both the result and its coverage label. A portfolio-wide percentage should not remain visible beside a table filtered to one program unless the distinction is explicit.

Check empty results, missing values and incompatible combinations. “No matching records” is different from “zero outcomes.” Give the reader a useful explanation rather than a blank chart.

Provide a readable alternative to the graphic

W3C’s guidance for complex images calls for text alternatives that convey the information in charts and diagrams. Provide a concise explanation and a table of the relevant values. Do not rely on color or hover alone.

Use clear labels, sufficient contrast and keyboard-accessible controls. Test at laptop and mobile widths, including horizontal tables. The reader should be able to identify the selected filter, move through controls and access the supporting data.

The table does not need to duplicate every underlying record publicly. It should provide an appropriate accessible equivalent of the displayed information while respecting the audience’s access.

Connect the view to the evidence

In a configured Sopact workflow, the same linked records can support recurring reporting questions and visual summaries. Confirm the available dashboard, mapping and export capabilities for your implementation rather than assuming a particular map component is included.

Keep the measure definitions and source relationships available. A reviewer should be able to move from a displayed result to the relevant authorized evidence or an indexed review packet.

Use this specification prompt before building:

Test the dashboard before sharing

Reconcile the default view to the source register. Test one filtered view manually. Verify that duplicates, exclusions and missing records are handled under the declared rules.

Check the refresh date and confirm what happens when a source changes. Preserve a dated snapshot when the dashboard supports a board or funder decision, so later updates do not obscure what was reviewed.

Ask a colleague to answer the original question using only the view and its supporting explanation. If they confuse count with rate, headquarters with service area or missing with zero, revise the labels and structure.

Course exercise: one question from collection to decision

Choose one grant-round question. Define the collection fields, connect the source documents, apply the review rules and prepare a short board summary with a supporting visual.

Introduce one missing report, one approved amendment and one changed measure definition. Confirm that those conditions remain visible throughout the workflow instead of disappearing in the final chart.

Pass condition: another person can explain the result, inspect its limits and trace it to the relevant source. The visual makes the evidence easier to understand without making it look more certain.

Frequently asked questions

What should a grant dashboard show?

Show the measures needed for a defined decision, with their period, scope, coverage and source. Keep supporting detail available without crowding the main view.

When is a grant map useful?

Use a map when a spatial pattern helps answer the question. For a few areas or a simple ranking, a labeled table or chart may be clearer.

Can headquarters be used as service location?

Only if the view explicitly represents headquarters. Do not label it service reach when the organization works across other places.

Should shaded-area maps show counts or rates?

Standardized rates are generally appropriate for choropleth comparisons. Choose the visual according to the measure and explain the denominator and coverage.

How should missing geographic data appear?

Label it separately from zero and from areas outside scope. Do not invent locations or imply absence of activity from an absent record.

Does a dashboard need a table?

Provide an accessible equivalent of the displayed information, such as a clear summary and relevant table. Do not make color or hover the only way to understand it.

Apply the course to one real workflow

Use the dashboard alongside the collection and review records that support it. Start with one program and one recurring decision, then improve the definitions, collection and review process before expanding.

Return to your course overview or explore Applications & Grants. For presentation support, use the impact report writing ebook and example reports.