Rules
Part of Public records reporting: a guide to finding and reading documents
Eight public records reporting problems and their fixes
Public records reporting problems and fixes for wrong versions, poor searches, missing context, redaction guesses, data errors, and unsupported conclusions.
What to take away
- A failed portal search does not prove that no record exists.
- An official document may be obsolete, incomplete, or wrong.
- Redaction codes do not reveal the hidden text.
- Dataset definitions and revision notes belong in the reporting.
- Conclusions should stay within the released record's scope.
Records can look firmer than interviews because they have dates, seals, and file numbers. Those features help establish provenance. They do not remove the need to check version, scope, meaning, and accuracy.
1. Searching the wrong custodian
Problem: The reporter searches the agency named in the story, but another office created and stores the records.
Fix: Map the workflow. Identify the creator, recipients, system owner, contracting office, and records custodian. Search each relevant repository before concluding that the item is absent. Custodian mapping is an early step in the public records reporting guide.
2. Treating a catalog as complete and current
Problem: A guide or index does not list the desired material, so the reporter writes that the archives do not hold it.
Fix: Read the catalog's coverage note and update date. The National Archives says its web Guide to Federal Records is based on a 1995 paper edition and is not updated as holdings grow, directing researchers to the current catalog for newer holdings information. That federal records guide notice supports treating an old finding aid as an entry point, not proof of absence.
3. Using the wrong version
Problem: A proposed rule, draft report, unsigned contract, or introduced bill is described as final.
Fix: Record the status label, publication history, signature, effective date, and later amendments. Compare the copy with the issuing repository. Say "the draft proposed" when that is what the evidence shows. The version tests in reading an official document exist for exactly this trap.
4. Ignoring attachments and incorporated material
Problem: The main document refers to schedules, exhibits, appendices, or data tables that were not downloaded.
Fix: Inventory every referenced component. Ask the custodian for missing attachments. Do not report a contract price without checking amendments and schedules that define optional work. The official record types comparison separates authorized maximum, obligated, invoiced, and paid amounts, exactly the split a missing attachment blurs.
5. Guessing behind a redaction
Problem: Context appears to suggest a name or phrase, and the story states the guess as fact.
Fix: Report the stated withholding basis and visible context. Seek the fact through another record or source. A black box establishes that text was withheld, not what the text contained.
6. Confusing no records with no event
Problem: A response says no responsive records were found, and the story says the reported meeting never happened.
Fix: Examine request scope and search description. Check other attendees, calendars, phone logs, meeting platforms, travel records, and retention schedules. Report the negative result narrowly.
7. Treating released data as fixed truth
Problem: A newsroom ranks places using estimates without reading definitions or revision rules.
Fix: Preserve the release date and method, inspect missing values, test calculations, and check for revisions. The Census Bureau's Population Estimates Challenge Program states that a challenge may lead to a revised estimate when specified technical errors in input processing or estimate production are found. The Census estimates challenge page supports the limited point that an official estimate can be corrected through a defined process. It does not imply that every estimate is suspect.
Revision handling for live stories is covered in developing news briefing problems, where a quiet number swap counts as an invisible correction.
8. Claiming more than the record shows
Problem: A payment list becomes the total cost, a sample becomes the whole population, or an allegation in a filing becomes a proven act.
Fix: Draft the finding and limit together. Name the period, population, source system, exclusions, and status. Use a second record or interview to test what the first document cannot answer.
A repair table
| Weak claim | Record-safe revision |
|---|---|
| The agency hid the manager's name | The released page redacts a name under the cited exemption |
| No meeting occurred | The named office reported finding no responsive records for the request |
| The program cost $2 million | The released payment file lists $2 million during the covered period |
| The rule changed | The agency published a proposal to change the rule |
| All inspections failed | The report found failures in the inspected sample |
Precision is not timid writing. It shows the reader exactly how far the evidence reaches.
Common questions
Is an archived copy less trustworthy than a live page?
Not necessarily. It may preserve the version in effect at a particular time. Record its source, capture date, and relationship to later versions.
Can a reporter infer meaning from a file name?
A file name is a clue, not enough proof for a central claim. Check metadata, contents, repository description, and issuing office.
Should a story mention every redaction?
Mention redactions that affect the finding, source context, or completeness. A large release may need a summary rather than a list of every mark.
What if an agency corrects data after publication?
Recalculate affected findings, update the article, and add a correction when the original result was materially wrong.
