If you've spent any time around screenwriters, you've heard the phrase "getting coverage." It's one of those industry terms that everyone nods at and almost nobody explains. Here's the full picture: what script coverage actually is, how the pass/consider/recommend system works, what's inside the report, and — most importantly — how to use it without letting it wreck your confidence.
Where coverage comes from
Coverage was invented as a triage system. A studio development executive might get dozens of scripts a week and can't read them all. So readers — usually junior staffers, interns, or freelance analysts — read each script and distill it into a 3–5 page report. The executive reads the coverage, not the script, and only requests the full screenplay when the coverage says it's worth their time.
That filtering function is why the verdict matters so much inside the industry — and why writers obsess over it. A "recommend" from a respected reader can get a script pulled from the pile. A "pass" means it quietly dies there.
Pass / Consider / Recommend, honestly explained
The three-tier system is simple, but the reality has nuance:
- Pass. The reader doesn't think this script should move forward. This is the overwhelming majority of coverage — something like 90%+ of scripts get a pass. A pass doesn't mean your script is garbage; it means this reader, on this day, didn't think it was worth the company's time and money. Most working writers have a drawer full of passes.
- Consider. The reader sees something worth a second look — maybe the writing is strong but the concept needs work, or vice versa. "Consider" means "don't throw this away yet." For a new writer, a consider with specific, actionable notes is genuinely useful.
- Recommend. Rare. The reader thinks the company should pursue this script — buy it, option it, meet the writer. Recommends are the ones that get circulated. If you're buying coverage as a writer, a recommend is nice validation, but it's the comments that you're actually paying for.
One uncomfortable truth: coverage is subjective. The same script can get a pass from one reader and a consider from another. Readers have tastes, bad days, and genre biases. That's why professionals never treat a single coverage report as gospel — they look for patterns across multiple reads.
What's actually inside a coverage report
A standard coverage report has four parts:
- The logline. One or two sentences capturing the story. Reading someone else's logline of your script is brutally illuminating — if their version doesn't match the movie in your head, your script isn't communicating what you think it is.
- The synopsis. A 1–2 page beat-by-beat summary of the plot, including the ending. This is where structural problems become visible: if the synopsis reads as a list of things happening rather than a story with momentum, the structure needs work.
- The comments. The heart of it — usually 1–3 pages on premise, structure, character, dialogue, pacing, and commercial viability. Good comments are specific: "the midpoint reversal on page 55 doesn't reframe the stakes" beats "the second act drags" every time.
- The grid. Many reports include a ratings grid — premise, structure, character, dialogue, pacing — scored as excellent/good/fair/poor. Take the grid as a rough heat map, not a report card.
Who writes coverage (and why it varies so much)
Studio coverage is written by whoever's cheapest: interns, assistants, freelance readers paid per script. Quality varies wildly. Some readers are aspiring writers with sharp story instincts; others are checking boxes.
Independent coverage services — the kind writers buy — range from junior-reader mills to working professionals. The difference matters enormously: a reader who's never sold anything can still spot a sagging second act, but a working writer sees why it sags and what the fix costs you structurally. When you're shopping for coverage, ask who actually reads the script. If the answer is vague, that's your answer.
Coverage vs. notes vs. consulting: what's the difference
These get used interchangeably, but they're different products:
- Coverage is an industry-style report: logline, synopsis, comments, verdict. It's evaluative — it tells you how the script plays to the system.
- Notes (or a notes call) are developmental: a conversation about what's not working and how to fix it. Less formal, more collaborative.
- Consulting is the ongoing version: a professional who reads your drafts, talks through rewrites, and tracks the script across multiple passes.
Most writers need coverage first (diagnosis) and notes or consulting after (treatment). Paying for a consulting relationship before you know what's wrong is like hiring a personal trainer before getting a checkup.
For a full breakdown of what each tier costs, see how much script coverage costs.
How writers should actually use coverage
Here's the workflow that works:
- Get coverage when the script is finished, not while you're drafting. Coverage evaluates a draft; it can't evaluate your intentions. If you know the third act is broken, fix it first — don't pay someone to tell you.
- Get at least two reads. One reader's opinion is an anecdote; two or three overlapping notes are data. If every reader trips on the same scene, that's your rewrite target.
- Read the comments before the verdict. The verdict is one person's taste. The comments contain the actual information. Plenty of produced films got passes from someone.
- Separate craft notes from taste notes. "Your protagonist has no discernible goal until page 40" is craft — fix it. "I don't like comedies" is taste — ignore it.
- Wait 48 hours before reacting. Coverage stings, especially the first time. The notes that make you angry on day one are often the ones you're grateful for on day three.
- Rewrite, then decide if you need another round. Coverage is a tool for revision, not a permission slip. The goal was never a "recommend" — it was a better script.
When coverage is a waste of money
Honesty matters here: coverage isn't always the right buy. Skip it when the script is a first draft (you already know what's wrong), when you're too raw to hear criticism without quitting (protect the writing impulse first), or when you're buying it hoping for validation rather than information. Coverage can't tell you you're a good writer. It can only tell you how this draft reads.
There's a longer version of this decision — when coverage is worth it and when it isn't — if you're on the fence.
The bottom line
Script coverage is the industry's filtering system and the writer's diagnostic tool. The pass/consider/recommend verdict gets all the attention, but the real value is in the comments: a stranger's honest account of what your script actually communicates. Used right — multiple reads, patterns over verdicts, craft over taste — it's the cheapest education in screenwriting there is.