← All posts Workflow

How to get sign-off on a video edit (so 'approved' actually means approved)

A 'looks good 👍' on WhatsApp isn't approval — it's the reason you're doing a third free revision. Here's how to get a clear, recorded sign-off on a video edit, so the client can't reopen a cut they already signed off.

A thumbs-up on WhatsApp is not sign-off — it’s a message you’ll be scrolling back to find during an argument. Real approval is one clear action, tied to the exact cut the client approved, with a record of who approved it and when — so “we approved that” and “no you didn’t” stop being a debate.

Most freelance editors and small studios in India lose money not on the edit, but on the fuzzy end of it. The client says “perfect, ship it” in a voice note. You deliver. A week later: “actually the client wants two changes, small ones.” Small for them. Another unpaid round for you. It happens because nobody ever actually closed the review — there was no moment where approval was given and recorded.

Why “looks good” costs you money

  • A chat message isn’t attached to a cut. “Looks good” over WhatsApp — good to which version? You’ve sent three. When they ask for changes, there’s no way to point at what they approved, because the approval isn’t on anything.
  • Verbal yes, verbal no. “I never said final” is impossible to argue when the yes was a voice note buried in a chat with 200 other messages. You’ll spend an hour scrolling to find it, and it still won’t be clear.
  • No line between “review” and “done”. If every cut is just “have a look”, the review never ends. There’s no button the client presses that means this one, we’re finished. So it never finishes.
  • Scope creep walks in through the gap. Without a recorded sign-off, “one more tiny change” after approval feels free to the client — because as far as any record shows, they never approved anything. The missing sign-off is what makes the extra round look reasonable.

This isn’t about distrusting clients. It’s that a casual yes gives neither side anything to stand on, so the honest client genuinely forgets they approved, and the difficult one exploits that there’s no proof.

What a real sign-off looks like

The fix is to make approval a single, unmistakable action on the actual video — not a message somewhere else:

  • The client approves or requests changes on the cut itself. One button on the review page. “Approved” is now a state on that exact version, not a phrase in a chat.
  • It’s tied to the version. Approval sits on v3, specifically. If they later want changes, it’s obvious that v3 was signed off and this is new, billable work — not a fix to something unfinished.
  • There’s a record with a name and a time. Who approved, which cut, when. Not to wave in anyone’s face — just so the question never turns into an argument. The share activity shows it plainly.
  • The client does it without an account. They open the link, watch, and click approve — no sign-up, no install. Approval that’s harder than a WhatsApp reply won’t get used; this is easier.

Now “approved” is a fact, not a memory. Both of you can see exactly what was signed off and what wasn’t.

How to run reviews so they actually close

  • Send one review link per round, not a new file each time. Stack every cut under one link with new versions so “the latest” is never in doubt. The client always approves the top of the stack.
  • Ask for the action, not the opinion. End the handoff with “if this is good, hit Approve — if not, drop your notes on the frame.” You’re giving them a clear way to say done, and a clear way to say not yet.
  • Treat approval as the line for billing. Changes before approval are the round. Changes after approval are a new round. The recorded sign-off is what makes that line real and fair — put it in your rate note up front.
  • Keep the feedback on the frame too. When they request changes instead of approving, the notes come back pinned to the exact frame, so the next round is clean. This is the same client review flow, just with a proper end to it.

Sign-off shouldn’t need a per-seat plan

The catch with most review tools: approval and activity records sit on paid tiers, and they charge per seat on top — so getting a client and your team onto a tool that closes reviews properly means paying per person for it. For a solo editor charging â‚č per project, that maths rarely works, which is why so many stay on the WhatsApp thumbs-up and keep eating the extra rounds.

Editlock is priced on storage, not per seat and billed in â‚č — the whole team and every client reviewer are free, and approval, versioning and the activity record are just how it works, not an upsell. Closing a review cleanly costs you nothing extra.

Stop chasing a “looks good” you’ll have to defend later. Let the client approve the cut, on the record, in one click. See the plans — the free tier runs a full review-and-approve loop before you pay a rupee.

Get started

Bring your whole team. Pay for none of them.

Start free and run the full review flow — share a cut, collect frame-exact feedback, lock the final. Upgrade only when your library grows.

No credit card. Unlimited reviewers and clients on every plan.