Use a rough-cut review log to connect each timecoded audience note to one export, a written revision decision, a student owner, and evidence from the next version.
1. Register the reviewed export
Write the exact filename, export date, runtime, and version label before anyone adds a note. Use a film the teacher has approved for classroom review. The editor opens that file while the keeper copies its displayed name into the log. A message saying latest cut cannot identify the evidence after another export replaces it. Give this review a short session ID, and put that ID beside every later decision. Preserve the reviewed file so the team can replay the original problem without trying to reconstruct an earlier timeline.
- People
- 2: editor and note keeper
- Place
- Shared review desk
- Time budget
- 3 minutes
- Writing skill
- Identifying a reproducible draft
2. Locate the note on this version
Assign a note ID and write the scene plus the minute and second visible in the reviewed export. For a problem spanning a cut, record start and end positions. Do not copy a camera clip timecode into an export-time field without labeling the difference. Write a short landmark, such as the door closes before the reply, beside the numbers. When a later edit shifts the scene, that landmark helps the team find the same event. Keep the original coordinates even when the new version needs different ones.
- People
- 2: reviewer and keeper
- Place
- Timestamp column
- Time budget
- 2 minutes per note
- Writing skill
- Citing a precise moment
3. Preserve the observation in writing
Copy what the reviewer actually saw, heard, or failed to understand. A useful sentence identifies the moment and consequence: I could not tell who received the note after the hallway cut. Keep a suggested solution in a separate field. The reviewer checks that the written observation still represents their experience before discussion changes its wording. Do not convert one person's confusion into a claim that the whole class was confused. If the source is an anonymous sheet, use its assigned sheet ID rather than inventing an author.
- People
- 1: original reviewer
- Place
- Evidence sentence box
- Time budget
- 2 minutes
- Writing skill
- Separating evidence from preference
4. State the intended story information
Beside the observation, write what the audience was meant to learn at that moment. For middle schoolers, use a complete sentence naming the character, action, and consequence rather than a technical editing term. Compare that sentence with the screenplay or assignment question. If the intention was never written down, mark it newly agreed during review. This makes an honest distinction between repairing a missing clue and changing the story's purpose. Keep the original audience observation intact even when the group chooses a different intention.
- People
- 2: writer and director
- Place
- Intent column
- Time budget
- 3 minutes
- Writing skill
- Explaining narrative purpose
5. Resolve conflicting interpretations
Link two note IDs when viewers interpret the same moment differently. Write each interpretation without choosing a winner by volume or friendship. Replay the named export and record the visible or audible detail each student uses as evidence. A disagreement can reveal ambiguity, but it does not automatically require a change. The keeper writes whether the team needs another viewing question, a clearer clue, or an intentional ambiguity decision. Leave both source notes attached so the editor can understand why the decision was made.
- People
- 3: two reviewers and keeper
- Place
- Conflict pair fields
- Time budget
- 4 minutes
- Writing skill
- Comparing claims fairly
6. Choose an action with a reason
Label the note act, retain, ask, or defer. Act means the team has chosen an edit; retain means the existing choice is deliberate; ask means a named question needs an answer; defer means the decision waits for a stated reason. Write one sentence connecting that label to the story intention and the observation. Do not mark a note resolved merely because the team discussed it. A retained choice still needs a rationale, while a deferred choice still needs a return date and a person responsible.
- People
- 3: writer, editor, keeper
- Place
- Decision and rationale boxes
- Time budget
- 4 minutes
- Writing skill
- Justifying a revision
7. Describe the smallest testable change
For an act decision, name the scene, the material to change, and the intended result. Replace improve pacing with remove the repeated entrance, then test whether the recipient is still clear. Record an alternate take or insert only when that material actually exists in the approved package. Otherwise write missing material and route the question to the teacher. Avoid promising a reshoot during review. One action sentence should describe one test, making it possible to tell later whether that particular change helped.
- People
- 2: editor and writer
- Place
- Action sentence box
- Time budget
- 3 minutes
- Writing skill
- Writing an executable instruction
8. Assign ownership and a return point
Write one student's name beside the action and the next class or agreed check time. Add the person who will receive the result. A group name alone makes it hard to know who should answer when the work is blocked. The owner repeats the action in their own words and records any dependency, such as access to the approved edit computer. If the task cannot be completed in the available session, reduce its scope or mark it blocked. Preserve the original due point when recording a later change.
- People
- 2: editor and task owner
- Place
- Owner and due fields
- Time budget
- 2 minutes
- Writing skill
- Making a workable commitment
9. Check the task boundary
Flag a proposed change that introduces private information, unapproved footage, a new performer, or a questioned music cue. Write the affected note ID and the specific unanswered question without copying sensitive details into a shared classroom sheet. A teacher assigns the appropriate review route; a student log cannot grant permission. Keep that action on hold until the authorized answer is recorded. The editor can still test an approved alternative, but must label it as an alternative rather than quietly treating the held material as available.
- People
- 2: teacher and keeper
- Place
- Hold and dependency boxes
- Time budget
- 3 minutes
- Writing skill
- Recognizing authority limits
10. Name the revised export
When an edit is ready for review, record its actual export filename and date beside the action ID. Keep the original export label in its own field. Write the new scene position and the old landmark if earlier trims moved the moment. Confirm that the revised file opens from the agreed classroom location. A project save, a timeline screenshot, and a rendered review file are different objects. If the export is not ready, write not exported and leave verification pending instead of attaching a file from another session.
- People
- 2: editor and keeper
- Place
- New version column
- Time budget
- 3 minutes
- Writing skill
- Tracing a revision across files
11. Retest the same question
Show the revised moment to a reviewer who can answer the original viewing question without being coached toward the desired response. Record what they understood and the new timestamp. Compare that response with the original observation and the written intention, then check whether the edit introduced another missing clue nearby. The verifier writes pass, fail, or inconclusive with a short evidence sentence. A student saying I changed it establishes implementation only; it does not establish that the audience problem was solved.
- People
- 2: reviewer and verifier
- Place
- Before and after evidence
- Time budget
- 5 minutes
- Writing skill
- Evaluating revision effects
12. Close, reopen, or carry forward
Close an action only when the new export and verification evidence are named. Reopen it when the test fails, linking the next action to the same note ID instead of erasing the first attempt. Carry an inconclusive test into the next session with its unanswered question, owner, and return point. Retain and defer decisions keep their own labels rather than becoming fake completed edits. Finish by reading the open rows aloud and having each owner confirm their task. The teacher receives a visible account of unfinished work.
- People
- 3: owner, verifier, keeper
- Place
- State and next session fields
- Time budget
- 3 minutes
- Writing skill
- Reporting outcomes honestly
Use the sheet as a revision record
Download the fillable rough-cut review log. The form follows one note from its original export through a decision and a new-version test. Duplicate the form for additional notes. The suggested people and time budgets above are classroom planning choices, not measured results or a required teaching schedule.
Before editing begins, collect audience observations with the screening feedback sheet. This log starts after those observations exist. When files change hands, use the edit handoff checklist for the transfer; the review log tracks decisions across exports rather than package delivery.
End with a short evidence paragraph
Ask each student owner to write three sentences: what the audience could not understand, what the team changed or retained and why, and what the next viewing actually showed. Cite the note ID and both export labels. If a result is inconclusive, say what evidence is missing. This makes revision an explainable writing task rather than a list of unexplained editing commands.