Research-To-Script

Research is not a pile. It is a chain of claims that can survive a hostile read.

8 min read Depth 3 / Build Ready

TL;DR

Turn every beat into a checkable claim.
Separate evidence from interpretation.
Write the source stack before the script sings.
Stop researching when the risk is mapped.

Job To Do

Make The Episode Falsifiable

A Blindspot script should be hard to knock down because the claims are visible before the rhetoric arrives. The joke, the outrage, the map, and the edit all depend on that.

Bill Kovach and Tom Rosenstiel put verification at the center of journalism. Tim Harrower turns that into newsroom behavior: check names, titles, numbers, spellings, claims, attribution, and disputed facts before the sentence hardens into copy.

For The Blindspot, that means the script is not the first artifact. The first artifact is a claim ledger. The script comes after the claims have receipts, context, and a note on what remains uncertain.

Key Rule

No load-bearing sentence enters the script without a source, a visual proof plan, and a risk label. If it cannot meet that bar, it becomes opinion, narration, or trash.

Claim Ladder

Script Beat

Visual Proof

Risk + Status

Source + Provenance

The sentence sits on the top. The evidence stack does the lifting underneath.

Operating Model

Seed, Stack, Beat, Lock

The pipeline should be boring enough to survive a bad week. Start with a seed question, then build a claim map, then attach sources, then write the beat sheet, then run the fact pass.

Steven Pinker's clarity work is useful here because the enemy is not vocabulary. The enemy is the curse of knowledge: you know why a detail matters, so you forget to build the bridge for the viewer.

The Blindspot Binder already points toward episode folders with research, scripts, footage, assets, exports, and a local _Sources.md. Use that structure. It turns research from a drawer into a production object.

Stage	Output	Exit Test
Seed	One question and one suspected mechanism.	You can state what the episode tests.
Claim map	Chronological or causal list of claims.	Every beat can be true or false.
Source stack	Primary, expert, context, and dissenting sources.	No source is doing a job it cannot do.
Beat sheet	Story order with proof images assigned.	The viewer can follow without a footnote cloud.
Fact pass	Marked copy: fact, interpretation, opinion, joke.	A hostile reader knows what you know and how.
Script lock	VO draft ready for visual planning.	No unresolved red claims remain.

Steal This

Create _Sources.md before the first draft. Add four headings: Primary, Context, Dissent, Visual Proof. If Dissent is empty, the episode is still shopping for confirmation.

Forum Note / r/editors / Anecdotal

Documentary editors often warn that transcripts and paper cuts can hide story holes. A quote may read perfectly and still fail because the usable footage, tone, or bridge is missing. Treat this as a production warning: source logic has to meet edit logic before scripting locks.

Marked addition: editor-forum heuristic, not a reporting standard.

Claim Map

Separate Fact, Read, And Punchline

Most script confusion comes from mixing three modes. Fact: the checkable thing. Read: the interpretation. Punchline: the pressure valve that makes the interpretation memorable.

Opinion: the best Blindspot paragraph usually contains one fact, one implication, and one turn. If it contains three facts, two dates, a joke, and a moral conclusion, the viewer is doing unpaid clerical work.

Ledger Column	What Goes There	Why It Exists
Claim	The exact sentence or beat.	Prevents vague sourcing.
Source	Document, interview, book, dataset, or clip.	Shows where the claim came from.
Status	Verified, disputed, inferred, opinion.	Stops uncertainty from wearing a tie.
Visual proof	Document zoom, map, chart, archive, quote card.	Hands the editor something real.
Risk	Legal, factual, ethical, tone, rights.	Moves danger upstream.
Script beat	Cold open, setup, turn, consequence, release.	Keeps research attached to story.

Harrower's checking habits belong in this ledger: spell the name, confirm the title, attribute the contested fact, and label disputed material. The viewer does not need to see the ledger. The edit needs to feel like one exists.

Reset

The claim map is the episode's skeleton. The script is muscle, timing, and attitude.

Fact Pass

Run The Hostile Read Before The Internet Does

The fact pass is not copyediting. It is a behavior pass. Ask what a motivated critic would attack, then decide whether the source, language, and visual support can handle it.

Mark phrases that overstate causality. "Led to" is stronger than "was followed by." "Proved" is stronger than "suggested." If the evidence only supports "suggested," write that and let the edit carry the pressure.

Unsettled debate: there is no universal source count per claim. A birth date may need one reliable source. An allegation against a living person may need primary records, corroboration, right-of-reply, and careful language. Risk decides the depth.

Skip This If

The beat is clearly labeled as opinion, interpretation, or comedy. Still check that it does not smuggle in a false factual allegation.

Stop Rules

Research Ends When The Decision Is Clear

Research becomes avoidance when it no longer changes the episode. Do one final sweep for gaps, then lock the beat sheet and move to edit grammar.

Use three stop rules. First, every main claim has a source and a status. Second, every disputed claim has the dispute represented fairly. Third, every visual proof need has an assigned asset or an honest placeholder.

Then stop. Not because the subject is exhausted. Because production needs a version it can test.

"If the source cannot change the script, it is probably not research anymore."

The Blindspot Almanac working rule

Print View

Just The Checklist

Research-To-Script Checklist

Write the seed question in one sentence.
Create _Sources.md with Primary, Context, Dissent, and Visual Proof headings.
Convert every major beat into a checkable claim.
Mark each claim as verified, disputed, inferred, opinion, or joke.
Assign one visual proof plan to every load-bearing claim.
Run a hostile read for causality, names, titles, numbers, dates, and attribution.
Represent the strongest dissenting source where the topic is contested.
Move legal, rights, or defamation risks into the ledger before the edit.
Cut claims that cannot be sourced at the needed risk level.
Lock the beat sheet once new research stops changing the story order.