Feedback
4 min read
Helpful feedback identifies the experience of reading a script before it tries to prescribe a fix.
Most notes fail for the same reason: they jump straight to solutions. The reader rewrites a scene in their own voice, suggests a different plot turn, or tells the writer what the character “should” do. The result is rarely useful. The writer is left with someone else’s instincts instead of clear evidence about how their own story is landing.
Useful feedback works the opposite way. It describes what happened for the reader, points to specific moments, and leaves room for the writer to find the solution that fits their story.
Start with the Reader’s Experience
Before offering any suggestion, describe what the script did to you as a reader.
Useful observations sound like this:
“I leaned in here because I suddenly understood what was at stake.”
“I got confused on page 42 — I wasn’t sure why the character made that choice.”
“I expected the confrontation to happen sooner, so the middle felt like it was delaying.”
“My attention drifted in this sequence; the same beat seemed to repeat without raising the cost.”
These statements give the writer concrete evidence. They can see where curiosity, confusion, tension, or loss of momentum actually occurred. That evidence is more valuable than any generic note about “pacing” or “character development.”
Avoid Rewriting the Script in Your Own Voice
One of the most common feedback mistakes is replacing the writer’s choices with your own.
When you rewrite a scene, suggest a different ending, or invent a new plot device, you are no longer diagnosing the script. You are proposing a different story. The writer then has to decide whether to imitate your instincts or defend their own.
Good feedback stays on the diagnostic side of the line. It points to the problem and explains why it created a particular experience. It does not supply the new dialogue, the new scene, or the new structure. See our article: "How to Rewrite a Screenplay Without Losing Its Voice."
A Practical Framework for Screenplay Notes
Use this simple sequence when giving notes:
Describe the experience
Where did you lean in? Where did you feel confused, bored, or surprised? What did you expect to happen next?Point to the specific moment
Name the page, scene, or beat. Vague comments (“the second act is slow”) are harder to act on than precise ones (“pages 48–55 feel like the same obstacle repeating”). See our article: "A Simple Way to Diagnose a Slow Second Act."Explain the effect
Connect the moment to the experience: “Because the character’s goal is unclear here, I stopped caring whether they succeeded.”Stop before the solution
Leave the “how to fix it” to the writer. Your job is to supply clear evidence, not to redesign the script.
This framework keeps the notes useful and respectful of the writer’s ownership of the story.
How This Connects to Revision
Writers who receive experience-based notes can sort them the same way they sort their own observations after a cold read (see What to Do After You Finish a Screenplay Draft). Notes about confusion or loss of momentum often point to problems with premise clarity, second-act pursuit, or escalation (see Notes on Premise and Diagnosing a Slow Second Act).
When feedback stays diagnostic, it becomes part of a productive revision process instead of a list of conflicting opinions.
External Resources
John August on giving and receiving notes — practical guidance from a working screenwriter.
Script Notes episodes on feedback — recurring discussions of useful vs. unhelpful notes.
The Black List reader guidelines — industry context on how professional coverage is structured (scores + written evaluation).
Ready to See How Your Draft Is Doing?
Upload your screenplay for free on Loglisted. The analysis provides observation-style notes on structure, pursuit, and attention so you can practice the same diagnostic approach on your own work.
Made by a writer. For writers.