What "As Needed" Actually Means in a Contract

You've seen the phrase. "Contractor will perform services as needed." Or "work as directed by client." Or "additional tasks reasonably related to the project."

Sounds flexible. It's actually a blank check.

When a contract says "as needed," that phrase has no ceiling. There's no definition of what "needed" means, no process for approving new work, and no mention of additional compensation. From a legal standpoint, your client can point to that phrase and argue that almost anything falls within the original scope.

The problem isn't that your client is malicious. It's that contracts with vague scope language create a structural incentive for scope creep. Every "quick addition" feels reasonable in isolation. Over a two-month engagement, those additions add up to a full extra week of work — work the contract technically authorized for free.

Courts interpret ambiguous contract language against the party who drafted it — usually the client. But that's cold comfort if you're in a dispute with someone you need a reference from.

The 3 Types of Scope Creep Clauses

Not all vague scope language looks the same. These are the three patterns to watch for.

Language like "all services required to complete the project" or "any work necessary to achieve client's business objectives." This is the most dangerous version. It ties your obligation to the client's goals rather than to a defined deliverable — and goals can expand indefinitely.

"Contractor shall perform work as directed by Client." This hands the client real-time authority to reassign your time. It's common in retainer agreements, where the assumption is ongoing flexible work — but without a cap, it has no logical limit.

"Contractor shall perform services and any reasonable additions thereto." The word "reasonable" sounds professional. It's actually doing the opposite — it creates a subjective standard that both parties will interpret differently. What's reasonable to a client on a deadline is different from what's reasonable to you at 11pm.

All three of these clauses appear in standard contract templates. They're often not red flags by intent — they're just badly drafted. But the effect is the same: unlimited liability for your time.

How Much Scope Creep Actually Costs

Let's put a number on it.

Say you're a freelance web developer. You sign a $6,000 project contract with a 6-week timeline. The contract says the project includes "website design and development as needed to meet client objectives."

Week two: the client asks for a new landing page. Reasonable. Week three: they want a blog section added. You say yes because the contract is ambiguous and you don't want conflict. Week four: can you redesign the footer to match the new brand direction? Week five: "while you're in there" can you hook up their email platform?

That's four additions. At your $100/hour rate, conservatively 15 hours of work. That's $1,500 in unpaid labor on a $6,000 project — a 25% haircut on your effective rate.

Multiplied across 4–6 projects a year, you're losing $6,000–$9,000 annually to scope language that takes 30 seconds to fix.

According to research on freelance payment practices, payment and scope disputes are the two most common sources of freelancer income loss. Scope is harder to see coming — which makes it more expensive.

The Change Order Clause That Fixes Everything

Here is the exact language to add to your contract. Three sentences:

"Any work requested by Client that falls outside the scope defined in this Agreement ('Additional Work') must be submitted in writing and approved by Contractor before work begins. Contractor will provide a written estimate for Additional Work, including timeline and cost. No Additional Work will be performed without a signed change order confirming scope, cost, and timeline."

That's it. Print it. Paste it into every contract you sign.

What this clause does: it creates a process. Anything outside the original deliverables goes through a written change order — which means a price, a timeline, and a signature. The client can still request changes. They just can't require you to do unpaid work.

A few things to note about this language. "Submitted in writing" means email counts — you don't need formal documents for every small change. "Signed change order" sets a clear bar that prevents verbal agreements from becoming scope additions. And "before work begins" is the critical phrase — it stops the pattern of completing work and then arguing about whether it was in scope.

If you've been seeing contract red flags in client agreements, vague scope language should be near the top of your watchlist. It often travels with other payment-side risks.

How to Negotiate This Before You Sign

Most clients will agree to a change order clause without any friction. They're not trying to steal your time — they just haven't thought about what happens when the project grows.

Here are three scripts depending on the situation.

"I work best with a clear process for scope changes so neither of us is surprised mid-project. I'd like to add a change order clause — anything outside the original scope gets a written estimate before I begin. Happy to share the language if that's helpful."

"I'm not trying to be rigid about changes — I expect projects to evolve. The change order process just makes sure we're aligned on what something costs before I do it, which protects both of us. I've had situations without this clause where a client and I disagreed about what was 'in scope,' and it wasn't fun for either party."

"I'm happy to get started. Before I do — can we agree by email that any work outside [list the deliverables] will be a separate line item? I'll send you language today."

The goal is to get something in writing before you start. Even an email thread where the client confirms "yes, changes outside X will be billed separately" is better than nothing. Tools like NovaDocs flag undefined scope language automatically, so if you're reviewing a client's contract and aren't sure whether the scope section is solid, run it through before you sign.

Reviewing clauses alongside the 12 most costly contract provisions gives you a full picture of where a contract exposes you financially — scope is one of the biggest, but not the only one.

FAQ

A scope of work clause defines exactly what services you're agreeing to provide under a contract — the specific deliverables, formats, rounds of revision, and any explicit exclusions. A good scope clause lists what's included and what's not. A bad one uses open-ended language that lets either party argue about what was meant after the fact.

If the contract language is vague enough — yes, technically. "As needed," "as directed," and "reasonable additions" are all phrases that could support a client's argument that extra work was part of the original agreement. The cleaner the scope definition, the less room there is for that argument. A change order clause removes the ambiguity entirely.

At minimum: that any work outside the defined scope must be requested in writing, that you will provide a written cost estimate, and that work will not begin until the client approves the estimate in writing. It doesn't need to be long — three sentences is enough. The important thing is that approval must happen before the work, not after.

If you have a detailed scope clause and a change order process, you point to the contract and ask them to show where the additional work was defined. If you don't have that language, you're in a he-said-she-said situation — and if the contract was drafted by the client, courts will often interpret ambiguity against the drafter, but that still means a dispute. The best outcome is to add the clause before you sign, not to win an argument after.

If a project is already underway, you can propose an amendment. Send the client an email: "I want to make sure we're aligned as this project evolves. I'd like to add a quick amendment confirming that any work outside [original deliverables] goes through a change order process. Here's the language — let me know if you'd like to adjust anything." Most clients will agree. If they won't, that tells you something important about how the rest of the project will go.