Do you actually know which cut the client is watching?
Yesterday the editor dropped a Google Drive link. Today a marketer on the client side forwarded a compressed mp4 to the director in WhatsApp. The director replied with a voice note: "something feels off in the middle." By evening the thread has four files, three opinions, and not one note you could hand to an editor without decoding it first.
That is the client video review process in a lot of small studios. Not because people are sloppy. Because a chat can move files around and cannot hold a version, a timecode, and an "approved."
What breaks when review lives in a messenger
"Make it punchier after the logo" can mean five different things. The client is watching one second. The editor is watching another. Both think they mean the same spot.
Then the argument stops being about the cut and starts being about the file. final_v3, final_this_one, a WhatsApp screenshot, a Drive link that opens for one person. Someone is already watching a crushed picture and commenting on messenger artifacts: mushy detail, thin audio, titles that don't read on a phone.
Meanwhile marketing, legal, and the director all type into the same thread. The editor does all three lists and gets a fourth round: "we never signed off on that." The producer becomes a translator of voice notes. Half the day goes to turning a conversation into something you can open in Premiere.
Take a 40-second product video. Monday, first assembly goes out. Tuesday, marketing writes in WhatsApp: "logo smaller." Wednesday, legal asks for a longer disclaimer in a different thread. Thursday, the director watches whatever got forwarded to their phone and says it "feels cheap." Friday, the editor has three lists, none of them attached to a version. They are not slow. They do not have one object everyone is looking at.
The client is not doing this to be difficult. They write where the conversation already is. If the only place the video lives is chat, the notes will stay in chat. A polite "please comment here instead" does not survive the third parallel project. A week later the voice note lands in the group thread anyway, because that is faster.
Chat will not become a player. You need a review tool
Video review is not a discipline problem in WhatsApp. It is a tool: a link to the current cut, a comment on a specific second, version history, and a clear approval.
The client opens the video, pins a note at 01:12, sees what colleagues already wrote, and hits approved or sends one list onward. The editor does not reconstruct the brief from three chats. They see the same second the client saw.
You do not get that from a spreadsheet with columns for "timecode / note / status." A doc next to a private Vimeo link is still chat, just in two tabs. A comment you cannot stick on a frame will drift off the picture again.
The actual category of tool is small, and pretending a drive folder plus a spreadsheet covers it is a waste of time.
Frame.io is what a lot of studios already know. It is a player: you upload a version, the client comments on the timeline from a link, you can see who wrote what, and you can compare v1 and v2. If review is the only hole, that is often enough.
Basalt is for a different hole. The same client will ask "where are we" tomorrow, drop new footage the day after, and the editor needs those notes inside the project, not in a neighboring app: which version this is, whether it is approved, what actually ships. Review stops being a tab you glue back onto WhatsApp.
The client does not need to join your company as a teammate. They need a link, a video, and a box for a note on a second. Frame.io and Basalt's client access both work that way. The pushback is almost always the same: "just send the file, I'll watch it tonight on my phone." That file is how you get a voice note with no timecode. Answer it directly: the file will compress, the director will see the wrong picture, and we will get notes on WhatsApp instead of notes on the video.
Chat also cannot do version compare. In WhatsApp people watch whatever was forwarded last and say "this got worse," without seeing which second they are judging. In a player, v1 and v2 sit next to each other. The "we already changed that" argument ends faster, because you can see whether you did.
Short version: notes go on a frame. Approval goes on a version. The publish file comes after that, not instead of it.
How to use review so it does not slide back into chat
The first time, the client will almost always ask for a file. Don't argue about "process." Tell them the link is the same picture you are looking at, they can tap the second they mean, and the director gets that link instead of a crushed mp4. If they still send a voice note in WhatsApp, don't take it as-is: "drop that on 00:34 in the player, otherwise the editor is guessing the frame." Two replies like that usually settle it.
A player does not close the job if you send the link "just in case" and keep making decisions in WhatsApp. A few rules stop the tool from becoming another tab.
Keep one link to the current cut. Chat and email stay for timing: when can you watch, who is looking today, here is the link. A voice note that says "take that out" does not count until it exists as a timecode in the player. Skip that, and two weeks later you are back to three answers for "which file."
On the client side you need someone who can say yes. The expensive version of this sounds polite: "I'll collect feedback from the team and come back." Three days later you get seven notes from people who never saw the brief and never watched the last cut. Let them argue internally. What reaches the studio is one list, and only that person writes "approved." If two people must sign off, split the lanes up front: marketing owns message and CTA, brand owns logo and color.
Every time you send a cut, say what you are asking them to watch. Otherwise they get a rough assembly and comment on color, then a fine cut and reopen the structure, then at polish they ask for a different pace. Rough cut is story, scene order, runtime. Fine cut is pacing, selects, titles. Polish is typos, levels, the last brand frame. "Rebuild the video" at polish is a new job, not a comment in the player.
And do not send the master as a chat video. The client should watch the same picture you are watching. A crushed WhatsApp file "so the director can see it quickly" produces notes on artifacts that are not in the master. For an internal preview, send the same review link, not a file with "forward this to whoever." The publish file goes out after "approved," with a version number and the name of the person who signed off. Otherwise a month later someone wants "the one we approved in March," and you are back in chat history.
How to tell you still have a chat, not a review
Open the last delivered project and answer honestly.
- Anyone can open the current cut from one link, without asking the editor where it went
- Notes sit on timecodes, not in voice messages across three threads
- One person on the client side can close the job with "approved"
- The master file did not go into WhatsApp before that
- A month from now you can find the closed version without scrolling the chat
If a review link exists and decisions still happen in the thread, you do not have a tool. You have a habit. Run the next video only in a player: Frame.io if you want a dedicated review app, or Basalt if review should live inside the project instead of in a neighboring tab.
Summary
As long as notes get written where it is easy to type, the editor will keep rebuilding the cut from scraps. That is not the client's personality, and it is not fixed by "being more organized."
Send the next rough cut as a player link, not a file in chat. Do not take a comment without a second. "Approved" belongs on a version, not in the head of whoever last watched a crushed mp4.