Studio Queues Team · Last updated June 24, 2026
Learn how to define project scope at booking and handle mid-project requests without scope creep.
The client booked "a character portrait." Then asked "could you add a simple background." Then "could it be full body instead." Then "could you add these three other characters in the background, just real quick."
Each request sounded small. None of them came with extra payment. Together they're a completely different commission, twice the work, same price. You said yes to all of them because each one in isolation felt like too small a thing to charge for. You finish the piece resentful, take longer than you should have because the scope ballooned, and end up undercharging by half on what the work actually was.
The fix isn't being more aggressive about saying no. The fix is having one phrase that handles every "can you just" request the same way, defining scope at booking so it's referenceable, and knowing the difference between a revision (in scope, included) and an addition (out of scope, costs extra).
Scope creep almost never starts as bad-faith negotiation. Most clients aren't deliberately trying to get more work for less money. They have a vague idea of what they wanted at booking, they see the sketch, they realize what they actually want is slightly different or has additional elements, and they ask.
The artist agrees because:
None of these are unreasonable instincts. They're just the path to the resentful weekend.
The artists who handle scope creep well aren't more aggressive. They have a clearer structure that the answers fall out of automatically.
The first piece of the structure: scope has to be defined at booking, not implied. "Character portrait" is too vague. The actual scope needs to specify what's included.
The intake form is where this happens. A good intake form captures the project type, the subject, the references, and the deliverable specifications. The scope is the set of all of these together. When a request comes later, the question is whether it's covered by the scope or not.
The specific scope items that matter most:
Subject count. One character or multiple. If multiple, how many. If the booking is for one character and the client asks for a second mid-project, that's a separate commission, not a revision.
Composition complexity. Bust, half body, full body, or full scene. These are different products at different prices. Mid-project upgrades cost the price differential.
Background. Transparent or solid color is one thing. Simple background (gradient, abstract, single environment element) is another. Detailed background (rendered environment) is a third. The intake should specify which one is included.
Color treatment. Flat, cell-shaded, fully rendered. Different work, different price. Mid-project changes between treatments are scope changes.
Props or accessories. Weapons, accessories, complex outfit elements. Some are included in a standard commission, some are add-ons. Define which is which.
For each scope item, the intake records what the client agreed to. The scope is then referenceable later. "The original booking was for a one-character bust on a transparent background, color shaded" is a sentence you can produce. You couldn't if the booking was just "character portrait."
When a request comes mid-project that you suspect is out of scope, the response is one sentence:
"That's outside the original scope. I can quote it as an addition."
That's it. Two parts. The first half identifies the request as out of scope. The second half offers a solution (an additional quote) rather than just refusing.
This phrase works for almost every scope expansion request. The client asked for a background that wasn't in the booking. The client asked for an additional character. The client asked for a different composition. Same phrase, every time. The client either agrees to pay for the addition (which is fine, you make more money) or decides it wasn't important enough to pay for (which is fine, you do the original scope).
The crucial part: the phrase isn't a refusal. You're not saying no. You're saying it costs more. The client decides whether to pay. This shifts the framing from "the artist won't do this" to "the artist will do it for additional fee, the client decides if it's worth it."
The second piece of the structure: the explicit difference between a revision (included) and an addition (extra cost).
A revision is a change to something that's already in scope. The client doesn't like the pose, asks for a different one. They want the eye color changed. They want the hair shorter. These are changes within the scope you both agreed to. Revisions are included up to the number specified in your TOS (commonly two to three included revisions per commission).
An addition is a request for something that wasn't in the original scope. A background where none was specified. An additional character. A more complex composition. These are new work, not changes to existing work.
The mental test: does this request change what was already going to be in the piece, or does it add new elements? Changes to existing elements are revisions. New elements are additions.
The reason this distinction matters: revisions don't trigger the "outside the original scope" phrase. They're included, you do them, you move on. Additions do trigger the phrase. The phrase isn't for every request, just for the ones that genuinely expand what you're producing.
When a client asks for a change that's borderline (you can read it as a revision or as an addition), default to the more generous interpretation if you'd been planning to include it anyway, or use the phrase if it's a clear expansion. The borderline cases get easier to call with practice.
Sometimes a request is genuinely small and you'd rather just do it than negotiate. The client asks for a tiny background element, it'll take you 20 minutes, and the goodwill of doing it is worth more than 20 minutes of your time.
This is fine. Do it. The structure doesn't require you to charge for every micro-expansion. The structure requires you to know that you're choosing to do it without charging, rather than getting talked into it.
The risk to watch for: if you do this on every commission, clients learn that "small extras" are free and the requests escalate. The micro-expansion that was a goodwill gesture on commission #1 becomes the expectation on commission #5. The way to avoid this is to do it occasionally, not as a pattern, and to use the phrase consistently for anything that isn't trivial.
Sometimes the scope expansion isn't a single request but a slow drift over the project. By the time you notice, the work in front of you is so different from the original booking that "additional quote" doesn't quite cover it. The whole structure has changed.
In that case, the conversation is bigger. "The project has expanded significantly from the original booking, and I want to pause and renegotiate the total scope and price before continuing." This is harder than the phrase because it's not a single targeted answer, it's an honest acknowledgment that the project drifted and needs to be reset.
Most clients accept this if you say it early. They generally know the project has grown too. The conversation that doesn't go well is the one where you finish the expanded work at the original price, resent it, and never bring it up. The renegotiation is uncomfortable. The silent resentment is worse.
Most scope creep is prevented at the intake stage rather than fought mid-project.
A well-structured intake form locks the scope at booking. The click-to-accept TOS at submit records the client's agreement to the scope definitions (including the revision/addition distinction and the additions-cost-extra rule). When a scope question comes up later, the agreement isn't theoretical, it's recorded.
The click-to-accept TOS guide covers the agreement mechanics. The intake form guide covers the questions that capture scope. Both feed into the same protective layer: scope defined and agreed to at booking, with the records that make the agreement enforceable.
If you're not on a platform that handles this automatically, the manual setup is a clear scope description in your intake, a TOS that distinguishes revisions from additions, and a click-to-accept checkbox at submit. Studio Queues bundles all three into the standard intake by default, so the scope, the agreement, and the timestamp are recorded together at booking. The structure works either way, just with more pieces to maintain in the manual version.
Scope creep isn't a personality flaw, yours or the client's. It's a structural gap. The artist has a vague scope at booking, the client has a slightly different idea of what they wanted, the requests come, the artist says yes to each one in isolation, and the project ends up undercharged.
Close the gap at booking. Define scope. Distinguish revisions from additions in your TOS. Use the phrase consistently for any request that expands the work. Choose to be generous occasionally on small things, not as a pattern.
The phrase is the single piece of this article most worth memorizing. "That's outside the original scope. I can quote it as an addition." Practice saying it out loud. It will feel awkward the first three times. By the fifth time it's just a sentence you have ready, and the project doesn't drift.
