River
Y CombinatorBacked by Y Combinator
FREE TEMPLATE

Investigative No-Surprises Letter Template

Three documents and two sheets that draft the letter from a finding-to-evidence map, then log each response so nothing changes without a documented reason.

Free download  ·  No account needed

Every no-surprises letter guide says the same thing: list every finding, set one deadline, and give the subject a real chance to respond before the story runs. The Ethics and Journalism Initiative's explainer on the no-surprises rule walks through exactly that, down to how many attempts to make first. What none of them cover is where the response goes once it arrives, or how a reader is supposed to know a correction actually reconciles against the original evidence rather than just replacing one assertion with another.

This pack keeps the two joined. The Finding to Evidence Map holds one row per finding, each paired with its specific evidence and a confidence rating, and the No-surprises Letter drafts straight from that map rather than being written separately. On the worked file, a nursing-home operator's payroll records showed 2.1 direct-care hours per resident per day, below the state's 2.5-hour minimum. Its response added 2,208 contractor hours the original tally had missed, which moves the average to 2.3, an amount that reconciles exactly and still leaves the finding standing.

Built for reporters and editors running a pre-publication comment process on a piece with enough findings that a single memory cannot hold what each one drew back. Nine findings on the worked file drew seven responses; two were revised, one was retracted outright, and four held with the subject's disputed context attached as a quote. That is the register doing its job, not the story getting softer. Pair it with the investigation evidence file upstream, add a records request for what a finding still needs, and send the piece to fact check before it runs.

One finding corrected, one finding dropped, both logged

The Finding to Evidence Map, the letter it drafted, and the Response Register showing what each answer actually changed.

Finding to Evidence Map

Illustrative example: Meridian Care Group, Riverside facility. 9 findings, each paired with its own evidence before the letter goes out.

IDFindingEvidenceConfidence
F-001Riverside averaged 2.1 direct-care hours per resident per day in Q3, below the 2.5-hour state minimum.Payroll export filed with the stateHigh
F-006Riverside's fall-related incident reports rose 18% in Q3 against Q2.Internal log + public filingMedium
F-009Meridian's staffing algorithm does not adjust for two-person transfer residents.Internal scheduling documentationMedium

Nine rows on the full map, each with its own evidence and confidence rating. A compound claim gets split into separate rows, because a subject who can dispute one part of a bundled finding gets to cast doubt on the whole row.

No-surprises Letter, excerpt

Drafted straight from the map. Every numbered item corresponds to a row, so a response naming “finding 1” is unambiguous.

FieldValue
Response requested by2026-01-26, 5:00 PM Eastern
Prior contact attempts3 since Nov 2025
Finding 1“Riverside averaged 2.1 direct-care hours per resident per day in Q3 2025, below the state's 2.5-hour minimum.” (F-001)
Finding 9“Meridian's staffing algorithm does not adjust for residents requiring two-person transfer assistance.” (F-009)

A finding stated plainly gives the subject something specific to respond to. A finding hedged into vagueness gives them nothing to correct, which defeats the letter's purpose.

Response Register

What came back, logged against the same row, with an outcome that is one of four things and not a fifth.

IDResponseOutcomeWhat changed
F-001Payroll correction: 2,208 contractor hours were logged in a separate system and omitted.Revised2.1 → 2.3 hrs/resident/day. Still below the 2.5-hr minimum; finding stands, corrected.
F-006Internal audit found 3 of 18 added incident reports were migration duplicates.Revised18% → 15% rise. Audit cited as the correction's source.
F-009Scheduling documentation shows a manual override exists for two-person transfers.RetractedFinding dropped. Piece instead reports override-usage frequency.

Two findings revised with documentation that reconciles against the original evidence, one retracted outright, four confirmed unchanged, two drew no response. Seven of nine answered is not the same as seven of nine changed, and the register is what keeps the difference visible.

What's in the pack

01

Finding to Evidence Map

One row per finding, written the way it will actually run, paired with the specific document, record or named source behind it and a confidence rating. A compound claim splits into separate rows.

02

No-surprises Letter

Drafts straight from the map rather than from a blank page, numbered to match so a response naming a finding by number is unambiguous, with a specific deadline and a named point of contact.

03

Response Register

One row per finding logging what came back: confirmed, revised, retracted or no response. A denial with no documentation does not move a finding that already has documentary support.

04

Revision Note

Every change explained for an editor or a legal read, with the specific document behind each correction and the arithmetic shown reconciling against it rather than just asserted.

05

Response Log

The narrative record of every contact attempt and every reply, in order, separate from the register's per-finding outcomes: what happened, and when.

06

A space rule that logs before it revises

A response gets logged with its date and documentation status before any finding changes, and silence on some findings while answering others is tracked as its own outcome, not blank.

How to use it

  1. 1

    Send your findings

    Whatever you have, a draft, source documents, or a list of claims you intend to run, however rough. River pairs each one with its specific evidence.

  2. 2

    River drafts the letter

    The No-surprises Letter draws directly from the map, numbered to match, with a deadline and a named point of contact for the response.

  3. 3

    Log each response as it lands

    Confirmed, revised, retracted or no response, logged against the finding it addresses before anything in the draft changes.

  4. 4

    Write the revision note

    Once every finding has an outcome, the note explains what changed, what was dropped, and what stood despite a reply, checkable against the record.

Frequently asked questions

Is this template free?

Yes. The No-surprises Letter, Response Log and Revision Note download as Word files and the Finding to Evidence Map and Response Register as CSV, with no signup. "Edit with AI" is a separate optional path for building the map and register from your own findings.

How is this different from just sending one letter listing every finding?

The letter is the easy part; most guides cover it well. What they skip is afterward. This pack ties each finding to its evidence before the letter goes out, then logs what comes back against that same row, so a reader can see a correction reconcile rather than just replace one assertion with another.

What if the subject doesn't respond at all?

Every finding with nothing logged by the deadline is marked no response, not left blank, and the piece states plainly that comment was sought on that specific point. On the worked file two of nine findings drew nothing despite seven others being answered.

What actually separates a revised finding from a retracted one?

Documentation that corrects a detail, a number or a date without contradicting the underlying claim gets the finding revised and run with the correction. Documentation that contradicts the claim itself gets the finding dropped; a nursing-home operator's own scheduling records retracting a staffing-algorithm finding is the worked example.

Does this replace a lawyer's pre-publication read?

No, it feeds it. The Reporters Committee's guide to pre-publication review notes that including the subject's response, even a flat denial, supports your defense if you're sued later. The Revision Note is exactly the document a legal read wants to see first.

What format are the downloaded files?

Word documents for the No-surprises Letter, Response Log and Revision Note. CSV for the Finding to Evidence Map and Response Register, one row per finding, matching the pack's structure exactly. Everything opens natively in Word, Excel or Sheets, with no conversion step.

What does 'Edit with AI' actually do?

It creates a free account and installs this exact pack as a private workspace. The agent reads whatever findings and evidence you send to build the map, drafts the letter from it, then logs each response as you report it.

Put every finding to the subject, and keep what they said

Download the blank map, letter, log and register as Word and CSV files, or open this exact pack in River and send it your findings as you have them.

Edit with AI