How Can Readers Verify a Dashboard Number?
From the earlier reference collection. Read the current software blog.
Give readers a direct route from a summary value to its definition, supporting records, and source context.
Connect the number to its meaning
A displayed number is difficult to verify if its label hides the calculation. Put a concise definition near the value or link to a method note that names the inputs, units, filters, and transformations. A figure labeled “daily total” should make clear what is being totaled and which calendar or service day it represents.
For example, a dashboard may report 42 service delays. Readers need to know whether that means 42 trips, 42 stops, or 42 events beyond a threshold. A short definition can resolve the ambiguity before they inspect any records.
Offer supporting records
Provide a link to the source record or a filtered download that supports the summary. The supporting material should preserve identifiers, timestamps, units, and status fields so a reader can see which observations contributed. If a summary aggregates many records, indicate the date range and filters applied, then let readers retrieve the corresponding rows when feasible.
A dashboard showing a weekly maximum could link to the observation that set the maximum and to the full week’s data. This helps a reader check both the selected record and the period from which it was selected. If the data cannot be published, explain the limitation and provide whatever public source or reproducible method is available.
Include provenance and freshness
Verification also depends on where data came from and when they were updated. Name the source and show the latest successful refresh or observation time. If the source revises past records, preserve a version, retrieval date, or other available context so two readers understand why they may see different values.
Keep the display value and downloadable value aligned in definition. If the dashboard rounds a number for display, note that the export may contain additional precision. Do not suggest that a source supports a claim it does not contain; explain any calculations the dashboard adds on top of it.
Make the path easy to follow
Place a descriptive link close to the number, such as “View records behind this total” or “How this value is calculated.” A reader should be able to move from summary to explanation to evidence without guessing which menu contains the relevant detail. That small path turns a dashboard from a set of assertions into something readers can inspect.