Summary

Most customer complaints about tradespeople aren't about poor work — they're about a gap between what the customer pictured and what was actually agreed. A customer who imagines "redecorate the bathroom" includes filling every hairline crack, re-grouting, and touching up the ceiling; the decorator who quoted "redecorate the bathroom" meant two coats of emulsion on the walls. Both parties are acting in good faith. The dispute exists because nobody wrote down where the line sat.

Setting expectations on scope means doing the work of imagining every reasonable misunderstanding before it happens, and closing each one off in the quote itself. This isn't about covering yourself with dense legal wording — an over-lawyered quote that a customer doesn't read is as useless as no quote at all. It's about a short, specific, plain-English description of exactly what's included, what's excluded, and what assumptions the price depends on, sent before work starts and confirmed in writing.

The commercial upside is real: a well-scoped quote reduces the two most common causes of margin loss on domestic jobs — unpaid extras ("well I assumed that was included") and time lost to disputes and re-negotiation mid-job. It also builds trust. Customers who receive a precise, professional scope document are more likely to book, less likely to haggle, and far less likely to leave a bad review over a misunderstanding that was actually preventable.

Key Facts

Quick Reference Table

Spending too long on quotes? squote turns a 2-minute voice recording into a professional quote.

Try squote free →
Scope element What to include Why it matters
Task description Specific actions (strip, prep, prime, 2 coats) not vague outcomes ("redecorate") Prevents "I assumed that was included"
Materials Brand/spec or "customer's choice up to £X allowance" Avoids disputes over quality expectations
Areas covered Named rooms/surfaces, explicitly excluding adjacent areas Stops scope drifting into unquoted spaces
Finish standard Number of coats, tolerance, standard referenced Removes subjective "is this good enough" arguments
Access assumptions Parking, working hours, keys, who's on site Protects against delay claims if conditions differ
Exclusions Named items NOT included (e.g. "excludes making good ceiling") The single most disputed omission in trade quotes
Provisional/PC sums Item, allowance amount, what changes the final figure Manages expectation that some prices are estimates
Programme/timeline Start date, expected duration, what could extend it See setting expectations on weather
Payment terms Deposit, stage payments, final balance trigger Separate from scope but always stated alongside it
Change process How extras get priced and agreed before starting Prevents disputed invoices for unagreed work

Detailed Guidance

Writing the scope so a non-expert understands it

Write for the customer, not for another tradesperson. "Prep and paint hallway, stairs and landing" tells a decorator what to do but tells the customer almost nothing about what they'll get. Better: "Fill and sand all cracks and nail holes, one mist coat and two topcoats of [paint type] to walls, one undercoat and one topcoat to woodwork (skirting, doors, frames), ceiling NOT included unless specified." Specificity here does two jobs at once — it sets the customer's expectation correctly, and it becomes the reference point if there's a dispute later.

Avoid subjective language that can't be measured: "tidy finish," "good standard," "as required." These phrases mean nothing in a dispute — a customer's idea of "tidy" and yours may be genuinely different, and neither of you is wrong, you just never agreed a definition. Replace with something checkable: number of coats, named standard, photograph of a sample finish, or a simple "snag list within 48 hours of completion, addressed within [X] days" clause.

Handling scope for jobs that can't be fully specified upfront

Some jobs genuinely can't be scoped in full detail before you start — you don't know what's behind that wall, under that floor, or in that loft until it's opened up. This is exactly what provisional sums and PC sums exist for. State clearly: "Making good to plaster behind removed radiator: provisional allowance £150, final cost confirmed once radiator removed and extent of damage visible." This tells the customer the number might move, sets a ceiling on their surprise, and gives you the contractual footing to invoice more if the reality is worse — provided you tell them and get agreement before doing the extra work.

Never leave an unknown unmentioned and hope it doesn't come up. If it does come up mid-job with no prior warning in the scope, the customer's default assumption — reasonably — is that it's included in the price you quoted.

What to exclude, explicitly

The exclusions section is where most disputes are prevented. Common gaps that cause arguments:

State each one as a short line: "Excludes: skip hire (customer to arrange or add £180), furniture removal (customer to clear room before start date), plumbing/electrical isolation if required (subcontracted, priced separately if needed)."

Confirming scope after a verbal conversation

Under s50 of the Consumer Rights Act 2015, a statement you make about the service — verbally, on the phone, in a WhatsApp message — can become a binding term of the contract if the customer relies on it when deciding to go ahead. This cuts both ways: it protects the customer from a trader who promises the earth and then quotes something smaller, but it also means a careless verbal aside ("yeah we'll sort the skirting too while we're there") can become a contractual obligation you didn't intend to make.

The fix is simple and takes two minutes: after any phone call or site visit where scope is discussed, send a short written recap the same day — email, text, or WhatsApp all count as "in writing" for this purpose. "Just to confirm what we discussed: [bullet list]. Let me know if I've got anything wrong before I send the formal quote." This closes the loop, corrects any misunderstanding immediately, and creates the paper trail that decides any later disagreement in your favour.

Scope and the written quote itself

The scope section belongs inside the formal written quote, not as a separate conversation. See written quote template for the full quote structure — scope of work sits alongside exclusions, provisional sums, and validity period as core sections. If the quote is accepted (signature, email reply, or deposit payment), the scope inside it becomes the contract. This is also why every material change to that scope after acceptance needs a variation order rather than a quiet adjustment — see variation orders and variation order template.

Frequently Asked Questions

The customer says "well I assumed X was included" — do I have to do it for free?

Not automatically. Check what was actually written in the accepted quote. If X isn't mentioned as included or excluded, you're in genuinely ambiguous territory, and a court applying the Consumer Rights Act would look at what a reasonable customer would have understood from the description given, industry norms, and any verbal representations made under s50. This is exactly why explicit exclusions matter — "assumed" disputes are almost always preventable with one more line in the original scope.

How detailed should the scope be for a small job (a day's work or less)?

Proportionate to the value and complexity, not a fixed rule. A same-day boiler service doesn't need a five-page scope document — a clear one-line description of what's checked/serviced, plus the standard terms, is enough. A £3,000 bathroom refit needs a proper itemised scope. The test: would a reasonable customer, reading only this document, know exactly what they're getting and what they're not?

Do I need the customer to sign the scope, or is a quote acceptance enough?

Formal signature isn't legally required for a binding contract — acceptance can be by email reply, verbal agreement followed by a deposit payment, or simply allowing you to start work after receiving the quote. What matters is evidence that the customer received and had the opportunity to read the scope before accepting. A signature or explicit "yes, go ahead" email is stronger evidence than an assumed acceptance, so it's worth asking for one even though it isn't strictly mandatory.

What if the site conditions turn out different from what I assumed when quoting?

This is exactly what the "assumptions" section of your scope protects against. If you stated "assumes standard access, existing wiring in serviceable condition" and it turns out the wiring is unsafe, you're entitled to raise a variation for the extra work — the original price was conditional on an assumption that turned out false. Without a stated assumption, you're on weaker ground arguing the extra work wasn't part of the original quote.

Regulations & Standards