Skip to main content
Ambiguous

does declining extra scope put me in breach of contract?

It depends — but declining to do work that was never in your contract is almost never a breach; a breach is failing to deliver what you did agree to. The narrow risk is if the request actually falls inside your existing scope, or if your refusal blocks a deliverable you're still obligated to complete.

Why this answer

Breach has a specific meaning, and it's narrower than the anxiety around it suggests. You breach a contract by failing to perform an obligation the contract created — missing an agreed deliverable, blowing a committed deadline, or abandoning the work midway. Declining a request that sits outside the agreed scope isn't a failure to perform; there was no obligation to perform it in the first place. A client asking for more than you signed up for and a client being entitled to more than you signed up for are different things, and the contract decides which it is. The reason this feels ambiguous is that the line between 'inside scope' and 'outside scope' is exactly what's in dispute. If the added request is genuinely within what you agreed to deliver, refusing it could be a breach. If it's beyond the agreed deliverables, your 'no' is just a boundary, not a violation — and a well-drafted change-order clause usually anticipates precisely this situation.

When the answer flips

The breach risk becomes real in a few situations. First, if the 'added' work was actually inside your original scope and you've misread your own contract — then refusing it is declining an obligation, not extra work. Second, if your refusal stalls a deliverable you're still on the hook for: you can decline the new request, but you can't hold the agreed work hostage to it. Third, if your contract contains unusually broad language — an open-ended 'as needed' or 'reasonable requests' clause — the scope boundary may be fuzzier than you assume, and a wide reading could pull the request inside. It tilts firmly toward not-a-breach when the work clearly exceeds the named deliverables, when your change-order clause governs additions, and when you remain ready and willing to complete everything you actually committed to.

What to do next

Separate two questions and answer them in order. First, is the request inside or outside your agreed scope? Re-read the deliverables and scope-of-work language before responding, because the whole analysis hinges on it. If it's outside, you're not declining the contract — you're declining an addition, which you're entitled to do. Communicate it that way: 'That's outside what we scoped, so it's not part of this contract — but I'm happy to handle it as a change order at [fee].' This frames the no as a boundary plus an offer, not a refusal to work. Keep delivering everything you did agree to, on schedule, so there's no question you're performing the contract. Document the exchange in writing. If the client insists you're contractually owed the work and you genuinely disagree, point to the specific clause and, for anything high-stakes, get a lawyer's read rather than guessing — this page is orientation, not legal advice.

Settled reads your contract and gives you the exact verdict for this situation — try it free →

Frequently asked questions

Can a client sue me for refusing out-of-scope work?+

They can attempt to claim breach, but a claim isn't a win. If the work was genuinely outside your agreed deliverables, there was no obligation to perform it, so refusing it isn't a breach. The realistic risk is friction, a withheld final payment, or a sour reference — not a successful suit over work you never contracted to do. The strength of your position rests on how clearly your scope was defined. This is general information, not legal advice.

What actually counts as a breach of a freelance contract?+

Failing to deliver what you agreed to: missing an agreed deliverable, abandoning the project, blowing a committed deadline without cause, or violating a specific term like confidentiality. The common thread is non-performance of an actual obligation. Declining work that was never an obligation doesn't fit. The question is always whether the contract created a duty you then failed to meet.

What if I'm not sure whether the request is in scope or out?+

Resolve that before you respond, because everything turns on it. Re-read the deliverables and scope-of-work sections carefully and compare them to the actual request. If it's genuinely borderline, treat it as a conversation rather than a flat yes or no — acknowledge the ambiguity, propose a fair reading, and offer a change order if it lands outside. Guessing wrong in either direction creates problems, so do the reading first.

Can I refuse the new work but still be required to finish the original work?+

Yes, and you should. Declining an addition doesn't release you from the deliverables you committed to. You can't withhold the agreed work as leverage to force acceptance of the new request — that flips the breach risk onto you. Keep performing the original contract on schedule while you negotiate the extra separately. The two are independent: no to the addition, yes to the obligation.

Does a change-order clause protect me here?+

Strongly. A change-order clause anticipates exactly this — it states that work beyond the agreed scope is handled through a separate, priced agreement. That language converts 'will you do this extra thing' from a dispute into a defined process, and it makes clear that additions are optional and chargeable rather than implied. If your contracts don't have one, add it; it's one of the highest-value clauses for preventing scope arguments.

What if the client withholds final payment because I said no to extra work?+

That's a separate problem, and often the client is the one in the wrong. If you've delivered everything the contract requires, payment for that work is owed regardless of a declined addition. Document that the agreed deliverables are complete, invoke your payment terms, and keep the extra-work negotiation distinct from the money you're already owed. For meaningful sums, consult a lawyer rather than absorbing the loss — this is orientation, not legal advice.

Related reading

Answer scope creep from your actual contract — not a template.

Settled reads your contract and the client's request, gives you a verdict (In Scope / Out of Scope / Ambiguous), and drafts the email grounded in your specific clause.

Try it free →Read the scope creep guide