How the Layered Read works
A note like “this scene drags” tells you something’s wrong, not what to change. The Layered Read looks for possible causes, with twelve axes in three groups, in every scene, sequence and act. Five minutes, shown on Green Book.
The idea
A note like “this scene drags” tells you something is wrong, not what to change. Dragging is a symptom. It can come from nothing pushing the scene, from a scene that’s longer than what happens in it, or from several other things, and each one needs a different rewrite.
The familiar coverage categories (premise, structure, character, dialogue, pacing) are symptoms too. The Layered Read uses twelve axes instead: twelve questions, each scored separately and each looking for a possible cause, in three groups (Design, Execution and Involvement). It reads every scene, every sequence, every act and the whole script with them.
You don’t need to learn the terms below to use it. The app explains each one where it appears. This page is here if you want the whole picture.
Every level
The same twelve axes read a scene, a sequence, an act and the whole script. Each level is read on its own, not averaged from the level below, so a sequence can work even when every scene in it needs attention, and the other way round.
That tells you where a problem lives. If the scenes are weak but the sequence holds, the fix is in the scenes. If every scene holds but the act doesn’t, the problem is at the act level, not in the scenes.
Video transcript
Click a time to jump the video there.
Where coverage comes from
Script coverage started in studio story departments. A reader summed up the script and graded it, so an executive could decide quickly: pass, consider, or recommend. It still looks the same today. Premise. Structure. Character. Dialogue. Pacing. It’s a good system for deciding whether to buy a script. But you’re not buying it. You wrote it. Along with the grades, you might get notes like this one.
A note is a symptom
That tells you something’s wrong. But not what to change. Dragging is a symptom. Maybe nothing is pushing the scene. Maybe it’s longer than what happens in it. Each needs a different rewrite. Guess wrong, and you cut the one thing that was working.
The hard question
It’s not just that note. Every grade on the report works the same way. “Fair” on Character or Pacing tells you how it read, not why. Could you grade the cause instead of the symptom? It’s a hard problem. One symptom can have many causes, and from the outside they look alike. AI has started solving open problems in math. We gave it one from screenwriting. ChatGPT worked out a new theory. Claude and Gemini tried to break it. Then we tested it on real screenplays, and rebuilt it, again and again. What came out of it: twelve axes, twelve questions, each scored separately, in three groups. They read every scene, every sequence, every act, and the whole script. We’ll start with the groups.
Three groups
A scene is planned, built, and experienced. Design is the blueprint: what the scene is built to do. Execution is the build: how it’s put on the page. Involvement is the experience: what it’s like to watch.
Polishing won’t fix the blueprint
A note like “this scene drags” could belong to any of them. And polishing the lines won’t fix a problem in the blueprint. Two characters who agree on everything can’t have a real fight, however good the lines are. Change the blueprint, and the same lines play differently.
Twelve axes
Our Pressure axis would catch that: nothing in the scene pushes back. And it’s one of five axes a dragging scene can point to. Is something actually pushing the scene? Does it go deeper, or repeat itself? Is something different by the end? Is every moment needed? Does it surprise you, in a way that’s earned? Seven more axes ask other questions about each group.
Every level
Now the levels, using a film you may know: Green Book. The same axes work on every scene, every sequence, every act, and the whole script. And each level is read on its own. It isn’t an average. In Dive Bar Rescue, all four scenes score lower than the sequence they make up. Each one needs work on its own. Together, they work. So the fix is in the scenes, not in the shape of the sequence.
Triage
Here’s Green Book in the Layered Read. You see the whole script, colour-coded. The default is Triage: what each part needs. Green means keep. Gold, polish. Orange, rework. Red, two or more groups are broken. The colour comes from the three groups. All three solid is green. One broken turns it orange. The whole script comes back green. Act 1 is the only act that doesn’t, so that’s one place to look first. You can also colour it by one group, or by a single axis.
Directions to try, and a conversation
Open any scene, sequence, act, or the whole script, and you see what’s behind its colour. Let’s open scene 8: the hot dog bet. Weak spots come with directions to try, each with what it gains, and what it costs. None of them is the answer. They’re places to start. And you can talk any of it through. Ask questions, push back, try another angle. Every part of the script has its own conversation.
You don’t need to learn the terms
That’s a lot of new words. You don’t need to learn them. You don’t write in these terms, and you shouldn’t have to. The app walks you through each one, right when you need it. And after a while, you may catch yourself thinking “the pressure isn’t there yet” while you write. Coverage was built to decide whether to buy a script. ScriptReader is built to help you rewrite one.