The Reader’s Report

What Does Script Coverage Actually Look Like?

Before a producer reads a single page of your screenplay, someone else reads all of them and writes a short report about it. That report is script coverage. It’s a two-to-four page document that decides whether a busy executive ever opens your script at all. Yet most writers have never seen one up close. They know the words Pass, Consider, and Recommend, but not the structure that sits above them. So let’s pull one apart, section by section, and look at what a coverage report actually contains.

So what does script coverage look like?

Script coverage looks like a short, standardized report — most often two to four pages — that an executive can skim in ninety seconds. The overwhelming majority of reports follow the same skeleton, a template studios have leaned on for decades: a header with the script’s vital stats, a one-line logline, a page or two of synopsis, the comments section, a ratings grid, and a final verdict. Everything funnels toward that last part.

Think of it less as an essay and more as a triage chart. Each section does one job, and the sections stack in the same order almost everywhere you go. Here’s the whole anatomy on one page.

The header: your script’s vital stats

The header is a compact block of metadata that sits at the very top, and it takes about five seconds to read. It lists the title, the writer, the genre, the page count, and the draft date. Depending on who ordered the coverage, it may also note the form (feature, pilot, novel), the setting and time period, who submitted it, the analyst’s name, and the date it was read.

None of this is glamorous, but it does real work. A 140-page “thriller” flags a pacing problem before anyone reads a word. A period setting hints at budget. The header is the reader’s index card — the frame everything after it gets judged against.

The logline: one or two lines that sell the film

The logline is a single sentence — two at the absolute most — that captures the concept: who the story is about, what they want, and what stands in the way. It sits right under the header, and in a lot of ways it’s the most important line in the document. If a reader can’t distill your script into a clean logline, that’s already telling them something about how clear your concept is.

Here’s what one looks like in practice:

A grief-stricken deep-sea welder realizes the offshore rig she’s repairing is hiding something alive in the dark — and it’s learning to imitate her crew one by one.

Concept, protagonist, engine of conflict, all in one breath. That’s the bar. The logline is the hook an executive repeats to a colleague in the hallway, so it has to land fast.

The synopsis: the whole story, ending included

The synopsis is a plain-language retelling of the entire plot, usually one to two pages, written in third-person present tense. It’s not a teaser and it’s not spoiler-free. It walks through the setup, the turning points, the climax, and — crucially — the ending. The point is to let an executive grasp your full story arc without cracking open 110 pages of Final Draft.

It quietly does a second job too. Writing a clean synopsis forces the reader to actually understand the material before critiquing it. If the story doesn’t track on the page, the synopsis exposes the gaps — a hole no summary can paper over is a hole in your script.

The comments: where the real evaluation happens

The comments section — sometimes just called notes or analysis — is the heart of the report, usually two to three pages of the reader’s actual assessment. This is where they break down the concept, structure, characters, dialogue, pacing, tone, and commercial appeal, naming both what’s working and what isn’t. Everything else in the report is scaffolding; this is the part with a point of view.

The quality of coverage lives or dies on specificity. Weak notes say “the second act drags.” Strong notes say “the midpoint stalls on page 52 when the protagonist’s goal goes fuzzy, and momentum doesn’t recover until the raid on page 74.” One is an opinion. The other is a map you can rewrite from.

Here’s the part that trips up almost every writer: this section isn’t written to you. Internal coverage is written for the executive who has to decide whether to spend real money and time on your script, which is why the tone can feel blunt to the point of cold. It’s answering one question above all others — would my boss want to make this? — not how do we help this writer improve?

The ratings grid: your script’s report card

The ratings grid is a scorecard — a table that grades each craft element on a fixed scale, most commonly Excellent, Good, Fair, and Poor. Some companies keep it tight at five or six categories; others run seventeen or twenty-five. The marks average out toward the final verdict, so the grid isn’t decoration. Executives scan it to prioritize which scripts earn a meeting or a second read.

One detail worth knowing: many reports grade the script and the writer separately. A screenplay can earn a Pass while its author earns a Consider, because the concept isn’t right for the company but the voice on the page is clearly worth tracking. That split is how a “no” on one script can still open a door for the next one.

The verdict: Pass, Consider, or Recommend

The verdict is the single-word judgment the entire report exists to deliver, and it’s usually the first thing anyone reads — sometimes the only thing. There are three standard grades. A Pass means this reader, in this moment, didn’t think the material was ready or right. A Consider means it shows real promise and should move up the chain. A Recommend means drop everything and read this — the reader is staking their credibility on it.

So how do those three actually shake out across a stack of scripts? Not evenly. The vast majority land on Pass — think roughly nine in ten. Consider is a genuine compliment that gets your script bumped to a development team. And Recommend? A working reader might hand out three or four in an entire year. It’s reserved for scripts that are close to green-light ready.

What a coverage report is not

Coverage is not the same as script notes, and confusing the two is where a lot of frustration comes from. Coverage is a screening document — a fast, standardized read built to help an industry professional decide whether to keep going. Script notes are the opposite: longer, warmer, and written directly to the writer to guide a rewrite. They can run ten or fifteen pages of hands-on feedback.

That difference explains the tone. When your coverage feels clinical, it isn’t being cruel — it just wasn’t built to hold your hand. It was built to sort a pile. Knowing which document you’re actually holding changes how you should read it.

How should you read your own coverage?

Start with the verdict, then almost immediately look past it. The grade exists for whoever ordered the report — the producer or exec — not for you. What’s useful to you lives in the comments, so that’s where your attention belongs. Don’t react to a Pass emotionally; treat it as one data point, not a life sentence.

Then hunt for patterns. If you get coverage from two or three sources and the same issue keeps surfacing, it’s real and it’s structural. One reader flags a slow second act? Maybe. Three readers flag it? Fix it. Use the specific, page-referenced notes to steer your rewrite — and let the grade fade into the background where it belongs.

Frequently Asked Questions

Coverage isn’t a mystery once you’ve seen its skeleton. Six parts, one order, one verdict at the end. Read it as the operational document it is — study the comments, ignore the sting of the grade, and let the specifics drive your next draft. The report that screened you out today is the same report that maps your way in.