Dealing with Notes: How to Take Criticism Without Crumbling
Interpreting the note behind the note. When to use feedback, when to push back, and when to let it go.
Prompt: Dark Mode Technical Sketch, script page with margin notes and a hand holding a pen, thin white lines on black, hand-drawn, no 3D --ar 16:9

The email arrives. Or the meeting ends. You have notes. Some of them are clear. Some are vague. Some feel wrong. And underneath the words, you feel something else: the sense that you've been judged and found wanting. That's the trap. Notes are not a verdict on you. They're information about the draft. Learning to take criticism without crumbling isn't about having a thick skin. It's about separating the note from the note behind the note—yours and theirs. It's about knowing when to use a note, when to push back, and when to let it go. Here's how to do that.
The Note Behind the Note
Every note has a surface meaning and often a deeper one. "The second act sags" might mean exactly that. It might also mean "I lost interest" or "I didn't understand the protagonist's goal" or "the tone shifted in a way I didn't like." Your job isn't to obey every note literally. It's to interpret. What problem is the reader actually having? Sometimes the fix they suggest isn't the right fix. Sometimes the right fix is something else that solves the same problem. So the first step when you get notes is: don't react. Don't defend. Don't agree or disagree yet. Read them. Sit with them. Ask: what would have to be true for this note to be right? What would fix the feeling they're describing? That's the note behind the note. Find it before you open the document. For more on when to stop taking notes and lock the draft, see feedback fatigue—sometimes the right move is to stop revising and move on.
Your job isn't to obey every note literally. It's to interpret.
Why It Feels Personal (And Why It Isn't)
You poured months into the script. Of course the notes feel like an attack. But the reader isn't judging your worth. They're responding to a document. They don't know how hard you worked. They don't know your intentions. They only have what's on the page. So when they say "the protagonist is passive," they're not saying "you're a bad writer." They're saying "on the page, in this draft, the protagonist didn't feel active to me." That's fixable. It might mean adding a choice, sharpening a reaction, or cutting a scene where things happen to them. It doesn't mean you're a fraud. Imposter syndrome will try to turn every note into proof that you don't belong. Don't let it. Notes are about the work. Your job is to decide what to do with them.
Relatable Scenarios
Scenario one. You get a pass from a producer. The note is "we didn't connect with the central relationship." You're crushed. You love that relationship. You think they missed something. Maybe they did. Maybe the script didn't put it on the page. The fix isn't to explain to them why they're wrong. It's to ask: what would make the relationship more legible or more compelling on the page? Sometimes that means adding a scene. Sometimes it means cutting a scene that's in the way. Sometimes it means one line that clarifies the stakes. You're not betraying your vision. You're giving the reader a way in. If you do the pass and still believe in the relationship, you've lost nothing. If you discover the note was right and the relationship was undercooked, you've made the script better.
Scenario two. You get conflicting notes. Reader A says "more backstory." Reader B says "cut the backstory." Reader C says "different genre." If you try to do all of it, you'll twist the script into a knot. The professional move is discernment. Look for patterns. What did two or three readers say in different words? Weigh notes against your intention. If your intention is clear and a note would dilute it, you're allowed to let that note go. You're not required to please everyone. You're required to make the script as good as you can while staying true to the story you want to tell. The rewriting process is where you apply that discernment—structure first, then character, then dialogue. Notes feed that. They don't replace your judgment.
Scenario three. The note is delivered badly. It's vague, harsh, or condescending. You're angry. You want to dismiss the whole thing. But the delivery and the content are separate. A note can be badly delivered and still be right. Your job is to extract the useful part. "The second act doesn't work" is not actionable. "I lost track of what the protagonist wanted" is. If the note is vague, you're allowed to ask for clarification—"Can you point to a moment where you felt that?"—or to interpret it in the way that's most useful. You don't have to accept the tone. You can still use the data.
What to Do When You Get Notes
Step 1: Don't respond immediately. Read the notes. Sit with them for at least a day. Let the emotional reaction pass. The first response is usually defensive or over-eager. Give yourself time to think.
Step 2: Write down the note behind the note. For each note, ask: what problem is the reader having? What would fix that problem? Sometimes the fix is exactly what they said. Sometimes it's something else. Write your interpretation. That becomes your to-do list, not the raw notes.
Step 3: Prioritize. Not all notes are equal. Some are structural—they affect the whole script. Some are scene-level. Some are taste. Do the structural fixes first. Then the character and scene fixes. Then decide which taste notes you agree with. You're allowed to disagree. You're not allowed to ignore every note and assume the reader was wrong. There's a middle: take what helps, leave what doesn't, and have a reason.
Step 4: Do the pass. Make the changes. Don't half-do it. If you're going to address a note, address it properly. If you're not going to address it, have a reason (and be prepared to explain it if asked). Nothing undermines trust like saying "I fixed it" when you didn't.
Step 5: Send it back or move on. If the notes were from a producer or a rep, send the revised draft when it's ready. If the notes were from a reader or a friend, you might not owe them anything—use the notes for your own rewrite. Know the relationship. Don't over-explain in the cover email. Let the draft speak.
| Note type | How to handle |
|---|---|
| Structural ("the middle sags") | Interpret: why? Fix at the story level first |
| Character ("I didn't buy the protagonist") | Clarify want, flaw, choices; add or cut beats |
| Taste ("I'd make it darker") | Consider; adopt only if it serves your vision |
| Vague ("something's off") | Ask for specifics or interpret generously |
| Wrong or hostile | Extract any useful data; discard the rest; don't engage the tone |
What Beginners Get Wrong: The Trench Warfare Section
Taking every note literally. The reader says "cut the best friend character." You cut the character. But maybe the note was really "the best friend doesn't have a function" or "the scenes with the best friend slow the pace." Maybe the fix is to give the best friend a function or to cut two of their scenes, not the whole character. Interpret. Don't obey like a robot.
Defending instead of listening. You get notes. You immediately write back explaining why the reader missed the point. That might feel good. It doesn't help. The reader's experience is the reader's experience. You can't argue them into liking the script. You can only fix what's on the page so the next reader doesn't have the same reaction. Save the defense for when someone asks "why did you do X?" Then you can explain. Until then, listen. Take notes. Then decide what to do.
Using notes as proof you're a fraud. One harsh pass and you're ready to quit. That's imposter syndrome talking. Notes are not a verdict on your talent. They're a snapshot of one reader's response to one draft. You can have a bad draft and still be a good writer. You can get a pass and still write the next script. Separate the note from the narrative about yourself.
Never pushing back. Some writers take every note and lose their voice. The script becomes a committee product. There are times when the right move is to say "I hear you, but I'm going to try it this way" or "that change would break something else I care about—here's what I did instead." You're not being difficult. You're being a collaborator. Push back with clarity and with an alternative. Not with defensiveness.
Notes are about the work. Your job is to decide what to do with them.

Prompt: Dark Mode Technical Sketch, script page with margin notes and a separate list titled "My interpretation", thin white lines on black, no 3D --ar 16:9
When the Note Is Right (And It Hurts)
Sometimes the note is right and it hurts. "Your protagonist is passive." "The central relationship isn't earned." "The theme is stated instead of shown." You know they're right. You don't want to face it. Doing the fix means admitting the draft had a real problem. That's okay. Admitting it is how you get better. The script can be fixed. You're not fixed or broken. You're learning. Kill your darlings is the same muscle: sometimes the right move is to cut what you love because the story is better without it. Notes are the same. Sometimes the right move is to change what you thought was working. It's not a defeat. It's draft two.
One External Anchor
Notes by the late director Mike Nichols (and compiled by others) and similar industry books often stress that notes are about the audience's experience, not the artist's intention—a useful frame when the note feels wrong. (<a href="https://www.wga.org/" rel="nofollow">WGA</a> resources and guild panels often discuss how writers handle notes in the room.)
[YOUTUBE VIDEO: A showrunner or producer explains how they give notes, what they're looking for, and what they wish writers would do with feedback—practical, non-theoretical.]

Prompt: Dark Mode Technical Sketch, one hand passing script pages to another hand, thin white lines on black, no 3D --ar 16:9
The Perspective
Notes are not an attack. They're data. Your job is to interpret them, find the note behind the note, and decide what to do. Take what helps. Push back when you have a reason. Let go of what doesn't serve the story. And don't let the emotional hit of criticism convince you that you're not supposed to be writing. The script can be revised. You're not on trial. Do the pass. Send it. Write the next one.
Continue reading

Feedback Fatigue: When to Stop Submitting and Start Rewriting
Analyzing coverage and knowing when a script is done. When the same note keeps appearing, when to lock the draft, and when to write the next one.
Read Article
AI-Assisted Translation: Adapting a Foreign Script for the US Market Without Losing Subtext
The French script is sixty-three pages. The dialogue is sharp. The silences say more than the words. Direct translation? Dead on arrival. How language models accelerate—but never replace—the human art of adaptation.
Read Article
Can AI Spot Pacing Issues in Your Second Act?
The second act is where scripts sag. AI can't feel boredom—but it can flag flat stretches, repetition, and rhythm. How to use it as a pattern detector, not a judge.
Read ArticleAbout the Author
The ScreenWeaver Editorial Team is composed of veteran filmmakers, screenwriters, and technologists working to bridge the gap between imagination and production.