Updated October 2026
Why a thumbs-up emoji is not a video approval
A thumbs-up on WhatsApp is not a reliable approval, because it doesn’t say who approved, which version they approved, or what they were approving. A real approval records three things: who approved, which exact version, and when. Anything less leaves you arguing from memory when the client changes their mind.
The “I never approved that” scenario
You send version 3 on a Tuesday. The client replies with a thumbs-up. You export the final, send it, and invoice. Two weeks later: “I never said it was final. The second paragraph needs changing, and I wanted a different ending.”
You scroll back. There’s a thumbs-up, but was it on version 3 or a message about version 2? Was it from the owner or from their assistant? Did they mean “approved” or “I’ve seen it”? You can’t tell, and neither can anyone else. Now you either redo the work for free or have an uncomfortable conversation about something that should have been settled.
This is not about distrusting clients. Most people aren’t lying. They genuinely remember it differently, because the approval was never clear in the first place.
What a real approval should record
For an approval to be worth anything later, it should capture:
- Who. A named person, ideally the agreed decision-maker, not “someone on the thread”.
- Which version. The exact file or version label, so “final” can’t drift to a later edit.
- When. A date and time.
- What they approved. A clear statement, such as “I approve version 3 as final”, not an emoji.
- How it was given. The channel and, where possible, technical details such as the IP address.
If any of these are missing, the approval is open to interpretation.
Why email and chat are weak records
- Ambiguity. “Looks good!” might mean approved, or might mean “good so far”. A thumbs-up can mean “received”.
- Version drift. Chat doesn’t tie a message to a specific file. If you send a revised cut after the “OK”, it’s unclear which one was approved.
- Messy threads. Approvals get buried among unrelated messages across several channels, and finding them takes time.
- Editable and deletable. People can delete messages in many chat apps, and screenshots are easy to dispute.
- Wrong person. The reply may come from someone who isn’t the decision-maker.
Email is better than chat because it keeps headers and timestamps, but it still lacks a version link and a clear “final” statement.
A simple approval workflow
You can do this with any tool. The point is to be consistent.
- Agree who approves in the brief, and write down their name.
- Label every version. V1, V2, final candidate. Never send an unlabelled file.
- State the question clearly. “Please confirm you approve version 3 as the final cut. After approval, changes are quoted as a new project.”
- Get an explicit yes. A sentence naming the version, not an emoji.
- Record it. Save the message with its date, or better, use a tool that stores the approval for you.
- Send the final only after the approval is on record, and invoice at approval, not weeks later.
Put the “approval is final” line in your revision policy and your contract, so the client agreed to the rule before they approved.
How a certificate and audit trail help
Doing steps 3 to 5 manually works, but it takes discipline and leaves you assembling evidence when you need it. A certificate and an audit trail do it automatically:
- An approval certificate summarises the approval in one document: who, which version, when.
- An audit trail is a time-ordered log of what happened in the project (views, comments, the approval itself, with technical details like IP address and device).
Together they let you answer “did you approve this?” with a record instead of a memory.
This does not turn a record into a court ruling. It gives you strong, clear evidence of what happened, which in practice settles most disagreements before they get serious. For anything contractual, see a professional.
How Revu records approvals
In Revu the client opens a private link, reviews the video, and approves with one click. The approval is recorded with the client’s name, the version and the timestamp, and an approval certificate PDF is emailed. Every key action is written to an audit log with IP address and user agent. The invoice is generated automatically when the client approves, so billing happens at the moment the project is actually done.
It works without a client account, so the client doesn’t have to learn anything new to give you a clear answer.
Why this matters to me
I’m Khalil, a video editor in Nice, and I run Naja Studio. I built Revu after one too many “are we sure they approved that?” moments, chasing approvals by email and hunting through WhatsApp for proof. A clear approval takes ten seconds when you set it up and hours when you don’t.
Frequently asked questions
Is a thumbs-up emoji a valid approval for a video?
It is weak evidence at best. It does not state who approved, which version, or what was approved, so it can be disputed later. Ask for an explicit statement naming the version, or use a tool that records the approval with name, version and time.
What should I record when a client approves a video?
The name of the approver, the exact version, the date and time, a clear statement that the version is approved as final, and, where possible, how and from where it was given.
How do I prove a client approved the final video?
Keep a record that shows who approved, which version and when: for example a dated written approval naming the version, or an approval certificate and audit log from a review tool. Ask a professional if you need legal proof for a specific dispute.
Should I invoice before or after approval?
Many editors invoice at approval, so billing is tied to a clear milestone and does not wait weeks. Agree the payment terms in your contract.
What if a client asks for changes after approving?
Treat them as a new request. If your contract and revision policy say approval is final, you can quote the changes as new work and point to the recorded approval.