Video Production Change Order: How Agencies Bill Late Client Requests
The cut is approved, then the client asks for a new scene, square versions and a restructure. Here is how I sort revisions from change orders, price the ripple and get a signed yes first.
The message usually lands a couple of days after the client has marked the cut as approved, right, and it opens with something warm like "loved it, just a few small things before we go live". Then the few small things turn out to be a new scene with the founder in it, square versions of every deliverable, and moving the pricing section to the very start of the film.
Every one of those asks is reasonable from where the client sits, and every one is work that was never in the quote. For years in my agency the pattern was that the producer said sure, the editor lost most of a week, and nobody wrote a video production change order, because sending one felt like picking a fight with a client who was paying us well. To be very honest, all of us knew the work was extra, and it still went out free, right, because nobody had a boring, pre-agreed piece of paper to send back.
So this is that piece of paper, for producers and production company owners sitting on a locked scope and an approved cut, covering where I draw the line, what goes in one, and how I price, send and track it so the approved version never depends on anyone's memory.
What a change order means in video production
Basically, a change order is a written amendment to the scope you already agreed, and the important word there is already, right, because it only makes sense when there is a signed statement of work or a proposal with a deliverable list underneath it. The contract says one 90-second hero film in 16:9, three 15-second vertical cutdowns, one shoot day and three rounds of revisions. The change order says here is what you are now asking for that isn't on that list, here is what it costs, here is how it moves the delivery date, and please sign before we start.
It matters more in video than in most services because a new ten-second scene can mean a pickup shoot, a grade match, a music re-cut and every cutdown from that section rebuilt, so our changes ripple in ways clients never see. Defining both terms in the contract is its own job, which I covered in what counts as a revision, so here I'm picking up once the project is live. The one contract line I'd still check is the change clause, because video production contract changes live or die on it. Mine says scope changes are quoted as a written change order at the scheduled day rate, and work starts only on signature, right, so nobody is surprised later.
Revision or change order: drawing the line on a live project
The test I use on a live project is two questions, asked in this order. First, could my team do this with the approved script, the footage already shot and the deliverable list in the contract? Second, does it reopen something the client has already approved? If the first answer is yes and the second is no, it's a revision and it counts against the rounds, and if either answer flips, it's a change order, however politely it was asked.
Let me run that message through the test. The client also noticed that the end card carries last year's logo, and that one is a revision, right, because the fix reopens no approved decision, so we fix it in the third round the contract still has left. The founder scene fails the first question straight away since the footage doesn't exist, and I've gone deeper on that headache in changing the script after filming. The square versions fail it too, because a 1:1 frame is a new deliverable where every shot gets reframed rather than just exported. Moving the pricing section passes the first question, since we have every clip we need, but it fails the second, because the structure was approved in MV2 and signed off again in MV3.
If the work fits the approved script, the footage already shot and the signed deliverable list, and reopens nothing already approved, it is a revision. If either condition fails, it is a change order.
So out of four small things in one friendly message, one is a revision and three are change orders, and I see that ratio really really often in my agency. That's why scope creep is so hard to catch on video projects, because it rarely arrives as one big request, it arrives as a bundle where the harmless item makes the expensive ones feel harmless too. Does that make sense, right, the size the client puts on a request has nothing to do with which bucket it lands in.
What to put in a video production change order
Write it for the person who wasn't on any of the calls, because at the end of the day that is who reads it, the client's finance person or the new marketing head who joined in month three, so keep it to one page that explains itself.
A simple change order template for video production
Mine open with the original agreement and its date plus the baseline version, then the request in the client's own words, copied from their timecoded comment so it's their wording rather than my summary of it. Then the work, written as deliverables rather than effort instead of something vague like additional editing, and then the ripple, right, which is the line people leave out and then regret, listing every other deliverable the change touches, the cutdowns, the captions file, the thumbnail frame and so on. After that comes the price, the new delivery date as an actual date, and how many rounds the new work includes, because otherwise the change order quietly becomes an unlimited round. The last line is the one I care about most, what happens if the client says no, which in mine is that MV3 ships as approved on the original date.
- Baseline version and its approval date
- The request quoted with its timecode
- New work written as deliverables
- Every deliverable the change ripples into
- Price, new delivery date and included rounds
- What ships if the client declines
Filled in for the founder scene, an illustrative version reads like this. Change order 1 against the 12 August agreement, with the hero film baseline at MV3, approved 8 September. The request is quoted from the comment at 00:00:42, a short piece with the founder just before the pricing section. The work is one new ten-second scene with a half-day pickup shoot, edit, grade match and music re-cut, rippling into the captions file and the thumbnail frame. The price is $400 plus the shoot at crew rate, delivery moves from 18 to 25 September, and one round of notes is included. If declined, MV3 ships on 18 September as approved.
Before sending I also check who signs it, right, because the person who left the comment often doesn't own the budget, and a yes from the coordinator is worth very very little when finance opens the invoice. So I address it to whoever signed the original agreement, and a written reply saying approved from them is enough for my agency.
Using the approved version as your baseline
The client swears the pricing came up in round one, the producer remembers a call where everyone agreed the story order, and the evidence is spread across an email thread, two WhatsApp groups and a Drive folder full of files called final_v3_REAL. Every change order argument I've seen go badly looked like that, two sides arguing from memory about a different approved cut.
Software teams solved this with version control, and the fix in video is the same idea, one place where every version lives in order and every approval is tied to a specific version. In PlayPause the versions stack on one card as MV1, MV2, MV3 and so on, and every note is a frame-accurate timestamped comment on the version it was left on. When the client signs off, I move the card to the Approved status we set up, with MV3 sitting on top of the stack, which is basically your baseline written into the tool instead of into somebody's inbox. The video approvals page and the client approval workflow walk through the mechanics, and my approval request email template is worded so the yes attaches to a named version.
the client remembers one approved cut, the producer remembers another, and the evidence is spread across five inboxes
the approved version, its timecoded notes and the new request all sit on one card in PlayPause
So when the request arrives I don't argue, right, I open the round one comments on MV1, where nobody asked for the pricing section to move, and on the Agency plan I put the approved MV3 next to the requested MV4 in side-by-side version compare, so the client watches the exact difference they're being asked to pay for.
Frame-accurate note, everyone sees the exact same thing.
Pricing and timeline impact of late client requests
I price the ripple rather than the request, and the catch here is that the client only ever sees the ten seconds on screen. In illustrative numbers you can swap for your own, say you bill an editor day at $400. The founder scene is about one day for the edit, grade match and music re-cut, so $400 plus a half-day pickup shoot at your crew rate. The restructure is a day on the hero film plus half a day rebuilding the three cutdowns that carried the pricing section, so $600. The square versions are four new deliverables at roughly a quarter day each to reframe, which is one more day and another $400.
That's $1,400 of post-production in illustrative terms plus a shoot, on a message that opened with just a few small things, and I'm pretty sure anyone who has eaten a request like this sensed it was that big. The timeline moves too, right, and the change order has to say so, because three and a half days of work plus a shoot you still need to book is at least a week on a real schedule. If the client needs the original date for a launch, I offer to ship the approved MV3 on that date and deliver MV4 a week later as a second version, and only if they want the full change on the original date does it become a rush, priced as one.
A revision fixes the film we agreed on, a change order builds a film we never agreed on, and the invoice should know the difference.
How to present a change order without souring the relationship
The moment a client reads out of scope they hear no, right, and they also hear that you've been counting, which is why opening with that word is the biggest mistake I see producers make. I reply the same day instead, before anyone touches the timeline, and lead with what they can have, something like happy to do all of this, the logo fix is in the current round, and the other three pieces are new work, so here's what they involve.
Then I give options rather than a single bill, because options keep the client in charge of the decision. Option one ships MV3 as approved on the original date, option two is the full change order with its price and new date, and option three is a trade, where they drop something still unbuilt, for instance one vertical cutdown, in exchange for the restructure so the budget stays flat. In my agency clients pick some mix of two and three far more often than they walk away.
I also log courtesy changes on the change order as $0 line items so the client sees the goodwill, and I cap them at one per project in our agency revision policy, because an uncapped courtesy is just scope creep with better manners. Done consistently, this is the most reliable way I've found to reduce revision rounds and keep out of scope video revisions from piling up, since clients who know extra work gets priced start batching their notes properly.
Tracking change orders alongside review status
What worries me on a live project is a polite comment on the review link, an editor who wants the client happy, and a producer who finds two unbilled days in the timeline weeks later, right, after the editor has quietly done the work. Trust me on any level, a separate spreadsheet won't stop that, the change order has to be visible where the review happens.
PlayPause lets me build custom statuses on every plan, so alongside In edit, Client review and Approved I add Change order pending and Change order approved, with one rule, nobody edits a card sitting in Change order pending. With the Slack integration every comment also posts to a channel, so the producer sees a late client change request the moment it's typed. Who-watched analytics show who opened the review link, when and from which city, which is useful context when the new marketing head asking for a restructure never opened it while MV2 and MV3 were being approved.
Link life matters too, because late requests like to arrive weeks after sign-off. A share link lasts 30 days on Creator, 90 days on Agency and never expires on Enterprise, so for client work I'd rather be on Agency, where the approved MV3 link still opens on day 40.
On Agency and up, each client's change order terms and courtesy cap live in that client's brand playbook inside Playbooks, since those are permanent rules, so any editor picking up that client sees them before touching a card. How all of this slots into intake, edit, review and delivery is in my post production workflow for agencies.
Frequently asked questions
Is a video production change order legally binding?
I'm not a lawyer, so this is an operator's view rather than legal advice. A change order is strongest when your original contract already says scope changes need a signed written amendment. Without that clause it's still a written record the client agreed to, which beats a verbal yes on a call, and for anything large I'd get the contract properly reviewed.
Do extra formats like square or vertical versions need a change order?
Only if they aren't on the signed deliverable list, because if they are, they're simply part of the job. If they aren't, every new frame shape means reframing each shot, rechecking where the text and captions sit and exporting a fresh master, which is real editor time. I quote formats per deliverable, so the client can pick the ones they'll actually post instead of ordering all of them by reflex.
What if the client refuses to sign the change order?
Then the approved version ships as agreed, which is exactly why every change order I send has the declined line in it. A refusal doesn't bother me much, right, because it just means the client decided the change wasn't worth the money or the delay, and that's a fair business call. I deliver MV3 on the original date and close the project cleanly, and the request often comes back later as a small new project.
Can I send a change order after the work is already done?
You can, but you're negotiating from a weaker spot, because the client never agreed a price and the work is already in front of them. When it has happened to me I've sent it anyway with a note that we should have flagged it first, usually at a discount, and then made sure a Change order pending status catches it next time.
If you want the approved version, the timecoded request and the change order status living on one card instead of across five inboxes, have a look at the plans on our PlayPause pricing page. Every one of them starts with a 7-day free trial, so you can run your next late request through it first.
So yeah. That's my way of saying it.
Saumyajit co-founded PlayPause after years watching review and approval quietly eat creative teams' deadlines. He writes about the workflow side of video, feedback, versioning, and getting to a clean sign-off.
Related resources
Keep reading
Bring your team into one review space
Centralize feedback, lock approvals, and deliver faster, start free today.
Sign Up for Free