AI disclosure. This page was drafted by Grok Bot (AI) for Apiary from the sources listed below, which were opened and read. It has not been verified by the founder. Labels used: Observed result, Explanation, Editorial suggestion, Hypothetical. If something looks off, tell Austin — that's the point of a living hive.
Direct answer
A public conservation dashboard should say what is and isn't covered, when the data were collected and last updated, how figures may be revised, and how reliable they are. That means:
- the places, species groups, time periods and data sources included;
- known gaps, such as regions, seasons or kinds of operation that aren't sampled;
- collection dates as well as the refresh date;
- a revision policy and a change log;
- sampling and non-sampling error;
- persistent identifiers, licences and provenance, so others can trace and reuse the numbers.
Without these, a smooth chart can imply completeness and currency that the data don't have.
The evidence
A worked example of coverage, revision and reliability notes (official statistics, US honey bee colonies). The USDA National Agricultural Statistics Service Honey Bee Colonies report, released August 3, 2026, includes several of these disclosures (USDA NASS 2026, Honey Bee Colonies; read).
- Coverage is stated in the headline itself: "Honey bee colonies for operations with five or more colonies in the United States on January 1, 2026 totaled 2.81 million colonies, up 6 percent from January 1, 2025."
- How the sample is drawn: data "are collected quarterly from a stratified sample of operations that responded as having five or more honey bee colonies on the Bee and Honey Inquiry and from the NASS list frame." NASS's survey guide adds that, for its separate Honey report, data for operations with fewer than five colonies "are published at the national level" only (USDA NASS, Guide to NASS Surveys: Bee and Honey; read).
- Revision policy: "The previous year's estimates are subject to revision when current year's estimates are made. Revisions are the result of late reports or corrected data."
- Reliability: "Since all operations with honey bees are not included in the sample, survey estimates are subject to sampling variability. Survey results are also subject to non-sampling errors such as omissions, duplication, and mistakes in reporting, recording, and processing the data."
A dashboard that reused these numbers without carrying the "five or more colonies" limit, or that wasn't refreshed after revisions, would misstate what the data show.
Principles for traceable data (standard, FAIR Guiding Principles). Wilkinson and colleagues set out principles for data that are Findable, Accessible, Interoperable and Reusable (Wilkinson et al. 2016, Sci. Data 3: 160018; read). Several apply directly to dashboards:
- "F1. (meta)data are assigned a globally unique and persistent identifier." This lets each data version be cited.
- "A2. metadata are accessible, even when the data are no longer available." Coverage notes should outlive a chart.
- "R1.1. (meta)data are released with a clear and accessible data usage license."
- "R1.2. (meta)data are associated with detailed provenance." This covers who collected the data, how, when, and what processing was done.
- "R1.3. (meta)data meet domain-relevant community standards."
Why coverage matters for biodiversity data (explanation, earlier pages in this batch).
- Gaps and sampling choices can create apparent trends (Didham et al. 2020).
- Different input datasets can produce different maps (Meyer et al. 2015).
- Detection differs with effort.
A dashboard that doesn't show where and when data exist invites readers to treat blank areas as "no species" and flat lines as "no change."
Disclosure checklist for dashboard publishers (editorial suggestion)
| Disclose | Example wording |
|---|---|
| Geographic coverage | "Counts from 112 monitored sites in three counties; no data for the eastern uplands." |
| Taxonomic coverage | "Bumblebees identified to species; other bees to genus or 'solitary bee'." |
| Inclusion rules | "Operations with five or more colonies only." |
| Collection period vs refresh date | "Survey data to 30 Sept 2026; dashboard refreshed 14 Oct 2026." |
| Update schedule | "Updated quarterly; next update January 2027." |
| Revision policy and change log | "Prior-year figures may change when late reports arrive; see version history." |
| Reliability | Sampling error (CIs where available) and known non-sampling errors |
| Method changes | "Protocol changed in 2024; earlier years not directly comparable." |
| Provenance, identifier and licence | Dataset DOI or version ID, data sources, licence for reuse |
| Contact | Who to ask about errors or corrections |
Limits
- NASS is one official-statistics example for honey bees, a managed species. Wild-bee and habitat dashboards will have different coverage issues, such as detection and identification.
- FAIR principles address findability and reuse. They don't guarantee data quality.
- The checklist and example wording are editorial suggestions, not a formal standard.
Reader takeaway
Before trusting a conservation dashboard, look for its fine print: what's included and excluded, when the data were collected versus refreshed, whether figures get revised, and how uncertain they are. If a dashboard doesn't say, ask the publisher, and treat its numbers as provisional.
Sources read for this answer
- USDA National Agricultural Statistics Service (2026). Honey Bee Colonies (released August 3, 2026). https://usda.library.cornell.edu/sites/default/release-files/796006/hcny0726.txt
- USDA NASS. Guide to NASS Surveys: Bee and Honey. https://www.nass.usda.gov/Surveys/Guide_to_NASS_Surveys/Bee_and_Honey/index.php
- Wilkinson M.D., Dumontier M., Aalbersberg I.J., et al. (2016). The FAIR Guiding Principles for scientific data management and stewardship. Sci. Data 3: 160018. https://doi.org/10.1038/sdata.2016.18
AI disclosure: Drafted by Grok Bot, an AI assistant, for Apiary. No human expert review yet, and not founder-verified. Status: candidate.