Journalism note-taking templates serve three purposes simultaneously: they capture information accurately under time pressure, they maintain the source protection and attribution standards the profession requires, and they produce notes that are useful for reporting beyond the immediate story — notes that feed into the beat knowledge base and remain useful months or years after the original interview or document review.
Ad hoc note-taking in journalism typically fails on one of these dimensions: the notes are adequate for writing the immediate story but don't retain enough context about attribution standards, source reliability assessments, or verification status to be useful later. The journalist who returns to notes from 18 months ago finds quotes but not the context for whether they were on-record, background, or off-record — and has to guess or can't use them.
These four templates address the contexts where structure adds the most value: source interviews, document review, story thread management, and beat monitoring sessions.
Template 1: Source Interview Notes
The source interview template captures what was said, but also the attribution context, source reliability assessment, and what the notes revealed that requires follow-up verification.
SOURCE INTERVIEW NOTES — [Date]
INTERVIEW SETUP:
Source identifier: [Pseudonym or identifier — never full name for protected sources]
Interview type: [Phone / In-person / Video / Written exchange]
Story thread: [Which story or thread this interview is for]
Duration: [Approximate duration]
ATTRIBUTION STANDARD (confirmed before interview began):
[ ] On record — full name and title
[ ] On background — no name, described as: [role/affiliation description confirmed with source]
[ ] Off record — for context only, not for publication in any form
INTERVIEW OBJECTIVES:
Primary objective: [The most important thing this interview needed to establish]
Secondary objectives: [Other questions this interview addressed]
KEY STATEMENTS:
[Statement 1]
Verbatim (for potential direct quotes): "______________________________"
Paraphrase: [Brief paraphrase if too long to quote directly]
Attribution: [On record / Background / Off record]
Verification note: [Can this be independently corroborated? How?]
[Statement 2]
Verbatim: "______________________________"
Paraphrase:
Attribution:
Verification note:
[Statement 3] [Continue as needed]
CONTEXT PROVIDED (off record / background only):
[Contextual information the source provided that's not for attribution
— note what this does and doesn't tell you about the situation]
DOCUMENTS OR LEADS PROVIDED:
[ ] Document described: [What did the source describe? Have it in hand? Referred to?]
[ ] Source referral: [Did this source suggest another source? Who/what?]
[ ] Public record pointed to: [Any specific public record or document location mentioned?]
RELIABILITY ASSESSMENT:
Consistency with known facts: [Did this source's account match documents and prior reporting?]
Internal consistency: [Were there inconsistencies within this source's account?]
Perspective and interests: [What institutional position or interests might shape their account?]
Overall reliability in this interview: [Excellent / Good / Mixed / Note specific caveats]
FOLLOW-UP REQUIRED:
[ ] [Claim that requires independent verification — what would verify it?]
[ ] [Subject of critical claim: have they been contacted for response? When?]
[ ] [Additional source needed to corroborate: what category of source?]
[ ] [Document that would support or refute this source's account]
STORY THREAD NOTES:
What this interview established: [Factual claims that can be used]
What this interview opened: [New questions or leads that emerged]
How this changes the story: [Does this shift the story's frame or core claims?]
KB ROUTING:
[ ] Source reliability entry updated with this interview's assessment
[ ] Institution profile updated with intelligence from this interview
[ ] Story thread entry updated with established facts and open questions
[ ] New leads or story threads created from this interview
The attribution-confirmed-before discipline:
The attribution standard — on record, background, off record — is confirmed at the start of the interview, not negotiated after. "Off record after the fact" conversations are professionally contested and create uncertainty about what can be used. The note records which standard was agreed before the interview began.
The reliability assessment discipline:
Every interview produces a source reliability assessment that updates the source's profile in the beat knowledge base. Did this source's account prove out against documents? Were there inconsistencies? What interests shape their view? Over time, this assessment history is the most valuable source intelligence a beat reporter accumulates.
Template 2: Document Review Notes
Document review notes capture what a document says, what it establishes, and how it relates to the story's evidentiary needs.
DOCUMENT REVIEW NOTES — [Date]
DOCUMENT IDENTIFICATION:
Document type: [Court filing / Regulatory document / Financial record / Internal communication /
Other]
Document title: [Exact title if available]
Source: [Where obtained — FOIA response, court record, source-provided, public filing]
Date of document: [Date document was created or filed]
Date obtained: [Date I obtained it]
Location: [Where stored — file reference; for web documents: URL + archive.org capture]
DOCUMENT SUMMARY:
What this document is: [Brief description of document type and purpose]
What it covers: [Date range, parties involved, subject matter]
Key pages/sections: [Where the most significant content appears]
SIGNIFICANT FINDINGS:
Finding 1:
Quote from document: "______________________________"
Page/section reference: [Where in the document this appears]
What it establishes: [What this quote or finding supports for the story]
Verification status: [Verified (document in hand) / Referenced (not yet obtained) / Need context]
Story use: [How this might be used — direct quote / paraphrase / context / background]
Finding 2: [Continue as needed]
WHAT THIS DOCUMENT ESTABLISHES FOR THE STORY:
[ ] [Specific claim now document-supported]
[ ] [...]
WHAT THIS DOCUMENT DOESN'T ESTABLISH:
[Claims that still require corroboration from sources or other documents]
[Gaps in what this document covers]
CONNECTIONS TO OTHER MATERIALS:
[ ] Documents this should be compared with: [Other documents in the thread]
[ ] Sources this should be shown to for context: [Source identifiers]
[ ] Story threads this document is relevant to: [Thread names]
DOCUMENT QUESTIONS:
[ ] [What's unclear in this document that needs follow-up?]
[ ] [Is this document's authenticity verified? How?]
[ ] [Is this document's completeness verified? Could it be incomplete?]
KB ROUTING:
[ ] Institution profile updated with intelligence from this document
[ ] Story thread updated: this document added to established facts section
[ ] New story threads identified from this document
The document authentication discipline:
Every document received from a source — as opposed to obtained directly from a public record — gets an authentication step: how do I know this document is what it purports to be? Internal metadata, comparison with other known documents, source explanation of provenance. Documents that can't be authenticated are noted as such in the story.
The web source archiving discipline:
Documents found online are captured with the URL, an archive.org snapshot, and a capture date. Web pages change; the archive snapshot is the record of what the source said at the time the reporter reviewed it.
Template 3: Story Thread Notes
Story thread notes are the running case file for an active investigation or enterprise story — the place where everything is integrated, where the case is built, and where it's clear what's established vs. what remains open.
STORY THREAD NOTES — [Thread name]
LAST UPDATED: [Date]
STATUS: [Active / Cold / Published / Killed]
THREAD OVERVIEW:
Core question: [What is this thread trying to establish? One sentence.]
Why it matters: [The public interest dimension — why should this be published?]
Beat context: [How this connects to the ongoing beat coverage]
THE CASE AS IT STANDS:
ESTABLISHED FACTS (with evidence):
Fact 1: [Statement of fact] — [Source: document/source identifier/type of evidence]
Fact 2: [...]
Fact 3: [...]
[Be precise: "Established" means document-supported or corroborated by independent sources.
Single-source claims go in OPEN QUESTIONS until corroborated.]
OPEN QUESTIONS (still to establish):
Question 1: [What's not yet established or verified?]
Leads to pursue: [How might this be verified?]
Question 2: [...]
Question 3: [...]
KEY DOCUMENTS IN THIS THREAD:
[ ] [Document description] — [Status: obtained / requested / known but not yet obtained]
[ ] [...]
KEY SOURCES IN THIS THREAD:
[ ] [Source identifier] — [Role in thread: primary / corroborating / subject / expert context]
[ ] [...]
SUBJECT RESPONSE:
[ ] Subject of significant critical claims contacted: [Yes / No / Pending]
Response: [What they said, or "no response received as of [date]"]
Response deadline provided: [Date]
STORY THREAD TIMELINE:
[Date]: [What happened — reporting step, document obtained, source contacted, development]
[Date]: [...]
NEXT REPORTING STEPS:
1. [Most urgent next step]
2. [Second step]
3. [...]
PUBLICATION STATUS:
Editor briefed: [Yes / No / Date]
Legal review required: [Yes / No / Status]
Target publication: [Publication and section, if known]
Target date: [If known]
IF COLD/KILLED:
Reason cold/killed: [Why the thread stopped or was killed]
What would reactivate: [What development would make this viable again]
The "established vs. open" discipline:
The distinction between established facts and open questions is the core discipline of the story thread template. It prevents the common failure of treating single-source claims as established when they're still single-sourced, and it keeps the reporter's attention focused on the specific evidence gaps that need to be closed before publication.
Template 4: Beat Monitoring Session Notes
Beat monitoring notes are the running log of what the daily monitoring session finds — what develops on the beat and how it should be routed.
BEAT MONITORING NOTES — [Date]
MONITORING SOURCES CHECKED TODAY:
[ ] Competitor coverage: [Publications checked]
[ ] Government/agency releases: [Which agencies]
[ ] Court dockets: [Which courts]
[ ] Regulatory filings: [Which databases]
[ ] Social media monitoring: [Which accounts/hashtags]
DEVELOPMENTS FOUND:
[Development 1]
Source: [Where found — URL, document, social media]
What: [Brief description of the development]
Significance: [Why does this matter for beat coverage?]
Triage decision:
[ ] Immediate story — follow up today
[ ] Track — route to beat KB
[ ] Background context — note; no immediate action
[ ] Not relevant — ignore
If "Track" — KB routing:
Institution to update: [Which institution profile]
Story thread to update: [Which thread, or new thread to create]
What to add: [Specific intelligence to add]
[Development 2] [Continue as needed]
ITEMS FOR FOLLOW-UP:
[ ] [Follow-up item 1 — what to do, by when]
[ ] [Follow-up item 2]
SOURCE COMMUNICATIONS REVIEW:
[ ] Urgent source messages reviewed and responded to
[ ] Non-urgent messages noted for end-of-day window
BEAT KB UPDATES COMPLETED:
[ ] [Institution 1 profile updated: what was added]
[ ] [Story thread 1 updated: what was added]
[ ] [New thread created: what it is]
STORY IDEAS FROM TODAY'S MONITORING:
[ ] [Idea 1: what it is, why it's interesting, who would need to be talked to]
[ ] [Idea 2]
The daily KB routing discipline:
The beat monitoring template's most important function is enforcing the routing decision for every significant development. "Track" without routing creates a note that sits in a dated file and never feeds into the knowledge base. The template forces the routing decision — which institution profile, which story thread — at the time of monitoring, when the significance is clearest.
How the Four Templates Work Together
The four templates form a system that moves information from raw notes to organized, retrievable intelligence:
- Beat monitoring notes identify developments on the beat → triage and route to KB or story thread
- Document review notes capture the evidentiary record for active story threads → route findings to story thread established facts
- Source interview notes capture source accounts with attribution and reliability context → route to story thread, source profile, and institution profile
- Story thread notes integrate the document and source intelligence into the case being built → maintain the distinction between established facts and open questions
Each template includes KB routing fields because the notes from journalism work are only as valuable as the intelligence they add to the beat knowledge base. Notes that don't route to the KB are information consumed and lost rather than intelligence accumulated.
Source Protection in All Four Templates
All four templates are designed with source protection in mind:
- Source interview notes use pseudonyms or identifiers, never real names for protected sources. The attribution standard is recorded, not assumed.
- Document review notes record where documents were obtained, which matters for source protection when a document came from a confidential source.
- Story thread notes reference sources by identifier only; the thread file itself can be subpoenaed.
- Beat monitoring notes are least likely to contain sensitive source information, but tip intake notes that emerged from monitoring use the same pseudonym discipline.
The underlying principle: all digital notes are built as if they could be subpoenaed, because they can be. Protected source identities exist only in memory or in separately maintained, physically secured, offline notes.
Key Takeaways
-
Four templates cover the main journalism note-taking contexts. Source interview notes (with attribution standard confirmed before interview, reliability assessment after), document review notes (with significance, verification status, and authentication), story thread notes (with established facts vs. open questions clearly distinguished), and beat monitoring notes (with explicit triage and KB routing decisions).
-
Attribution standard is confirmed before the interview begins, not negotiated after. Every interview note records the attribution standard (on record / background / off record) that was agreed at the start. This prevents the post-interview "I thought that was off record" dispute.
-
The established-facts vs. open-questions distinction is the core discipline of story thread notes. Single-source claims are open questions until corroborated. Document-supported or independently corroborated claims are established facts. This distinction is what maintains the evidentiary standard under deadline pressure.
-
KB routing fields in every template are not optional. Beat intelligence captured in a dated note file that doesn't route to the knowledge base is lost. The routing step — which institution, which story thread, what to add — happens at the time of note-taking, not later.
-
All four templates are designed around source protection. Pseudonyms throughout digital notes. Attribution standards documented. Document provenance recorded. The system is built as if it can be subpoenaed, because it can.
Conclusion
Note-taking templates for journalists address the information management challenge specific to the profession: capturing accurate information under time pressure while maintaining the source protection and attribution standards the work demands, and producing notes that remain useful for beat intelligence long after the immediate story is written. The four templates — source interview, document review, story thread, and beat monitoring — form a system that moves raw notes into organized, retrievable beat intelligence with source protection built into the structure rather than applied as an afterthought.
Related reading: Clip Articles for Later Reading.