A document on a screen can look finished long before it is proven. A seal, a signature, a case number, and a clean PDF can all create a sense of certainty that the evidence has not earned.
When we verify news documents, we are not asking only whether a file exists. We are asking who issued it, whether it is complete, when it appeared, and whether the story describes it fairly.
That work takes longer than reading a screenshot. It also prevents a shortcut from becoming a conclusion.
Start with the claim, not the document
News stories often make the document sound clearer than it is. "Records show," "a memo proves," or "court papers confirm" may point to something real. They may also flatten a disputed allegation into a fact.
Before searching, write down the exact claim being made. Identify the person or institution involved. Note the document's stated title, date, page number, case number, agency, and quoted language.
Separate facts from the story’s interpretation
A lawsuit is real if it was filed. That does not mean its allegations are proven. An inspector general report may identify a problem. It may not support the headline's broadest claim.
Look for verbs that carry more certainty than the document does:
- "Alleges" is not the same as "proves."
- "Says" is not the same as "finds."
- "A draft" is not the same as an adopted policy.
- "An internal email" is not the same as an agency decision.
A real document can still be quoted out of context, given the wrong date, or used to support a claim it never makes.
Read the sentence before and after a quoted passage. Check whether the story leaves out conditions, denials, corrections, or later developments. A document is evidence. It is not a verdict by itself.
Know what kind of copy you are seeing
Not every version of a document carries the same weight. The first question is simple: are you looking at the issuer's copy, or someone else's version of it?
This distinction matters most when a fast-moving story relies on images passed through social media, group chats, or reposted articles.
| Type of copy | What it can show | What it cannot prove alone |
|---|---|---|
| Official copy | What the issuing body published or filed | That a news story interpreted it correctly |
| Leaked copy | What may have circulated before publication | Who created it, whether it is complete, or whether it changed |
| Screenshot | What appeared on one screen at one moment | The source, full content, date, or file integrity |
| Secondary reproduction | How another outlet or person presented it | That their version matches the original |
The strongest starting point is an official repository, court docket, agency website, legislative archive, corporate filing system, or direct release from the issuing organization.
Official copies leave a trail
An official document usually has a home beyond the article that cites it. A federal court filing can be checked through PACER's federal court records system. A federal agency record may be available through its reading room, press office, or a request process explained at FOIA.gov.
For federal publications, GovInfo's authentication information explains how its authenticated files provide evidence of identity, source, and ownership. That is stronger than a PDF uploaded to an unknown account.
Still, an official website is not a magic stamp. Check the web address carefully. Look for the agency or court name. Confirm that the file title, date, and document number match what the story claims.
Leaks need independent support
A leak can be genuine. It can also be incomplete, outdated, altered, or presented without the surrounding record.
Treat a leaked file as a lead. Search for the same language in a later court filing, public report, agency archive, meeting agenda, or company statement. If the claim is important, look for a second independent record that confirms the key point.
Do not assume a leak is false because it is unofficial. Do not assume it is true because several accounts posted the same pages. Repetition shows circulation. It does not show origin.
Trace the document back to its issuer
A good verification search starts with precise identifiers. Search the document title in quotation marks. Add the issuing body, date, case number, docket number, report number, or a distinctive sentence from the text.
If a story cites a court complaint, find the docket and the filed PDF. If it cites a city decision, look for the agenda, minutes, ordinance, or recorded vote. If it cites a government report, search the agency's publication page before relying on a news excerpt.
Use the right public record
Different documents live in different places. A federal civil complaint belongs in the court record. A campaign finance claim may require filings. A nonprofit's leadership or tax documents may be checked through public records. A local policy claim may rest on meeting minutes, not a press release.
We should not expect one search engine result to settle every question. Search results can surface copied files, broken links, or pages that rank well for reasons unrelated to reliability.
The Truth in Journalism Project's fact-checking guide gives a useful baseline: confirm a factual claim with a primary source when possible, or with two sound secondary sources when a primary source is unavailable.
Check the date and status
Documents change meaning with time. A 2023 draft may have been abandoned. A complaint may have been dismissed. A proposed rule may never have taken effect. A report may later be revised.
Check four details before treating a cited record as current:
- The date the document was created or filed.
- The date it was published or obtained.
- Its status, such as draft, final, withdrawn, amended, sealed, or superseded.
- Any later record that changes its effect.
A story can cite a genuine document and still give readers an old picture of a moving situation.
Compare the file, not its appearance
Visual polish is weak evidence. People can copy letterheads, add signatures, change dates, and export a convincing PDF in minutes. A crooked image is not proof of a leak either. Real records are often photographed badly.
When you can obtain both a cited copy and an official version, compare them line by line where the claim matters. Check page counts, headers, footers, paragraph numbering, attachments, redactions, and quoted passages.
Look for breaks in the record
A missing first page may hide the author, recipient, or date. A missing final page may remove a signature or qualification. Cropped screenshots can conceal a reply thread, a correction, or the name of a different document.
Pay attention to small mismatches:
- A case number that does not match the court's format.
- Page numbers that skip or repeat.
- Different fonts inside a single line of text.
- A quoted paragraph that does not appear in the full file.
- A signature block without a named signer or office.
- A document date that conflicts with the event timeline.
None of these signs proves fraud alone. They tell you to slow down and seek the original.
Metadata can help, but it cannot settle everything
Files often contain metadata, such as creation dates, author fields, software names, and revision details. These clues can reveal that a PDF was made after the date printed on it. They can also be missing or changed during copying.
The Berkeley Advanced Media Institute's verification guidance lists tools for checking image and PDF metadata, including ExifTool, pdfinfo, and pdftotext. For most readers, the larger point is enough: compare the file's hidden details with its visible claims.
Metadata supports a finding when it matches other evidence. It should not carry the whole case.
Treat screenshots as pointers, not proof
Screenshots travel fast because they are easy to view and hard to inspect. They usually remove the address bar, file location, access date, surrounding material, and source history.
A screenshot may accurately show a real document. It may also show an edited crop, a mock-up, or a genuine page stripped of the part that changes its meaning.
Rebuild the missing context
Ask where the screenshot first appeared. Find the earliest available post, then trace backward. Does the person who posted it say how they obtained it? Did a newsroom publish the full document? Can the same page be found in an official archive or filing?
If the image shows a web page, search the title and exact wording. Look for an archived version with the original address and capture date. Save the full page, not only the portion that supports one claim.
Some images and files carry provenance data called Content Credentials. The Content Credentials verification tool can show available information about how supported content was created or edited. Its absence does not prove deception. Its presence is one useful piece of a larger record.
Check what the document actually says
Once a document appears real, the next task begins. Read it. Do not let a headline read it for you.
Start with the title page, date, author, recipient, and stated purpose. Then find the exact page cited by the story. Read enough around it to understand who is speaking, what evidence is being described, and what limits the document places on its own conclusions.
Watch for selective quotation
A short phrase can carry a different meaning inside a longer sentence. "No evidence was found" may refer to one narrow allegation, not the entire issue. "Could not verify" may mean records were unavailable, not that an event did not happen.
We often see stories turn provisional language into final language. Words such as "may," "preliminary," "according to," and "subject to revision" matter. They are not decorative cautions. They tell you how far the document can take you.
A document's existence answers one question. Its full context answers another.
Preserve the evidence trail
Verification should leave a trail that another person can follow. Save the original link, the date you accessed it, the document title, and the page numbers that matter. If the page may disappear, preserve an archive link or download the file while recording where it came from.
Keep the original file separate from notes, highlights, and screenshots. Give saved files clear names that include the source and date. Avoid renaming a downloaded document in a way that makes it look official.
Record uncertainty instead of hiding it
Sometimes you cannot locate the original. Say so. A fair conclusion might be: "The screenshot matches language reported elsewhere, but we could not confirm an official copy." That is more useful than pretending the evidence is stronger than it is.
Preserving uncertainty also protects against later changes. If an agency updates a report or a court adds an order, you can return to the earlier version and see what changed.
A short checklist before sharing
Use this quick check when a story rests on a document:
- Can you name the issuing body, date, and document number?
- Did you find an official copy, docket entry, archive, or primary record?
- Does the quoted language appear in the full document?
- Is the file complete, with its pages and attachments intact?
- Is the document current, or has it been amended, replaced, or challenged?
- Are you treating a screenshot, leak, or repost as a lead rather than proof?
- Did you save the source link and the citation details?
If several answers are no, pause. The story may still be right. The document claim has not earned confidence yet.
The habit that keeps claims in proportion
To verify news documents is to check the trail behind the claim. Find the issuer. Compare the version. Read the surrounding text. Keep a record of what you found and what remains unknown.
A polished file can mislead. A real document can mislead when a story clips its words or ignores its limits. The stronger conclusion is the one the full record can carry.