Documentary review is a scale problem wrapped in a trust problem. The scale: hundreds of hours of dailies and interview footage feeding a cut that changes shape for months. The trust: unreleased footage of real people, under representation agreements, reviewed by directors, editors, producers, executive producers, funders, and sometimes lawyers - each of whom needs a different slice of access. The workflow that survives both is built on protected links, versioned assemblies, and review stages that match the film's own ladder: dailies, selects, assembly, rough cut, fine cut, picture lock.
What makes documentary review different
- The source volume dwarfs the cut. A 90-minute feature can rest on 200+ hours of footage; review has to happen at every rung of the ladder, not just at the end.
- The stakeholders are heterogeneous. An EP watches story, a funder watches for deliverables and milestones, a clearance reviewer watches for legal exposure - same link, different concerns.
- The material is sensitive by definition. Real people, pre-publication. One leaked assembly can burn a source relationship or a subject's trust - access controls are not enterprise nice-to-haves here, they are the job.
- The timeline is nonlinear. Structure changes for months; a note pinned to scene 4 in February may need re-answering against a cut where scene 4 no longer exists. Version-attached comments are the only durable memory.
Review at every rung of the ladder
Each stage has its own review question, and the link settings should change with it:
- Dailies review. The team confirms coverage and sync daily - internal, tight access, watermark always. The definitions and workflow are in what is dailies review.
- Selects. The best moments pulled into stringouts and selects reels, shared with story stakeholders to align on direction before structure exists - the mechanics are in what is a selects reel.
- Assembly → rough cut. The first cuts where external stakeholders (producers, EPs) see story; frame-pinned notes on the assembly, resolved thread-by-thread into the next cut. The stage definitions live in what is a rough cut.
- Fine cut → picture lock. The round where notes shift from story to polish - and where "no new structural notes" needs to be said out loud. The locking discipline is in what is picture lock.
- Funder/network reviews. Milestone screenings with explicit sign-off records - the approval chain version of the loop, covered in the video approval workflow guide.
Controls for sensitive footage
Every documentary link should leave the building with: a password (anything with unpublished material), a watermark (identifies whose copy escaped - the full argument is in why watermark video reviews), downloads off (the master never rides in a reviewer's inbox), and a named owner who can revoke the link the day a reviewer's involvement ends. For funder diligence questions - data residency, retention, security attestations - ask vendors in writing and keep the answers; the twelve questions worth asking are listed in enterprise video review requirements.
Storage and resolution reality
Documentaries are where free tiers go to die: 200 hours of interview footage at 4K overwhelms a 2 GB plan in an afternoon. As of November 2026, Frooty's Studio plan carries 2 TB plus 1 TB per member, plays original-resolution files for internal reviewers (the colorist and the sound designer judge the real pixels), and reviewers on links are never billed seats; the Free tier (5 GB, 1080p playback, 2 members) is enough for a selects-stage pilot before any purchase. Frame.io's comparable tiers run $15/member/mo (Pro) and $25/member/mo capped at 15 members (Team) with 2 GB on the free tier - the seat-capped model is worth modeling against an editor-and-producer-heavy documentary team, where members multiply. The reviewer-versus-member question is unpacked in video review tools with unlimited reviewers.
FAQ
How do funders review without seeing everything?
Milestone screenings: one link per milestone, password and watermark on, downloads off, expiry set to the review window, and a named sign-off recorded against that exact version. Funders do not need standing access to the project - they need a record of what they approved, when.
Can reviewers leave notes on hundreds of hours of footage?
Review runs on cuts and selects, not on raw source. Share the selects reel or the assembly - the material someone can meaningfully react to - and keep raw dailies internal to the team's own review.
What stops an assembly from leaking?
Four controls in combination: password, per-reviewer watermark, downloads off, and revocation the moment a reviewer's role ends. No single control is airtight; the combination makes leaks attributable and rare, which changes reviewer behavior by itself.
Do notes survive when the cut changes shape?
Only if notes attach to versions rather than to chat threads. A comment pinned to a scene in the February assembly stays attached to that assembly; when the April cut restructures the film, the editor works from resolved-and-carried notes instead of from memory.