Compare two lists line by line for a script review

During a script review, two lists can look almost identical while one has a missing cue, a changed character name, or entries in a different order. Reading them side by side makes small differences easy to miss, especially when the list is long.

Use the Text Compare tool to check the versions line by line. A careful setup helps you spot meaningful script changes without mistaking harmless formatting edits for content changes.

Compare the script lists line by line

1. Open Text Compare and keep the two script versions available in separate documents or windows.
2. Copy the earlier list into one side of the comparison and the revised list into the other. Keep the original order and line breaks in both versions.
3. Review the differences from the top. Check each highlighted addition, removal, or changed line against the script, not just against the neighboring text.
4. Look closely at character names, scene or cue numbers, entrances, exits, props, and any repeated lines. These can be easy to overlook when the wording around them is unchanged.
5. Confirm each meaningful difference in the full script, then record the decision in your review notes. Do not replace either source version until the changes have been approved.

If the tool shows a lot of differences at once, check whether the lists use the same line breaks, numbering, and blank-line pattern. A small layout change can shift many lines and make a simple review harder to read.

What the differences mean

A line appears only in the revised list

This may be a new cue, a new character, or an added instruction. Check whether the line appears in the current script and whether it belongs at that point in the sequence. Also check whether it was copied from another scene or version by mistake.

A line appears only in the earlier list

The revised list may have dropped a line that still matters, such as a sound cue, a short response, or a note about a prop. It may also be an intentional cut. Ask the writer or reviewer to confirm before treating every removal as an error.

The same entry has changed

Read the full line rather than relying on the highlighted words alone. A changed character name may correct attribution, but a changed cue number or stage direction could alter what happens on stage. Check punctuation too when it affects pauses, emphasis, or the meaning of a line.

Several lines appear changed or out of place

This can mean a section was moved or reordered. Some comparison views show a moved entry as one removal and one addition rather than identifying it as a move. Search the revised list for the missing wording and verify that the new order matches the intended scene sequence.

Many lines differ even though the wording looks the same

Formatting may be driving the result. Different blank lines, numbering, indentation, or labels can make lines fail to match in the expected positions. The comparison reports textual differences, not whether a director or performer would interpret the script differently.

How to make the comparison easier to review

1. Choose matching boundaries. Compare the same scene, act, or section in both versions. If one list begins earlier, the extra lines can make later differences harder to locate.
2. Keep one entry per line. If a list has multiple cues on one line in one version and separate lines in the other, split or join entries consistently in a working copy. Preserve the source files so you can check the original formatting later.
3. Use consistent labels. Apply the same style for names and cues, such as JAMIE: in both lists. Do not change the actual script content just to make the comparison look cleaner.
4. Preserve repeated entries. Scripts often repeat a line or cue intentionally. Do not remove duplicates before comparing, because that can hide a repeated response or a recurring sound cue.
5. Check sequence separately. If the review asks whether the items are in the correct order, verify the full sequence from beginning to end. A matching set of entries can still be in the wrong order.
6. Confirm each change with context. Open the surrounding scene in the full script before approving a difference. A list may omit blocking, speaker context, or a stage direction that explains why a change was made.

Review changes without losing context

A line-by-line comparison is useful for finding where two versions differ, but it cannot decide whether a change improves the script or is intentional. Keep a short review record with the line or cue, the difference, and the question that needs an answer. For example, note whether a character label changed, a cue moved, or a line was removed, then ask the responsible reviewer to confirm the intent.

When the two lists come from different script formats, compare a clean working copy first, then inspect any formatting-sensitive lines in the original documents. The Text Compare tool runs in your browser, so the text you compare stays on your device.