Screenwriters work in multiple professional contexts that generate different kinds of knowledge: solo research and script development, development meetings where feedback and relationship intelligence are both important, writers' rooms where story knowledge is built collaboratively, and craft learning moments that come from reading produced scripts or watching produced work. Each context generates knowledge that's valuable if captured and unavailable if not.
Four note-taking templates structure the most important professional contexts for screenwriters: story and world research notes, script notes and feedback notes, writers' room notes, and craft and professional development notes. Each template captures the layer of knowledge that specific context generates, organized for retrieval when the relevant need arises.
Template 1: Story and World Research Notes
Story and world research notes convert research — reading, expert conversations, primary document review — into retrievable professional knowledge that supports both the current project and future projects set in similar worlds.
STORY AND WORLD RESEARCH NOTES
Source: [Title + Author/Expert + Publication/Affiliation]
Research type: [ ] Reading [ ] Expert conversation [ ] Site/field research [ ] Document review
Date: [When]
Project: [What project this is for, or "general KB" if not project-specific]
IF EXPERT CONVERSATION:
Expert: [Name + Role + How I know them]
Topics covered: [Main areas of the conversation]
Key things they told me: [The specific insider knowledge]
What I should follow up on: [Questions that arose]
Can I quote them? [ ] Yes [ ] No [ ] Ask first
IF READING/DOCUMENT:
What I captured: [Key information — verbatim for direct quotes, paraphrase noted]
URL (if online): [Link]
Archive URL: [Backup link]
Citation: [For any work where sourcing matters]
FOR THE SCRIPT:
Dramatic implication: [What conflict, complication, or authenticity this enables]
Specific scene application: [If applicable — where in the script this matters]
What NOT to show (authentic but dramatically slowing): [What to keep as background]
KB UPDATE:
[ ] World/research KB updated
[ ] Professional contacts KB updated (if new expert relationship)
[ ] Relevant to future projects: [Yes — tag for what type of project]
The "can I quote them?" field in expert conversation notes is the professional ethics field. Expert consultants who contribute to a script's authenticity may expect to be credited in the "special thanks" section; some may have professional reasons to not be publicly associated with a project's specific portrayals. Capturing this at the time of conversation avoids the awkward retrospective negotiation.
The "relevant to future projects" field converts project-specific research into general KB investment. A writer who has researched emergency medicine for one medical pilot has built a research library; tagging that research for "medical world" makes it retrievable for future projects rather than siloed in one project's folder.
Template 2: Script Notes and Feedback Notes
Script notes — from development executives, producers, showrunners, agents, and managers — are professional communications that require careful processing. The notes session is not a passive receiving; it's an active interpretation exercise: what is being asked for, what's the concern behind the specific note, and what response serves the script.
SCRIPT NOTES AND FEEDBACK NOTES
Project: [Script title]
Notes from: [Who + Their role]
Date received: [When]
Type: [ ] Development meeting [ ] Written notes [ ] Phone call
THE NOTES:
Issue 1: [What they raised]
My interpretation: [What I think the concern is behind the note]
My assessment: [ ] Agree [ ] Agree with concern, not their solution [ ] Disagree
Issue 2: [Continue for each note]
WHAT THEY'RE REALLY SAYING:
Underlying concern (if not explicit): [What I think is driving these notes]
What kind of rewrite they're looking for: [Light pass / structural rework / tone shift / other]
THE NOTES I'M TAKING:
Will address: [Specific changes I'll make]
Will discuss first: [Notes I want to understand better before implementing]
Will explain rather than change: [If I think something was misread]
THE NOTES I'M NOT TAKING:
Notes that conflict with the script's intentions: [What I'm not incorporating]
Why: [My reasoning]
How I'll address this with the person: [How to handle the disagreement professionally]
RELATIONSHIP NOTE:
What I learned about how this person gives notes: [Pattern observation]
What I'd do differently in the next conversation: [If applicable]
"The notes I'm not taking" is the professional judgment field that makes this template different from a simple note-transcription. Not all development notes are correct; some represent the note-giver's preferences, some reflect misreading of the script's intentions, some are genuinely helpful. The professional skill of distinguishing notes worth taking from notes to respectfully decline requires explicit assessment — and that assessment should be captured, not just felt.
Template 3: Writers' Room Notes
Writers' room notes capture the story knowledge and collaborative intelligence generated in story-breaking sessions: what was discussed, what was decided, what the logic is behind the decisions, and the professional dynamics and patterns that inform how to contribute effectively.
WRITERS' ROOM NOTES
Show: [Title]
Session: [Date + Episode or story area being broken]
Room participants: [Optional — may be sensitive; note only if useful]
STORY DECISIONS:
What was decided today: [Specific story decisions made]
The logic behind it: [Why this was the right choice]
What was rejected and why: [What didn't work + the reason]
STORY IN PROGRESS:
Current state of the episode/story: [Where we are in breaking it]
Open questions: [What still needs to be solved]
What I think about the open questions: [My thinking on the problems]
WHAT WORKED IN THE ROOM:
Story ideas that landed: [My contributions that were taken or developed]
Why I think they worked: [Pattern observation]
WHAT DIDN'T:
Ideas that didn't land: [What I pitched that wasn't taken]
Why I think they didn't: [My assessment — pitch problem? story problem? tone problem?]
SHOWRUNNER/ROOM INTELLIGENCE:
What the showrunner emphasized: [Pattern observations about their priorities]
How the room works best: [What produces productive sessions]
What to avoid: [What slows or derails the room]
The "why I think they didn't" field on pitches that didn't land is the professional development field. Understanding why a story idea didn't work in the room — was it the wrong story level? the wrong tone? did it solve a problem the room didn't have? — is the learning that improves pitch quality over time. Without this reflection, the writer who pitches ineffectively keeps pitching ineffectively.
Showrunner intelligence captured from room observations is the professional knowledge that doesn't appear in any job description: what this specific showrunner emphasizes, how this specific room generates its best work, what kinds of contributions are most valued. This is the context-specific professional intelligence that lets the writer contribute most effectively.
Template 4: Craft and Professional Development Notes
Craft and professional development notes capture the professional learning that comes from produced script analysis, industry conversations, career reflection, and observation of professional patterns.
CRAFT AND PROFESSIONAL DEVELOPMENT NOTES
Date: [Date]
Type: [ ] Script analysis [ ] Industry learning [ ] Career reflection [ ] Craft observation
IF SCRIPT ANALYSIS:
Script: [Title + Writer + Format + Year produced]
Why I analyzed this: [What drew me to study it]
CRAFT OBSERVATIONS:
What this script does particularly well: [Specific technique]
How it handles [specific craft challenge]: [The approach]
Specific scene/sequence to note: [Page numbers + what to observe]
WHAT I TAKE FROM IT:
How I'd apply this to my own work: [Specific connection]
What I want to try in the next script: [Application plan]
[ ] Craft KB updated
IF INDUSTRY LEARNING:
Context: [Where/how I learned this]
The learning: [What I now understand]
How it changes my approach: [Concrete implication]
Where this differs from conventional wisdom: [If applicable]
[ ] Professional/career KB updated
IF CRAFT OBSERVATION:
The observation: [What I noticed]
From what: [The experience that produced it]
Application: [How I'll use this]
[ ] Craft KB updated
Craft observations from produced script analysis should include specific pages. The scene on page 47 of a specific pilot that handles the world-establishment problem elegantly is a specific craft reference; "this pilot establishes the world well" is a general observation. The specific page reference is what makes the note a resource the writer can return to when facing the same craft challenge in their own work.
The KB Update Step
Every template ends with a KB update step because note-taking without KB updating is filing without indexing. The note is captured; the KB update makes it findable when needed.
For screenwriters, the KB update routes captured knowledge to the domain it belongs in: world/research KB for world and procedural intelligence; story development KB for story patterns and character observations; craft KB for craft insights from script analysis; professional/career KB for industry learning and professional dynamics observations; professional contacts KB for expert relationships and professional connections.
The routing discipline — deciding which KB domain each note belongs in — is the practice that makes the KB function as a retrieval system rather than a storage system.
Key Takeaways
-
Expert conversation notes should capture "can I quote them?" The professional ethics of expert consultation — crediting, association concerns — is best documented at the time of conversation, not reconstructed later.
-
"The notes I'm not taking" is a professional judgment field. Not all development notes are right; the assessment of which to take and which to decline respectfully is a professional skill that improves with explicit practice and capture.
-
Writers' room pitch analysis should include "why I think it didn't land." The pattern recognition that improves room contributions comes from explicit diagnosis, not from the vague sense that some ideas work and some don't.
-
Showrunner intelligence is the context-specific professional knowledge that makes room contributions effective. What this specific showrunner emphasizes, how this specific room generates its best work — this doesn't appear in any career guide.
-
Script analysis notes should include specific page references. The craft observation you can return to is the one attached to a specific scene you can re-read.
Conclusion
Four note-taking templates structure the professional knowledge contexts most important for screenwriters: story and world research notes with "can I quote them?" as the professional ethics field and "dramatic implication" as the research-to-drama conversion; script notes and feedback notes with "the notes I'm not taking" as the professional judgment field and "relationship note" as the contact intelligence capture; writers' room notes with "why I think it didn't land" as the pitch learning field and "showrunner/room intelligence" as the professional context capture; and craft and professional development notes with specific page references as the standard for craft observation usefulness. The KB update step on each template — routing captured knowledge to the appropriate domain — is what converts individual note-taking sessions into the professional knowledge infrastructure that compounds across a career.
For more on this, see AI Knowledge Management in 2025.