What “interview preparation” means in practice
Interview preparation is the reporting work you do before you ask a single question: collecting reliable background material, mapping who knows what, and predicting what claims will surface so you can verify them quickly. The goal is not to script the interview, but to arrive with enough context to (1) ask precise questions, (2) spot evasions or inaccuracies, and (3) follow up in real time with informed, fair pressure.
A practical workflow: from documents to a source map
Step 1: Gather primary documents first (build your “fact spine”)
Primary documents anchor your understanding and reduce dependence on secondhand summaries. Start by creating a folder (or case file) and saving every document with a consistent naming convention (date_source_topic). Then build a one-page “fact spine” that lists what the documents establish with high confidence.
- Official records: laws, regulations, court filings, judgments, police reports, inspection reports, audit reports, procurement records, meeting minutes, budgets.
- Original datasets: government open data, regulatory filings, election results, health/environmental monitoring data, financial statements.
- Direct artifacts: emails (where obtained lawfully), internal memos, contracts, invoices, photos/videos with metadata, transcripts, public presentations.
- First-person materials: diaries, letters, contemporaneous notes, recorded statements (verify authenticity and context).
Practical move: For each document, write a two-line annotation: (a) what it proves, (b) what it does not prove. This prevents overclaiming and helps you craft careful questions.
Step 2: Scan prior coverage (identify what’s known, disputed, and missing)
Prior coverage helps you avoid blind spots and reveals recurring claims, contradictions, and unanswered questions. Treat it as a map of the conversation, not as proof.
- Collect: major investigations, local reporting, trade press, press releases, op-eds, watchdog reports, academic papers, and relevant social media threads (as leads).
- Extract: key allegations, named sources, timelines, numbers, and any “everyone says” statements that lack attribution.
- Flag: points of consensus vs. points of dispute; note where coverage relies on anonymous sourcing or single-source claims.
Practical move: Create a “coverage ledger” table with columns: Claim, Outlet/Author, Evidence Cited, Who Benefits, What’s Missing, Verification Plan.
- Listen to the audio with the screen off.
- Earn a certificate upon completion.
- Over 5000 courses for you to explore!
Download the app
Step 3: Identify stakeholders (who is involved, impacted, and accountable)
Stakeholders are not just the loudest voices. They include people with decision power, people with knowledge, and people who bear consequences. Listing them early prevents a source list that is skewed toward institutions or PR-ready spokespeople.
- Direct actors: individuals/organizations taking actions central to the story.
- Decision chain: who approved, funded, signed, supervised, or enforced.
- Oversight: regulators, auditors, inspectors general, ethics boards, ombuds offices.
- Affected communities: residents, workers, customers, patients, students—especially those with limited access to media.
- Intermediaries: contractors, consultants, vendors, lobbyists, trade associations.
Practical move: For each stakeholder, write: “What do they want?” and “What do they fear?” This helps you anticipate incentives and evasions.
Step 4: Note potential conflicts of interest (COI) and incentives
Conflicts of interest are not accusations; they are context that can shape statements and decisions. Document them carefully and neutrally, and prepare to ask about them with specificity.
- Financial: ownership stakes, contracts, donations, grants, consulting fees, speaking honoraria.
- Professional: career advancement, pending promotions, performance metrics, legal exposure.
- Political: party roles, campaign ties, endorsements, appointments.
- Personal: family relationships, close friendships, rivalries (verify before raising).
- Institutional: agency mandates, budget pressures, reputational risk, litigation strategy.
Practical move: Separate “verified COI” (documented) from “possible COI” (needs confirmation). Only the first should drive direct questioning; the second should drive further reporting.
Research checklist (use before every major interview)
Use this checklist to ensure you can ask informed questions and verify answers. Treat it as a minimum baseline; add story-specific items.
1) Bios and role clarity
- Current title, responsibilities, reporting line, and decision authority.
- Employment history and relevant prior roles.
- Board memberships, advisory roles, side businesses.
- Public statements: speeches, testimony, interviews, social posts (archived).
- Known affiliations: professional associations, political committees, nonprofits.
2) Public records and filings
- Corporate registrations, beneficial ownership (where available), annual reports.
- Contracts, procurement awards, bids, change orders.
- Campaign finance records, lobbying disclosures.
- Court records: civil/criminal cases, settlements (when public), injunctions.
- Regulatory actions: citations, consent decrees, inspection outcomes.
- Property records, permits, zoning applications (as relevant).
3) Timeline (build and stress-test)
- Key events with dates, locations, and who was present.
- Decision points: approvals, sign-offs, policy changes, budget allocations.
- Public communications: press releases, advisories, internal-to-public shifts.
- External triggers: incidents, audits, elections, market changes.
Practical move: Mark each timeline entry with a confidence level: confirmed by document, confirmed by 2 sources, single-source, unconfirmed.
4) Terminology and technical basics
- Define key terms in plain language (your own glossary).
- Identify units and thresholds (ppm, dollars, rates, margins, risk categories).
- Know the standard process: how things “should” work vs. how they did.
- List common misunderstandings and misleading framings.
5) Numbers and claims you expect to hear
- Common statistics used in public debate; original sources for each.
- Baseline comparisons (year-over-year, peer cities, industry averages).
- Known disputed figures and why they differ (definitions, denominators, time windows).
6) Legal/ethical constraints and safety
- Any reporting restrictions relevant to the topic (court orders, privacy laws, minors).
- Source protection plan: how you will store notes, recordings, and documents.
- Risk assessment for vulnerable sources (retaliation, doxxing, job loss).
Source mapping: build a roster that matches knowledge to accountability
A source map is a structured list of who can answer what—and why their perspective may be partial. It helps you avoid over-relying on official spokespeople and ensures you include those most affected.
Source categories (distinguish clearly)
- Eyewitnesses: saw/heard events directly. Strength: immediacy. Risk: limited context, memory errors, stress effects.
- Experts: can interpret evidence (scientists, auditors, engineers, clinicians, statisticians). Strength: analysis. Risk: theoretical bias, consulting ties.
- Decision-makers: had authority to approve/deny/implement. Strength: accountability. Risk: legal exposure, reputation management.
- Affected communities: live with outcomes. Strength: impact and lived reality. Risk: may lack access to documents; may generalize from personal experience.
Source map template (copy/paste)
| Category | Name/Org | What they likely know | What they may not know | Incentives/COI | Access to evidence | Best questions to ask | Verification needs |
|---|---|---|---|---|---|---|---|
| Eyewitness | Photos/video? contemporaneous notes? | Corroborate with time/location records; metadata; other witnesses | |||||
| Expert | Datasets? standards? peer-reviewed work? | Check credentials; ask for methods; seek independent expert | |||||
| Decision-maker | Emails? minutes? approvals? budgets? | Match statements to documents; confirm chain of authority | |||||
| Affected community | Receipts? medical records? logs? community data? | Aggregate patterns; verify individual cases with consent |
How to use the source map during prep
- Balance: ensure each major claim has at least one source from knowledge (eyewitness/expert) and one from accountability (decision-maker).
- Redundancy: for high-stakes facts, plan at least two independent verification routes.
- Gaps: highlight “missing nodes” (e.g., the contractor who executed the work, the regulator who reviewed it, the community group tracking impacts).
Anticipate sensitive areas (and prepare to handle them responsibly)
Sensitive areas are topics that can trigger harm, legal risk, or retraumatization—or that sources may avoid because of stigma or fear. Anticipating them lets you ask necessary questions with care and clarity.
Common sensitive zones
- Trauma and violence: assault, accidents, deaths, domestic abuse.
- Health and privacy: diagnoses, disability status, medical records.
- Minors and vulnerable people: school discipline, foster care, immigration status.
- Employment retaliation: whistleblowing, union activity, harassment complaints.
- Legal exposure: ongoing litigation, criminal investigations, NDAs.
Preparation practices
- Define what you must know vs. what is optional: write “need-to-know” questions first; avoid curiosity-driven probing.
- Plan consent language: how you will explain on/off the record, attribution, and what publication could mean.
- Offer control points: allow pauses, clarify that they can decline, and avoid surprise graphic questions.
- Pre-check support resources: if interviewing traumatized sources, know local support services to share if appropriate.
Prepare verification paths for likely claims (so you’re not stuck in the moment)
Before the interview, list the claims you expect to hear—especially those that are convenient, reputationally protective, or politically useful—and pre-plan how you will verify them. This allows you to ask sharper follow-ups and reduces reliance on “he said/she said.”
Build a “claim-to-proof” matrix
| Likely claim | Why they might say it | Fast check during interview | Post-interview verification path | Independent cross-check |
|---|---|---|---|---|
| “We followed protocol.” | Deflect blame | Ask which protocol, version/date, and who signed off | Obtain SOPs, training logs, audits, incident reports | Independent expert reviews SOP vs. actions |
| “The numbers are being misrepresented.” | Undermine critics | Ask which metric, denominator, time window | Pull original dataset; replicate calculation | Statistician validates method |
| “We informed the public promptly.” | Limit liability | Ask for exact date/time and channel | Check press logs, emails, website archives, alerts | Compare with third-party timestamps (media, social, web archive) |
| “This was an isolated incident.” | Minimize pattern | Ask how they define ‘isolated’ and what period they reviewed | Request complaint logs, prior incidents, settlements | Interview affected community; review regulator data |
Verification tools to line up in advance
- Documents: policies, minutes, contracts, logs, emails, memos, inspection reports.
- Datasets: raw data, codebooks, methodology notes, data dictionaries.
- Independent experts: at least one with no visible stake; prepare a short brief and the key questions you’ll ask them.
- Technical validation: metadata checks for photos/video; geolocation; timestamp corroboration; reverse image search (as a lead, not proof).
- Field confirmation: site visits, observation, measurements (when safe and lawful).
Interview prep sheet (one-page working document)
Use a single page to keep your prep actionable during the interview.
INTERVIEW PREP SHEET (1 page) Date: ____ Interviewee: ____ Role: ____ Setting: ____
1) What is confirmed (fact spine):
-
-
2) What is disputed / unclear:
-
-
3) Top 5 questions (with document anchors):
1. Q: ____ Anchor: (doc/date/quote) ____
2. Q: ____ Anchor: ____
3. Q: ____ Anchor: ____
4. Q: ____ Anchor: ____
5. Q: ____ Anchor: ____
4) Likely claims & verification paths:
- Claim: ____ Verify via: ____ Independent check: ____
5) Sensitive areas & approach:
- Topic: ____ Why sensitive: ____ How to ask: ____
6) Source map gaps to fill:
- Missing voice: ____ How to reach: ____