How to Write a Scope of Work That Protects You

A scope of work is your protection against scope creep. It's also your client's protection against being surprised.

Most agency scopes are vague. "Website design project" could mean anything. Smart scopes are specific.

Here's how to write one that protects you without feeling legalistic.

The Core Components

A good scope has five sections:

Objective - What are we doing?
Included Services - What's actually in scope?
Excluded Services - What's not included?
Timeline - When is everything happening?
Terms - How does this actually work?

That's it. One page. Clear. Specific.

Section 1: Objective

"The objective of this project is to design and develop a website for XYZ Company that showcases their services, attracts potential customers, and captures leads through a contact form."

Not: "Website design" This specifies what the website does.

Section 2: Included Services

Be extremely specific. Don't say "web design." Say what that means:

"Included Services:

Discovery call(s) with 2-3 stakeholders to understand goals, audience, and technical requirements
Competitive research and mood board creation
Information architecture and site map (up to 8 pages)
Three website design concepts
Design refinement based on client feedback (two revision rounds)
Mobile responsive design
Front-end development and technical setup
Basic SEO optimization (meta tags, page titles, sitemap)
Testing and quality assurance
Deployment and handoff

Deliverables:

Design files in Figma
Deployed website on client's hosting
Admin guide showing how to update content
Launch meeting to train client on basic maintenance"

This is crystal clear. No ambiguity.

Section 3: Excluded Services

List things you explicitly will NOT do:

"Excluded Services (not included, additional cost if requested):

Content writing or copyediting
Photography or videography
Custom illustrations
Complex custom functionality (forms, database, API integrations)
Ongoing support or maintenance
Logo design or brand identity
Email marketing setup
E-commerce functionality (shopping carts, payment processing)
Performance optimization beyond standard web practices
Third-party platform integrations

If you request any of these services, we'll provide a separate estimate for additional cost."

This is critical. Clients will request these. You have documentation ready.

Section 4: Timeline

"Project Timeline:

Week 1: Discovery and kickoff (your input required by [date])
Week 2: Competitive research and concepts (we'll share 3 options)
Week 3: Design refinement (you'll provide feedback by [date])
Week 4: Development and technical setup
Week 5: Testing and revisions (final feedback by [date])
Week 6: Launch and handoff

Key dates:

Kickoff: [date]
Design concepts ready: [date]
First revision due: [date]
Final launch: [date]

Important: Delays in client feedback will extend the timeline. We'll notify you if this happens."

This protects you from scope creep by setting clear boundaries on when things happen.

Section 5: Terms

This is the business part:

"Terms & Conditions:

Project Cost: $16,000

Payment Terms:

50% ($8,000) due upon project start
50% ($8,000) due upon project completion

Payment Method: Invoice via email. Accepted: credit card, bank transfer.

Revision Rounds: Your project price includes two rounds of feedback and revisions. Revisions beyond two rounds are billed at $150/hour.

Approval & Feedback: Please provide consolidated feedback (all changes in one message) to minimize back-and-forth. We'll implement feedback within 5 business days.

Change Requests: Requests outside the original scope will be documented and quoted separately. We can discuss timeline and cost adjustments.

Delays & Extensions: If client feedback is delayed, we'll extend the timeline. If external factors delay the project, we'll notify you.

Ownership: Upon final payment, you own all deliverables (website files, designs, etc.). You may use our design as a portfolio piece.

Confidentiality: We keep client information confidential. You agree the same for us.

Cancellation: If you cancel within 7 days of start, we'll refund 50% of deposit. After 7 days, fees are non-refundable."

This covers the business side clearly.

Example: A Full Scope Document

SCOPE OF WORK: Website Design & Development for [Client Name]

Objective

Design and develop a professional website that showcases [Company]'s services, attracts [target audience], and captures leads.

Included Services

Discovery and strategy call with key stakeholders
Competitive analysis and mood board development
Information architecture and site map (up to 8 pages)
Three website design concepts
Design refinement (two revision rounds)
Mobile responsive design
Front-end development
Basic SEO optimization
Testing and quality assurance
Deployment and client training

Excluded Services

Content writing
Photography or videography
Custom functionality or API integrations
Ongoing support or maintenance
Logo design or branding

Timeline

Week 1-2: Discovery and concepts Week 3: Design refinement Week 4: Development Week 5: Testing and revisions Week 6: Launch

Project Cost

Total: $16,000 Payment: 50% upfront ($8,000), 50% on completion ($8,000)

Terms

Revisions: Two rounds included. Additional revisions: $150/hour. Feedback: Please consolidate all feedback in one message.

Changes: Any out-of-scope requests will be quoted separately. Ownership: You own all deliverables upon final payment.

Clean. Professional. Clear. That's the goal.

How To Present The Scope

Send after the kickoff call:

"Hi [Client],

It was great talking with you about the project. Here's the scope we discussed:

[Scope document]

Please review and let me know if this aligns with our conversation. Once you confirm, we'll get started.

A few questions:

Does the timeline work for you?
Are there services listed under 'excluded' that you'd like to add?
Do the payment terms work?

Let me know and we'll be all set."

This gives them a chance to modify before you start. Much better than discovering disagreements mid-project.

FAQ

How detailed should exclusions be?

Detailed enough that a client can't claim confusion. If you exclude "logo design," a client might argue "I thought that was included in branding." Be specific: "Logo design and brand guidelines are not included."

Should I share the scope with the client before kickoff?

I recommend sending it after kickoff, not before. Kickoff is when you understand their needs.

Then you write the scope. Before kickoff, you're guessing.

Can the client modify the scope?

Yes. That's the point. Send it, they review, they say "I need X added." You quote X and add to scope. That's the process.

Should I use a contract or just a scope?

Use both. Scope is the "what." Contract is the "how and why" (payment, IP, liability). Many clients expect both.

What if the client rejects the scope?

That's useful information. "I thought you'd do content writing" reveals a mismatch.

You either add it to scope or walk away. Better to know now than halfway through.