Getting & Reading Feedback
Other people can see what you can't. But notes are dangerous too — follow the wrong ones and you'll rewrite a good script into a worse one. Here's how to get useful feedback and read it wisely.
No matter how well you learn to read your own work, you will always have blind spots — the whole point of distance is that you can never fully get outside your own head. That's why feedback is essential: a fresh reader experiences your script the way an audience will, and can feel problems you've gone numb to. But feedback is a double-edged tool. Good notes, well interpreted, can transform a script. Bad notes, blindly followed, can wreck one. Learning how to get feedback on a screenplay — and, just as importantly, how to read that feedback — is a skill in itself.
Who to ask (and who not to)
Not all readers are equal. The best feedback comes from people who can be honest and have some sense of story.
- Trusted, honest readers. You need people who'll tell you the truth, not just praise you. A friend who loves everything you write is worthless as a note-giver.
- A few readers, not a mob. Three or four thoughtful readers beat twenty. Too many voices create noise and contradiction.
- Some who know story, some who don't. Writers and filmmakers catch craft issues; "civilian" readers tell you honestly where they got bored or confused — which is gold.
- Not your mom. Unless your mom is brutally honest, love makes a bad critic. Choose readers who can separate you from the work.
Ask the right questions
Vague requests get vague notes. "What did you think?" invites "It was good!" Instead, direct your readers toward useful, specific reactions:
- Where did you get bored or check out? The single most valuable question you can ask.
- Where were you confused? Confusion is a clear, fixable signal.
- Who did you care about — and when did you start? Tells you if your hero is landing.
- What did you think it was about? Reveals whether your theme is coming through.
- What do you remember a day later? What sticks is what's working; what evaporates may not be earning its place.
The golden rule of notes
That pullquote — a famous piece of Hollywood wisdom, often attributed to Neil Gaiman — is the single most important thing to understand about feedback. Readers are excellent at telling you where something isn't working (the symptom) and terrible at telling you how to fix it (the cure). So separate the two. When a note says "I think you should give the villain a dog to make him likable," don't argue about the dog — ask what problem the dog is trying to solve. Usually the reader felt the villain was flat or one-note. That's the real note. The dog is just their guess at a fix, and your fix will probably be better. Trust the diagnosis, distrust the prescription.
Look for patterns, then decide
You are still the author. Feedback informs your rewrite; it doesn't dictate it. The way to use notes wisely:
- Hunt for consensus. If one person trips on something, maybe it's them. If three people trip on the same spot, it's the script. Patterns are truth.
- Translate every note into a problem. Ignore the suggested fixes; write down the underlying issues each note points to.
- Weigh it against your vision. A note that would make the script "better" but not your film can be respectfully set aside. Serve the story you're trying to tell.
- Sit with the sting. The notes that make you defensive are often the true ones. Feel the flinch, then get curious about why.
My process for reading notes: I read them all, feel insulted for about a day, then read them again once my ego has calmed down. The second read is the useful one. I ignore every proposed solution and just collect the problems — the where and the what. Then I look for anything two or more readers hit independently; that's my rewrite list. The suggestions I almost never take, because I know my story better than they do. But the problems? The problems are a gift, and the sharper they sting, the more likely they're real.
That completes your foundation: you can gain distance, diagnose problems, and gather outside eyes. Now you have a clear, prioritized list of what's broken. It's time to actually fix it — starting with the biggest, most important pass of all: the structural rewrite. That's Module 2.
Hear your script out loud without gathering a cast. The Table Read tool gives your pages voices so you can catch clunky dialogue, dead scenes, and pacing problems the eye skips right over — the fastest way to find what a rewrite needs to fix.