Client changed their mind after approval: how to handle scope creep in 3D projects

Your client approved the 3D model last week. Today they want the handle moved, a second colour option and "just one more angle". When a client changes their mind after approval, that's scope creep, and in 3D work it's expensive: a small change to the geometry can mean new UVs, new textures, new renders and another review round.

This guide covers how to handle it without losing the client or working for free: what to agree before the work starts, how to reply when it happens, and how to price the change. It's written for 3D artists, visualisation studios and product designers, and it works whatever tools you use.

#Why does scope creep happen in 3D projects?

Most of the time it isn't bad faith. A few common causes:

• The client sees the product properly for the first time. A flat sketch and a 3D model you can turn round are different things. Seeing it "for real" prompts new ideas.
• Someone new joins. The person who approved isn't the person who signs the budget, or the marketing lead sees it a week later.
• "Approved" meant different things. You heard "final". They meant "fine for now".
• Nobody wrote down what was approved. Without a record of the exact version, a change and a correction look the same.

The last two are the ones you can fix, and they're cheaper to fix before the project starts than after.

#What should you do when the client changes their mind?

1. 1

   Don't answer straight away

   Read the request twice. Work out which parts are new and which, if any, are fixes for something you got wrong. Errors on your side are yours to fix at no charge; new ideas are not.

2. 2

   Check what was approved

   Find the exact version they signed off, the date and who approved it. Compare it with what they're asking for now. If the change contradicts an earlier instruction, note where that instruction came from.

3. 3

   Sort the request into three piles

   Corrections (your mistake), changes within the agreed revisions, and new work. Be honest about the first pile; it buys you goodwill for the third.

4. 4

   Estimate the knock-on work

   Moving a part might mean re-UVing, re-baking, re-rendering every angle and updating drawings. Clients rarely see that chain, so spell it out.

5. 5

   Reply with options, not a refusal

   Give a price and a time for the change, and say what happens to the delivery date. Offer a smaller version if the full change is costly.

6. 6

   Get a yes in writing before you start

   An email reply saying "yes, go ahead at that price" is enough for most small jobs. Then start a new version, so the approved one stays untouched.

#How do you reply to a client who wants changes after approval?

Keep it friendly, factual and short. You're not accusing them of anything; you're explaining that this is new work and what it costs. Wording you can adapt:

Hi Sam,

Thanks for the notes. Happy to make these changes.

For reference, v3 was approved on 14 October, so these count as a
new round rather than revisions. Here's what that involves:

- Moving the handle 20 mm back: remodel, new UVs, re-render of
  all 6 angles
- A second colour option: new material set, 6 more renders

That's [price] and adds [number] working days, so the new delivery
date would be [date]. If you'd prefer, I can do the handle change
alone for [smaller price].

Let me know which you'd like and I'll get started.

If part of the request is a genuine correction, say so first:

The logo position on the lid is my mistake, so I'll fix that at
no charge. The other two changes are new to this round; details below.

And if the client pushes back on paying, point to what was agreed rather than arguing about effort:

Our agreement includes two rounds of revisions before approval,
and v3 was signed off after round two. I'm glad to keep going;
this round is just charged separately, as set out in the quote.

#What should you agree before the project starts?

Most scope creep is settled at the quote stage. A short checklist for your quote or terms:

• What's included. Number of models, parts, colour options, render angles and their sizes. "Up to 6 renders at 3000 × 2000 px" is clearer than "a set of renders".
• How many revision rounds. For example, two rounds before approval. Define a round: one batch of feedback, answered in one go.
• What approval means. Approval of a version ends the revision rounds for it. Changes after that are a new piece of work, quoted separately.
• Who approves. Ask for the name of the person who can say yes, and send the approval request to them.
• How changes are priced. An hourly rate, or a fixed price per change agreed before work starts.
• What happens to the timeline. New work moves the delivery date.

Example: a product visualisation quote might say "Model and 6 renders, two rounds of revisions. Changes after approval are quoted separately at [rate]." One sentence like that saves a lot of awkward emails later.

#How do you price changes after approval?

There's no single right method, but these work well in practice:

• Price the chain, not the click. "Make it blue" might take a minute. Re-rendering twelve angles and checking them takes far longer. Quote the whole chain.
• Use a minimum charge. Small changes still mean opening the project, exporting and sending a new round. A minimum of an hour or half a day covers that.
• Batch small requests. Ask the client to collect changes into one round rather than sending them one by one.
• Offer a cheaper path. If a new colour only matters for the web shop, perhaps two renders are enough, not twelve.

#Keeping a clear record of what was approved with MeshMarkup

The hardest part of a scope conversation is often "what exactly did you approve?". MeshMarkup keeps that on the record. On the final round you send a Sign it off link (Solo plan and up). Your client sees an Approve button for that version, such as Approve v3, and it only goes through when no notes are OPEN or IN PROGRESS. The model's status becomes Approved, and the name the client typed and the date are recorded.

When the change request arrives, you don't overwrite anything. Click Upload v4 on the same model, and v3 stays as it was, with its own notes. Compare draws the approved version as a ghost behind the new one, so you can show exactly what moved. Click Report on the approved version and Save as PDF for a record of every note, reply and status, with Approved and the date. See versions and comparing and export a round as a PDF.

#Questions

#Should I ever make small changes after approval for free?

That's your call. Doing a quick fix as goodwill is fine, as long as you say it's a one-off: "Happy to do this one at no charge; further changes would be quoted." That keeps it from becoming the expected norm.

#What if the client says they never approved it?

Point to the record: the version, the date and who approved it. That's why it's worth asking for approval in a form that records all three, by email or a sign-off link, rather than "looks good" on a call.

#What counts as a correction and what counts as a change?

A correction fixes something that doesn't match the brief or an earlier instruction. A change asks for something the brief didn't include. If the brief was vague, meet halfway and tighten the next brief.

#Can I limit revision rounds without putting clients off?

Yes. Most clients like knowing what's included. Frame it as clarity: "two rounds included, more available at [rate]".