The Notes You Should Keep During a Table Read

During a read, the temptation is to write everything down or nothing at all. Both are mistakes. The notes worth keeping are short, specific, and tied to a moment you can point to on the page.

A good note tells you what to do next. A bad note just records that you felt something, without telling you where or why. Train yourself to write the first kind and let the second slip by.

I write notes in the margin, not in a separate document. Margin notes stay attached to the line that caused them, and that attachment is half their value.

A note that cannot tell you which line to change is not a note. It is a mood.

The four notes worth writing

First, stumbles: the words that tripped you as you spoke. Second, drags: the places where you wanted to skip ahead. Third, breaths: the spots where you ran out of air mid sentence. Fourth, questions: the moments where you lost track of what the script was saying.

Each of these points at a specific location and suggests a specific action. A stumble wants a rewrite, a drag wants a cut, a breath wants a pause or a shorter clause, and a question wants clarity.

You will not need all four every time. Some scripts only stumble, some only drag. Notice which category dominates your notes and it will point straight at the weakness in your draft.

Notes that waste your time

Vague notes like this part feels off give you nothing to act on. So do notes about your own nerves, which are real but not useful to the script. And notes that rewrite the line on the spot, before you have even finished reading it, tend to solve the wrong problem.

Try not to editorialize. You are collecting symptoms during the read, and the diagnosis comes later, once you can see all the notes together and find the pattern.

If you must write a feeling, force yourself to add the line number next to it. Half the time you will realize you cannot, which means the note was never about the script at all.

Key takeaways

• Write short, specific notes tied to a line on the page.
• Track stumbles, drags, breaths, and questions.
• Each note type points to a clear fix.
• Skip vague notes that only record a feeling.
• Diagnose patterns after the read, not during it.

A note system you can run in one pass

Pick two or three symbols and use them consistently. A circle for a stumble, a squiggle for a drag, an underline for a question. Symbols let you mark without breaking your reading pace, and they are faster to scan later than full sentences.

After the read, transfer the marks into a short list. Group them by type so the fixes cluster naturally. When you can see that six drags all sit in the same section, you have found a structural problem hiding inside six small notes.

Keep the notes even after you make the fixes. The next read will produce a new set, and comparing the two shows you whether the script is actually getting tighter or just changing shape. The comparison between two sets of notes is the clearest evidence you have about whether the revision helped. Look for the categories that shrank and the ones that grew, because a new batch of the same drags means your fix missed the real problem. Notes are a record, and records let you see the trend.