A rejection email can tell you almost nothing about the script. You read “not for us” three times, then start wondering whether to throw out the opening, change the ending or give up on the whole thing.
Save the email before making any of those decisions. A pass is an outcome; useful feedback explains a reader’s experience. Below are six things to investigate, followed by a week-long plan for deciding what to revise. Treat them as questions, not a diagnosis of why one particular person said no.
1. The pitch didn’t make the project clear
If you sent a query and nobody requested the screenplay, you don’t yet have feedback on the screenplay. Check what the recipient actually saw: your subject line, introduction, logline and requested materials.
Can another person explain the central situation after reading the pitch? Ask them to describe it without your help. If their version sounds like a different film, work on the explanation before changing the story. Our logline guide gives you a way to connect the protagonist, goal and obstacle.
2. The opening didn’t orient the reader
Ask a fresh reader where they first became confused or stopped feeling curious. Get a page or scene, not just “the beginning was slow.” Look for an unclear relationship, an unexplained change of location, or information the scene assumes they already know.
You don’t have to begin with an explosion. A quiet exchange can create a compelling question. Revise the point of confusion, then see whether the next scene reads differently. Don’t cut a scene solely because nobody runs or shouts in it.
3. The character’s decisions weren’t convincing
A note such as “I couldn’t connect with her” can mean several things. Perhaps the reader doesn’t understand what she wants. Perhaps a major decision contradicts what the script has shown. Perhaps the behavior is clear, but the reader dislikes it.
Those require different responses. Ask what action prompted the reaction, then trace the setup for that action. A protagonist needn’t be admirable, and a character doesn’t have to grow into a better person. The reader does need enough context to follow the story you’re telling.
4. The middle repeated itself
Mark what changes in each scene of the sequence under discussion: information, leverage, a relationship, the plan. Two arguments may cover the same subject while doing different dramatic jobs. Or the second may simply repeat the first, louder.
Try one revision at a time: combine repeated information, move a revelation earlier, or give a decision a consequence. For a more detailed pass, use our story-problem checklist. Structure diagrams can help you see a pattern; they don’t decide what your particular scene is worth.
5. The dialogue made the scene harder to believe
Look for information exchanged only because the audience needs it, speakers with identical rhythms, or a conversation that keeps explaining an emotion after the action has made it clear.
Read the scene aloud with someone else. Note where they stumble, misunderstand or supply an emphasis you hadn’t intended. Direct speech can be exactly right for an admission or confrontation; the fix isn’t to make every character evasive. A focused table read gives you evidence to work with.
6. The project wasn’t a fit
Read the recipient’s stated interests and submission rules. Does the project match the format, genre and eligibility they asked for? If the reply names a particular mismatch, record it. If it doesn’t, don’t turn your guess into a fact about the market.
Changing a whole screenplay to chase a trend is a big response to a vague email. You may need a different recipient rather than a different film. Use your submission tracker and research to distinguish a clear mismatch from a useful craft note.
Turn notes into a revision you can test
In this discussion of receiving notes, John August distinguishes the problem a reader encountered from the solution they propose, and recommends paying attention when several readers report a recurring issue.
Fictional example: one reader wants you to cut a brother, another wants him to betray the lead, and a third says the reunion drags. Before doing all three, reread what the brother contributes. Perhaps the reunion repeats a conversation we’ve already seen. Test a version where he arrives with information that changes the plan, then ask a new reader what they understood.
- Monday: Separate the actual reply from your assumptions.
Keep: What was read, what was said, what remains unknown. - Tuesday: Ask a reader about one specific sequence.
Keep: Page references and their reactions. - Wednesday: Choose one underlying problem.
Keep: A short explanation of the change you want to test. - Thursday: Revise that sequence and read it in context.
Keep: An alternate version, with the original saved. - Friday: Check whether the change worked and review the next recipient’s rules.
Keep: A decision: revise further, submit where appropriate, or work on the next script.
You can spread this over longer than a week. If there were no notes, don’t invent a reason for the rejection or buy feedback in a panic. Get a useful reading, make a deliberate change if one is warranted, and keep writing. Persistence is useful; it isn’t a guarantee that this script will sell.






