How to Deal With Scope Creep: Say Yes and Bill It

The request usually arrives at the end of something. The call is over, the agenda has been worked through, two people have already said goodbye, and somebody adds that while they have you, there is just one quick thing. It is phrased as a favour because it genuinely feels like one to the person asking. It is five minutes of their attention and, quite often, two working days of yours.

Almost nobody loses money on this by saying yes. They lose it by saying yes in a way that contains no price, no date and no record, and then finding out four weeks later that the job grew by a fifth while the invoice stayed the same size.

So this page is not about refusing. It is about the reply that keeps the same warm answer and makes the work billable, what each part of that reply is doing, and which sentence in your own contract it is leaning on.

The silence costs more than the task

Federal contracting has been running this exact problem for decades, on much larger amounts, and its solution is a clause that does nothing except require the contractor to speak up quickly. The Notification of Changes clause says that except for changes identified as such in writing and signed by the contracting officer, the contractor must give written notice, within a negotiated number of days, of any government conduct including actions, inactions, and written or oral communications that the contractor regards as a change to the contract.

Then it attaches a consequence worth reading twice, because it is the whole argument for answering the same afternoon. When the change is confirmed, the contractor gets an equitable adjustment in price, schedule, or both, except that the adjustment "shall not include increased costs or time extensions for delay resulting from the Contractor's failure to provide notice" (48 CFR 52.243-7(e)(2)). I pulled that clause text from the eCFR versioner API on 16 September 2026; the version in force dates from January 2017.

The policy section behind it is plainer still: when a contractor considers that the government has effected a change that has not been identified as such in writing and signed by the contracting officer, "it is necessary that the contractor notify the Government in writing as soon as possible" (48 CFR 43.104(a), read 16 September 2026).

None of this binds you. Unless you are working under a federal prime contract the FAR is not your law, and a client asking for a second thumbnail size is not a contracting officer. What it gives you is a well-tested shape for a document, written by the organisation that buys more services than anyone else on earth and has had every possible argument about what counts as extra. The shape says: the moment the request lands, the clock you care about is not the delivery date. It is the one on your own answer.

What your own paper already says about this

Before writing anything, find the clause you are about to rely on. In freelance and agency contracts it hides under one of five headings: Changes, Additional Services, Amendments, Revisions, or Assumptions and Exclusions. Most people have never read theirs.

AIGA's standard form is a useful reference point because it is public and widely copied. Its changes clause reads, in the blank-filled template:

Unless otherwise provided in the Proposal, and except as otherwise provided for herein, Client shall pay additional charges for changes requested by Client which are outside the scope of the Services on a time and materials basis, at Designer's standard hourly rate of ____ per hour. Such charges shall be in addition to all other amounts payable under the Proposal, despite any maximum budget, contract price or final price identified therein. Designer may extend or modify any delivery schedule or deadlines in the Proposal and Deliverables as may be required by such Changes.

(AIGA, Standard Form of Agreement for Design Services, 2022 update, clause 4.1, read 16 September 2026.) Three things are doing work in that paragraph, and they are the three things your reply will quote. Out-of-scope changes are chargeable. They are chargeable on top of the agreed price, whatever maximum the proposal names. And the delivery date moves if the change requires it.

The clause immediately after handles the big ask. Where changes amount to a revision in or near excess of a stated percentage of the time required to produce the deliverables, or of the value or scope of the services, the designer may submit a new and separate proposal, and "work shall not begin on the revised services until a fully signed revised Proposal" and any additional retainer are received (clause 4.2). AIGA's own commentary suggests filling those blanks with something like ten per cent of the original schedule or budget, or a fixed dollar amount such as $1,000, whichever is greater. Those are suggestions in a template rather than a standard, and the number you pick matters less than having one, because a threshold converts an argument about whether something is "big" into arithmetic.

State agencies write the same idea in simpler words. The model freelance contract published by the New York State Department of Labor, produced to meet the contract requirements of the Freelance Isn't Free Act, gives the client a fixed number of revisions within a stated window and then says plainly that "Additional revisions are subject to additional compensation" (NYS DOL, Freelance Worker Agreement, section 11, read 16 September 2026). Its section 17 carries the standard bar on informal changes: no change or modification is valid unless in writing and signed by the parties.

If you find nothing under any of those headings you are not without a position. You fall back on what the scope of work lists as deliverables, and on what it excludes. That is one reason a scope of work with an exclusions list is worth the twenty extra minutes at the start. Without one, every conversation about extra work begins with an argument about what "the job" meant.

The reply, in six moves

The federal clause happens to list the contents of a good notice, and the list maps onto a freelance email almost line for line. Here is each move, what it is for, and what goes wrong when it is missing.

One: agree to the work before you mention money. The first sentence should be an unqualified yes to the thing itself. Everything after it is administration. Reverse the order and a routine message reads as resistance.

Two: fix the date and the person. The federal notice has to state the date, nature and circumstances of the conduct regarded as a change, and the name and function of each individual involved (52.243-7(b)(1) and (b)(2)). In your version that is one clause: following your note on Tuesday afternoon. It is the least literary sentence in the email and the one that settles every later disagreement about sequence.

Three: describe it twice. Once in their words, once in deliverable terms. The federal version asks for the substance of any oral communication involved, because the request that causes the dispute is almost always the one that only ever existed as speech (b)(3). "A version for the German market" becomes "one additional landing page variant, German copy supplied by you, same layout, one round of amends". That translation is the part that stops the change from quietly doubling between the email and the delivery.

Four: say what it does to the rest of the job. This is the move that gets dropped, and it is the expensive one. The clause asks what labour has been added, and what delay and disruption in the manner and sequence of performance has been caused (b)(5)(ii) and (iii)). Freelance replies tend to name a fee and go silent on the calendar, which leaves the original deadline standing over a job that just got bigger. Write the date line even when the answer is that nothing moves. A sentence saying the delivery date is unchanged is a decision. Leaving it out is not.

Five: put a number on it, or a number about the number. Ideally the fee. Where the request is too vague to price, the federal notice accepts an estimate of the adjustments to price and schedule (b)(5)(iv)), and so should you: a not-to-exceed figure, or a rate plus an estimated range, counts as a price for this purpose. What does not count is "I'll let you know what it comes to".

Six: set a reply-by date and say what you are doing until then. The federal contractor states the time by which the government must respond to minimise cost and delay (b)(6)), and is separately told to keep performing the original contract in the meantime (52.243-7(c)). Both halves matter. Without a date, your email joins a queue. Without the second half, a client can read the message as a work stoppage over a small sum, which is a far larger conversation than the one you wanted.

One detail in that clause is worth borrowing precisely because it refuses to be helpful: the number of days allowed for the notice is printed as a blank marked "to be negotiated". The organisation with the most standardised procurement in the world declined to pick a universal number, so there is no point pretending one exists. Choose yours, put it in the scope of work, and then actually use it.

Three replies you can send today

These are written to be pasted and edited. The clause each one leans on is noted underneath.

A. The small ask, mid-project.

Yes, happy to do that. Just so the file stays straight: this one sits outside the deliverables in section 2 of the SOW dated 4 May, so it goes on as a change at my standard rate. Estimate is 3 hours, so $450, and it does not move the 19 September delivery. Send me a yes here and I will start it tomorrow morning; I am carrying on with the homepage build in the meantime. If you would rather hold it for phase two, that is fine too and costs nothing now.

Leaning on: the changes clause in your agreement (the AIGA analogue is 4.1), plus the exclusions list in your scope of work. The last sentence is the easy no, and it is the reason this email rarely causes friction.

B. The ask that lands after sign-off.

Happy to pick this up. One thing to flag first: the brand film was accepted on 2 September under section 6, which closed the two included revision rounds, so this comes in as new work rather than an amend. It is a re-edit at 30 seconds plus a new end card, 6 hours at $150, so $900, delivered five working days from your go-ahead. I will send a one-page change order for signature if that is easier for your AP team, and I will raise it as a separate invoice so it does not hold up the one already with you.

Leaning on: your acceptance clause and your revisions clause. The last line matters more than it looks. Keeping the new amount off an invoice already sitting in the client's system avoids the hold that a purchase order mismatch triggers, which is the mechanism described in the one-page change order.

C. The ask from somebody who did not sign anything.

Glad to help with this. Because it adds to the deliverables list, I need a yes from Priya as the named contact on the agreement before I start, so I have copied her here. For her: this is one extra social cutdown, 2 hours at $150, no change to the 19 September date. Priya, a reply to this email is enough.

Leaning on: the authority point below, plus whatever your contract says about notices. It is deliberately friendly to the person who asked, because they have done nothing wrong.

Who is actually allowed to ask

Government contracting solved this by naming names. Only contracting officers acting within the scope of their authority may execute contract modifications, and other government personnel must not execute modifications, act in a manner that causes the contractor to believe they have authority to bind the government, or "direct or encourage the contractor to perform work that should be the subject of a contract modification" (48 CFR 43.102(a), read 16 September 2026). The Notification of Changes clause then defines a Specifically Authorized Representative as a person the contracting officer has designated by written notice, with a copy provided to the contractor, issued before that person exercises any such authority (52.243-7(a)).

Translated into a freelance job, that becomes one line in the scope of work naming the person whose written yes counts. The New York State model contract reaches the same place from a different direction: its first section asks each side to name a contact person, a phone number and an email, and commits the hiring party to respond within three business days (NYS DOL, Freelance Worker Agreement, section 1, read 16 September 2026).

This is not bureaucracy for its own sake. Requests that turn into unpaid work overwhelmingly come from people who are not the signatory and who genuinely do not know what the contract covers: an intern with a good idea, a stakeholder who joined in week three, a founder copied on one thread. Naming the authorising person at the start makes the redirect later procedural instead of personal.

Pricing it without reopening the whole deal

Three structures cover nearly everything.

Time and materials is the default in most template clauses and the easiest to justify: a stated hourly or daily rate, an estimate, and a not-to-exceed ceiling so the client is not signing a blank cheque. Put the ceiling in. It costs you nothing and removes the main objection before it is raised.

A fixed fee per change suits repeatable asks such as an extra size, an extra cutdown or an extra language, and it approves faster because the client is agreeing to a number rather than to a method.

A new proposal is for anything past your substantive-change threshold. That is what AIGA's clause 4.2 exists for, and the reason is worth stating: a pile of change orders on a job that has fundamentally changed shape leaves the original acceptance criteria and the original assumptions applying to a different project.

Two smaller decisions are worth making once, in advance, rather than during each request. Set a minimum billing increment, commonly fifteen or thirty minutes, so genuinely tiny changes have a defined cost instead of an implied zero. And decide what you do with the free ones. Waiving a fee is perfectly reasonable; waiving it silently is what builds the expectation. One line, no charge on this one, noted for the record, does the goodwill and keeps the ledger honest.

When the answer comes back "the budget is fixed"

This is the standard reply, and it is usually sincere. The person saying it has a number in a spreadsheet and no authority to change it.

Notice first that the standard changes clause anticipates exactly this objection. AIGA's version says the additional charges are payable "despite any maximum budget, contract price or final price identified therein" (clause 4.1). The budget in the proposal is the price of the scope in the proposal. A fixed budget is not the same thing as a fixed scope, and once the second one moves the first one has stopped describing the same job.

The practical answer is almost never to fight over that sentence. It is the swap: something already in the scope of work comes out, the change goes in, and both halves are written down in the same message. That reply keeps the budget intact, which is the thing your contact is actually accountable for.

There is a separate squeeze that some states now address directly, and it should not be confused with this one. Under New York's Freelance Isn't Free Act, which added Article 44-A to the General Business Law with effect from 28 August 2024, once a freelance worker has begun performing the services the hiring party "shall not require as a condition of timely payment that the freelance worker accept less compensation than the amount of the contracted compensation" (N.Y. Gen. Bus. Law section 1411, read 16 September 2026; the Department of Labor publishes the model contract quoted above and directs complaints to the New York State Attorney General). That provision is about being asked to take less than what was agreed in order to get paid on time. It does not make your extra work billable, and quoting it at a client who is declining a change order would be both wrong and counterproductive. The thresholds, the double damages and the two overlapping New York regimes are set out in the New York Freelance Isn't Free Act. Illinois has its own written-contract statute, with a different threshold and a different agency.

Whether a written yes in an email thread is enough to amend a contract that says amendments must be signed is a genuine state-by-state question rather than a detail. New York General Obligations Law section 15-301(1) provides that a written agreement containing a provision that it cannot be changed orally cannot be changed by an executory agreement unless that agreement is in writing and signed by the party against whom enforcement of the change is sought. California approaches modification from a different starting point. The clause-level version of that difference, with the sections, is in the nine clauses that decide whether you get paid. Nothing here is legal advice and I am not a lawyer. Where real money turns on whether a thread amended your contract, that is a question for a lawyer in the state whose law your contract names.

The two sentences that do most of the work

Strip everything above and two sentences survive.

The first goes out within a few hours of the ask: happy to do that, it sits outside the deliverables in the SOW, here is the price and the effect on the date, send me a yes and I will start. The second goes into the scope of work before the job begins, naming who can authorise a change and what happens to the schedule when one is approved.

Everything else in a scope creep problem is downstream of those two. The federal machinery, the model contracts and the state statutes all arrive at the same unglamorous conclusion: the money is protected by the written answer, not by the quality of the work or the reasonableness of the person who asked.