Scope of Work Template

Scope creep — the gradual expansion of project requirements beyond what was agreed — is the #1 source of unpaid work for freelancers. The solution is a detailed scope of work (SOW) that defines exactly what is and is not included in a project. The more specific your SOW, the better protected you are when a client says "can you just also add..." A good SOW is your professional record of what was agreed.

When to Use This Template

✓For any project that might expand beyond the initial brief
✓As an attachment to your contract, giving the contract legal specificity
✓When a client has a history of adding "small" requests
✓After a client asks for a change mid-project (create a Change Order based on this template)
✓For retainer agreements to define what the monthly deliverables are

What to Customize

→[PROJECT NAME] — specific project title
→[CLIENT] and [FREELANCER] — both parties' names
→[INCLUDED DELIVERABLES] — exhaustive list of what you will deliver
→[EXCLUDED ITEMS] — the "not in scope" list is as important as what's included
→[REVISION POLICY] — number of rounds and definition of a revision
→[APPROVAL PROCESS] — how and when the client formally approves work
→[CHANGE ORDER RATE] — your hourly rate for out-of-scope additions

The Template

Copy all text below

SCOPE OF WORK Project: [PROJECT NAME] Client: [CLIENT NAME / COMPANY] Freelancer: [YOUR NAME / BUSINESS] Date: [DATE] Version: 1.0 --- 1. PROJECT OVERVIEW [2-3 sentences summarizing the project goal and context. What are we building and why?] --- 2. INCLUDED DELIVERABLES The following are included in this project scope: Phase 1 — [PHASE NAME] □ [Deliverable 1 — be specific. "Homepage design" is not specific. "1 homepage design in Figma, responsive for desktop (1440px) and mobile (375px), including header, hero, 3 feature sections, and footer" is specific.] □ [Deliverable 2] □ [Deliverable 3] Phase 2 — [PHASE NAME] □ [Deliverable 1] □ [Deliverable 2] □ [Deliverable 3] Total page/asset/deliverable count: [NUMBER] --- 3. EXPLICITLY NOT INCLUDED (OUT OF SCOPE) The following are NOT included in this project and would require a separate Change Order: □ [Common expansion item — e.g., "Additional pages beyond those listed above"] □ [Common expansion item — e.g., "Copywriting or content creation (client provides all text)"] □ [Common expansion item — e.g., "Ongoing maintenance after project delivery"] □ [Common expansion item — e.g., "Social media graphics or marketing assets"] □ [Common expansion item — e.g., "Print or physical deliverables"] □ Any work not explicitly listed in Section 2 --- 4. REVISION POLICY This project includes [NUMBER] revision rounds per phase. A revision round is defined as: a single consolidated set of feedback submitted at one time via [email/shared document/etc.]. A revision round is NOT: ongoing drip feedback, redesigns based on change of direction, or feedback submitted in multiple batches. Additional revisions beyond those included will be billed at $[HOURLY RATE]/hour with a minimum of [1 HOUR] per revision session. --- 5. APPROVAL PROCESS Client agrees to provide written approval (email is acceptable) for each phase before work on the next phase begins. If Client does not provide feedback or approval within [NUMBER] business days of receiving work, the work will be considered approved and Freelancer will proceed to the next phase. --- 6. CLIENT RESPONSIBILITIES For this project to proceed on schedule, Client agrees to: □ Provide all required materials (content, assets, access credentials) by [DATE] □ Designate one primary point of contact for all feedback □ Provide consolidated feedback (not individual team member feedback delivered separately) □ Respond to approval requests within [NUMBER] business days Delays caused by Client will extend the project timeline accordingly. --- 7. CHANGE ORDER PROCESS Any additions to this scope require a written Change Order. Freelancer will provide a Change Order with estimated time and cost for Client's approval before proceeding with out-of-scope work. Verbal requests for additional work are not binding. Change Order rates: $[HOURLY RATE]/hour or flat project rate as agreed. --- 8. ACCEPTANCE By proceeding with project payment and/or signing this document, Client acknowledges that they have read and agree to this Scope of Work. Client: _________________________ Date: _______ [CLIENT NAME] Freelancer: _________________________ Date: _______ [YOUR NAME]

Select all text above and copy (Ctrl+A / Cmd+A, then Ctrl+C / Cmd+C)

Pro Tips for Using This Template

💡

The "not in scope" list is often more important than the "included" list — think about every way this project could expand and explicitly exclude those expansions

💡

Never start work without written approval on the SOW — "we talked about it" is not enforceable

💡

Add a "client responsibilities" section — missed deadlines from clients are the most common cause of project delays, and this clause gives you cover

💡

Update the SOW version number (v1.0, v1.1, v2.0) every time you make changes — this creates a clear audit trail

💡

For retainers, create a monthly SOW that defines what 10 hours per month actually includes

💡

The "approval within X business days" clause prevents clients from holding projects in limbo indefinitely

⚠️ Common Mistakes to Avoid

✗Assuming the client understands what's included — what seems obvious to you is not obvious to them
✗No explicit exclusions list — without "not included" language, clients assume everything is included
✗Soft revision language ("unlimited minor tweaks") — this is a scope creep guarantee
✗No client responsibility clause — makes it impossible to hold clients accountable for delays
✗Version 1.0 and never updating it — changes discussed verbally need to be captured in an updated SOW or change order

💰

Know What to Put in the Rate Fields

Templates protect you once you have a client. But first you need to know what rates to put in them. The FreelanceRateIQ guide shows you exactly what to charge — by niche, city, and experience level.

Get the Freelance Rate Guide — $27 →

Frequently Asked Questions

What's the difference between a scope of work and a contract?

A contract is the legal agreement covering general terms (payment, IP, dispute resolution, liability). A scope of work defines the specific deliverables and project parameters. They work together: the contract governs the relationship; the SOW governs the specific project. Many freelancers include the SOW as an exhibit to the contract.

How specific should deliverables be in a scope of work?

As specific as possible. Instead of "website design," write "8 responsive web pages designed in Figma including: homepage, about, services, 4 service sub-pages, contact. Each page includes desktop (1440px) and mobile (375px) designs. Final deliverables: Figma source file and exported assets." Specificity prevents disputes.

What is a change order?

A change order is a mini-contract for out-of-scope work. When a client requests something not in the original SOW, you write a change order that describes the addition, the cost, and the timeline impact. Client signs or approves it, you do the work, you invoice for it. Change orders protect you from doing unpaid work while keeping the project moving.

Should I charge for creating a scope of work?

For small projects (under $5,000), typically not — the SOW is part of project setup. For large, complex projects where scoping requires significant discovery work, a paid discovery/scoping phase (usually $500-$2,000) is common and professional. The paid discovery produces the SOW as a deliverable.

More Free Templates

Freelance Contract →Project Proposal →NDA Template →All templates →

Ready to set your rates? Use the free calculator.

Free freelance rate calculator →