Client Wants Changes After Final Photo Approval?

Why changes after final approval happen

Clients rarely reopen an approved gallery out of bad faith. The usual causes are ordinary: a new stakeholder saw the images for the first time, the brand team changed a colour, legal flagged a claim, or the client simply looked again at full size and noticed something.

Each cause calls for a different response, so name it before you quote anything.

The last two rows are why a clear record matters: it protects the client as much as you. If the note was on the approved round and you missed it, you fix it without a conversation.

It also helps to separate the request from the person making it. A creative director who says "can we warm this up?" two days after sign-off is usually not testing your boundaries; they are doing their job with new information. Treating the request as a normal event, with a normal process, keeps the tone professional and keeps you from taking it personally. The goal is a process that works the same way for every client, so that no single conversation has to carry the weight of a negotiation.

Define what 'final approval' means before the shoot

The cleanest defence is a definition written into the contract or the kickoff email: final approval is the client's written sign-off on a specific version of a specific set of frames. After it, requested changes are billable as new work at a stated rate.

Three clauses carry most of the weight:

• What counts as sign-off. A button press or a reply that says "approved", from the named decider, not a thumbs-up from someone copied on the thread.
• What stays free. Defects and unaddressed notes from the approved round. Say so explicitly; it reads as fair and costs you little.
• What is billable. Everything else, at an hourly rate or a per-image rate you state up front.

If you have not yet set the number of rounds, start with how many revision rounds a photo contract should include; a post-approval clause is the same idea applied after the last round closes.

Script the conversation

Reply quickly and in writing. A speedy, calm answer signals that the process is routine, not that you are annoyed. A workable script has four beats:

1. Acknowledge. "Thanks for flagging this. I can make that change."
2. Anchor to the record. "The set you approved on the 14th had this frame as it is now."
3. Quote. "Because this is outside the approved version, I'll treat it as a change order: 6 images, about 20 minutes each, so 2 hours at my hourly rate."
4. Ask for a yes. "Reply 'confirmed' and I'll start. Revised files in two working days."

Notice the script never says no. It says yes, with a price.

Price the change order with arithmetic you can show

Estimate per image, multiply by image count, and state the assumption. A hypothetical example, with every figure illustrative and not a benchmark:

• Client wants a background colour shifted in 12 images.
• You estimate 15 minutes per image: 12 × 15 min = 180 min = 3 hours.
• At an illustrative hourly rate of $80: 3 × $80 = $240.

Add a minimum, such as one hour, because opening files, exporting and re-delivering have a fixed cost regardless of how small the change looks. A change that takes five minutes of editing still takes real time to re-deliver and re-confirm.

Use your own measured edit times, not someone else's. If you have no data, time the next three changes you make and use the average.

Keep the paper trail in the review itself

The change order only works if you can prove which version was approved. Email attachments make that hard: the approved file is one of several with similar names. The fix is a review record in which each round is a numbered version and the approval is stamped against it. The same logic applies to your files; photo version control covers how to know which edit is current.

In Appruva, a share link shows the client the current version of each frame, and notes and markup are stored against the version they were written about. So when someone writes "can we change this?" after sign-off, you can point to the round that was approved and to what the client said on it. That is the anchor in step two of the script.

Whatever tool you use, the test is the same: can you answer "what exactly did they approve, and when?" in under a minute?

A change-order template you can paste

Keep the template short enough to read on a phone. Clients who see a wall of terms ask for a call; clients who see five lines reply "confirmed".

• Approved version: the set and round the client signed off, with the date.
• Requested change: one sentence per image or per group of images, in the client's own words where possible.
• Estimate: number of images, minutes per image, total hours, rate, total price.
• Delivery: the date the revised files arrive, counted from the client's confirmation, not from the request.
• What happens next: the revised files become a new version, and that version needs its own sign-off.

The last line matters more than it looks. A change order that ends in a new approval keeps the loop closed. Without it, the revised files drift into a second round of informal feedback, and you are back where you started with a different set of unbilled edits.

Send the template as a reply on the same thread as the request. A new thread splits the record, and the record is the point.

What to do when the client objects to paying

Some clients will push back: "I thought revisions were included." Resist the urge to defend. Instead, separate two questions: what did we agree, and what is fair?

Start with what was agreed. Quote the clause, or the kickoff email, in one sentence. Then offer a choice that keeps control with the client:

1. Proceed as quoted. They confirm, you deliver.
2. Reduce the scope. They pick the images that matter most, and the price falls with the count. This often resolves the objection on its own, because it forces a priority call the client had skipped.
3. Defer. The change goes into the next engagement or the next batch of work, at the same rate.

Reducing scope is the strongest of the three. A client who asked for changes to every frame often cares about two of them. Letting them choose shows you are working for their outcome, not for the invoice.

If the objection is really about a stakeholder who arrived late, the fix is upstream. Client keeps adding reviewers? covers naming one decider so that late opinions arrive before sign-off, not after it.

Fixing it upstream: fewer post-approval surprises

The cheapest change order is the one you never need. Most late changes trace back to a review round that was too easy to approve without looking, or approved by someone who could not speak for the whole client.

Four habits cut them down:

• Name the decider at kickoff. Sign-off from anyone else is a comment, not an approval.
• Ask for approval frame by frame on hero images. A blanket "looks great" on a gallery of two hundred is the approval most likely to be reopened.
• Show the images at the size they will be used. Problems found at full size after sign-off are usually problems nobody could see in a thumbnail.
• Put a date on approval. A request that says "approve by Friday, after which changes are billable" turns a vague closing into a decision point.

None of this removes the occasional late request. It moves most of them to a moment when changing is free, and leaves the rest for the change-order process above.

When to waive the fee

Not every change deserves an invoice. Waive deliberately, and say that you are doing so:

• A one-off, tiny change from a client who pays well and promptly.
• A change that makes your portfolio piece better.
• A mistake that is yours.

Write the waiver as "no charge this time" with the change-order language intact. That keeps the rule alive while the goodwill is real, and the client sees the value of what they received.

Never waive silently and repeatedly. Three silent freebies become the contract.