Build Your Local Evidence Lab: How Small Teams Verify Big Claims

The mission

Turn neighbors into verifiers. Pick one claim. Pull the primary record. Cross-check with one solid outside source. Say limits. Update if facts change. That is the receipts test. It works at the local level where most power hides in plain sight.

Team of five. That’s enough.

  • Lead runs scope, timeline, and quality.
  • Records files open records requests and tracks responses.
  • OSINT searches public data, budgets, contracts, corporate filings.
  • Context interviews subject-matter folks and logs quotes.
  • Publishing packages the post, visuals, and change log.

The Receipts Stack

  1. Name the claim. Write it in one sentence and date it.
  2. Primary record. Budget line, contract, docket, statute, invoice, email, meeting minutes, sworn statement, or dataset.
  3. Outside check. Auditor report, court order, neutral database, or independent newsroom piece that cites documents.
  4. Limits. What the record does not show. Gaps, redactions, timing.
  5. Update rule. If better evidence appears, fix the post and log the change.

Primary Evidence

List the exact documents you pulled. Use file names people can click and understand. Example:

  • 2024-05-14_CityBudget_Amendment_Ordinance_24-113.pdf
  • VendorContract_RiverWorksLLC_StormDrain_#SD-2023-071.csv
  • CourtOrder_Case_22-CV-01988_PublicRecords_Granted.pdf

Add the retrieval path. Agency, clerk window, or portal. Note fee waivers and timelines.

Contradictions

Put the conflict on the table. What the claim said versus what the documents show. Quote the line that matters. Then show the exact cell, page, or timestamp that disagrees. If both can be true under different definitions, spell out the definitions and why they matter.

Analytical Summary

Write the bottom line in plain language. One paragraph. No spin. Tell readers what is proven, what is likely, and what still needs work. Link back to the primary record above.

Simple workflow that ships

  1. Scope: 1 claim, 7 day window, single question to answer.
  2. Records request: file today. Track deadlines. Calendar appeals.
  3. OSINT sweep: budgets, meeting videos, permits, company registries.
  4. Phone a human: one subject-matter call for context. Record with consent.
  5. Assemble packet: PDFs, datasets, and a one-page summary.
  6. Publish: post, feature image, alt text, and a change log at the bottom.
  7. Distribution: Facebook group, neighborhood app, email list, and a one-minute vertical video that points to the post.

Copy-paste templates

Claim line: “On [date], [person/office] said [claim].”

Records request subject: “Public Records Request — [topic] — Narrow scope for fastest release.”

Change log entry: “Updated [date]: Added [document]. Conclusion unchanged.”

Tools that stay free or cheap

  • Agency portals for agendas, minutes, budgets, and bids.
  • State business registry for ownership and filings.
  • Court search for orders and docket entries.
  • Public meeting video archives for exact quotes and timestamps.
  • Spreadsheet and a shared folder. Keep it boring and organized.

Safety and fairness

  • Redact private info that the law protects.
  • Right of reply. Give 24 hours for comment when feasible and note the outcome.
  • Separate facts from opinions. Put opinions in a labeled section.

What to publish at the end

  • A one-paragraph verdict in plain English.
  • A short receipts list with links to the exact files.
  • One clean chart if numbers drive the story.
  • A change log that keeps trust high.

Leave a Comment

Your email address will not be published. Required fields are marked *

Copyright © 2026 Evidence Matters. All rights reserved.
Scroll to Top