What does a script coverage report actually include?
If you've never seen a coverage report before, or you've seen one and it didn't make sense, here's what's actually in them and why each part matters.
You hear “script coverage” thrown around a lot. Agents mention it. Competitions offer it. Services charge $200+ for it. But if you've never actually seen a coverage report, the whole thing can feel like a black box. It's not. Coverage is just a structured set of notes from someone who read your screenplay carefully. Here's what's inside, piece by piece.
What script coverage actually is
Script coverage is the document a reader writes after reading your screenplay. That's it. The script coverage definition is straightforward: it's a structured evaluation that breaks down the strengths and weaknesses of your script. Whether you hear it called screenplay coverage or script reader coverage, it's the same thing.
Studios use coverage to decide whether a script is worth passing up the chain. A development assistant reads 5-10 scripts a week and writes coverage on each one. The producer or exec reads the coverage, not the script, and decides whether to keep going.
For independent writers, coverage serves a different purpose. You're not trying to get past a gatekeeper. You're trying to figure out what's working and what isn't. Good coverage gives you that signal. It tells you where readers get confused, where the pacing drags, where the characters fall flat. It's a diagnostic tool.
Don't overthink it. Coverage is just structured feedback. The structure is what makes it useful.
The parts of a standard coverage report
So what does a script coverage report include? The script coverage format has been mostly the same since studios started using it decades ago. Here's what you'll find in a standard report:
Logline
One sentence that captures the concept of your script. Protagonist, goal, conflict, stakes. This is what someone reads to decide if the premise is worth their time. If the reader can't write a clear logline from your script, that tells you something about your concept clarity.
Synopsis
A full plot summary, usually 1-2 pages. This covers everything: setup, turning points, climax, resolution. It's not a teaser. The synopsis includes the ending. The point is to show the exec the full story arc without them having to read 110 pages. For you as the writer, it's useful because it exposes structural holes you might not see when you're deep in the pages.
Comments and Analysis
This is the meat of the coverage report. The reader breaks down story, character, dialogue, structure, and pacing. Good coverage notes are specific. They reference actual scenes and moments in your script. They tell you what's not working and, more importantly, why. This section is where you'll find the notes that actually help you rewrite. If you're learning how to write coverage on a script yourself, this is the section that separates useful analysis from filler.
Recommendation
Pass, Consider, or Recommend. That's the standard scale. In studio coverage, this is the single most important line because it determines whether anyone else reads your script. For independent writers, the recommendation matters less than the reasoning behind it. A “Consider” with great notes is more useful than a “Recommend” with no explanation.
Scores and Ratings
Some coverage services grade individual elements: premise, character, dialogue, structure, originality. These scores give you a quick snapshot of where the script is strong and where it's weak. Not every service includes them, but when they're there, they're useful for tracking progress across drafts.
What good coverage looks like vs. bad coverage
Not all coverage is created equal. The script coverage meaning changes depending on who wrote it and how much effort they put in. Here's how to tell the difference.
Good coverage is specific. It references actual scenes in your script. It says “the confrontation in act two between Sarah and Mark lacks stakes because we don't know what Sarah stands to lose.” It points at the problem and explains why it's a problem. It gives you something to work with.
Bad coverage is vague. It says “the pacing feels off in the second act” and leaves it there. No specifics, no scenes referenced, no explanation of why. This kind of feedback could apply to literally any script. You get this from overworked readers cranking through a stack, or from cheap services that don't spend real time with your material.
Good coverage also balances the negative with the positive. It tells you what's working, not just what's broken. If your dialogue is sharp but your structure needs help, a good reader says both. That way you know what to protect in the rewrite, not just what to fix.
When you're evaluating a coverage service, ask for a sample. If the sample reads like it could be about any screenplay, keep looking.
Try OnDesk
See what a real coverage report looks like on your script
3 full reports free, no credit card. After the report, use the chat to pressure test ideas, generate pitches, or dig into specific scenes with something that's actually read your whole script.
Your script is never stored and never used to train AI models. It's your work, it stays yours.
How script coverage format varies by source
The script coverage format isn't universal. It changes depending on where the coverage comes from. Here's a quick breakdown:
Studio coverage
The most standardized format. Logline, synopsis, comments, recommendation. Studios have been using roughly the same template for decades. The reader is usually a development assistant or a freelance reader on the studio's list. You don't get this unless someone submits your script to a studio.
Competition coverage
Festivals and screenplay competitions give you scores and a paragraph or two. Sometimes helpful, sometimes not. You don't usually get a full synopsis or detailed analysis. It's more of a scorecard than a development tool.
Paid coverage services
Quality varies wildly. Some services employ experienced readers who write thoughtful, detailed coverage notes. Others hire anyone willing to read for cheap and crank through scripts fast. Prices range from $50 for a basic evaluation to $300+ for detailed notes with a follow-up call.
AI coverage tools
Tools like OnDesk give you the full studio-format report in minutes. Logline, synopsis, character breakdowns, structural analysis, development notes, and a recommendation. The advantage is speed and consistency. You get the same thorough format every time, and you can run coverage on every draft without waiting weeks or spending hundreds of dollars.
What to do with your coverage once you have it
You got your coverage report. Now what? First, don't react emotionally to a Pass. A Pass doesn't mean your script is bad. It means this reader, in this moment, didn't think it was ready. That's information, not a verdict.
Look for patterns across multiple reads. If you get coverage from two or three sources and they all flag the same issue, it's real. One reader says the second act drags? Maybe. Three readers say it? Fix it.
Use the specific notes to guide your rewrite, not the recommendation grade. The grade exists for the person who asked for the coverage (the producer, the exec). The notes exist for you (the writer). A “Consider with reservations” that gives you five specific things to fix is worth more than a “Recommend” with no details.
This is where tools like OnDesk become especially useful. Because you can run coverage on every draft, you can track whether the problems readers flagged are actually getting resolved. You're not guessing. You're measuring.
And remember: knowing how to write script coverage, or at least understanding what goes into it, makes you a better reader of your own work. Once you know what readers are looking for, you start catching those problems yourself.