Scope creep almost never starts with a dramatic ask. It starts with a small sentence on a Tuesday: “Oh, you’re handling the copy too, right?” A proposal assumptions section is what lets you answer that calmly instead of staring at your screen wondering how much of your life you just lost.
Most freelance proposals describe what’s getting built. Few describe what the price assumed. That gap is where scope creep lives, and an assumptions section closes it in about 200 words. Lawyers will roll their eyes at how informal this is. Lawyers don’t have to do your week 4.
What an assumptions section actually is
It’s a list of conditions you treated as true when you priced and scheduled the project. Five to ten bullets, plain English, no legalese.
Examples of things it covers:
- Who provides what (copy, images, access, approvals)
- How fast the client responds (3 business days is a common assumption)
- How many revision rounds are included
- The tools and platforms you’ll use
- The number of stakeholders giving feedback
- Working hours and timezone
- That brand assets exist in usable formats
If any of these turn out to be false, the proposal allows price and timeline to be adjusted. That’s the whole mechanism.
Why bury it in the proposal at all?
Because the alternative is having the conversation mid-project, when emotions are higher and one side already feels burned.
A clean proposal assumptions section means you get to say, in week 4, “Per assumption 3, copy was being supplied. Since we’re now writing it, here’s a change order for an extra $1,200 and 5 business days.” That sentence lands very differently when the client signed a doc with assumption 3 in it than when they didn’t.
What to actually list
Here’s a working starter list. Trim it to fit the project. Don’t ship a 30-bullet wall.
| Assumption | Why it matters |
|---|---|
| Client provides copy in editable format | Saves 4 to 10 hours of writing/cleanup |
| Up to 2 rounds of revisions per deliverable | Caps the rework spiral |
| Feedback consolidated from one point of contact | Prevents the 4-stakeholder email war |
| Client responds to questions within 3 business days | Protects your timeline |
| Brand assets (logo, fonts, colors) exist in vector/web formats | Avoids unbudgeted asset cleanup |
| Hosting, domain, and platform access provided by client | Keeps you out of their IT |
| Work performed in [your timezone] business hours | Sets sane communication expectations |
That’s seven. Most projects can live with five to ten.
The phrasing that doesn’t sound hostile
Tone matters here. The same bullet can read as “I trust you” or “I expect to sue you” depending on word choice.
Try framing the section with one sentence at the top:
The pricing and timeline below assume the following. If any of these change, we’ll adjust the scope, price, or timeline before doing extra work.
Then list the bullets in neutral language. “Client provides” instead of “Client must provide.” “Within 3 business days” instead of “Failure to respond within 3 business days will result in.” You’re describing a working arrangement, not threatening litigation.
Where the section sits
Order in the proposal matters more than people think. The flow that works:
- Cover note / context
- Goals or outcomes
- Scope and deliverables
- Assumptions
- Timeline
- Pricing
- Payment terms
- Acceptance
Assumptions sit between scope and price because the price is a direct function of the assumptions. Client reads what they’re getting, then the conditions, then the number. The number makes sense in that order.
If your tool puts pricing first by default, change the template. People glaze past anything after the dollar figure.
Assumptions vs exclusions vs scope
These get conflated. A clean separation:
- Scope: what you will deliver. Specific outputs.
- Assumptions: the conditions under which the scope and price hold.
- Exclusions: what is explicitly not included.
Example for a small website project:
- Scope: 5-page Webflow site, custom design, basic on-page SEO setup, launch support.
- Assumptions: copy provided by client, brand assets exist, one stakeholder approves, 2 revision rounds per page.
- Exclusions: copywriting, photography, ongoing maintenance, paid ad setup, email marketing integration.
Three short sections. Maybe 250 words total. They prevent thousands of dollars of scope-creep arguments.
What to do when an assumption breaks
It will happen. Plan the response in advance so you’re not improvising mid-deadline.
The script:
Hey [client], quick heads up. The proposal assumed [assumption X] but it looks like [what changed]. That puts us outside the original scope. Two options:
- We keep the original scope and you handle [the missing piece]
- I add a change order for [hours/cost] and we move the deadline by [X days]
Either works. Let me know by [date] so we don’t lose time.
Send it the day you notice. Not in week 3 of resentment. The assumptions section gave you the right to have this conversation, and the change order is how you act on it.
What not to put in the assumptions section
A few things belong elsewhere or nowhere:
- Payment terms, those go in their own section
- Liability caps and IP, those belong in the services agreement
- Vague threats (“Late feedback may incur penalties”), be specific or skip it
- Anything the client cannot actually verify or commit to at signature time
If you find yourself writing an assumption that’s really a hidden price, pull it into the pricing section as a line item instead.
The 5-minute audit for your current template
Open your most recent proposal. Run this check:
- Is there a section titled “Assumptions” or similar?
- Does it have 5 to 10 bullets in plain language?
- Does it sit before the price?
- Does it cover content, revisions, response time, and stakeholders?
- Does it include a sentence allowing scope/price adjustment if assumptions change?
If you missed three or more, the next proposal you send is leaking money. An assumptions section is one of the few template additions that pays for itself the first time it gets used.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
