What Dashboards Should Show

Executive frame

The public value of a long-form policy article lies less in confident tone than in a source path that another careful reader can reproduce. What Dashboards Should Show applies that discipline to a field in which operational monitoring, public accountability, exploratory signal, official statistic, and performance judgment are easily conflated. A public dashboard should expose definitions, denominators, cohorts, time, severity, uncertainty, missingness, revisions, workflow stages, distribution, targets, and download metadata—not merely attractive totals and rankings. This is not a plea for indecision. It is a method for making conclusions strong enough to survive a later document, a revised dataset, a different denominator, or a skeptical reader who follows every link.

The governing sequence for What Dashboards Should Show is source systems → extraction → transformation → quality checks → metric computation → visualization → release → revision and archive. Each arrow represents a possible change in actor, legal authority, evidence threshold, time period, and available remedy. A report that starts at the final visible event and works backward may miss a screening rule, a confidential stage, a superseding order, a data transformation, or an implementation choice. The safer method builds the chronology first, labels each document by function, and only then asks what conclusion the assembled record supports.

The evidence framework is deliberately plural. For What Dashboards Should Show, binding statutes and regulations may answer what an institution is authorized or required to do; final orders and judicial decisions may determine a particular dispute; official guidance may explain present administration; datasets may reveal patterns; and original policy analysis may propose reform. Those categories can inform one another, but they are not interchangeable. Every recommendation in this article is presented as analysis rather than disguised as law, and every legal proposition is confined to the jurisdiction and status of its cited source.

Measurement requires the same restraint. The relevant indicators include volume, rates, cohorts, age, tail delay, severity, geography, subgroup where valid, target, uncertainty, missingness, revision history, and data freshness. No single number captures all of them. Counts can rise because the underlying problem worsened, because reporting improved, because jurisdiction expanded, because staffing changed, or because a backlog was cleared. Rates can also mislead if the numerator, denominator, observation period, case definition, and population coverage do not match. A defensible article makes these design choices visible instead of allowing a graph to imply comparability.

The stakes are not symmetrical but they are connected: a dashboard can create false precision, invite invalid comparisons, hide queues behind totals, and make corrected data impossible to trace. Public protection, professional fairness, institutional learning, and accurate information are therefore not competing decorations. They are interacting conditions of a legitimate system. A procedure that is fast but routinely wrong can create new harm; a procedure that is meticulous but indefinitely delayed can also fail the public. The task is to identify which safeguards fit the consequence and which evidence can test whether they work.

This article's reform position is metric cards with definitions and denominators, downloadable data, version history, accessibility, privacy review, annotations, and clear ownership for corrections. The proposal is intentionally testable. It implies named owners, a documented source chain, reviewable decision rules, a correction path, and outcome measures that extend beyond institutional activity. It also implies humility about evidence that cannot yet answer the question. Where the record is incomplete, the appropriate sentence describes the gap and the next verification step; it does not fill the gap with certainty.

Definitions and source hierarchy

In What Dashboards Should Show, a fact is a proposition supported by a source competent to establish it; an allegation is a claim not yet accepted as true by the relevant decision-maker; a finding is a determination made through an authorized process; an inference is a reasoned conclusion drawn from facts; and a recommendation states what an institution should do. Using those labels is not semantic fussiness. The label tells the reader how much reliance the sentence can bear and what later event would require revision.

A primary source for What Dashboards Should Show is the instrument or record closest to the asserted authority or event: enacted text, adopted regulation, operative order, actual opinion, originating dataset, official transcript, or underlying study. An official summary can be useful, especially for navigation, but it should not silently replace the controlling text when wording, exceptions, dates, or procedural posture matter. A secondary source can add context and critique; it cannot cure failure to inspect the source on which the core claim depends.

A scope limit states what a source does not establish. In What Dashboards Should Show, scope may be limited by jurisdiction, population, agency program, profession, time, data coverage, procedural stage, or technology version. Scope limits belong next to the claim because readers rarely carry a caveat forward from a distant methodology section. When a source supplies an important but narrow result, the article should preserve that narrowness even if a broader sentence would sound more decisive.

A correction path is the practical route by which a person or institution can identify an error, submit contrary evidence, obtain a reasoned response, and repair downstream uses. For What Dashboards Should Show, correction is part of accuracy rather than an afterthought. The original version, date, data or document source, change, reason, and propagation step should be retained. Otherwise a silent overwrite can improve the originating page while leaving derivative reports, search results, decisions, or personal harm untouched.

Naming the dashboard's decisions and users

This dimension is best approached as a verification problem. For naming the dashboard's decisions and users within What Dashboards Should Show, the reporter or decision-maker should identify the actor, the power being exercised, the information available at that moment, and the consequence of error. The central boundary remains operational monitoring, public accountability, exploratory signal, official statistic, and performance judgment. The distinction has practical consequences for sourcing and language. A term that is appropriate at one point in the sequence—source systems → extraction → transformation → quality checks → metric computation → visualization → release → revision and archive—may become inaccurate after the record advances, or may never have described the authority of the actor who issued it.

U.S. Government Accountability Office — Standards for Internal Control in the Federal Government (Green Book) provides the first official anchor for naming the dashboard's decisions and users: GAO's 2025 Green Book revision sets federal internal-control principles concerning objectives, risks, information, monitoring, and corrective action, effective beginning in fiscal year 2026. Its legal or evidentiary weight must remain visible. The Green Book applies directly within its federal scope and is a useful benchmark elsewhere; it is not a universal state-agency statute. For What Dashboards Should Show, the source supports a bounded proposition, not a universal conclusion. The link should be opened, the current version and date confirmed, and the relevant language read in context before it is converted into a declarative sentence.

Chronology is the simplest protection against assigning a later meaning to an earlier document. For naming the dashboard's decisions and users, record the source creator, date, jurisdiction, version, procedural stage, population, quoted or coded field, and any later modification. Map that evidence to source systems → extraction → transformation → quality checks → metric computation → visualization → release → revision and archive. If interviews conflict, say which proposition each person is competent to establish and seek documents that can resolve the conflict. If material information is confidential or unavailable, describe the access limit and narrow the conclusion; absence from a public database is not proof that an event did not occur.

The metric design is part of the substantive argument. In What Dashboards Should Show, candidate measures include volume, rates, cohorts, age, tail delay, severity, geography, subgroup where valid, target, uncertainty, missingness, revision history, and data freshness. For naming the dashboard's decisions and users, specify whether the number is a stock or flow, whether cases belong to an intake or disposition cohort, which time clock is used, and how duplicates, revisions, missing records, small cells, and changes in reporting rules are handled. A trend should be tested against changes in jurisdiction, staffing, technology, and ascertainment before it is described as a change in underlying risk or performance.

Operational discipline matters more than a generic promise of oversight. For naming the dashboard's decisions and users, name the decision owner, evidence threshold, unresolved question, exception route, review date, and correction mechanism. The analysis should test for the specific harm that a dashboard can create false precision, invite invalid comparisons, hide queues behind totals, and make corrected data impossible to trace. It should also ask whether an apparent efficiency merely transfers burden to patients, professionals, families, another agency, or a less visible part of the system. The preferred direction—metric cards with definitions and denominators, downloadable data, version history, accessibility, privacy review, annotations, and clear ownership for corrections—is credible only if affected people can understand the rule, present contrary information, and see whether outcomes improve.

Metric definitions beside the chart

The first task is classification. For metric definitions beside the chart within What Dashboards Should Show, the reporter or decision-maker should identify the actor, the power being exercised, the information available at that moment, and the consequence of error. The central boundary remains operational monitoring, public accountability, exploratory signal, official statistic, and performance judgment. The distinction has practical consequences for sourcing and language. A term that is appropriate at one point in the sequence—source systems → extraction → transformation → quality checks → metric computation → visualization → release → revision and archive—may become inaccurate after the record advances, or may never have described the authority of the actor who issued it.

HHS — Information Quality Guidelines provides the first official anchor for metric definitions beside the chart: HHS publishes guidelines for quality, objectivity, utility, integrity, and correction of information it disseminates. Its legal or evidentiary weight must remain visible. The guidelines apply within their defined federal information-quality framework and do not create a universal private right to correction. For What Dashboards Should Show, the source supports a bounded proposition, not a universal conclusion. The link should be opened, the current version and date confirmed, and the relevant language read in context before it is converted into a declarative sentence.

Verification improves when the evidence is arranged by function instead of drama. For metric definitions beside the chart, record the source creator, date, jurisdiction, version, procedural stage, population, quoted or coded field, and any later modification. Map that evidence to source systems → extraction → transformation → quality checks → metric computation → visualization → release → revision and archive. If interviews conflict, say which proposition each person is competent to establish and seek documents that can resolve the conflict. If material information is confidential or unavailable, describe the access limit and narrow the conclusion; absence from a public database is not proof that an event did not occur.

A numerical comparison needs a population and a mechanism, not merely two totals. In What Dashboards Should Show, candidate measures include volume, rates, cohorts, age, tail delay, severity, geography, subgroup where valid, target, uncertainty, missingness, revision history, and data freshness. For metric definitions beside the chart, specify whether the number is a stock or flow, whether cases belong to an intake or disposition cohort, which time clock is used, and how duplicates, revisions, missing records, small cells, and changes in reporting rules are handled. A trend should be tested against changes in jurisdiction, staffing, technology, and ascertainment before it is described as a change in underlying risk or performance.

The response should be proportionate to both uncertainty and consequence. For metric definitions beside the chart, name the decision owner, evidence threshold, unresolved question, exception route, review date, and correction mechanism. The analysis should test for the specific harm that a dashboard can create false precision, invite invalid comparisons, hide queues behind totals, and make corrected data impossible to trace. It should also ask whether an apparent efficiency merely transfers burden to patients, professionals, families, another agency, or a less visible part of the system. The preferred direction—metric cards with definitions and denominators, downloadable data, version history, accessibility, privacy review, annotations, and clear ownership for corrections—is credible only if affected people can understand the rule, present contrary information, and see whether outcomes improve.

Denominators and population coverage

The first task is classification. For denominators and population coverage within What Dashboards Should Show, the reporter or decision-maker should identify the actor, the power being exercised, the information available at that moment, and the consequence of error. The central boundary remains operational monitoring, public accountability, exploratory signal, official statistic, and performance judgment. Once the stage is named, the evidentiary burden becomes clearer. A term that is appropriate at one point in the sequence—source systems → extraction → transformation → quality checks → metric computation → visualization → release → revision and archive—may become inaccurate after the record advances, or may never have described the authority of the actor who issued it.

Data.gov — DCAT-US dataset metadata standard provides the first official anchor for denominators and population coverage: DCAT-US defines metadata fields that support dataset discovery, ownership, temporal coverage, update frequency, access, and other provenance information. Its legal or evidentiary weight must remain visible. Metadata improves interpretability but does not validate the underlying observations, eliminate missingness, or establish causal meaning. For What Dashboards Should Show, the source supports a bounded proposition, not a universal conclusion. The link should be opened, the current version and date confirmed, and the relevant language read in context before it is converted into a declarative sentence.

The underlying record should then be reconstructed forward rather than narrated backward from the outcome. For denominators and population coverage, record the source creator, date, jurisdiction, version, procedural stage, population, quoted or coded field, and any later modification. Map that evidence to source systems → extraction → transformation → quality checks → metric computation → visualization → release → revision and archive. If interviews conflict, say which proposition each person is competent to establish and seek documents that can resolve the conflict. If material information is confidential or unavailable, describe the access limit and narrow the conclusion; absence from a public database is not proof that an event did not occur.

Quantification becomes useful only after the unit of analysis is fixed. In What Dashboards Should Show, candidate measures include volume, rates, cohorts, age, tail delay, severity, geography, subgroup where valid, target, uncertainty, missingness, revision history, and data freshness. For denominators and population coverage, specify whether the number is a stock or flow, whether cases belong to an intake or disposition cohort, which time clock is used, and how duplicates, revisions, missing records, small cells, and changes in reporting rules are handled. A trend should be tested against changes in jurisdiction, staffing, technology, and ascertainment before it is described as a change in underlying risk or performance.

The most credible reform is one that an external reviewer can test. For denominators and population coverage, name the decision owner, evidence threshold, unresolved question, exception route, review date, and correction mechanism. The analysis should test for the specific harm that a dashboard can create false precision, invite invalid comparisons, hide queues behind totals, and make corrected data impossible to trace. It should also ask whether an apparent efficiency merely transfers burden to patients, professionals, families, another agency, or a less visible part of the system. The preferred direction—metric cards with definitions and denominators, downloadable data, version history, accessibility, privacy review, annotations, and clear ownership for corrections—is credible only if affected people can understand the rule, present contrary information, and see whether outcomes improve.

Cohorts, stocks, and flows

The first task is classification. For cohorts, stocks, and flows within What Dashboards Should Show, the reporter or decision-maker should identify the actor, the power being exercised, the information available at that moment, and the consequence of error. The central boundary remains operational monitoring, public accountability, exploratory signal, official statistic, and performance judgment. The distinction has practical consequences for sourcing and language. A term that is appropriate at one point in the sequence—source systems → extraction → transformation → quality checks → metric computation → visualization → release → revision and archive—may become inaccurate after the record advances, or may never have described the authority of the actor who issued it.

Federal Data Strategy — Practices provides the first official anchor for cohorts, stocks, and flows: The Federal Data Strategy organizes practices concerning governance, quality, access, protection, use, and learning across the data lifecycle. Its legal or evidentiary weight must remain visible. The practices are a federal governance framework, not a substitute for program statutes, privacy rules, statistical standards, or local validation. For What Dashboards Should Show, the source supports a bounded proposition, not a universal conclusion. The link should be opened, the current version and date confirmed, and the relevant language read in context before it is converted into a declarative sentence.

Verification improves when the evidence is arranged by function instead of drama. For cohorts, stocks, and flows, record the source creator, date, jurisdiction, version, procedural stage, population, quoted or coded field, and any later modification. Map that evidence to source systems → extraction → transformation → quality checks → metric computation → visualization → release → revision and archive. If interviews conflict, say which proposition each person is competent to establish and seek documents that can resolve the conflict. If material information is confidential or unavailable, describe the access limit and narrow the conclusion; absence from a public database is not proof that an event did not occur.

The relevant denominator follows the exposure that could actually produce the event. In What Dashboards Should Show, candidate measures include volume, rates, cohorts, age, tail delay, severity, geography, subgroup where valid, target, uncertainty, missingness, revision history, and data freshness. For cohorts, stocks, and flows, specify whether the number is a stock or flow, whether cases belong to an intake or disposition cohort, which time clock is used, and how duplicates, revisions, missing records, small cells, and changes in reporting rules are handled. A trend should be tested against changes in jurisdiction, staffing, technology, and ascertainment before it is described as a change in underlying risk or performance.

A publication-ready treatment should end with an accountable next step. For cohorts, stocks, and flows, name the decision owner, evidence threshold, unresolved question, exception route, review date, and correction mechanism. The analysis should test for the specific harm that a dashboard can create false precision, invite invalid comparisons, hide queues behind totals, and make corrected data impossible to trace. It should also ask whether an apparent efficiency merely transfers burden to patients, professionals, families, another agency, or a less visible part of the system. The preferred direction—metric cards with definitions and denominators, downloadable data, version history, accessibility, privacy review, annotations, and clear ownership for corrections—is credible only if affected people can understand the rule, present contrary information, and see whether outcomes improve.

Time trends and data freshness

The analysis should begin with the decision actually being made. For time trends and data freshness within What Dashboards Should Show, the reporter or decision-maker should identify the actor, the power being exercised, the information available at that moment, and the consequence of error. The central boundary remains operational monitoring, public accountability, exploratory signal, official statistic, and performance judgment. This framing prevents an early signal from acquiring the force of a final conclusion. A term that is appropriate at one point in the sequence—source systems → extraction → transformation → quality checks → metric computation → visualization → release → revision and archive—may become inaccurate after the record advances, or may never have described the authority of the actor who issued it.

Centers for Medicare & Medicaid Services — Data and Research provides the first official anchor for time trends and data freshness: CMS organizes program datasets, research resources, statistics, and data documentation across Medicare, Medicaid, CHIP, Marketplace, and other programs. Its legal or evidentiary weight must remain visible. Each dataset has its own population, lag, suppression, coding, and completeness constraints; CMS data do not automatically represent the entire U.S. health system. For What Dashboards Should Show, the source supports a bounded proposition, not a universal conclusion. The link should be opened, the current version and date confirmed, and the relevant language read in context before it is converted into a declarative sentence.

The underlying record should then be reconstructed forward rather than narrated backward from the outcome. For time trends and data freshness, record the source creator, date, jurisdiction, version, procedural stage, population, quoted or coded field, and any later modification. Map that evidence to source systems → extraction → transformation → quality checks → metric computation → visualization → release → revision and archive. If interviews conflict, say which proposition each person is competent to establish and seek documents that can resolve the conflict. If material information is confidential or unavailable, describe the access limit and narrow the conclusion; absence from a public database is not proof that an event did not occur.

A numerical comparison needs a population and a mechanism, not merely two totals. In What Dashboards Should Show, candidate measures include volume, rates, cohorts, age, tail delay, severity, geography, subgroup where valid, target, uncertainty, missingness, revision history, and data freshness. For time trends and data freshness, specify whether the number is a stock or flow, whether cases belong to an intake or disposition cohort, which time clock is used, and how duplicates, revisions, missing records, small cells, and changes in reporting rules are handled. A trend should be tested against changes in jurisdiction, staffing, technology, and ascertainment before it is described as a change in underlying risk or performance.

A publication-ready treatment should end with an accountable next step. For time trends and data freshness, name the decision owner, evidence threshold, unresolved question, exception route, review date, and correction mechanism. The analysis should test for the specific harm that a dashboard can create false precision, invite invalid comparisons, hide queues behind totals, and make corrected data impossible to trace. It should also ask whether an apparent efficiency merely transfers burden to patients, professionals, families, another agency, or a less visible part of the system. The preferred direction—metric cards with definitions and denominators, downloadable data, version history, accessibility, privacy review, annotations, and clear ownership for corrections—is credible only if affected people can understand the rule, present contrary information, and see whether outcomes improve.

Severity and case mix

The strongest account begins by identifying the operative record. For severity and case mix within What Dashboards Should Show, the reporter or decision-maker should identify the actor, the power being exercised, the information available at that moment, and the consequence of error. The central boundary remains operational monitoring, public accountability, exploratory signal, official statistic, and performance judgment. Once the stage is named, the evidentiary burden becomes clearer. A term that is appropriate at one point in the sequence—source systems → extraction → transformation → quality checks → metric computation → visualization → release → revision and archive—may become inaccurate after the record advances, or may never have described the authority of the actor who issued it.

National Practitioner Data Bank — Public Use Data File provides the first official anchor for severity and case mix: NPDB provides a de-identified public-use file for statistical analysis of report types and actions, with stated update dates and documentation. Its legal or evidentiary weight must remain visible. The public file cannot identify individuals, and one row or report should not automatically be treated as one practitioner, one event, or proof of wrongdoing. For What Dashboards Should Show, the source supports a bounded proposition, not a universal conclusion. The link should be opened, the current version and date confirmed, and the relevant language read in context before it is converted into a declarative sentence.

A reproducible account preserves both the source and the transformation applied to it. For severity and case mix, record the source creator, date, jurisdiction, version, procedural stage, population, quoted or coded field, and any later modification. Map that evidence to source systems → extraction → transformation → quality checks → metric computation → visualization → release → revision and archive. If interviews conflict, say which proposition each person is competent to establish and seek documents that can resolve the conflict. If material information is confidential or unavailable, describe the access limit and narrow the conclusion; absence from a public database is not proof that an event did not occur.

The relevant denominator follows the exposure that could actually produce the event. In What Dashboards Should Show, candidate measures include volume, rates, cohorts, age, tail delay, severity, geography, subgroup where valid, target, uncertainty, missingness, revision history, and data freshness. For severity and case mix, specify whether the number is a stock or flow, whether cases belong to an intake or disposition cohort, which time clock is used, and how duplicates, revisions, missing records, small cells, and changes in reporting rules are handled. A trend should be tested against changes in jurisdiction, staffing, technology, and ascertainment before it is described as a change in underlying risk or performance.

The practical safeguard is a visible decision trail. For severity and case mix, name the decision owner, evidence threshold, unresolved question, exception route, review date, and correction mechanism. The analysis should test for the specific harm that a dashboard can create false precision, invite invalid comparisons, hide queues behind totals, and make corrected data impossible to trace. It should also ask whether an apparent efficiency merely transfers burden to patients, professionals, families, another agency, or a less visible part of the system. The preferred direction—metric cards with definitions and denominators, downloadable data, version history, accessibility, privacy review, annotations, and clear ownership for corrections—is credible only if affected people can understand the rule, present contrary information, and see whether outcomes improve.

Distribution and small-number protection

This dimension is best approached as a verification problem. For distribution and small-number protection within What Dashboards Should Show, the reporter or decision-maker should identify the actor, the power being exercised, the information available at that moment, and the consequence of error. The central boundary remains operational monitoring, public accountability, exploratory signal, official statistic, and performance judgment. Once the stage is named, the evidentiary burden becomes clearer. A term that is appropriate at one point in the sequence—source systems → extraction → transformation → quality checks → metric computation → visualization → release → revision and archive—may become inaccurate after the record advances, or may never have described the authority of the actor who issued it.

CDC Field Epidemiology Manual — Describing epidemiologic data provides the first official anchor for distribution and small-number protection: CDC explains that rates and proportions relate event counts to an appropriate population and time, allowing more meaningful comparisons than raw counts. Its legal or evidentiary weight must remain visible. The numerator, denominator, case definition, geography, and observation period must correspond; a rate does not repair biased ascertainment. For What Dashboards Should Show, the source supports a bounded proposition, not a universal conclusion. The link should be opened, the current version and date confirmed, and the relevant language read in context before it is converted into a declarative sentence.

The next step is a claim-by-claim provenance map. For distribution and small-number protection, record the source creator, date, jurisdiction, version, procedural stage, population, quoted or coded field, and any later modification. Map that evidence to source systems → extraction → transformation → quality checks → metric computation → visualization → release → revision and archive. If interviews conflict, say which proposition each person is competent to establish and seek documents that can resolve the conflict. If material information is confidential or unavailable, describe the access limit and narrow the conclusion; absence from a public database is not proof that an event did not occur.

A numerical comparison needs a population and a mechanism, not merely two totals. In What Dashboards Should Show, candidate measures include volume, rates, cohorts, age, tail delay, severity, geography, subgroup where valid, target, uncertainty, missingness, revision history, and data freshness. For distribution and small-number protection, specify whether the number is a stock or flow, whether cases belong to an intake or disposition cohort, which time clock is used, and how duplicates, revisions, missing records, small cells, and changes in reporting rules are handled. A trend should be tested against changes in jurisdiction, staffing, technology, and ascertainment before it is described as a change in underlying risk or performance.

A publication-ready treatment should end with an accountable next step. For distribution and small-number protection, name the decision owner, evidence threshold, unresolved question, exception route, review date, and correction mechanism. The analysis should test for the specific harm that a dashboard can create false precision, invite invalid comparisons, hide queues behind totals, and make corrected data impossible to trace. It should also ask whether an apparent efficiency merely transfers burden to patients, professionals, families, another agency, or a less visible part of the system. The preferred direction—metric cards with definitions and denominators, downloadable data, version history, accessibility, privacy review, annotations, and clear ownership for corrections—is credible only if affected people can understand the rule, present contrary information, and see whether outcomes improve.

Missingness and uncertainty

The useful question is narrower than the public label suggests. For missingness and uncertainty within What Dashboards Should Show, the reporter or decision-maker should identify the actor, the power being exercised, the information available at that moment, and the consequence of error. The central boundary remains operational monitoring, public accountability, exploratory signal, official statistic, and performance judgment. This framing prevents an early signal from acquiring the force of a final conclusion. A term that is appropriate at one point in the sequence—source systems → extraction → transformation → quality checks → metric computation → visualization → release → revision and archive—may become inaccurate after the record advances, or may never have described the authority of the actor who issued it.

OECD — Measuring regulatory performance provides the first official anchor for missingness and uncertainty: OECD organizes methods for assessing regulatory policy, institutions, tools, implementation, and outcomes rather than relying on activity counts alone. Its legal or evidentiary weight must remain visible. Comparative indicators simplify institutional differences and do not establish the effectiveness of a particular regulator without local outcome evidence. For What Dashboards Should Show, the source supports a bounded proposition, not a universal conclusion. The link should be opened, the current version and date confirmed, and the relevant language read in context before it is converted into a declarative sentence.

Chronology is the simplest protection against assigning a later meaning to an earlier document. For missingness and uncertainty, record the source creator, date, jurisdiction, version, procedural stage, population, quoted or coded field, and any later modification. Map that evidence to source systems → extraction → transformation → quality checks → metric computation → visualization → release → revision and archive. If interviews conflict, say which proposition each person is competent to establish and seek documents that can resolve the conflict. If material information is confidential or unavailable, describe the access limit and narrow the conclusion; absence from a public database is not proof that an event did not occur.

A numerical comparison needs a population and a mechanism, not merely two totals. In What Dashboards Should Show, candidate measures include volume, rates, cohorts, age, tail delay, severity, geography, subgroup where valid, target, uncertainty, missingness, revision history, and data freshness. For missingness and uncertainty, specify whether the number is a stock or flow, whether cases belong to an intake or disposition cohort, which time clock is used, and how duplicates, revisions, missing records, small cells, and changes in reporting rules are handled. A trend should be tested against changes in jurisdiction, staffing, technology, and ascertainment before it is described as a change in underlying risk or performance.

Operational discipline matters more than a generic promise of oversight. For missingness and uncertainty, name the decision owner, evidence threshold, unresolved question, exception route, review date, and correction mechanism. The analysis should test for the specific harm that a dashboard can create false precision, invite invalid comparisons, hide queues behind totals, and make corrected data impossible to trace. It should also ask whether an apparent efficiency merely transfers burden to patients, professionals, families, another agency, or a less visible part of the system. The preferred direction—metric cards with definitions and denominators, downloadable data, version history, accessibility, privacy review, annotations, and clear ownership for corrections—is credible only if affected people can understand the rule, present contrary information, and see whether outcomes improve.

Targets, benchmarks, and gaming

A careful review starts with chronology and institutional role. For targets, benchmarks, and gaming within What Dashboards Should Show, the reporter or decision-maker should identify the actor, the power being exercised, the information available at that moment, and the consequence of error. The central boundary remains operational monitoring, public accountability, exploratory signal, official statistic, and performance judgment. Once the stage is named, the evidentiary burden becomes clearer. A term that is appropriate at one point in the sequence—source systems → extraction → transformation → quality checks → metric computation → visualization → release → revision and archive—may become inaccurate after the record advances, or may never have described the authority of the actor who issued it.

U.S. Government Accountability Office — Standards for Internal Control in the Federal Government (Green Book) provides the first official anchor for targets, benchmarks, and gaming: GAO's 2025 Green Book revision sets federal internal-control principles concerning objectives, risks, information, monitoring, and corrective action, effective beginning in fiscal year 2026. Its legal or evidentiary weight must remain visible. The Green Book applies directly within its federal scope and is a useful benchmark elsewhere; it is not a universal state-agency statute. For What Dashboards Should Show, the source supports a bounded proposition, not a universal conclusion. The link should be opened, the current version and date confirmed, and the relevant language read in context before it is converted into a declarative sentence.

Chronology is the simplest protection against assigning a later meaning to an earlier document. For targets, benchmarks, and gaming, record the source creator, date, jurisdiction, version, procedural stage, population, quoted or coded field, and any later modification. Map that evidence to source systems → extraction → transformation → quality checks → metric computation → visualization → release → revision and archive. If interviews conflict, say which proposition each person is competent to establish and seek documents that can resolve the conflict. If material information is confidential or unavailable, describe the access limit and narrow the conclusion; absence from a public database is not proof that an event did not occur.

Measurement should test the claimed outcome rather than reward the easiest available count. In What Dashboards Should Show, candidate measures include volume, rates, cohorts, age, tail delay, severity, geography, subgroup where valid, target, uncertainty, missingness, revision history, and data freshness. For targets, benchmarks, and gaming, specify whether the number is a stock or flow, whether cases belong to an intake or disposition cohort, which time clock is used, and how duplicates, revisions, missing records, small cells, and changes in reporting rules are handled. A trend should be tested against changes in jurisdiction, staffing, technology, and ascertainment before it is described as a change in underlying risk or performance.

The most credible reform is one that an external reviewer can test. For targets, benchmarks, and gaming, name the decision owner, evidence threshold, unresolved question, exception route, review date, and correction mechanism. The analysis should test for the specific harm that a dashboard can create false precision, invite invalid comparisons, hide queues behind totals, and make corrected data impossible to trace. It should also ask whether an apparent efficiency merely transfers burden to patients, professionals, families, another agency, or a less visible part of the system. The preferred direction—metric cards with definitions and denominators, downloadable data, version history, accessibility, privacy review, annotations, and clear ownership for corrections—is credible only if affected people can understand the rule, present contrary information, and see whether outcomes improve.

Revisions, downloads, and correction notices

This dimension is best approached as a verification problem. For revisions, downloads, and correction notices within What Dashboards Should Show, the reporter or decision-maker should identify the actor, the power being exercised, the information available at that moment, and the consequence of error. The central boundary remains operational monitoring, public accountability, exploratory signal, official statistic, and performance judgment. That boundary changes what the evidence can support. A term that is appropriate at one point in the sequence—source systems → extraction → transformation → quality checks → metric computation → visualization → release → revision and archive—may become inaccurate after the record advances, or may never have described the authority of the actor who issued it.

HHS — Information Quality Guidelines provides the first official anchor for revisions, downloads, and correction notices: HHS publishes guidelines for quality, objectivity, utility, integrity, and correction of information it disseminates. Its legal or evidentiary weight must remain visible. The guidelines apply within their defined federal information-quality framework and do not create a universal private right to correction. For What Dashboards Should Show, the source supports a bounded proposition, not a universal conclusion. The link should be opened, the current version and date confirmed, and the relevant language read in context before it is converted into a declarative sentence.

The underlying record should then be reconstructed forward rather than narrated backward from the outcome. For revisions, downloads, and correction notices, record the source creator, date, jurisdiction, version, procedural stage, population, quoted or coded field, and any later modification. Map that evidence to source systems → extraction → transformation → quality checks → metric computation → visualization → release → revision and archive. If interviews conflict, say which proposition each person is competent to establish and seek documents that can resolve the conflict. If material information is confidential or unavailable, describe the access limit and narrow the conclusion; absence from a public database is not proof that an event did not occur.

Quantification becomes useful only after the unit of analysis is fixed. In What Dashboards Should Show, candidate measures include volume, rates, cohorts, age, tail delay, severity, geography, subgroup where valid, target, uncertainty, missingness, revision history, and data freshness. For revisions, downloads, and correction notices, specify whether the number is a stock or flow, whether cases belong to an intake or disposition cohort, which time clock is used, and how duplicates, revisions, missing records, small cells, and changes in reporting rules are handled. A trend should be tested against changes in jurisdiction, staffing, technology, and ascertainment before it is described as a change in underlying risk or performance.

Operational discipline matters more than a generic promise of oversight. For revisions, downloads, and correction notices, name the decision owner, evidence threshold, unresolved question, exception route, review date, and correction mechanism. The analysis should test for the specific harm that a dashboard can create false precision, invite invalid comparisons, hide queues behind totals, and make corrected data impossible to trace. It should also ask whether an apparent efficiency merely transfers burden to patients, professionals, families, another agency, or a less visible part of the system. The preferred direction—metric cards with definitions and denominators, downloadable data, version history, accessibility, privacy review, annotations, and clear ownership for corrections—is credible only if affected people can understand the rule, present contrary information, and see whether outcomes improve.

Cross-cutting tests

Authority test. For What Dashboards Should Show, every material proposition should identify whether it rests on controlling law, a final order, official guidance, an international instrument, a dataset, research evidence, an interview, inference, or recommendation. If a source changes status—because a bill is enacted, draft guidance becomes final, a decision is stayed, or a dataset is revised—the public sentence must change as well.

Scope test. In What Dashboards Should Show, ask who, where, when, and what version the source covers. Public-sector health and regulatory performance reporting is the frame used here, but the same term can have a different legal meaning in another state, country, payer program, profession, or procedural system. A useful comparison preserves those differences instead of treating a common label as proof of a common rule.

Causation test. In What Dashboards Should Show, sequence and association are not sufficient to show cause. A rise in reports can reflect more events, better awareness, mandatory submission, easier technology, duplicated records, or clearance of a backlog. A lower count can mean prevention, underreporting, narrower jurisdiction, or loss of capacity. The article should name plausible alternative explanations and identify evidence that would distinguish them.

Proportionality and reversibility test. The procedural protection should match the consequence. A low-stakes screening signal can justify another look; a durable public label, deprivation, professional restriction, or denial of needed care requires stronger evidence, reason-giving, and meaningful review. What Dashboards Should Show should state how long an erroneous result can persist and whether correction reaches every downstream system that used it.

Distribution and burden-shifting test. For What Dashboards Should Show, average improvement can coexist with concentrated harm. Evaluate geography, language, disability, specialty, practice setting, institution size, and other relevant groups only when the data support responsible analysis. Then ask where work moved. A faster front-end process may produce appeals, rework, uncompensated coordination, or risk elsewhere; net benefit is a system result, not the metric preferred by one actor.

Correction test. The minimum audit record for What Dashboards Should Show includes source, date, version, actor, criteria, denominator, decision, reason, exception, reviewer, and correction history. A credible system also has a re-verification date. Public trust is strengthened when institutions distinguish a clarification from a substantive correction, preserve earlier versions, notify affected users, and explain how recurrence will be prevented.

A ten-step verification protocol

1. Write the exact claim about What Dashboards Should Show before searching; separate its factual, legal, causal, and normative parts.
2. Identify the jurisdiction, institution, population, program, time period, and procedural or technical version.
3. Locate the primary authority or originating dataset and preserve a stable link, title, issuer, and retrieval date.
4. Classify the source as law, regulation, final order, proposed action, guidance, standard, data, research, testimony, or analysis.
5. Extract the language or field that supports the claim and record exceptions, definitions, and scope limits beside it.
6. Reconstruct the relevant sequence: source systems → extraction → transformation → quality checks → metric computation → visualization → release → revision and archive.
7. Choose measures that match the objective, including where appropriate volume, rates, cohorts, age, tail delay, severity, geography, subgroup where valid, target, uncertainty, missingness, revision history, and data freshness.
8. Seek disconfirming records, later history, alternative explanations, and comments from people with different roles in the process.
9. Draft with stage-accurate verbs and labels; distinguish verified fact, attributed assertion, inference, uncertainty, and recommendation.
10. Run a final current-status, quotation, number, denominator, link, name, date, and correction-path check immediately before publication.

Overstatement risks

• Treating operational monitoring, public accountability, exploratory signal, official statistic, and performance judgment as interchangeable categories.
• Using the existence of a record as proof that the record's assertions were accepted.
• Generalizing a jurisdiction-specific rule, program-specific dataset, or selected sample to a broader population.
• Reporting a raw count as incidence, prevalence, quality, danger, or effectiveness without the relevant denominator and ascertainment limits.
• Describing draft, proposed, voluntary, interpretive, or recommendation-level material as controlling final law.
• Ignoring later documents, changed versions, stays, appeals, corrections, restorations, or implementation dates.
• Celebrating speed or volume without testing whether a dashboard can create false precision, invite invalid comparisons, hide queues behind totals, and make corrected data impossible to trace.
• Presenting an original policy preference as though an official source required it.

Questions for decision-makers, journalists, and reviewers

• What exact decision or public claim is being made in What Dashboards Should Show?
• Which actor has legal authority, information control, and operational control at each stage?
• What is the current primary source, and when was its status last checked?
• Is the cited document an allegation, proposal, final action, guidance document, dataset, or analysis?
• Which jurisdiction, population, program, profession, version, and time period does it cover?
• What proposition does the source establish, and what does it explicitly or practically leave unresolved?
• What numerator, denominator, case definition, cohort, and observation period support each number?
• Could a trend reflect reporting, staffing, jurisdiction, backlog, coding, or technology changes rather than the claimed mechanism?
• Who bears the cost of a false positive, false negative, or delayed decision?
• Can an affected person inspect the material, present contrary evidence, receive reasons, and obtain meaningful review?
• How will a material error be corrected in the originating and downstream records?
• Would the proposed reform—metric cards with definitions and denominators, downloadable data, version history, accessibility, privacy review, annotations, and clear ownership for corrections—produce observable improvement, and what evidence would falsify that expectation?

Reform direction

The reform direction for What Dashboards Should Show is metric cards with definitions and denominators, downloadable data, version history, accessibility, privacy review, annotations, and clear ownership for corrections. Design should begin with a written objective, the authority for action, and the population whose outcomes matter. It should identify decision owners and operational dependencies instead of assigning abstract responsibility to a committee, a vendor, or the last frontline person in the chain. Resources, staffing, training, and data access must be assessed because a procedural promise without implementation capacity can create a new layer of delay.

Evaluation should use volume, rates, cohorts, age, tail delay, severity, geography, subgroup where valid, target, uncertainty, missingness, revision history, and data freshness. The public report should show definitions, denominator, time, cohort, severity, missingness, revision history, and distribution where valid. Independent review is most useful when the reviewer has access to the necessary record, discloses conflicts, uses stated methods, and can communicate uncertainty. A single annual total is rarely enough to establish whether the reform protected people, improved accuracy, reduced delay, or shifted burden.

Fairness controls for What Dashboards Should Show should be built into ordinary operation: timely notice where permitted, access to the substance of the case, a realistic opportunity to respond, reasoned outcomes, escalation for urgent harm, and correction capable of repairing public and downstream records. These protections should be scaled to consequence and should not be used to defeat lawful confidentiality or urgent intervention. Their purpose is better decisions, not procedure for its own sake.

Finally, What Dashboards Should Show needs an explicit learning cycle. Leaders should review errors, appeals, reversals, delays, near misses, disparate impacts, user feedback, and unintended consequences; publish what can lawfully be disclosed; and retire metrics or tools that no longer match the objective. A reform is not proven by adoption. It earns credibility through current sources, observable outcomes, transparent limitations, and willingness to correct course.

Conclusion

A public dashboard should expose definitions, denominators, cohorts, time, severity, uncertainty, missingness, revisions, workflow stages, distribution, targets, and download metadata—not merely attractive totals and rankings. That conclusion is deliberately narrower than a slogan. What Dashboards Should Show crosses institutions in which authority, information, incentives, and consequences do not sit in one place. Responsible action does not require perfect certainty, but it does require an honest account of uncertainty and safeguards proportionate to the harm an erroneous conclusion can cause.

The durable reform is metric cards with definitions and denominators, downloadable data, version history, accessibility, privacy review, annotations, and clear ownership for corrections. Implemented seriously, that direction turns abstract accountability into inspectable work: a stage-labeled record, current authority, appropriate measures, named ownership, meaningful review, and correction that reaches downstream uses. It also makes performance claims falsifiable. If the chosen outcomes do not improve, if disparities widen, or if burden merely moves, the policy should be revised rather than defended by activity statistics.

The final editorial test for What Dashboards Should Show is whether a skeptical reader can reconstruct the path from source to sentence. Law should be called law, guidance called guidance, allegations attributed, findings tied to the authorized decision-maker, numbers paired with denominators and limits, and recommendations claimed by their author. That discipline protects both the public and the credibility of the institutions whose work is being explained.

Sources and Authorities

Each source below was verified against the official publisher, current through August 10, 2026. Laws, proposed rules, and agency pages change; every link is re-opened live at deployment, and time-sensitive requirements should be checked against the current official source.

U.S. Government Accountability Office — Standards for Internal Control in the Federal Government (Green Book)

HHS — Information Quality Guidelines

Data.gov — DCAT-US dataset metadata standard

Federal Data Strategy — Practices

Centers for Medicare & Medicaid Services — Data and Research

National Practitioner Data Bank — Public Use Data File

CDC Field Epidemiology Manual — Describing epidemiologic data

OECD — Measuring regulatory performance

Related Articles

• Correcting Public Errors
• Independent Experts in Oversight
• How Board Panels Review Proposed Decisions: The Closed-Door Stage That Actually Decides Physician Discipline