Clauses  ›  Scope of work

Scope of work.
The clause that draws the line.

What's included. What isn't. What a change costs. Without a concrete scope, every "quick ask" is technically in scope — because nothing defined it out.

Draft an agreement with a concrete scope

Free. No registration. No card. No catch.

In plain English.

A scope of work clause is the precise description of what the provider will deliver — and just as importantly, what is explicitly excluded. It's the contractual boundary between the project and everything else the client might want.

Plain English definition

The scope of work names the specific deliverables, tasks, and services covered by the contract — and lists what is explicitly excluded. Both lists matter. Without the exclusions list, clients assume everything not mentioned is included.

When you need it

Every service agreement needs one. If you provide a service — design, development, consulting, marketing, writing, construction — and you charge a fixed price or hourly rate for a defined project, the scope of work clause is the most important clause in the contract.

What happens without it

Without a concrete scope, the project boundary is determined by the client's expectations at any given moment. Those expectations expand. The contract provides no anchor, no "out of scope" line to point to, and no mechanism to price additional work fairly.

Vague scopes happen for concrete reasons.

Why missed

The project feels obvious

"A website" or "marketing strategy" sounds clear enough in conversation. Both parties think they understand. Both are imagining different things. The contract makes neither concrete.

Why missed

Listing exclusions feels rude

Writing "this does NOT include blog setup, e-commerce, or third-party integrations" feels defensive. It's not. It's the half of the clause that does most of the work.

Why missed

The scope changes during the project

The scope is vague at signing because the client doesn't know exactly what they want yet. The answer isn't to leave it vague — it's to define what's known and build a change order mechanism for what isn't.

The downstream consequences.

Scope creep at scale

A vague scope clause is the root cause of scope creep. Each small addition is defensible because nothing defined it out. The project doubles in scope at the same price.

Payment disputes

Client says the deliverable doesn't match what was agreed. You say it does. Without a specific scope, neither can prove it. The dispute often ends with you discounting or redoing work.

Deliverable disagreements

The client expected ten pages, you delivered five. Or the client expected mobile-optimized, you built desktop only. Concrete scope prevents the conversation entirely.

Change order friction

Without a defined baseline, every change order becomes a negotiation about whether the change is actually a change. Good scope clauses make change orders frictionless because the baseline is clear.

Scope language that sounds specific but isn't.

These phrases are in millions of contracts. Each leaves the scope boundary open to interpretation — and the client's interpretation will always be broader than yours.

Red flag

"A complete website"

Complete to whom? Defined how? Five pages or fifty? With or without e-commerce? Every word not written becomes an assumption — usually an expensive one.

Red flag

"Marketing support as required"

"As required" is an unlimited obligation. The client decides what's required. You absorb it.

Red flag

"All design work"

"All" is every designer's nightmare word in a scope clause. It means everything the client imagines falls inside the scope, no matter how it wasn't discussed.

Red flag

"Work described in our conversations"

Conversations expand. What was discussed in week one is not the same as what was discussed in week four. The scope must be fixed in the document, not floating in chat history.

Red flag

"Per client direction"

This transfers scope control to the client entirely. Whatever they direct is in scope. There is no limit.

The scope of work clause that holds the line.

A strong scope of work clause has two parts: an inclusion list and an exclusion list. The inclusion list names what's covered. The exclusion list names what's not — and that's the half that does the work in a dispute.

BizDraft builds scope of work clauses from your project description, with exclusion language calibrated to your industry's common scope-creep vectors.

The pattern

  • Be specific about deliverables. Not "a website" but "a five-page marketing site comprising: homepage, about page, services page, contact page, and a blog index. Each page built in Webflow to the provided brand guidelines."
  • List exclusions explicitly. "This scope excludes: blog post creation, e-commerce functionality, third-party API integrations, SEO services, or any pages beyond those listed above."
  • Define the change order mechanism. "Any work outside this scope requires a written change order signed by both parties before work begins, specifying additional fees and timeline."
  • Name the format and delivery method. "All deliverables will be delivered as Figma source files and exported PNG assets. Print-ready formats are not included."
  • Reference the deliverables clause. For complex projects, cross-reference the deliverables clause for acceptance criteria and sign-off procedures.

Agreement types where scope of work matters most.

Generate an agreement with a scope of work clause
that actually holds the line.

Free. Five minutes. Yours to keep.

Draft your agreement

Clauses that work alongside scope of work.

⚠ Legal disclaimer: Agreements generated by BizDraft are AI-produced for informational purposes only. They do not constitute legal advice and do not create an attorney-client relationship. For any agreement of significant legal or financial importance, consult a qualified attorney before signing.