What Should a Dashboard Say About Data Coverage?
From the earlier reference collection. Read the current software blog.
Coverage notes tell readers which locations, dates, and fields are represented and which gaps or exclusions could affect interpretation.
Name the represented locations and dates
A dashboard should state the geographic and time coverage of the data it displays. “Current readings” is vague if only some locations report regularly or if the page omits older observations. Name the included sites or explain how readers can see the list, and give the period covered by the view.
For instance, a map might show 12 reporting stations across a region, with observations from 08:00 through 10:00 local time. That tells readers what is represented and helps them avoid assuming that the same coverage applies to every part of the map. If the displayed period is selected by a filter, make the start and end dates visible.
Describe fields and completeness
Coverage applies to fields as well as places and dates. A dataset may include a timestamp and location for every record but lack a measurement for some records. Explain which fields are present and whether missing values are common or concentrated in a particular period. Distinguish zero from missing so readers do not mistake an absence of observations for a true zero.
Useful summaries can include the number of reporting locations, the number of expected observations, and the number received, when those counts are available. For example, “18 of 20 stations reported this hour” gives a different picture from a map that simply shows 18 dots. Avoid presenting a percentage without saying what the denominator represents.
Call out exclusions and known gaps
If certain locations, dates, or record types are excluded, say why and how that affects interpretation. A sensor under maintenance, a source that publishes only weekdays, or a field removed during validation can change what a total means. State whether the exclusion is temporary or part of the dataset’s scope when that is known.
Keep this note close to the chart, map, or metric it affects. A general “data may be incomplete” footer is too broad to help someone decide whether a particular comparison is sound. Link to fuller documentation for detailed inclusion rules, while keeping the immediate limitation readable.
Help readers judge fitness for use
Coverage information lets readers decide whether the dashboard supports their question. A regional trend based on a stable set of stations may be comparable across months; a trend with changing locations may need qualification. Reporting locations, dates, fields, and exclusions makes those boundaries visible and helps prevent a partial view from being mistaken for a complete one.