A project review needs a clear question more than a large audience. Use a Zopley screening to show one version, collect specific observations and decide what to investigate afterward.
1. Define the purpose of the session
Tell viewers whether you are checking pacing, clarity, sound or the overall story. Choose a small number of questions that fit the stage of the edit. Feedback about a polished title sequence is not useful if you are still deciding the structure.
Write one decision the review should inform, such as whether the opening makes the subject clear. Send that question with the version and runtime.
For vocabulary to describe what you noticed, consult Yale's Film Analysis Guide. Bring one scene back to the conversation instead of treating a technical term as a verdict.
Choose a timestamp and describe what is visible. What did the shot make easy to notice, and what stayed outside the frame?
Yale's Film Analysis Guide · Editorial viewing prompts
2. Prepare the same version for everyone
Upload and test the intended cut before the meeting. Give the file a recognizable name and select it in the room. Avoid switching to a different edit midway through comments without telling the group.
Open the named final review file and check audio plus the ending. Make sure the room queue contains the same cut named in the invitation.
Compare your observations with Yale's cinematography guide, which covers framing, focus, color and camera movement. Start with what is visible in the scene.
3. Separate viewing from discussion
Let the first playback run unless a technical issue stops it. Ask people to note the time and describe what they experienced. Then use shared playback controls to revisit the relevant passage together.
Play the whole video once, then invite observations with timestamps. Save proposed changes until everybody has had a first response.
Use Yale's film sound guide to discuss sound inside the story and music or narration heard by the audience. Identify the moment before interpreting it.
4. Record observations before solutions
A note that a transition felt abrupt is useful even if the proposed fix is wrong for your project. Ask where the feeling began and what preceded it. Take the observations away, then choose changes with the whole edit in mind.
Use notes with timestamp, observation and effect on the viewer. Mark proposed solutions separately so an editing suggestion does not replace the underlying problem.