A table read is a session where people sit around a table and read your script aloud, in character, start to finish, without stopping. It exists because a script is a set of instructions for a performance, and you cannot evaluate a performance by looking at the instructions.
There are two different events sharing the name. The writer's read is a private diagnostic, organized by the writer, often long before anything is financed. The production table read happens once a film is cast, usually in the first week of pre-production, with the actual cast, the director, and heads of department in the room. Same format, very different purpose.
Why it works
Silent reading is forgiving in ways that are actively harmful. Your eye skips the line that does not scan, fills in the pause you intended, and hears every character in your own head, with your own rhythm, meaning what you meant.
Out loud, none of that survives. The line that does not scan makes an actor stumble. The joke that only worked typographically dies in a silence you can hear. The two characters who sound identical become obvious the moment two different people say their words. And the scene you thought was tense turns out to be four minutes of people agreeing with each other.
Nothing in your script is real until someone who does not love it has said it out loud.
Running a writer's read
Who to invite. Actors, if you can get them, and you probably can. Actors read scripts for free far more often than writers expect, because it is enjoyable, it is short, and it is a way to meet people who make films. Local theatre is a better source than film for this: stage actors are practiced at cold reading and will give you a usable performance from a first look.
If you cannot get actors, get anyone. A bad read still exposes structural problems. It just will not tell you much about performance.
Cast it loosely but not carelessly. You do not need a match for the eventual role. You do need distinct voices for characters who share scenes, and you do need to avoid one person reading two characters who talk to each other, which is confusing and unfair to them.
Use a narrator. One person reads the sluglines and the action lines. This job matters more than people think, so give it to someone who reads well and brief them: read the action, do not perform it, and keep moving. A narrator who editorializes ruins the timing.
Instruct the narrator to read sluglines briskly. "INT. KITCHEN, NIGHT" and straight on.
Send pages in advance if you can, at least to the leads. A day is enough. Cold reads are perfectly usable but you will be listening past the stumbles.
Do not stop. This is the rule that gets broken and it is the one that matters most. No corrections, no explanations, no "sorry, that should be sarcastic". You are measuring whether the script communicates without you in the room, and the moment you intervene you have destroyed the measurement. Write your note down and keep going.
Time it. Start a stopwatch and note the time at each act break or every twenty pages. This gives you a real running time, which as covered in the page count post is often quite different from what your page count implied.
Record it. Audio is enough. You will not catch everything live, because you will be busy being mortified. The recording is where the real notes come from, two days later, when you can listen to it as a listener.
Not "is it good". You will not be able to tell, and asking yourself will only make the afternoon painful. Listen for four specific things: where people shift in their seats, where a laugh you expected did not come, where a laugh you did not expect did, and where you personally lost interest in your own script. That last one is the most reliable signal in the room and writers routinely ignore it. If you drifted during your own table read, page 62 has a problem.
The notes session afterward
Break for ten minutes first. Everyone needs it and so do you.
Then, if you want feedback, run it deliberately rather than opening the floor.
Ask specific questions. "What did you think?" produces politeness and structural noise. Better questions:
- Whose story is this?
- What does she want?
- Where did you get confused about what was happening?
- Was there anywhere you stopped caring?
- Which character would you want to see more of?
The confusion question is the most valuable and the least ego-threatening for everyone involved.
Ask actors what their character wanted. If their answer does not match your intent, the script has not conveyed it. This is a fact about the script, not a criticism of the actor.
Do not defend anything. Not one line. The instinct is overwhelming and it is fatal, because the moment you explain, the room learns that notes will be argued with and stops giving them. Write everything down, thank people, decide later. Half the notes will be wrong. Which half is not knowable in the room.
Note where people agreed. One person disliking something is data. Five people describing the same problem in different words is a fact.
The production table read
A different animal, and worth knowing about before you are in one.
It happens after casting, in pre-production, and typically includes the cast, the director, the producers, the writer, and heads of department. Sometimes financiers and the broadcaster.
Its purposes are practical and partly social:
- Everyone hears the same film for the first time. Costume, production design and camera have all been reading the script alone with their own version in their heads. This is where those versions converge.
- The cast meet each other. For an ensemble, this matters enormously and is half the reason for the ritual.
- Final rewrites get identified. After this read there are usually a few days of adjustment before pages lock. If dialogue is going to change, this is the last comfortable moment.
- The running time gets measured with the actual cast, which is a real production data point.
It is also, quietly, a performance for the people paying. Nobody says this out loud.
For the writer, the same rule applies with even more force: do not defend, do not explain, take notes.
If you cannot gather people
Remote reads work. Video calls have latency problems that hurt fast overlapping dialogue, but for most scripts it is entirely usable, and it removes every scheduling excuse.
The worst option, which is still much better than nothing, is reading it aloud yourself, all parts, recording it, and listening back a week later. You will catch the unspeakable lines and the dead stretches. You will not catch the characters who sound the same, because they will all sound like you.
Next
The script has been heard and it is about to change. Next: how those changes are tracked once a script is locked, and why production paper comes in colors.
Get new posts by email
New posts and free templates by email. Unsubscribe in one click.