How are the deliverables defined — specific, or vague?
The scope-of-work clause is where the contract says what you actually agreed to do, and vague deliverables are where scope creep begins. "Design a website" invites endless interpretation; "design and deliver a five-page marketing site with the pages, features, and layouts listed in Exhibit A" leaves far less room for a client to expect more than you priced. The tighter and more specific the description, the easier it is to point back to it when a request lands outside what was agreed. If the deliverables are described in a sentence, the scope is doing very little work.
Watch for: Deliverables described in broad, open-ended language ("all necessary work," "a complete solution") with no itemized list, exhibit, or specification defining exactly what you will produce.
Ask for: A specific, itemized description of the deliverables — ideally in an attached statement of work or exhibit — so both sides can point to exactly what was agreed.
Revisions — a set number, or unlimited?
Revisions are one of the most common ways a fixed-price project quietly becomes an open-ended one. A scope that promises "revisions until the client is happy" has no floor, and can turn a finished project into weeks of unpaid rework. Defining a set number of revision rounds — with anything beyond that billed separately — keeps the work bounded and gives you a clear line to hold. The exact number that is normal varies by trade and by the size of the job, so treat it as something to agree explicitly rather than leave to assumption.
Watch for: "Unlimited revisions," "revisions until satisfied," or silence on revisions entirely — any of which can leave you reworking the deliverable indefinitely at no extra pay.
Ask for: A defined number of revision rounds included in the fee, with additional rounds billed at a stated rate — so the scope of rework is agreed up front rather than negotiated after the fact.
Acceptance criteria — objective, or the client's "satisfaction"?
Acceptance is the moment the client agrees the work is done, and how it is defined decides how easily you can call a project finished. Objective criteria — the deliverable meets the specification, passes defined tests, or matches the agreed brief — give you a concrete standard to point to. Acceptance tied to the client's "satisfaction" or "sole discretion" is subjective, and can let a client withhold sign-off (and sometimes payment) simply by saying they are not happy, even when you met everything that was agreed. This clause often connects directly to when you get paid, so it is worth reading alongside the payment terms.
Watch for: Acceptance conditioned on the client's "satisfaction," "approval," or "sole discretion," rather than on the deliverable meeting a defined specification or brief.
Ask for: Acceptance measured against objective, written criteria — the deliverable meets the agreed specification — with a set review window after which the work is deemed accepted if no specific issues are raised.
Change orders — the process (and pay) for out-of-scope requests
Even a tightly defined scope will meet new requests, and a change-order clause is what turns "can you also just..." into agreed, paid work rather than free additions. A good process says that anything outside the defined deliverables requires a written change order specifying the extra work, the additional fee, and any timeline impact before you start it. Without that mechanism, out-of-scope requests tend to get absorbed into the original price, which is exactly how a profitable project becomes an unprofitable one. The clause protects both sides by making changes explicit instead of assumed.
Watch for: No change-order process at all, or language letting the client request additional work "within the general scope" without a corresponding adjustment to the fee or timeline.
Ask for: A written change-order process for anything outside the defined deliverables — capturing the added work, the extra fee, and any schedule change — that must be agreed before the additional work begins.
Does your scope actually say what "done" means?
Upload your agreement and Initialed flags vague deliverables, unlimited revisions, acceptance tied to the client's "satisfaction," or a missing change-order process — in about two minutes. Your first credit is free.
Review your contract freeFrequently asked
How do I prevent scope creep?
Scope creep is best prevented in the contract, before the work starts. Define the deliverables specifically — ideally in an itemized statement of work or exhibit — cap the number of revision rounds, tie acceptance to objective criteria rather than the client's "satisfaction," and include a written change-order process so out-of-scope requests come with extra pay and a timeline adjustment. Together these give you a clear line to point back to when a request drifts beyond what was agreed, which is what keeps a fixed-price project from quietly expanding.
How many revision rounds is normal?
There is no single fixed number — what counts as normal varies by trade, by the complexity of the work, and by how the project is priced. The more important point is that the number is defined at all: a set count of revision rounds included in the fee, with additional rounds billed separately, protects you far better than an open-ended promise of "revisions until satisfied." Agreeing the number explicitly up front, rather than leaving it to assumption, is what keeps rework from becoming unlimited.
What is a change order?
A change order is a written agreement to adjust the scope of a project after work has started — typically capturing the additional work requested, the extra fee for it, and any impact on the timeline. It exists so that out-of-scope requests become explicitly agreed, paid work rather than free additions absorbed into the original price. A scope-of-work clause that references a change-order process gives both sides a clear, documented way to handle the new requests that almost every project eventually produces.
Keep reading
All guides →Repairs, auto-renewal, uncapped rent, personal guaranties, and early-termination traps — what to watch for before you sign a lease.
The five clauses that decide whether a freelancer gets paid — scope, payment, IP, termination, and liability.
Comp and clawbacks, equity and vesting, IP assignment, non-competes, and arbitration — what to check before you accept a job offer.
Duration, geography, scope, and enforceability — how to read a non-compete before you sign (and why it varies so much by state).
Property, support, custody, and retirement — the terms in a divorce settlement that most often come back to bite.
The clauses that quietly decide what happens to a home, a business, or a career years from now — in plain English.
This guide is general information, not legal advice, and Initialed AI is not a law firm. How scope-of-work and acceptance terms are interpreted and enforced can vary by jurisdiction. For a large or high-stakes engagement, consult a qualified attorney before you sign.