How to Run a Table Read: A Simple Guide for Writing Groups

A table read is a group reading a script aloud so the writer can hear how it works. Readers speak the characters’ lines, and a narrator reads the agreed scene headings and action. The writer listens for things that are harder to notice on the page: confusing moments, repeated information, character voices, and the pace of a scene.

To run one, choose a manageable script or excerpt, assign the roles, send everyone the same version, read it aloud, and leave time for focused feedback. You can do this around a table or on a video call.

You don’t need professional actors or a full cast. A small group can cast multiple characters per reader with a little planning.

What is a table read for?

For a writing group, the main purpose is to help the writer understand the draft.

A performance asks readers to entertain an audience. An audition helps someone choose actors. A developmental table read gives the writer a chance to hear the work before revising it. Make that purpose clear so nobody feels they need to impress the room with an accent or a polished performance.

Readers should speak clearly, follow the script, and give the lines room to land. A simple reading is enough.

1. Choose the script and the question

Ask the writer what they want to learn. One or two questions give listeners something useful to notice:

• Can you tell what the main character wants?

• Where does your attention drift?

• Is the ending clear?

• Do these two characters sound different?

Agree on the pages you will read. Leave time for introductions, technical problems, and feedback. Try timing a few representative pages aloud rather than assuming every page takes the same amount of time.

For a one-hour meeting, a short script or an excerpt that takes about 25 minutes to read is a practical starting point. If the work is longer, choose a stopping point with the writer beforehand.

Also ask about sensitive material. Give readers a brief content note where appropriate and let them decline a role or participation without needing to explain why.

2. Cast the readers

List every speaking character in the selected pages. Add a narrator for scene headings and action, if needed. Then check which characters speak in each scene.

When you have fewer readers than characters, cast multiple characters per reader. When possible, avoid assigning one reader two speaking parts in the same scene. Switching between characters in a conversation can make both reading and listening harder.

Here is a simple example with four readers:

• Scene 1: Maya speaks with her brother, Ben.

• Scene 2: Maya speaks with a pharmacist, Priya.

• Scene 3: Ben speaks with a neighbor, Luis.

Reader assignments:

• Alex reads Maya.

• Jo reads Ben.

• Sam reads Priya and Luis.

• Casey reads narration and action.

Sam can cover two characters because Priya and Luis never speak in the same scene. Everyone still knows exactly which lines are theirs.

If doubling within a scene is unavoidable, flag it before you begin. Ask the reader to make a small pause when switching roles, or briefly say the character’s name if listeners need help. Elaborate voices are optional.

Give the narrator a manageable amount of text, too. A script with long action passages may make narration the biggest reading job.

3. Share the latest script and assignments

Send readers the script early enough to look over their parts. Include:

• The meeting time and location or video-call link

• The script title and version date

• The exact pages or scenes being read

• Each person’s character assignments

• The writer’s feedback questions

• Any content notes and sharing restrictions

Use one clearly named current version. If the writer makes a late change, tell everyone which version replaces the old one. At the start, check that readers have the same file.

Each reader should be able to find all their characters’ lines easily. Highlighting is especially helpful when someone covers multiple roles. Ask readers to check that every assigned character is included, and that their highlighting matches the latest version.

Rotato supports table-read casting, automated casting emails and script distribution, and automatic script highlighting for multiple characters per reader. Those tools can help you keep assignments and reading materials together as your group prepares.

4. Agree on what gets read aloud

Decide with the writer how the narrator will handle scene headings and action.

Some scripts benefit from hearing every description. Others contain lengthy visual passages that may take up much of the session. Only trim or summarize narration and action with the writer’s consent. Agree on those changes before the read, so the narrator doesn’t have to make editorial decisions while everyone waits.

Keep information listeners need to understand the scene. A silent action, a change of location, or a character entering the room may explain the next line of dialogue.

Also agree on interruptions. A useful default is to pause for a lost place or technical problem and save comments about the writing until the end.

5. Run the read

Start by checking names, roles, script versions, and pronunciation of any unfamiliar character names. Remind everyone of the planned stopping point.

Give the writer room to listen. If possible, have someone else moderate and someone else read the writer’s characters. The writer can note where the scene feels clear, where something surprises them, and where listeners seem lost.

Reading slips happen. Briefly correct a missed cue if needed, then keep going. Avoid turning each stumble into a discussion about the draft.

For an online read, check audio before starting and agree on how to signal a problem. If someone drops from the call, pause and assign a temporary reader rather than leaving everyone guessing.

A sample 60-minute table-read agenda

This schedule fits an excerpt timed to take about 25 minutes:

• 00:00–00:05: Welcome, introductions, and privacy agreement

• 00:05–00:10: Confirm roles, script version, reading approach, and writer’s questions

• 00:10–00:35: Read the selected pages aloud

• 00:35–00:40: Quiet note-taking

• 00:40–00:55: Balanced feedback from each reviewer; writer listens silently

• 00:55–01:00: After feedback: writer’s follow-up questions, thanks, and next steps

Keep an eye on the clock. If the read runs long, use the agreed stopping point and let the writer choose whether to cover the remaining pages another time.

6. Give feedback the writer can use

Return to the writer’s questions first. Balance what is working and what is not working for you as a reviewer. Give specific observations, with a scene or line reference where possible.

“I thought Ben already knew about the letter, so I was confused by his surprise in the last scene” gives the writer something concrete to examine.

Speak from your own experience: “I was confused here” is more useful than “This scene doesn’t work.”

Include specific strengths, too: “Ben’s hesitation before opening the letter made me feel his dread.” Explain what worked for you so the writer knows what may be worth preserving.

Let each reviewer finish. If several readers have the same point, acknowledge the pattern without making everyone repeat it. Agree before feedback whether the writer wants suggested rewrites or just reactions.

The writer remains silent during feedback, listening and taking notes without defending or explaining choices. Save follow-up questions until feedback has ended; revisions can wait until later.

Before, during, and after: a quick checklist

Before:

• Agree on pages, timing, and feedback questions.

• Confirm readers and assign every role.

• Check doubled roles against the scenes.

• Share the latest script and clear assignments.

• Agree on narration, privacy, and any recording.

During:

• Confirm everyone has the right version.

• Read to the agreed stopping point.

• Save writing feedback until the discussion.

• Give quieter participants space to contribute.

• Balance specific observations of what works and what doesn’t for you.

• The writer listens silently and takes notes during feedback.

After:

• Share notes only with the agreed recipients.

• Let the writer choose their revisions.

• Thank the readers and clarify any agreed next step.

Frequently asked questions

Do we need actors for a table read?

No. Willing readers who speak clearly and follow the script can help a writer hear a draft. Give them time to check their roles before starting.

Can one person read several characters?

Yes. Cast multiple characters per reader when the group is small. Check scenes carefully and avoid giving one person both sides of a conversation when possible.

Should we record the session?

Only with the writer’s permission and everyone’s consent. Agree beforehand on who can access the recording, how it will be used, and when it will be deleted. If anyone declines, use agreed written notes instead. Keep scripts and feedback within the agreed group.

What if a reader cancels?

Reassign their characters and check for new scene conflicts. Send the updated assignments and make sure affected readers can find their additional lines before restarting.

Make the next read easier to organize

A clear cast list, one script version, and a focused feedback question give your group a strong starting point. If you want help coordinating the practical details, explore Rotato at https://myrotato.com for table-read casting, script distribution, and automatic highlighting for multiple characters per reader.