A team usually damages an opening through untracked intentions, not through a lack of opinions. The cure is to hand off decisions, not just documents.

Multiple editors can improve an opening, but only if they share the intended reader effect. The system here keeps voice, continuity and revision authority visible so collaboration does not flatten the scene into committee prose.

Use the checks as lenses, not commandments. Genre, medium and authorial intent can justify different openings, but the intended effect should still be observable in the text. This boundary is recorded specifically for Opening Scenes in a Team: Handoffs, Notes and Version Control Without Killing the Voice.

The handoff rule

The handoff for Opening Scenes in a Team: Handoffs, Notes and Version Control Without Killing the Voice should answer five concrete questions: what artifact is moving, which decision is already fixed, what may still change, which evidence must travel with it, and who owns the next decision. Missing answers become guesswork at the next desk.

Write the opening brief

Before revisions, state the intended reader promise, viewpoint anchor, emotional temperature and non-negotiable facts in one page.

For Write the opening brief, preserve authorial intent in a form another editor can inspect. Write the intended reader effect next to the note, then allow the next collaborator to solve for that effect rather than copying one proposed sentence.

Separate diagnosis from rewrite

A note should first name the reader problem and evidence. A replacement sentence is optional; otherwise teams confuse one proposed fix with the underlying issue.

For Separate diagnosis from rewrite, preserve authorial intent in a form another editor can inspect. Write the intended reader effect next to the note, then allow the next collaborator to solve for that effect rather than copying one proposed sentence.

Tag note authority

Mark notes as factual correction, continuity requirement, legal/safety requirement, editorial preference or experiment. They do not carry the same weight.

For Tag note authority, preserve authorial intent in a form another editor can inspect. Write the intended reader effect next to the note, then allow the next collaborator to solve for that effect rather than copying one proposed sentence.

Use scene IDs, not line numbers

Line numbers shift. Stable scene and beat IDs survive revisions and make approvals traceable.

For Use scene IDs, not line numbers, preserve authorial intent in a form another editor can inspect. Write the intended reader effect next to the note, then allow the next collaborator to solve for that effect rather than copying one proposed sentence.

Keep a rejected-changes log

Short reasons for rejected notes stop the same debate from restarting every round and help new collaborators understand the design.

For Keep a rejected-changes log, preserve authorial intent in a form another editor can inspect. Write the intended reader effect next to the note, then allow the next collaborator to solve for that effect rather than copying one proposed sentence.

Read the merged opening cold

After merging, one person who did not make the changes reads from zero context. Local edits can each be correct and still produce a globally confusing scene.

For Read the merged opening cold, preserve authorial intent in a form another editor can inspect. Write the intended reader effect next to the note, then allow the next collaborator to solve for that effect rather than copying one proposed sentence.

Keep the scene's intention attached

A revision note should name the effect it wants: faster orientation, stronger suspicion, clearer desire, cleaner continuity. That gives collaborators room to solve the same problem without cloning one editor's voice.

When two notes conflict, compare their priorities rather than averaging the prose. A continuity correction, a taste preference and a deliberate mystery are not equal kinds of instruction.

Close a revision round with one accepted scene state and a brief rejected-change log. That record prevents old arguments from silently returning in the next pass.

A focused scenario for Hooks & Openings

Hooks & Openings context: Simulate a handoff to a person who missed every meeting. Give them the current artifact plus the fields implied by Write the opening brief and Separate diagnosis from rewrite. Any question they must answer by guessing belongs in the next handoff template.

Evidence notes unique to this workflow

Hand Write the opening brief to a cold collaborator with the intended reader effect but without a suggested rewrite. Note 1 records whether the collaborator can preserve the effect in their own words; if not, the brief needs more context rather than stronger line editing.

Hand Separate diagnosis from rewrite to a cold collaborator with the intended reader effect but without a suggested rewrite. Note 2 records whether the collaborator can preserve the effect in their own words; if not, the brief needs more context rather than stronger line editing.

Hand Tag note authority to a cold collaborator with the intended reader effect but without a suggested rewrite. Note 3 records whether the collaborator can preserve the effect in their own words; if not, the brief needs more context rather than stronger line editing.

Hand Use scene IDs, not line numbers to a cold collaborator with the intended reader effect but without a suggested rewrite. Note 4 records whether the collaborator can preserve the effect in their own words; if not, the brief needs more context rather than stronger line editing.

Hand Keep a rejected-changes log to a cold collaborator with the intended reader effect but without a suggested rewrite. Note 5 records whether the collaborator can preserve the effect in their own words; if not, the brief needs more context rather than stronger line editing.

Hand Read the merged opening cold to a cold collaborator with the intended reader effect but without a suggested rewrite. Note 6 records whether the collaborator can preserve the effect in their own words; if not, the brief needs more context rather than stronger line editing.

Hand Write the opening brief to a cold collaborator with the intended reader effect but without a suggested rewrite. Note 7 records whether the collaborator can preserve the effect in their own words; if not, the brief needs more context rather than stronger line editing.

Hand Separate diagnosis from rewrite to a cold collaborator with the intended reader effect but without a suggested rewrite. Note 8 records whether the collaborator can preserve the effect in their own words; if not, the brief needs more context rather than stronger line editing.

Hand Tag note authority to a cold collaborator with the intended reader effect but without a suggested rewrite. Note 9 records whether the collaborator can preserve the effect in their own words; if not, the brief needs more context rather than stronger line editing.

Hand Use scene IDs, not line numbers to a cold collaborator with the intended reader effect but without a suggested rewrite. Note 10 records whether the collaborator can preserve the effect in their own words; if not, the brief needs more context rather than stronger line editing.

Hand Keep a rejected-changes log to a cold collaborator with the intended reader effect but without a suggested rewrite. Note 11 records whether the collaborator can preserve the effect in their own words; if not, the brief needs more context rather than stronger line editing.

Hand Read the merged opening cold to a cold collaborator with the intended reader effect but without a suggested rewrite. Note 12 records whether the collaborator can preserve the effect in their own words; if not, the brief needs more context rather than stronger line editing.

Hand Write the opening brief to a cold collaborator with the intended reader effect but without a suggested rewrite. Note 13 records whether the collaborator can preserve the effect in their own words; if not, the brief needs more context rather than stronger line editing.

Hand Separate diagnosis from rewrite to a cold collaborator with the intended reader effect but without a suggested rewrite. Note 14 records whether the collaborator can preserve the effect in their own words; if not, the brief needs more context rather than stronger line editing.

Sources

Related Reading