Skills on AI

Active theme: Light

Government Performance Report

Use when asked to write or review a government performance report — a government body's disclosure of its own performance against stated goals or metrics, to a legislature and/or the public — distinct from [[sustainability-report]], which is specifically ESG/environmental-social-governance disclosure rather than broader mission-accountability reporting.

A government performance report discloses how well a government body is doing against its own stated goals or metrics, typically to a legislature, an oversight body, and the public. Its purpose is accountability: letting an outside reader judge whether the agency is actually delivering on its mission, not just whether it produced a document that says so.

Key components

  • Specific, pre-defined metrics tied to the agency's actual mission — measures set in advance, and tied to the agency's stated goals, not metrics chosen after the reporting period because they happen to look good.
  • Performance shown against a target or prior-period baseline — a number on its own tells a reader nothing; the same number next to a target or last period's figure lets them judge whether performance is actually improving, flat, or declining.
  • Honest reporting of missed targets alongside met ones — a report that shows only the wins isn't an accountability document, it's a press release wearing an accountability document's format.
  • Clear scope and reporting period — which programs, offices, or functions the figures cover, and over what dates, stated explicitly.
  • Context for anomalies — a one-time event, a funding change, or a methodology shift that moved a number, disclosed rather than left for the reader to guess at.

Why metrics must be defined before the reporting period, not after

A metric chosen after the numbers are already in can always be chosen to look good — pick the one indicator that improved and it looks like success, ignore the three that didn't. This is why a genuine performance report commits to its metrics before the period it covers, usually in a budget request, strategic plan, or prior year's report, so the metrics reported at the end are the same ones promised at the start. A metric that changes after the period it was meant to measure, with no visible commitment to it beforehand, tells a reader nothing about performance — only about which numbers turned out favorable.

Common pitfalls

  • Metrics chosen or changed after the reporting period specifically because they look better than the ones originally set — swapping out an underperforming metric for a new one that happens to show progress defeats the report's purpose, even when every number in it is individually accurate.
  • Missed targets omitted or buried while met ones are prominently highlighted — a shortfall mentioned once in a footnote while every success gets a headline and a chart is selective disclosure, not accountability.
  • Metrics reported with no baseline or trend for comparison — a bare figure with nothing to measure it against lets an agency claim success or explain away failure without the reader ever being able to check.
  • Vague, unmeasurable goals dressed up as metrics — "improve service quality" is not a metric; a specific number (average response time, percentage of cases resolved within a stated window) is.
  • No explanation for a broken trend — a number that jumps unexpectedly, with no note about a methodology change, a one-time event, or a scope change behind it, misleads a reader into thinking performance itself changed.

Learn more

View government-performance-report/SKILL.md on GitHub