When you compare a first draft and a revision in a three-pane Mac text editor, the most important result is not three documents returning to the same screen position. It is an evidence trail that explains each change. Put the first draft on the left, the editable revision in the center, and a change record on the right. Give every change an ID, then connect that ID to a before quotation, an after quotation, a classification, a reason, and a review result.
This article is not about checking the current manuscript against character and timeline references. It also does not use restart layout recovery as the acceptance decision. Its narrow job is to make one change from draft to revision auditable.
Make the change ID—not the line number—the comparison unit
Adding one sentence to a draft shifts every line that follows it. Splitting a paragraph or reordering dialogue makes matching line numbers even less useful. Opening three panes does not solve that identity problem by itself.
Move the comparison unit from screen position to a change ID. A fourteenth revision decision in scene eight might be labeled M14. Read the earlier wording in the left pane, the revised wording in the center pane, and locate M14 in the right-hand record. Later insertions can move both passages without moving the identity of the decision.
A change ID is therefore more than a navigation anchor. It is the key that binds the editor’s decision to its evidence. The purpose of the three panes is not to recover the same location. It is to inspect one decision from three directions: what the draft said, what the revision says, and why the change was made.
Record six facts for every change
You can apply the general method with a spreadsheet or ordinary notes. Create one row per change and record:
- the change ID;
- the chapter, scene, or paragraph affected;
- the smallest useful quotation from the first draft;
- the corresponding quotation from the revision;
- the class: deletion, addition, or meaning change; and
- the reason plus the reviewer’s result.
Keep short quotations rather than relying only on filenames and line numbers. The quotations remain searchable after surrounding prose moves. A useful reason says what changed: “made the subject explicit,” “withheld this clue in the current scene,” or “changed the speaker’s intention from refusal to hesitation.” “Edited for clarity” is too broad to support an audit.
Do not edit the original while creating this record. The left pane is the before evidence, the center pane is the working revision, and the right pane owns the decision record. If the original is saved with the new wording, the reviewer loses the source needed to verify the before quotation.
Do not reduce every meaning change to deletion plus addition
A textual diff can describe most changes as removed characters and inserted characters. An editorial audit needs another level.
Suppose “He said he would go” becomes “He said he had not decided yet.” Characters were deleted and added, but the important change is that the character’s intention moved from commitment to uncertainty. Recording one deletion and one addition would hide the consequence for the next scene.
Use the classes this way:
- Deletion removes information or expression without replacing its role.
- Addition supplies information or description while preserving the existing meaning.
- Meaning change alters intention, fact, time, causality, or point of view.
When one edit fits more than one class, make the class with the largest story consequence the primary one and note the mechanical deletion or addition separately. The goal is not tidy totals. The goal is to prevent a later review from missing the effect of the edit.
Audit M14 across the three panes
Consider a worked editorial example in scene SC08, recorded as change M14.
The first draft in the left pane says, “I will go to the harbor.” The revision in the center says, “I will not decide whether to go to the harbor until dawn.” The right-hand record contains target=SC08, change ID=M14, primary class=meaning change, and reason=changes a committed action into an unresolved choice that remains available in the next scene.
The reviewer first checks that both quotations match their source texts. Next, the reviewer asks whether the explanation about uncertainty is visible in the revised sentence. Finally, the reviewer checks separately whether the following scene incorrectly assumes that the harbor trip is already settled.
The result does not pass merely because all three panes are visible. It is auditable when another editor can read the two quotations and the M14 record and explain the same change. A beautifully arranged screen with a reason such as “revised” still lacks the evidence needed for that result.
Use Rune Studio as an audit desk, not an automatic decision system
Rune Studio’s feature materials document one-to-three rows and columns plus moving tabs among panes. This is documentation evidence, not evidence of the current screen or a completed operation. This article treats that documented scope as a candidate audit desk for reading three forms of evidence together.
For example, you can try placing the first draft on the left, the revision in the center, and the change record on the right so that the M14 quotations and reason remain visible together. However, this article does not contain reproducible start-to-result evidence for opening three tabs and placing them in an h3 layout. Confirm that arrangement in the current version with a disposable manuscript copy.
The documented screen features do not establish automatic text-difference detection, automatic classification into deletion, addition, and meaning change, or automatic merging. The editor owns the M14 class and explanation. Keep the documented feature scope separate from the unverified arrangement procedure and from any claim that an entire manuscript audit has been completed.
Know which work belongs elsewhere
This method suits revisions whose reasons must remain explainable: responding to an editor, reviewing work with another person, or changing a clue, fact, or character intention in a long manuscript. It is useful when the meaning of the change matters as much as its text.
Checking one current manuscript against authoritative character and timeline references is the separate role of STUDIO-005. Testing whether linked scrolling follows the correct content across nonadjacent screenplay anchors belongs to STUDIO-329. This article does not replace general reference checking, restart layout recovery, automatic diff detection, or automatic merge.
Start by making one change explainable
Do not begin a three-pane comparison by arranging every chapter. Select one change in one scene and complete its ID, before text, after text, class, reason, and review result.
If another editor can read that row and the two source passages and explain what changed and why it matters, comparison has become an audit. Use the Mac text editor to keep those three forms of evidence visible together. Prove one change such as M14 first, then extend the same record to the rest of the manuscript.
If you are considering the three-tab audit desk, check the current split-view scope on the Rune Studio product page and test the same record with a disposable copy of one scene.
