Script Coverage Example: A Full Professional Report, Annotated
Most writers have never seen the document that decides their script’s fate. Coverage gets written about them, not for them. It lands in a development executive’s inbox, gets skimmed in ninety seconds, and the writer never learns whether the reader misunderstood the second act or simply didn’t care about the protagonist.
So here’s the whole thing. Below is a full script coverage example — every section a real report contains, written the way a working reader writes it, with annotations explaining what each part is doing and why. The script is HOMING, an original sample we use internally at First Draft Filmworks. It isn’t real, but the coverage is written exactly as it would be if it were.
Key Takeaways
- A professional coverage report has five fixed parts: title block, logline, synopsis, comments, and a grid with an overall rating.
- The comments section is what the buyer actually pays for — everything above it is retrieval, not judgment.
- Good coverage argues a position. Bad coverage summarizes and hedges.
- Length is not quality: two pages of specific reasoning beats five pages of plot recap.
What Does a Professional Script Coverage Example Actually Contain?
Five sections, in a fixed order: the title block, the logline, the synopsis, the comments, and the evaluation grid carrying the rating. That order isn’t arbitrary. It runs from cheapest to most expensive — cheapest in reader effort, most expensive in reader judgment — so an executive can bail out at any point once they’ve got what they need.
The structure has barely moved in fifty years, and that’s the point. A development executive reading forty reports a week needs to know that page one, line four is always the logline. Novelty in formatting is a tax on the reader.
Here’s a quiet irony about the grid: it sits at the bottom of most templates but gets read first. Executives scroll to the rating, then scroll back up if the rating surprises them. Write accordingly.
The Title Block: Facts Only
The title block is administrative and should be boring. It exists so the report can be filed, searched, and attributed six months from now when nobody remembers the submission.
Sample Report — Excerpt
| TITLE | HOMING |
| WRITER | A. Renwick |
| FORM | Feature screenplay |
| PAGES | 104 |
| GENRE | Contained thriller / family drama |
| DRAFT | Third, dated 12 Feb |
| SETTING | Coastal Maine, present day |
| READER | First Draft Filmworks |
| DATE | 18 Feb |
Annotation — Note the draft number and date. A reader who ignores those fields will hand back notes on problems the writer solved two drafts ago. Note also the page count sitting near the top: 104 tells an executive this is a normal-shaped feature before they’ve read a word. A 141-page contained thriller telegraphs its own problem.
The Logline: One Sentence, Fully Loaded
The logline is the first place a reader’s competence becomes visible. It has to carry protagonist, engine, opposition, and stakes in about thirty words — without adjectives doing the work that structure should be doing.
Logline
When a grounded air-traffic controller discovers her estranged brother is piloting a plane she can’t get on the radio, she has ninety minutes to talk him down before the search-and-rescue call goes out that will end his career — and expose what he’s carrying.
Annotation — Four working parts. Protagonist with a defined limitation (“grounded”). Engine (“can’t get on the radio”). Clock (“ninety minutes”). And a stake that’s both external and personal (“his career — and expose what he’s carrying”). Strip any one of those out and the sentence goes soft. Notice what isn’t here: no “gripping,” no “poignant,” no tone words. Loglines that reach for adjectives are usually compensating for a missing engine.
The Synopsis: Structure Made Visible
A synopsis is not a summary of what happens. It’s an X-ray. The job is to render the script’s architecture so an executive can see the load-bearing walls without reading 104 pages — which means compression is a judgment act, not a clerical one.
Standard length runs one to two pages for a feature, written in present tense, third person, with character names capitalized on first appearance. Subplots get a sentence each, or get cut. If a subplot can be cut from the synopsis without the spine collapsing, that’s a note worth making downstream.
Synopsis — Opening Movement
MARA VOSS, 41, works the overnight desk at a regional tower in coastal Maine, a posting that reads to everyone around her as a demotion and reads to her as penance. Six years ago she signed off on a clearance that ended badly. She has not flown since.
At 2:40 a.m. an unscheduled single-engine aircraft enters her airspace without a filed plan. Mara recognizes the tail number. It belongs to her brother DECLAN, whom she has not spoken to since their mother’s funeral.
Declan won’t respond on the assigned frequency. When Mara finds him on a discarded channel, he tells her he’s fine, he’s just flying, and asks her — reasonably, warmly — to stop calling. She checks the flight log. He’s been in the air for four hours with fuel for two.
Annotation — Look at what’s doing work in that last line. “Fuel for two” is a plot fact, but it’s placed as a button — the synopsis is honoring the script’s own reveal structure rather than front-loading information for efficiency. That’s the difference between a synopsis and a plot dump. A reader who wrote “Declan is suicidal and Mara must save him” would have flattened the script’s actual mechanism into a premise.
One more thing this excerpt does: it puts Mara’s backstory in the first paragraph, in two lines, without a flashback. If the script needs eleven pages to deliver what the synopsis delivers in two sentences, that’s an act-one pacing note writing itself.
The Comments: Where the Money Is
Everything before this section is retrieval. Anyone attentive can produce a title block and a synopsis. The comments are the analysis — the reason a company pays for coverage instead of asking an intern to skim.
Strong comments do four things: state a verdict early, argue it with page-specific evidence, distinguish what’s fixable from what’s structural, and end somewhere useful. Weak comments do the opposite — they meander through impressions, hedge every claim, and finish with “with some work, this could be strong,” which is true of literally every screenplay ever written.
Comments — Excerpt
HOMING is a genuinely well-built contained thriller whose central mechanism — two people, one radio, one clock — generates more tension than most scripts manage with an entire second unit. The writing is confident, the dialogue is lived-in, and the technical world of the tower is rendered without ever stopping to explain itself. The problem is that the script loses its nerve in the third act.
The first sixty pages are close to exceptional. Mara’s guilt is dramatized rather than stated — the moment on p. 23 where she reflexively reaches for a headset she isn’t authorized to wear tells us everything the script otherwise avoids saying aloud. Declan’s warmth is the film’s best instinct. He isn’t a man in crisis performing crisis; he’s a man being kind to his sister while doing something unforgivable, which is far more frightening.
Then p. 71 arrives, and the script introduces SUPERVISOR HALE, who spends nine pages threatening to pull Mara off the desk. This is manufactured obstruction. The clock and the fuel gauge are already sufficient antagonists; Hale exists to create conflict the premise doesn’t need, and every page he occupies is a page stolen from the only relationship that matters. The strongest version of this draft cuts him entirely and gives those nine pages back to the radio.
The ending is the harder issue. Declan lands. Mara is reinstated. A closing scene on a pier suggests reconciliation. After ninety pages of refusing easy comfort, the last eight pages deliver nothing but. The script has earned an ambiguous ending and declines to take it.
Annotation — Count the page numbers: 23, 71, “the last eight pages.” Specificity is the tell of a reader who actually read. Note also the shape — praise first, but concrete praise, then the structural objection, then the fixable one, then the one that isn’t fixable without a decision by the writer. And notice the verdict is embedded in sentence four of paragraph one: “loses its nerve in the third act.” An executive who reads only that sentence has the whole report.
The Hale note is the report’s most valuable paragraph, and it’s worth understanding why. It doesn’t say “the third act drags.” It identifies a cause (an unnecessary antagonist), explains the mechanism (the premise already supplies opposition), and proposes a specific remedy (cut him, redistribute the pages). That’s the difference between a symptom and a diagnosis.
The Grid: The Verdict in Six Rows
The grid compresses the comments into something scannable. Most templates use a three- or five-point scale across a fixed set of craft elements, plus an overall rating. It’s the last thing you write and the first thing anyone reads.
| Element | Rating |
|---|---|
| Premise | Excellent |
| Structure | Fair |
| Characterization | Excellent |
| Dialogue | Good |
| Commercial Potential | Good |
| OVERALL | CONSIDER |
Annotation — The grid must agree with the comments. Rating Structure as “Fair” while the prose calls act three a nerve failure is coherent. Rating it “Good” while writing that paragraph would tell an executive the reader is hedging — and readers who hedge get replaced. If the grid and the comments disagree, the report is worthless regardless of how well it’s written.
What Separates Good Coverage From Bad
Nearly all bad coverage fails in one of three ways, and none of them are about writing ability.
It summarizes instead of judging. Four pages of plot recap with two paragraphs of impressions at the end. The reader has proven they turned the pages and nothing else. Whoever paid for the report still doesn’t know whether to read the script.
It reviews instead of analyzing. “I didn’t connect with Mara” is a review. “Mara’s guilt is stated in dialogue on pp. 14, 31, and 58 but never dramatized after the headset moment on p. 23” is analysis. One is a taste report. The other is actionable regardless of taste.
It hedges. Every hedged sentence pushes the decision back onto the reader’s client. Coverage exists to absorb risk on someone else’s behalf. A reader who won’t commit is charging for a service they aren’t providing.
The test is simple: could someone act on this document? Not agree with it — act on it. Good coverage produces a decision. Everything else is a book report with a header.
Want coverage that reads like the example above?
ScriptCoveragePro delivers full professional reports — logline, synopsis, comments, and grid — on your script.
Frequently Asked Questions
How long should a script coverage example be?
Two to four pages for a feature. The synopsis takes one to two, the comments one to two, and the grid a few lines. Reports past five pages are almost always padding the synopsis, which nobody reads carefully. Length signals effort; specificity signals competence. Only one of those matters.
Do all studios use the same coverage template?
The sections are effectively universal — title block, logline, synopsis, comments, grid. What varies is the grid: some companies use three ratings, some five, some add categories like Setting or Production Value. If you’re writing coverage on spec, use the standard five and you’ll be legible anywhere.
Should coverage include the reader’s personal opinion?
It should include the reader’s judgment, which isn’t the same thing. “I found it slow” is opinion. “Act two runs 62 pages against a 104-page total, and pp. 71–80 introduce an antagonist the premise doesn’t need” is judgment. Judgment survives disagreement. Opinion doesn’t.
Can a script get a Consider rating with a Fair structure score?
Yes — that’s exactly what a Consider often looks like. Consider means the material has something worth pursuing and a problem worth fixing. A script with an excellent premise and a broken third act is the canonical case. Uniformly good scores across every category with a Consider overall would be the incoherent report.
Does a writer ever see the coverage written on their script?
Almost never, when it’s internal. Studio and agency coverage is written for the company, and it follows the script through the industry in ways the writer can’t see or correct. That asymmetry is the entire reason paid coverage services exist — you commission it, so you get to read it.
The Short Version
A coverage report is five sections doing one job: turning 104 pages into a decision. The title block files it. The logline tests whether the premise holds in a sentence. The synopsis exposes the architecture. The comments make the argument. The grid delivers the verdict.
If you’re writing coverage, the whole discipline reduces to this — be specific, be early with your verdict, and make sure your grid and your prose are telling the same story. If you’re the writer being covered, read the example above and ask what your script’s third paragraph would say. That’s the paragraph that decides.