Public records
Public records and denominator checklist
Organization byline: Measurement Press editorial desk. This page does not list an individual author or reviewer. Read the editorial method and corrections policy.
About 11 min read
A newsroom, analyst, or campaign team can see a public-record download with a count, percent change, or "highest since" phrase and feel the number is settled. It is not settled until the reader can see the denominator: the "out of how many?" base that gives the number size.
Public records can make a claim more inspectable, but a record is not the same thing as a rate base. Before trusting a story built from incident logs, filings, government tables, budgets, inspections, dockets, or open-data portals, check what the record covers, what it omits, and what baseline would make the number meaningful.
This checklist is for readers, editors, analysts, and researchers who need to slow down claims that sound precise because they cite a public source. The goal is not to dismiss official records. The goal is to keep the claim within the population, time period, definitions, and revision limits that the record can actually support.
One-page record check
| Question | Strong disclosure shows | Weakens confidence |
|---|---|---|
| What is the original record? | The story links the filing, table, transcript, docket, budget line, inspection record, release, or download page closest to the claim. | The citation points to a summary, screenshot, thread, or paraphrase while the underlying record remains hard to inspect. |
| Who maintains it? | The agency, court, office, data owner, reporting program, or record custodian is named with its role. | The source is described only as "public records" or "government data" without naming the collector. |
| What is included? | Eligibility rules, geography, population, reporting units, fields, filters, and known exclusions are visible. | A count is treated as universal even though only reported, filed, inspected, adjudicated, or eligible cases enter the record. |
| What is the denominator? | The claim gives the total population, eligible cases, transaction base, agency workload, prior-period level, or rate base needed for interpretation. | A numerator, anecdote count, percent change, or "highest since" phrase carries the frame alone. |
| What time period is covered? | Record date, event date, release date, fiscal/calendar period, access date, and update cadence are separated when they matter. | A lagged, revised, partial, or event-date dataset is written as if it were final and current. |
| Are definitions stable? | The story notes definition changes, reporting-rule changes, boundary changes, category changes, and classification uncertainty. | A trend line crosses a definition break without warning readers. |
| What comparison is fair? | The article compares like geographies, similar institutions, comparable periods, rate-adjusted counts, or pre-specified benchmarks. | The comparison shifts between national, local, peer, historical, and anecdotal frames depending on which sounds strongest. |
| What could be missing? | The article names underreporting, nonresponse, redaction, exemptions, backlog, selection into enforcement, and records not created. | The absence of a visible record is treated as proof that nothing happened, or one visible record is treated as the full universe. |
Read public-record claims in order
1. Name the record typeA complaint log, arrest record, inspection report, court filing, administrative dataset, budget table, open-data export, and press release answer different questions. Decide what the record is before deciding what it proves.
2. Separate event date from record dateMany records are created after the underlying event. A spike in filings, releases, or uploads may reflect processing, backlog, policy, or reporting changes rather than a spike in the underlying condition.
3. Convert counts into rates when the base changedIf population, transactions, inspections, staff, eligibility, or reporting volume changed, raw counts can mislead. Ask whether the right comparison is per person, per case, per dollar, per transaction, per inspection, or per eligible unit.
4. Treat missing records as a source problemMissing records may mean no record exists, the wrong agency holds it, the record is exempt, the search was narrow, the request is pending, or the data system does not capture the event. Do not turn absence into proof without checking the record process.
5. Keep revisions near the claimOfficial data often changes after initial release. If the claim depends on a fresh estimate, preliminary table, or incomplete period, the headline should preserve that limit.
Denominator translation table
| If the story says | Ask for | Careful wording |
|---|---|---|
| "Incidents rose 40%." | The starting count, ending count, total eligible population, time window, and reporting-rule changes. | Reported incidents rose from X to Y in this record over this period; the rate and reporting context determine how large the change is. |
| "The agency received hundreds of complaints." | Total transactions, customers, cases, inspections, or contacts during the same period. | The record shows X complaints among Y relevant contacts or cases; complaint volume alone does not show prevalence. |
| "This is the highest level in years." | The full series, definition changes, population changes, and whether the latest point is preliminary. | The record reaches its highest reported level since year Z under the available series; comparability limits remain visible. |
| "The city spends more than peers." | Per-capita, per-household, per-case, inflation-adjusted, and service-level comparisons. | The city spends more on this line under this rate base; the service mix and accounting definitions need checking. |
| "Only a small share was affected." | The denominator used, who was excluded, and whether the excluded group could still matter to the decision. | The measured share is small under this denominator; a different eligible base may change the practical meaning. |
Choose the denominator that matches the claim's job
Do not ask only which denominator is easiest to find. Ask what judgment the sentence is asking the reader to make. A safety claim, workload claim, trend claim, spending claim, and fairness claim can all use the same public record but need different bases.
| The claim asks readers to judge | First denominator to request | What changes if the base is missing |
|---|---|---|
| Prevalence | The eligible population, transactions, cases, or people who could have entered the record. | The count can sound common or rare without proof. |
| System workload | Total requests, inspections, filings, contacts, dockets, or service units handled in the same period. | More records may reflect a busier system rather than a worse outcome. |
| Trend direction | The prior comparable period under the same definitions, reporting rules, and release status. | A fresh, revised, partial, or backlog-driven figure can masquerade as a real-world change. |
| Peer comparison | A comparable geography, agency, facility, population, case mix, or service level. | The article may compare unlike institutions because the contrast sounds stronger. |
| Decision readiness | The denominator a reasonable editor, buyer, analyst, or public official would need before acting. | The number may be true but still too thin for the requested decision. |
Public-record gap language
When a story cannot yet inspect the best record, say that plainly. "Records were not available" is not the same as "records do not exist." "The agency did not provide records by publication time" is not the same as "the agency has no support for the claim." Clean public-record writing separates request status, legal access, agency custody, search scope, and evidence strength.
| Status | What it means | What not to infer |
|---|---|---|
| Record requested | A requester has asked for records, but release, redaction, denial, or appeal may still be pending. | That the requested record exists or will support the frame. |
| Record withheld or redacted | Some information was not released under an access rule or exemption. | That the hidden material proves the strongest interpretation. |
| No responsive records | The custodian did not identify records matching that request and search scope. | That no relevant event occurred, no other office holds records, or no different search would find material. |
| Partial dataset | The record covers a subset, period, geography, or reporting program. | That the subset represents the whole population without adjustment. |
Minimum citation packet
- Original record link, table number, docket, filing ID, release, data portal, or request response when available.
- Record owner, reporting program, geography, population, record type, release date, event date, and access date.
- Numerator, denominator, time window, filters, exclusions, and whether the figure is preliminary, revised, estimated, or final.
- Definition notes, reporting-rule changes, missing fields, redactions, underreporting risks, and comparability breaks.
- Comparison class: prior period, peer group, population-adjusted rate, eligible-case base, or stated benchmark.
- One disconfirming record or base rate that would materially weaken the public frame if it appeared.
Simulated Worked Example: separate count growth from rate growth
This is a Simulated Worked Example, not a real public-record result. The numbers are fictional and show how to reproduce a denominator check. Replace them with the source's actual record definition, coverage notes, and eligible base before publishing a real claim.
Suppose a reporting program lists 180 incidents in Period A and 240 in Period B. A count-only headline would say incidents rose by 33.3%. The reviewer also finds 10,000 eligible inspections in Period A and 12,000 in Period B, with the same incident definition and comparable reporting window.
| Period | Reported incidents | Eligible inspections | Rate |
|---|---|---|---|
| A | 180 | 10,000 | 180 ÷ 10,000 = 1.80% |
| B | 240 | 12,000 | 240 ÷ 12,000 = 2.00% |
- Count change = (240 − 180) ÷ 180 = 33.3%.
- Rate change = (2.00% − 1.80%) ÷ 1.80% = 11.1%.
- The denominator grew by 20.0%, so the count change overstates the change in the rate under this stated base.
Decision rule: the source packet is not ready for a prevalence headline until the reviewer can verify that “eligible inspections” is the right universe, both periods use the same definition, and the record explains missing, delayed, or reclassified cases. A bounded sentence could say: “Reported incidents increased from 180 to 240 in the simulated record, while the rate rose from 1.80% to 2.00% among eligible inspections.” It should not claim the underlying condition increased by 33.3% without stronger evidence.
Reproduction and sensitivity check
To reproduce the example, copy the two numerators and denominators into a worksheet, calculate each rate as numerator ÷ denominator, then compare the two rates. Keep the denominator label beside the result; changing the base changes the conclusion.
| Alternative Period B base | Period B rate | Change vs. Period A rate | Interpretation |
|---|---|---|---|
| 9,000 confirmed eligible inspections | 240 ÷ 9,000 = 2.67% | +48.1% | Narrower base makes the rate look materially larger. |
| 12,000 stated eligible inspections | 240 ÷ 12,000 = 2.00% | +11.1% | Primary simulated result; depends on the eligibility definition. |
| 15,000 broader eligible universe | 240 ÷ 15,000 = 1.60% | −11.1% | A broader base reverses the direction of the rate comparison. |
The sensitivity rows are not competing estimates of a real event. They show why the source packet must identify the population that could have entered the record. Census statistical quality guidance connects administrative-record use, analysis, and public documentation to transparency and reproducibility; Standard B2 and Standard F2 are useful reference points. For access requests, FOIA.gov explains that a request should reasonably describe the records sought and that FOIA does not require an agency to create a new analysis. These references guide the review boundary; they do not validate the fictional figures above.
What the official documentation supports
These sources sharpen the review method; they do not turn a linked record into proof of the article's conclusion. The boundaries below are the ones to carry into a real source packet.
| Source check | What the official guidance supports | What still requires the article's own verification |
|---|---|---|
| Administrative-record quality | Census Standard B2 calls for a study plan, review of source documentation, record counts and distributions, missing-data and coverage checks, and documentation that supports evaluation. | Whether this particular record is complete, comparable across periods, correctly classified, and fit for the claim being made. |
| Transparency and reproducibility | Census Standard F2 points readers toward the data program, target population, definitions, reference dates, methods, quality measures, and known limitations. | The source packet must still provide the exact table or file, filters, denominator, revisions, and calculation needed to reproduce the sentence. |
| Records access | FOIA.gov says a request should reasonably describe existing records; FOIA does not require an agency to create a new record, conduct research, or perform an analysis. | “No responsive records,” a pending request, a redaction, and a missing denominator are different states and cannot be collapsed into one claim. |
| Citation and retrieval | Census citation guidance keeps the original product, table/file or tool, version or release date, persistent identifier, URL, and access date visible. BLS retrieval tools and BEA data pages provide direct paths into series, tables, topics, places, and accounts. | A link to a data portal is not enough: record the exact series or table, geography, period, vintage, unit, denominator, and any revision or estimation note used in the analysis. |
Practical source-packet rule: if a reader cannot identify the record owner, universe of inference, reference period, denominator, retrieval path, and revision status from the cited material, lower the claim's confidence or narrow the wording. The official guidance gives a documentation standard; it does not certify the fictional example or substitute for checking the underlying record.
Official references
FOIA.gov's request guide is a starting point for federal public-record requests and request status language. U.S. Census Bureau citation guidance is useful when official tables, tools, technical documents, or research need a replicable citation path. BLS data retrieval tools and the BLS information guide help readers find labor, price, productivity, and economic data sources. BEA data pages are useful for economic accounts, regional data, and national-account context.
Takeaway
A public record makes a claim easier to inspect, not automatically true in the way a headline suggests. Strong public-record writing names the source, shows the denominator, explains the missing universe, and keeps comparisons inside the record's limits.