When was the last time every client revision reached the editor without something getting lost?
The client sends a revision in WhatsApp. The producer forwards it to the editor via Telegram. The editor asks for clarification over email. A week later, nobody can find what timecode was being discussed – and the whole cycle starts over.
This isn't just inconvenient. It's a systemic problem that eats into your profits. Every lost revision means an extra iteration. Every extra iteration means hours of editor work that the studio pays for out of pocket.
From what we've seen, studios without a structured review process spend 2–3x more time on approvals than those with a proper workflow. At the scale of ten projects a month, that's dozens of hours that could have been spent on new work.
Why "Just Message Us" Doesn't Work
Messengers are great for quick communication but terrible for managing revisions. Here's why:
- Feedback gets lost in the message stream. Finding a specific comment a day later is a quest – a week later, nearly impossible
- No content reference. "Somewhere in the middle where the guy walks" is not a timecode. The editor spends 15 minutes decoding a single note
- Duplication. Clients send the same feedback to multiple channels because they're not sure they were heard
- No statuses. It's unclear which revisions are in progress, done, or rejected
- No version history. Clients watch an old version and repeat feedback that was already addressed. The editor does the same work twice
5 Stages of a Proper Review Process
1. Preparing for Review
Before sending video to the client, confirm three things:
- The version is clearly numbered – "Commercial_v2_rough_cut", not "final_final_last_2". If the client doesn't know which version they're watching, feedback will get confused
- There's a cover note – explaining what specifically needs feedback at this stage. Without context, clients will comment on everything, including things that aren't finalized yet
- Revision scope is defined – the client should know that at the rough cut stage, color grading comments aren't needed yet. Clear boundaries save time for both sides
2. Collecting Feedback in One Place
The golden rule: one entry point for revisions. This could be:
- A client portal with a video player and comment form – the ideal setup
- A specialized video review tool with timecoded comments
- As a last resort – a single document with a clear structure: timecode, description, priority
It's critical that feedback is tied to timecodes. "Remove the cutaway from 1:23 to 1:30" is a clear task an editor can start on in a minute. "Something feels off in the middle" is a reason for a call, not a work order. The difference between these two phrasings is 30 minutes per revision.
3. Processing and Prioritizing
Not all revisions are equally important, and not all need to be executed literally. After collecting feedback, the producer should:
- Group revisions by type: editing, graphics, audio, color. Editors work more efficiently when they can handle all similar tasks in one pass
- Prioritize: critical → important → nice-to-have. Critical means the video can't be shown to the client without this fix. Nice-to-have means it can be discussed
- Filter contradictory feedback. Yes, a client can ask to "make it more dynamic" and "add a pause" in the same message. The producer's job is to resolve the contradiction before it reaches the editor
- Resolve debatable points with the client before work begins. Better to spend 10 minutes clarifying than 3 hours redoing
4. Handing Off to the Editor
The editor should receive a clear task list, not a stream of forwarded messages. Each revision includes:
- Timecode or range
- Description of the required change
- Priority level (critical / important / nice-to-have)
- Reference material, if available
When an editor gets a structured list instead of "check what the client wrote in the chat," they spend time working, not decoding. In our experience, structured handoffs reduce iteration time by 30–40%.
5. Final Approval
After revisions are made, the client should see not just a "new version" but what exactly changed:
- The client receives a new version with notes on which revisions were addressed
- Each revision has a status: completed, completed differently (with an explanation of why), or declined (with reasoning)
- The client approves the version as a whole or leaves specific notes on particular timecodes
Transparency at this stage reduces the number of iterations. When clients see that they've been heard and every revision was processed – trust grows, and the endless "just one more small change" cycle fades away.
Tools for Organizing Reviews
Specialized Solutions
- PMS with a client portal – clients watch video and leave comments in one interface, editors see all tasks with timecodes and statuses. Tools like Basalt combine review, task management, and finances in one place
- Standalone video review tools – if you only need viewing and timecoded comments, without project management
Minimum Viable Setup
If a specialized tool isn't in the budget yet:
- Upload video to a private channel (password-protected Vimeo, unlisted YouTube)
- Create a feedback collection template: timecode → description → priority. Send it to the client along with the video
- Keep all revisions in one document, not scattered across conversations. Even a Google spreadsheet with columns "timecode / revision / status / editor's comment" is better than messenger chaos
- Assign one person responsible for collecting and processing feedback. If revisions go to the producer, manager, and editor simultaneously – things will get lost
Checklist: Is Your Review Process Working?
- Every video version has clear numbering
- Clients leave feedback in one place, not across different chats
- Feedback is tied to timecodes
- The producer processes and prioritizes feedback before handing it to the editor
- Editors receive a structured task list, not forwarded messages
- Every revision has a status (in progress / completed / declined)
- Clients can see exactly what changed in the new version
- There's a history of all versions and comments
If more than two items aren't checked – there's serious room for improvement. And the sooner you organize your review process, the less time and stress you'll spend on every project.
Summary
A good review process isn't bureaucracy. It's an investment that pays off on every project: fewer iterations, fewer misunderstandings, happier clients, and a less burned-out team. Start small – define one entry point for feedback and require timecodes. Even that single step will change a lot.