Immigration Claims Checklist for Political Journalism

Log verbatim wording with timecode, outlet, and event context in your CMS. Precision prevents paraphrase creep and supports tight sourcing under scrutiny.

Pull a clean clip that includes lead-in and aftermath to preserve context. Store the original file with a checksum in your shared drive.

Save URLs, timestamps, and sender information for campaign emails and social posts. Use archive links to guard against deletions.

Add fields for topic (immigration), subtopic (border encounters, crime, caravans), speaker, venue, and target audience. Structured tags enable rapid comparisons and trend tracking.

Mark numbers for immediate data retrieval workflows. Quant claims often anchor narratives and require precise denominators and timeframes.

In your CMS, link to earlier instances, previous fact-checks, and related footage. Recurrence analysis strengthens pattern reporting.

Download official Border Patrol and OFO tables from cbp.gov, noting release date and any revisions. Do not rely on screenshots circulated by campaigns.

Check CBP glossary and policy notes to distinguish event counts from unique persons and Title 42 expulsions. Misstated definitions can flip trend lines.

Use TRAC reports and DOJ data releases, saving methodology notes and date ranges. Backlogs are often cherry-picked across different metrics.

Request incident summaries from police PIOs and query state repositories for the same period and geography. Avoid conflating arrest data with conviction outcomes or immigration status.

Use Congress.gov and Clerk roll calls to verify statements about border bills or funding. Log bill versions and conference changes to avoid version confusion.

Download EOs, interim final rules, and guidance memos with effective dates. Policy timing is essential to avoid false causation claims.

Use rolling 12-month windows and month-over-month comparisons, noting migration seasonality. Display both absolute counts and rates where appropriate.

Contextualize counts by population, workforce, or geographic scale. Avoid misleading base effects by stating denominators clearly.

Use CBP sector-level breakdowns to separate legal crossings from interdictions. Claims that blur these categories distort enforcement impact.

Annotate data visualizations with start dates of key policies like asylum rule changes. Visual markers help avoid implying trends predate policy shifts.

Use international datasets to sanity-check 'caravan' narratives and regional drivers. Add notes on collection methods and lags.

Report the stage of the justice process and whether immigration status is recorded. Many databases do not reliably track status, which limits conclusions.

Use precise terms like 'asylum-seeker', 'migrant', or 'noncitizen' consistent with style guidance. Flag loaded language that frames policy as warfare.

If evidence overwhelmingly contradicts a claim, state that clearly and early. Do not frame it as a political dispute when it is a matter of fact.

Include the claim and outcome in 70 characters when possible, using 'unsupported' or 'no evidence' where warranted. Avoid attributing criminal intent without proof.

Insert a sidebar or callout that outlines screening, credible fear, and parole authority in plain language. This reduces confusion that leads to misreads.

Balance official data with voices from border officials, legal experts, and migrant advocates. Note when a source cannot provide status-verified crime data.

Summarize the claim, when and where it was made, the ruling, and link primary sources. A consistent pattern improves audience trust and newsroom reuse.

Confirm falsity with citations, identify the speaker, and document your verification steps. Public figure standards still require accuracy and fairness.

Use only what is necessary to illustrate the claim and retain full copies with cryptographic hashes. Note transformative purpose in your editorial log.

Blur faces of minors and redact asylum case numbers. Avoid exposing migrants to retaliation or legal jeopardy without consent.

Send specific questions with a deadline and note the time sent and response. Publish responses in full or summarize with links.

Coordinate with your desk on check-ins, local fixers, and de-escalation protocols. Prepare for restricted zones and CBP media rules.

Store source files, emails, and notes in WORM or similarly protected folders. This supports challenges and long-tail legal needs.

Create a dedicated box listing each dataset and document with direct links. Mirror key files to an internal drive in case of link rot.

Use schema.org ClaimReview with claim date, rating, and citation URLs. This improves platform surfacing for fact-check content.

Overlay short clips with the claim and a tiny URL to the receipts. Short, cited snippets reduce out-of-context sharing.

Write concise, legally vetted scriptlines stating the claim and evidence outcome. Include pronunciation notes for agencies and acronyms.

Calendar data drops and auto-notify editors to revisit charts and language. Add a changelog to note what changed and why.

Aggregate claims by theme to spot coordinated messaging across cycles. Use tags to power quick backgrounders for anchors and hosts.