# Script coverage

## Draft identity
- Title:
- Writer:
- Format: feature / pilot / short / other
- Genre:
- Page count:
- Draft date / version:
- Reader:
- Date read:
- Purpose: submission / development / internal evaluation / education

## Logline
One or two sentences describing the protagonist, goal, pressure, and central conflict.

## Synopsis
Summarize the story that is actually on the page. Separate summary from evaluation so a later reader can tell what happened before reading what you thought about it.

## Evaluation
Use only dimensions that serve the decision this coverage supports.

| Dimension | Rating / note | Evidence from the draft | Why it matters |
|---|---|---|---|
| Premise / concept | | | |
| Character | | | |
| Structure | | | |
| Scene construction | | | |
| Dialogue / voice | | | |
| Pace / clarity | | | |
| Tone / execution | | | |

## Strengths
### 1. [Specific strength]
- Evidence:
- Effect on the read:
- What should be protected in a rewrite:

## Risks / weaknesses
### 1. [Specific issue]
- Evidence:
- Reader consequence:
- Likely underlying diagnosis:
- A question for the writer, not a prescribed line edit:

## Highest-leverage note
If only one issue changed in the next draft, which one would improve the greatest number of downstream scenes or decisions?

## Verdict
Define the decision language before using it.

- **Recommend:**
- **Consider:**
- **Pass:**
- **Other / not applicable:**

**Verdict for this draft:**

## Next action
- Who needs this coverage?
- What decision should happen next?
- What evidence would change the verdict?

## Reader calibration note
A score is not self-explanatory. If several readers use this form, compare the evidence and reasoning behind their ratings, not only the averages.