

Documentary Script Example: From Research to Scenes
by ByThen Editorial
October 2, 2026
You have a topic, a pile of open tabs, and a rough sense of the story. What you don't have yet is a plan for what to say, what to show, and how you know each line is true. That plan is your documentary script.
A documentary script ties every spoken line to a picture and every factual line to a source. The second half matters more on YouTube than ever. Viewers check your facts in the comments, and YouTube asks creators to disclose realistic AI-generated scenes.
The fastest way to learn it is to watch one get built. So this guide takes a single real topic from the first question to finished scene plan.
Documentary Script Example Used Throughout This Guide
Example topic: The Great Molasses Flood, Boston, 1919
On January 15, 1919, a storage tank in Boston's North End burst and released about 2.3 million gallons of molasses. Twenty-one people died and about 150 were injured.
It works as a teaching case for two reasons. It is well documented, with a years-long liability hearing and a 2016 physics study behind it. And its sources disagree on several details, which gives the fact-checking steps real problems to solve.
Each step below explains the method first, then shows it applied to the molasses film, then gives you a blank template where one applies.
What You Will Build
- A documentary angle, written as one question the film answers
- A source log that tracks every factual claim
- A paper edit that turns research into story beats
- A two-column audio and visual script, with a source column and a visual-status column
- A revision log for when the evidence shifts
- A YouTube description built from the same research
Step 1: Pick a Documentary Angle Before You Research Deeply
A topic is what the film is about. An angle is the question the film answers. "The Great Molasses Flood" is a topic. It could become a disaster recap, a courtroom drama, or a physics lesson. Pick one before research swallows your week.
For this example, the angle is:
Why did a thick, slow liquid kill 21 people, and why was it so hard to pull survivors out?
That question does three jobs. It creates tension, because molasses and "fast and deadly" don't belong in the same sentence. It points to evidence that exists: a 2016 fluid dynamics study found that the cold January air thickened the spreading molasses and made rescue harder. And it tells you what to leave out. The Prohibition backstory is interesting, but it only earns a line or two.
Angle template
Topic: [the event, person, or idea]
Angle question: Why / how did [surprising outcome] happen?
What makes it surprising: [the contradiction the viewer feels]
Evidence that can answer it: [studies, records, archives, experts]
What this angle cuts: [interesting material you will NOT cover]
Run one test before moving on. If you can't name at least two sources that could answer your angle question, change the question. A great angle with no evidence becomes a script full of guesses.
Step 2: Build a Source Log for Factual Claims
A source log is a table with one row per factual claim. Each row records where the claim comes from and how confident you are. It exists so every fact in the final script can be traced back in seconds.
Journalists call a version of this an annotated draft, where each statement is tied to a source a fact-checker can verify. Documentary fact-checkers want the same thing. One told the International Documentary Association that the best script a filmmaker can bring is one fully annotated with its sourcing.
Here is the log for the molasses film. Notice how often trusted sources disagree.
| ID | Claim | Sources | Status | How the script may say it |
|---|---|---|---|---|
| C01 | The tank ruptured on January 15, 1919 | Boston.gov, Britannica | Confirmed | State as fact |
| C02 | 21 people died, about 150 were injured | Mass Moments, HISTORY | Confirmed | State as fact |
| C03 | About 2.3 million gallons spilled | Boston.gov, HISTORY | Confirmed (spill). Tank capacity varies by source | "About 2.3 million gallons." Don't quote a capacity |
| C04 | Time of the rupture | Britannica: about 12:30 pm. APS abstract: shortly after 12:40 pm. Boston.gov: a rumble at about 1 pm | Conflicting | "Just after noon" or "at lunchtime" |
| C05 | Height of the wave | Britannica: reports of 15 to 40 feet. APS abstract: contemporary accounts of about 7.6 meters (25 feet) | Estimate | "Accounts put the wave between 15 and 40 feet tall" |
| C06 | Speed of the wave | Boston.gov: about 35 mph. APS abstract: over 15 m/s, from contemporary accounts | Estimate | "Roughly 35 miles per hour, by contemporary accounts" |
| C07 | Cold air thickened the molasses and slowed rescue | ScienceDaily on the 2016 Harvard study | Confirmed (research finding) | State as a finding and name the researchers |
| C08 | A court-appointed auditor blamed structural failure and rejected the sabotage claim | Mass Moments, Old North Church | Confirmed | State as fact, attribute to auditor Hugh W. Ogden |
| C09 | Damages paid to victims | HISTORY: $628,000. Old North Church: Ogden assessed $300,000 | Conflicting | Cut until checked against the auditor's report |
| C10 | The molasses was "hot" | A HISTORY retelling calls it hot. The 2016 research describes warm molasses added to a tank of colder molasses | Rejected wording | Say "warmed for transfer," never "fiery hot" |
Source log template
| ID | Claim (one fact per row) | Source + link | Source type (primary / secondary / research / interview) | Status (confirmed / estimate / conflicting / rejected) | Approved script wording |
|---|---|---|---|---|---|
Three rules keep the log honest:
- One claim per row: "21 dead and 150 injured" can stay together only because the same sources report both.
- Write to the confidence level: An estimate gets estimate wording. A conflict gets vague wording or gets cut.
- Log the claims you reject: C10 stops a dramatic but shaky word from sneaking back in during the edit.
Step 3: Organize Research Into a Paper Edit
A paper edit is your film assembled on paper before anyone touches a timeline. Filmmakers usually build it after shooting, from transcripts and a "selects" list that records the file, timecode, and speaker for each chosen moment. Some teams lay it out like a spreadsheet, with columns for source, timecode, visuals, audio, and notes.
If you make voiceover-led videos, your "footage" is your research. Your selects are archival photos, documents, published expert findings, and the claims in your source log. The job stays the same: put the strongest material in an order that answers your angle question.
The molasses film targets about 8 minutes, split roughly 25 / 50 / 25 across three acts. That split follows the three-act guide Documentary Film Academy recommends.
| Beat | Act | Target runtime | Material (selects) | Claim IDs | Job in the story |
|---|---|---|---|---|---|
| 1. A warm lunch hour | 1 | 0:00 to 0:45 | Archival street photos, 1919 newspaper front page | C01, C04 | Hook: normal day, strange threat |
| 2. The tank that leaked | 1 | 0:45 to 2:00 | Tank photos, historian's account | C03, C11 | Set up the warning signs |
| 3. The rupture | 2 | 2:00 to 3:15 | Aftermath photos, illustrative wave sequence | C05, C06 | The inciting event |
| 4. How a slow liquid moved fast | 2 | 3:15 to 4:45 | Physics findings, simple diagrams | C12 | Answer half of the angle question |
| 5. The cold trap | 2 | 4:45 to 6:00 | 2016 study findings, rescue photos | C02, C07 | Answer the other half |
| 6. Who was to blame | 3 | 6:00 to 7:15 | Court record, auditor's report | C08 | Resolve the conflict |
| 7. What the flood left behind | 3 | 7:15 to 8:00 | Present-day street, memorial plaque | C13 | Reflection and closing line |
Paper edit template
| Beat | Act | Target runtime | Material (selects) | Claim IDs | Job in the story |
|---|---|---|---|---|---|
| 1. |
The "Job in the story" column is the one to guard. If you can't say what a beat does for the angle, cut it. Beat 2 almost lost its place until C11 gave it a real job: the warning signs everyone ignored.
Step 4: Use a Two-Column Audio and Visual Template (Then Add Two Columns)
The classic documentary script template has two columns. Visuals sit on one side, and the audio that plays over them sits on the other, lined up row by row. Start a new row whenever the picture changes.
For factual videos, two columns leave out two questions a viewer, an editor, or a fact-checker will ask. Where did that line come from? And is that picture real? So this template adds a Source column and a Visual status column.
Documentary script template (four columns)
| Visual | Visual status | Audio | Source IDs |
|---|---|---|---|
| What the viewer sees | FILMED / ARCHIVE / DOCUMENT / RECON / ILLUS / GRAPHIC | Tagged line: NARR, INT, ARCH, SFX, MUSIC | Claim IDs from your source log |
To time a draft, count narration words. Most creators speak between 130 and 160 words per minute. An 8-minute film lands near 1,000 to 1,300 words of narration, minus the space you leave for sound and archive audio.
Step 5: Separate Interviews, Archives, and Narration
Tag every audio line by where it comes from. Viewers trust these voices differently, so your script should never blur them.
- NARR: your narration. You wrote it, so every factual sentence needs a Source ID.
- INT: an interview you recorded. Log the file name and timecode.
- ARCH: audio or text from the historical record, like a newspaper headline read aloud or a court transcript line. Log where it lives.
- SFX / MUSIC: sound design. No source needed, but note anything AI-generated (Step 6 explains why).
The same logic applies to pictures. A 1919 photo and a modern street shot are both "real," but only one shows the event. The Visual status column keeps that difference visible all the way to export.
Step 6: Label Reconstructions and Illustrative Visuals
Most history videos need pictures that don't exist. Nobody filmed the molasses wave. You will fill that gap with one of two things, and they need different labels.
| Label | What it is | Example from this film | What to do |
|---|---|---|---|
| RECON | A realistic depiction of the real event, made after the fact (staged or AI-generated) | A photorealistic shot of the wave hitting Commercial Street | Label it on screen and disclose it on upload (see below) |
| ILLUS | A non-literal visual that supports the narration without claiming to show the event | A stylized animation of molasses thickening as it cools | Keep it clearly stylized. Never place it as proof of a claim |
YouTube requires creators to disclose AI content that generates a realistic scene that didn't actually occur, or that alters footage of a real event or place. A photorealistic AI wave in 1919 Boston fits that description. YouTube also lists AI-generated music as something to disclose. Clearly unrealistic content and production help, like using AI to draft a script or thumbnail, does not need disclosure. Creators who repeatedly skip required disclosure risk labels being added for them, content removal, or suspension from the YouTube Partner Program.
The documentary industry goes further. The Archival Producers Alliance's best practices suggest a temporary watermark on generative AI material during editing, plus audience-facing disclosure through lower thirds, narration, or top-of-show language. They also recommend a cue sheet listing every generative AI element.
For a solo creator, that translates to three habits:
- Mark RECON and ILLUS in the script, so the label survives into the edit.
- Put a small on-screen label on every RECON shot, like "Reconstruction" or "AI-generated illustration."
- List reconstructed and AI-generated elements in the video description.
Step 7: The Worked Example, From Research to Scene Plan
Here is the documentary script example itself, written in the four-column template. It covers the key rows of beats 1 through 6. Every narration line matches the "approved wording" column of the source log.
| # | Visual | Visual status | Audio | Source IDs |
|---|---|---|---|---|
| 1 | 1919 photo of Commercial Street, slow push-in | ARCHIVE | MUSIC: sparse piano. NARR: "January 15, 1919. Just after noon in Boston's North End, and the air is unusually mild for winter." | C01, C04, C14 |
| 2 | Stylized silhouette of a tall steel tank against a pale sky | ILLUS | NARR: "Above the street stands a steel tank about 50 feet tall. It holds molasses bound for industrial alcohol." | C15 |
| 3 | Close-up drawing of dark streaks running down riveted seams | ILLUS | NARR: "It also leaks. According to historian Stephen Puleo, the company painted the tank brown so the seepage would be harder to see." | C11 |
| 4 | Photorealistic wave of molasses surging down a cobbled street. On-screen label: "AI reconstruction" | RECON | SFX: low rumble, then rushing liquid. NARR: "Then the tank splits open. About 2.3 million gallons pour out. Accounts put the wave between 15 and 40 feet tall, moving at roughly 35 miles per hour." | C03, C05, C06 |
| 5 | Scan of the Boston Post front page, January 16, 1919 | DOCUMENT | ARCH: headline read aloud, "Huge molasses tank explodes in North End. 11 dead, 50 hurt." NARR: "The real toll was worse." | C16, C02 |
| 6 | Two beakers, water and molasses, tipped side by side | GRAPHIC | NARR: "Molasses is about one and a half times as dense as water, and roughly 4,000 times more viscous. A wave of it doesn't splash. It shoves." | C12 |
| 7 | Stylized animation of molasses turning thick and glossy as it cools | ILLUS | NARR: "Then the cold went to work. In 2016, fluid dynamicist Nicole Sharp and Harvard researchers found the winter air thickened the spreading molasses. That made every rescue harder." | C07 |
| 8 | 1919 photo of rescuers in the wreckage | ARCHIVE | NARR: "Twenty-one people died. About 150 were injured." | C02 |
| 9 | Title page of the auditor's liability report | DOCUMENT | NARR: "The company blamed sabotage. In 1925, court-appointed auditor Hugh W. Ogden rejected that claim and found the tank had failed structurally." | C08 |
A few choices are worth copying:
- Row 4 is the only RECON shot. It carries an on-screen label, and the narration beneath it uses estimate wording. The picture shows what the accounts describe. It doesn't pretend to prove them.
- Row 5 turns a sourcing problem into a story beat. The early headline undercounted the dead. Instead of hiding that, the script uses the gap between first reports and the final toll.
- Rows 2, 3, and 7 are ILLUS, not RECON. They are stylized on purpose, so no viewer mistakes them for 1919 footage.
- This film has no interviews. If you add one, it gets its own INT row with a file name and timecode in the Source column.
Step 8: Revise the Script as Evidence Changes
A documentary script is never locked while you are still learning. Information that looked solid during research can turn out irrelevant or false later, so every claim needs checking right up to the end.
Published sources revise too. The Live Science report on the 2016 molasses study carries an editor's note saying it was updated to correct the temperature of the molasses. If you had copied the first version into your script, your film would now be wrong.
Claim IDs make revision fast. When a fact changes, you fix the log row first, search the script for that ID, and rewrite every row that cites it. Then you record the change.
Here is how the molasses script changed across its drafts:
| Version | Claim ID | Change | Reason | Script rows affected |
|---|---|---|---|---|
| v4 | C09 | Cut the damages figure from row 9 | Two credible sources give different amounts | 9 |
| v3 | C10 | Replaced "hot molasses" with no temperature claim | The 2016 research describes warmed molasses. "Hot" overstates it | 4 |
| v2 | C05 | "A 40-foot wave" became "between 15 and 40 feet tall" | 40 feet is the top of a reported range, and the APS summary cites about 25 feet | 4 |
| v2 | C04 | "At 12:30" became "just after noon" | Sources place the rupture anywhere from 12:30 to about 1 pm | 1 |
Revision log template
| Version | Claim ID | Change | Reason | Script rows affected |
|---|---|---|---|---|
| v1 |
If the video is already live, update the sources and corrections in the description, and pin a short correction comment when the change matters. The source log tells you exactly what to fix.
Step 9: Turn Your Source Log Into the YouTube Description
The description is the last page of your documentary script. It is where viewers check your sources, where your AI disclosure lives, and where search engines learn what the video covers. This is the end-to-end playbook: why it matters, how to structure it, where keywords go, what to link, and how to write it in the same session you generate the video.
Why the Description Matters
- It tells YouTube what the video is about. YouTube says descriptions inform both the algorithm and viewers, and that search terms are matched against the video and its description text.
- The first lines do most of the work. Viewers see only the opening lines until they tap "Show more" on desktop or "more" on mobile.
- It proves the research is real. A documentary without sources asks for blind trust. A linked source list lets curious viewers check you, and it separates your work from low-effort uploads. YouTube's spam policy specifically targets channels that mass-produce near-identical AI videos.
- It carries your disclosure. Step 6 flagged every RECON shot and AI music cue. The description is where viewers can read that list.
Description Structure: Best-Practice Order
YouTube allows up to 5,000 characters and recommends a unique description for every video. Use the space in this order:
- Opening lines (above the fold). One or two sentences with your main keyword and what the viewer will learn. Third-party guides treat the first 100 to 160 characters as the visible window, since it varies by device.
- Short summary. Two or three sentences that restate your angle question. Work in one or two secondary keywords where they read naturally.
- Chapters. Timestamps with titles. YouTube requires the first to start at 00:00, at least three in ascending order, each chapter at least 10 seconds long.
- Sources. The confirmed rows of your source log, with links.
- Visuals and AI disclosure. Which shots are reconstructions or AI-generated, plus any AI music. Also set "AI use" to Yes in YouTube Studio when your content meets the disclosure rules.
- Links and one CTA. A related video or playlist, credits for collaborators, and a single ask.
- Hashtags. Two or three relevant ones at the end. Up to three appear near the title, and a video with more than 60 hashtags has all of them ignored.
Links and CTA
Keep one primary call to action. Everything else is navigation: a playlist of related videos, credits for people who helped, and your channel links. YouTube recommends linking playlists and mentioning collaborators for exactly this reason. Put the CTA after the sources, so trust comes before the ask.
YouTube Description Template
[Main keyword] + [what the viewer learns, in one sentence].
[Second sentence: the surprising angle, in plain words.]
[2 to 3 sentence summary. Restate the angle question. Use 1 to 2 related terms naturally.]
CHAPTERS
00:00 [Beat 1 title]
[mm:ss] [Beat 2 title]
[mm:ss] [Beat 3 title]
SOURCES
- [Source title], [publisher]: [link]
- [Source title], [publisher]: [link]
ABOUT THE VISUALS
Archive: [where historical images come from]
Reconstructions: [which scenes are staged or AI-generated]
AI audio: [AI music or voice, if used]
WATCH NEXT: [related video or playlist link]
[One CTA]
#[hashtag1] #[hashtag2] #[hashtag3]
Filled Example: The Molasses Film
The Great Molasses Flood of 1919 killed 21 people in Boston. This documentary explains how a slow, sticky liquid turned deadly.
On January 15, 1919, a 50-foot tank in Boston's North End split open and released about 2.3 million gallons of molasses. We follow the physics of the wave, the cold that trapped survivors, and the court case that decided who was to blame.
CHAPTERS
00:00 A warm lunch hour
00:45 The tank that leaked
02:00 The rupture
03:15 How a slow liquid moved fast
04:45 The cold trap
06:00 Who was to blame
07:15 What the flood left behind
SOURCES
- Boston.gov: 100 years ago today, molasses crashes through Boston's North End
- APS Division of Fluid Dynamics (2016): Sharp, Kennedy & Rubinstein, the physics of the Boston Molasses Flood
- Mass Moments: Hugh Ogden issues report on cause of the Molasses Flood
- Boston Post, January 16, 1919, via Boston Public Library
ABOUT THE VISUALS
Archive: 1919 photographs and newspaper scans, credited on screen.
Reconstruction: the wave sequence at 02:00 is AI-generated and labeled on screen.
Illustrations: the tank and cooling sequences are stylized, not historical footage.
WATCH NEXT: [your history playlist]
#history #boston #documentary
Check the chapter times against your final export before publishing. The paper edit gives you targets, and the edit decides the truth.
Write It While the Video Generates
You don't need a separate writing session. Every part of the description already exists in your script files:
| Description part | Comes from |
|---|---|
| Opening lines and summary | Your angle question (Step 1) |
| Chapters | Paper edit beats and runtimes (Step 3) |
| Sources | Confirmed rows of the source log (Step 2) |
| About the visuals | Visual status column and audio tags (Steps 5 and 6) |
So draft it in the same sitting you produce the video. Paste your finished script into your video tool, start generation, and fill the template while it renders. When the edit is final, lock the chapter timestamps and publish both together.
From Script to Video With ByThen
A finished four-column script is a production plan. ByThen is an AI video producer built for long-form storytelling, and it can turn that plan into a video up to 30 minutes long. Script, voice, music, visuals, and editing all happen in one place.
Here is how the script maps onto it:
- Your approved wording stays approved. Paste your own final script and ByThen visualizes it, instead of rewriting it from a topic.
- The storyboard is your label check. Review the film scene by scene before full generation. ILLUS scenes should look stylized. RECON scenes need a label.
- Archive stays real. Upload your licensed photos and newspaper scans in the editor and place them on the ARCHIVE and DOCUMENT rows.
- Labels go on in the editor. Add a text overlay like "AI reconstruction" to every RECON shot. Captions are generated automatically.
- Disclosure follows the audio too. If you use generated music, list it under "About the visuals" and answer YouTube's AI use question honestly.
The research is yours. The production doesn't have to take a week.
FAQ
What is a documentary script? expand_more
A documentary script is the plan that matches every spoken line to a picture and every factual line to a source. It usually takes the form of an A/V script, a paper edit, or both. Unlike a fiction screenplay, it gets rebuilt as research and footage come in.
What is the best documentary script template? expand_more
Start with the standard two-column audio and visual layout, then add a Source IDs column and a Visual status column. The extra columns show where each fact comes from and whether each picture is archive, reconstruction, or illustration. The four-column template in Step 4 is ready to copy.
How long should a documentary script be for a 10-minute video? expand_more
At 130 to 160 spoken words per minute, 10 minutes of nonstop narration is about 1,300 to 1,600 words. Most documentaries need less, because music, sound, and archive audio take up time too.
Should I write the script before or after research? expand_more
After your angle and your first research pass, before production. Documentary Film Academy recommends writing the A/V script before filming for narrator-led films. For interview-led films, it suggests an outline first and a detailed paper edit once interviews are done.
What is the difference between a paper edit and an A/V script? expand_more
A paper edit orders your selected material into story beats. An A/V script turns those beats into row-by-row pictures and sound. In this guide, the paper edit comes first (Step 3) and the A/V script is built from it (Step 7).
Do I have to disclose AI-generated visuals in a YouTube documentary? expand_more
Yes, when they look realistic. YouTube requires disclosure when AI generates a realistic scene that didn't happen or alters footage of a real event or place. Clearly unrealistic visuals don't need it. YouTube also says disclosure won't limit a video's audience or its eligibility to earn money.
Can I use AI to help write a documentary script? expand_more
You can. YouTube treats AI help with outlines and scripts as production assistance that doesn't need disclosure. The facts still need checking. Generative AI can produce hallucinated information with made-up citations, so trace every claim back to a real source (CSUN Library). Your source log is where that check happens.
Sources & Citations
keyboard_arrow_up
- YouTube. (2026). Disclosing use of GenAI content. Official YouTube Help guidance on what altered or synthetic content must be labeled, with examples that require and do not require disclosure.
- YouTube. (2026). Tips for video descriptions. Official YouTube Help guidance on the first lines viewers see, keyword choice, unique descriptions, and the 5,000-character limit.
- YouTube. (2026). Video Chapters. Official rules for adding chapters through timestamps, including the 00:00 start, the three-timestamp minimum, and the 10-second minimum length.
- YouTube. (2026). Find playlists & videos using hashtags. Official hashtag rules, including the three hashtags shown near the title, the 60-hashtag limit, and the ban on repetitive descriptive tags.
- YouTube. (2026). Spam Policy. Official policy on misleading metadata and mass-produced, repetitive AI content.
- New York Film Academy. (2023). How to Write a Documentary Script. Film school guide describing the standard video and audio column layout.
- Documentary Film Academy. (n.d.). How to Write a Documentary Script: The Complete Guide (With Free Templates). Filmmaker guide to A/V scripts, paper edits, selects documents, and three-act structure.
- Beverly Boy Productions. (2025). How to Write a Documentary Script. Production company guide describing the paper edit as a spreadsheet of timecodes, visuals, audio, and notes.
- International Documentary Association. (2024). The No-Spin Zone: How Journalistic Documentaries Check Their Facts. Feature on documentary fact-checking and the value of scripts annotated with sources.
- The TiJ Project. (n.d.). The TiJ Fact Checking Guide: Fact-Checking as Part of the Editorial Process. Journalism guide to annotated drafts, where each statement is tied to a verifiable source.
- Journalism University. (2026). Crafting Engaging Scripts for Documentaries. Guide stressing that every claim in a documentary script must be verified throughout production.
- StudioBinder. (2026). Script Writing on YouTube Examples. YouTube scriptwriting guide citing a speaking pace of 130 to 160 words per minute.
- vidIQ. (2026). YouTube Video Descriptions: How to Write Them Better in 2026. Third-party guide suggesting the first 100 to 160 characters as the visible description window.
- California State University, Northridge Library. (2026). Citing Sources: CTVA 331 Producing the Documentary. University research guide warning that generative AI can produce hallucinated citations that must be verified.
- PBS Standards. (n.d.). Archival Producers Alliance Develops Guidelines for AI Use in Documentaries. Summary of the APA's inward and outward transparency recommendations, including watermarks and on-screen disclosure.
- Desktop Documentaries. (n.d.). Best Practices for Use of GenAI in Documentaries. Overview of the APA guide, including its recommendation to keep cue sheets for all generative AI elements.
The Great Molasses Flood (worked example)
- City of Boston. (2019). 100 Years Ago Today: Molasses Crashes Through Boston's North End. City account of the tank's size, the 2.3 million gallons, the wave speed, and the painted-over leaks.
- Encyclopaedia Britannica. (2026). Great Molasses Flood. Encyclopedia entry with the tank's dimensions, the reported wave height range, and the time of the rupture.
- HISTORY. (2017). Great Molasses Flood of 1919: Date, Deaths & Facts. Narrative history covering the mild weather, the spill volume, and a damages figure.
- HISTORY. (2025). Why the Great Molasses Flood Was So Deadly. Article on the physics and neglect behind the disaster, including casualty figures.
- Mass Moments. (n.d.). Hugh Ogden Issues Report on Cause of the Molasses Flood. Massachusetts history entry on the auditor's 1925 finding of structural failure.
- Old North Church. (2026). The 1919 Molasses Flood: Destruction, Immigration, and Active Citizenship in Boston's North End. Historic site article on the auditor's report, the rejected sabotage claim, and a differing damages figure.
- American Physical Society. (2016). In a Sea of Sticky Molasses: The Physics of the Boston Molasses Flood. Conference abstract by Sharp, Kennedy, and Rubinstein with contemporary estimates of wave height and speed, plus molasses density and viscosity.
- ScienceDaily. (2016). Molasses Creates a Sticky Situation. Research summary explaining how cooling thickened the molasses and complicated rescue.
- Live Science via Fox News. (2016). Great Molasses Flood of 1919: Why This Deluge of Goo Was So Deadly. Report on the 2016 study, with an editor's note correcting the molasses temperature.
- Boston Public Library. (1919). Huge Molasses Tank Explodes in North End; 11 Dead, 50 Hurt (Boston Post, January 16, 1919). Digitized front page from the library's collection, listed with no known restrictions.
