Story Notes
Coverage and development notes that lead to clearer next steps.
Not summaries. Not generic feedback. Story Notes identify what's working, what isn't, and what to do next — with the structural precision your team needs.
Request a PilotTraditional coverage leaves teams guessing.
Traditional Coverage
- Generic pass / consider / recommend.
- Surface-level summaries.
- Notes that describe problems without solutions.
- Weeks of turnaround.
Story Notes
- Structural analysis tied to specific pages.
- Actionable next steps for the writer.
- Compare multiple approaches side by side.
- Minutes, not weeks.
What's Included
Three tools in every set of notes.
Executive Summary
Where the story stands, at a glance.
A concise assessment of strengths, concerns, and recommended priorities. Written for decision-makers who need a clear picture before going deeper.
EXECUTIVE SUMMARY Strong protagonist setup with clear internal conflict. The B-story needs structural integration with the main arc. Act-two midpoint requires strengthening — currently functions as a plot event without connecting to the protagonist's internal need. PRIORITY: Strengthen midpoint reversal (p.32) to tie external plot turn to established internal want.
Structural Notes
Page-specific. Act by act.
Observations organized by act and sequence — what's working and what needs attention, with page references so writers know exactly where to look.
STRUCTURAL NOTES ACT ONE (pp. 1–28) ▸ Opening sequence efficiently establishes world, stakes, and character want within 12 pages — strong setup ▸ Inciting incident (p.15) lands clearly but consider raising the personal cost to the protagonist ▸ Act one break is well-positioned but the decision feels externally forced rather than character-driven ACT TWO (pp. 29–68) ▸ The midpoint reversal (p.32) doesn't connect back to the internal need established in the opening ▸ Consider merging warehouse and diner scenes (pp. 44–48) — they serve the same dramatic function
Compare View
Two drafts, side by side.
Evaluate multiple drafts or approaches simultaneously. See what changed, what improved, and what still needs work — without losing track of earlier decisions.
DRAFT 1
Midpoint: plot event only. No internal connection.
Act one break feels externally forced.
B-story unresolved at end of act two.
Warehouse + diner scenes redundant.
DRAFT 2
Midpoint now ties to internal need. Resolved.
Act one break is character-driven. Strong.
B-story unresolved at end of act two.
Scenes merged. Pacing improved.
Who It's For
Built for both sides of the table.
Development Teams
Generate notes for every submission. Compare drafts across rounds. Give writers actionable direction instead of vague feedback.
- Cover more material in less time
- Align internal notes before they go to the writer
- Track what changed between drafts
- Make packaging decisions with better information
Writers
Get structural feedback on your own work. Identify blind spots before sending to producers. Iterate with precision.
- Know what works before you send it out
- Get page-specific notes, not vague impressions
- Compare your drafts to track real progress
- Arrive at meetings with clearer answers
Your scripts and IP remain yours. We do not train on your work.
See Story Notes on your own material.
We run a limited pilot with development teams and invited writers. Tell us about your project.