Scope of work template · Independent consultant
Consultant scope of work template
Write a tight SOW for a consulting engagement — included scope, exclusions, deliverables, acceptance criteria, milestones, change-request policy, and fees. Free PDF.
When to use this template
For any engagement longer than two weeks where deliverables and acceptance need to be written down. SOWs are typically attached to an MSA or a one-off engagement letter — they spell out the specific work that this engagement covers, while the MSA covers the legal terms that apply to every engagement.
What to include
- Engagement summary (one paragraph — what, for whom, why now)
- In-scope deliverables, specific enough to point at
- Out-of-scope items: the things you're explicitly not doing — usually where scope disagreements come from, so the more specific the better
- Acceptance criteria: what the client needs to see to sign off on each deliverable
- Milestones with target dates and dependencies
- Client responsibilities (decision-maker access, data access, internal SME time)
- Change request process — how scope changes are estimated and approved
- Fees and payment schedule (often tied to milestone acceptance)
- Confidentiality and IP terms (usually deferred to the MSA but worth noting)
Sample sections
Scope — included
Activities and deliverables covered by this SOW:
- Discovery interviews with 6 internal stakeholders + 8 customers
- Quantitative analysis of 18 months of usage and support data
- Synthesis into a written diagnostic + recommended operating model
- Two readouts: one to the working team, one to the executive sponsor
Scope — excluded
Explicitly outside this SOW:
- Implementation of the recommended changes
- Hiring or interviewing for new roles
- Vendor selection or RFP management
- Ongoing advisory or coaching after the final readout
Acceptance criteria
Each deliverable is accepted when:
- Diagnostic doc is reviewed by the executive sponsor and either signed off or returned with specific written comments within 5 business days
- Operating-model recommendation references all six functional areas covered in discovery
- Both readouts are delivered live, with deck circulated 24h in advance
Change request policy
Any change to scope, deliverables, timeline, or fees is captured in a written change request signed by both parties before work proceeds. Estimates for change requests include impact on timeline and fees and are valid for 10 business days from issue.
Example copy you can adapt
This SOW covers a six-week diagnostic engagement assessing Acme's customer support operating model, beginning May 20 and concluding with executive readout on July 1. Fees are quoted as a fixed engagement fee paid in three milestones tied to acceptance of each deliverable. This SOW is governed by the Master Services Agreement signed by Acme and [Consultant] dated [date], to which it is attached as Exhibit B.
Ready to create your scope of work?
Fill in the form, download a clean PDF — no signup, no email.
Open the scope of work generatorFrequently asked
- SOW versus contract versus engagement letter — which do I send?
- An SOW lists the work; a contract (or MSA) lists the legal terms. For a single one-off engagement with a client you'll never work with again, an engagement letter is often a combined SOW + light contract in one document. For repeat clients, sign an MSA once and attach an SOW per engagement.
- Hourly, daily, or fixed-fee?
- All three show up in consulting. Daily-rate engagements are common in senior consulting; the rate varies widely by niche, region, and experience, so treat any number you see online as illustrative rather than a benchmark. Fixed-fee tends to work when deliverables are clear (audits, diagnostics, training programs). Hourly is fine for advisory retainers and post-engagement support. Mixing models is normal — many SOWs use a fixed core fee plus an hourly bucket for change requests.
- What goes in 'client responsibilities'?
- Anything that, if it doesn't happen, blocks you. Common ones: a named project sponsor with decision authority, internal SME time (estimate hours per week), access to relevant data and systems, a single point of contact for scheduling. Be specific — 'client provides timely feedback' is too vague to enforce.
- Do I need acceptance criteria for every deliverable?
- Yes, if the client has any say in whether a deliverable is 'done.' Without explicit criteria, 'done' becomes whatever the client feels on the day of the readout. Acceptance criteria don't need to be elaborate — three crisp bullet points per deliverable is usually enough.