ScopeSnap › Templates › Consulting
A consulting engagement rarely blows up in one meeting. It drifts. The operations review that was supposed to cover one warehouse quietly becomes three. The strategy deck grows a financial model nobody priced. The client's board wants a second presentation. Two more stakeholders join the interview list. Each ask sounds small, and without a written scope you have no clean way to say it costs extra.
This page shows you how to write a consulting scope of work before you quote. It lists what to include, the items clients most often assume are free, and how common pricing structures affect the number. There is a worked example for a typical engagement and a blank fill-in template you can copy into your proposal or email today.
Scoping a new consulting job right now?Paste the email or chat thread. One-page scope in under a minute. Free preview, then $19 for 10 scopes.
Scope my requestThese are the things consulting clients most often assume are included. Listing them up front is what keeps the project from growing after you've quoted.
This is the kind of request that usually lands in your inbox:
We're a 60-person manufacturing company and our ops are a mess: inventory in spreadsheets, jobs slipping, owner is the bottleneck on every decision. We want someone to come in, figure out what's broken, and recommend an ERP or whatever we need. Maybe help us hire an ops manager too. We did a strategy thing with a consultant 2 years ago and got a 60-page deck nobody read. How would you structure this?
And this is the one-page scope ScopeSnap produced from it, unedited:
You need a short, decision-focused diagnostic that pinpoints what is actually breaking, recommends a right-sized system, and gets the owner out of the daily critical path.
A six-week solo-consultant diagnostic at roughly 80–120 hours, driven mainly by on-site days, number of locations, and depth of the ERP shortlist.
Consulting work is usually priced one of five ways: a fixed fee for a defined deliverable set, an hourly rate, a day rate for on-site or workshop-heavy work, a monthly retainer for ongoing advice, or packaged offers such as a two-week diagnostic. The number goes up with the count of interviews and workshops, the number of business units or locations covered, the depth of data analysis, tight deadlines, and travel. Until you know how many people you will interview, what data exists, and who signs off, quote a range. Tie the final figure to the answers, and put those answers in the scope.
Copy this, fill in the brackets, and delete anything that doesn't apply.
PROJECT Client: [CLIENT NAME] | Consultant: [YOUR NAME] | Date: [DATE] | Version: [1.0] Engagement: [ENGAGEMENT TITLE, e.g. pricing review for the B2B product line] SUMMARY The goal is to [BUSINESS OUTCOME] by [WHAT YOU WILL ASSESS OR DESIGN] for [DEPARTMENT OR BUSINESS UNIT]. IN SCOPE Discovery: [NUMBER] stakeholder interviews of up to [LENGTH] each, [NUMBER] workshop(s) of up to [LENGTH], and review of [DATA SOURCES OR DOCUMENTS] supplied by the client Deliverable 1: [FINDINGS DECK, NUMBER OF SLIDES] in [FORMAT] Deliverable 2: [RECOMMENDATIONS MEMO OR ROADMAP] in [FORMAT] One [LENGTH] presentation of findings to [AUDIENCE] OUT OF SCOPE Implementation of recommendations, including [EXAMPLES, e.g. vendor selection, process rollout] Interviews, workshops or presentations beyond the counts listed above [OTHER EXCLUSION, e.g. editable financial models, data cleaning, staff training] ASSUMPTIONS Client data and documents are provided in [FORMAT] by [DATE] Stakeholders are available for interviews between [DATE] and [DATE] Work is [REMOTE / ON SITE]; on-site days beyond [NUMBER] are billed separately at [DAY RATE] CLIENT RESPONSIBILITIES Single point of contact and approver: [NAME, ROLE] Schedule interviews and grant [SYSTEM OR DATA] access within [NUMBER] business days of kickoff Return one consolidated set of feedback on each draft within [NUMBER] business days TIMELINE Kickoff: [DATE] | Discovery complete: [DATE] | Draft deliverables: [DATE] | Final delivery: [DATE] Dates move day for day if client inputs or feedback arrive late REVISIONS [NUMBER] round(s) of consolidated revisions per deliverable; further rounds billed at [RATE] A revision is a change within the agreed scope; new questions, data sets or audiences are a change order PRICE AND PAYMENT [FIXED FEE / DAY RATE / HOURLY RATE / RETAINER]: [AMOUNT], excluding [TAXES AND EXPENSES] [PERCENT]% due at signing, [PERCENT]% at draft delivery, [PERCENT]% at final delivery; payment terms net [NUMBER] days ACCEPTANCE Deliverables are accepted when [APPROVER NAME] confirms in writing or [NUMBER] business days pass without written comment Signed: [CLIENT NAME, DATE] / [CONSULTANT NAME, DATE]
Rather not fill in the blanks by hand?Paste the email or chat thread. One-page scope in under a minute. Free preview, then $19 for 10 scopes.
Scope my requestDetailed enough that a stranger could tell whether a request is in or out. Name each deliverable with a quantity and format. Count the interviews, workshops and presentations. State the revision rounds. One to two pages is normal for a project under three months. If you cannot write a line for something, you have not scoped it yet, and it belongs in your open questions before you quote.
Take a pricing review for a software company. In scope: eight customer interviews of 45 minutes, analysis of two years of deal data supplied as a spreadsheet, one 20-slide findings deck, one recommendations memo, one 60-minute presentation to the leadership team, two revision rounds. Out of scope: building the new price list, updating the website, training sales staff. Timeline: six weeks from kickoff. Fixed fee, half at signing, half at final delivery.
Do not say no and do not quietly absorb it. Say it sounds useful, point to the scope line it falls outside, and offer a short change order with the extra time, cost and any date shift. Send it in writing the same day. Most clients accept or drop the request once they see the trade-off. The scope only protects you if you use it the first time it is tested.
No. The scope describes the work: deliverables, counts, dates, price and acceptance. The contract covers the legal terms: confidentiality, intellectual property, liability, termination and payment disputes. Many freelancers attach the scope to a short master agreement so the legal terms are signed once and each new project only needs a new scope. If you have no contract yet, a signed scope with clear payment terms is far better than an email thread.