How to Read Script Coverage: Understanding Your Notes

You submitted your screenplay. You got coverage back. And now you're staring at a report full of grades, comments, and a recommendation that's either going to make or break your week.

Coverage reports follow a consistent format because they're designed for internal use — not for writers. Understanding that format makes the difference between taking the right lessons from your notes and getting lost in the wrong ones.

The Anatomy of a Script Coverage Report

Most professional coverage reports contain the same core sections, in roughly the same order:

1. Title page with script details
2. Logline
3. Synopsis
4. Element grades
5. Reader comments
6. Recommendation

Each section tells you something different. Reading them in order — from bottom up, rather than top down — is the most efficient way to use your coverage.

Start With the Recommendation

Read the recommendation first, before anything else. It's the most important line in the report, and it tells you immediately where you stand.

• PASS — The script isn't ready or isn't a fit. This is the most common result. It does not mean your script is bad; it means it's not ready to move forward in this context.
• CONSIDER — Real merit, but significant issues remain. Often the most actionable result: the reader sees potential but isn't willing to fully recommend. The notes that follow a CONSIDER are usually specific and worth acting on.
• RECOMMEND — The reader believes the script is strong enough to move forward. Rare. Take the notes seriously regardless — a RECOMMEND with caveats is not the same as a clean pass.

Once you know the verdict, read the element grades. Then read the comments. This order — verdict, grades, comments — prevents you from reading the comments through a defensive lens before you know what the reader actually thought.

Understanding Element Grades

Coverage grades evaluate specific craft elements, usually on a four-point scale: Excellent / Good / Fair / Poor. Some services use numeric scores. The graded elements vary slightly by company but typically include:

• Premise / Concept — Is the central idea original and commercially viable?
• Structure — Do the acts work? Is the midpoint clear? Are act breaks proportional?
• Character — Is the protagonist compelling? Are supporting characters distinct?
• Dialogue — Does each character have a distinct voice? Is dialogue functional or theatrical?
• Pacing — Does the script move efficiently? Are there dead zones?
• Tone — Is the tone consistent with the genre and premise?

How to Interpret the Grades

Don't average the grades to get a verdict — that's not how readers think. Instead, look for patterns:

• One very low grade — If structure is "Poor" while everything else is "Good," that's your problem. Fix the structure first.
• Uniformly low grades — The script needs substantial revision across the board. Don't patch individual problems; look for the root issue.
• High grades but PASS — The reader likes the craft but not the concept, or sees a market problem. Read the comments carefully for the real objection.
• Low grade on Premise — This is the hardest to fix because it's often about the story at the most fundamental level. The comments will tell you whether the premise can be rescued or whether a more substantial rethinking is needed.

Reading the Synopsis Section

The synopsis — a 1–3 page summary of your plot — tells you how the reader understood your story. Read it carefully, because misreadings are important data.

If the reader summarized your midpoint incorrectly, or missed a major plot turn, or described a character's motivation in a way that doesn't match your intention, that's not the reader's failure. It's a signal that the script didn't communicate clearly enough. Fix the scene, not the reader's notes.

If the synopsis accurately describes your story but the reader still gave you a PASS, the problem isn't clarity — it's the story itself.

Reading the Comments Section

The comments — typically one to two pages — are where a coverage report earns its money. This is where the reader explains their grades, identifies specific pages and scenes, and sometimes offers suggestions.

What to look for in comments:

• Page-specific references — "The scene on page 54 where Sarah reveals her father's secret doesn't land because we haven't established their estrangement." This is the most useful feedback. It's specific, locatable, and actionable.
• Pattern observations — "The protagonist tends to be reactive throughout the second act" is harder to localize but points to a systemic issue worth addressing.
• Questions the reader had — If the reader notes confusion about a character's motivation or a plot logic gap, assume the audience will have the same confusion.

What to be careful about:

• Taste-based feedback — "I found the horror elements unsettling" is not the same as "the horror elements aren't working." Know the difference between a genre preference and a craft observation.
• Suggestions presented as problems — Some readers frame their own creative preferences as structural issues. "I would have liked to see X instead of Y" is a preference, not a flaw. Evaluate whether the underlying concern is valid independently of the suggestion.
• Vague generalities — "The dialogue feels a bit flat overall" without specific examples is hard to act on. Note it as a signal and compare against other readers or re-read your dialogue cold.

How to Extract Actionable Notes From Coverage

After reading the report, do this before you revise:

1. List the specific pages mentioned — Go through the comments and extract every page number cited. These are your most localized problems.
2. Separate structural notes from surface notes — Structure problems (act breaks, midpoint, protagonist passivity) need to be fixed before character or dialogue notes. Surface changes on top of a broken structure waste revision time.
3. Identify the root cause — If a reader notes three separate scenes where character motivation is unclear, the issue probably isn't those three scenes — it's how you've established the character's goal in act one.
4. Set a one-line revision goal before you open the script — "Fix the protagonist's goal in the first 15 pages" is more useful than "apply all the notes."

When Coverage Notes Conflict

If you get multiple coverage reports and they contradict each other — one reader loved the dialogue, another found it flat — look for the overlap first. If both readers flagged the pacing in act two, that's a real problem regardless of whether they agreed on anything else.

For notes that genuinely conflict, trust the one that comes with a specific page reference over the one that makes a general observation. Specificity means the reader engaged closely enough to locate the problem.

One Practical Tip: Read the Report Twice

Read coverage once immediately — then wait 24 hours and read it again. Your first read is emotional. Your second read is analytical. The notes you remember differently the second time are usually the ones worth acting on. The notes that still sting the same way are usually the ones that hit a real problem you already knew was there.

Coverage isn't a verdict on you as a writer. It's diagnostic information about one draft of one script. Use it that way, and it becomes one of the most efficient tools in your revision process.