Most disappointing consulting engagements fail before they start, at the point where nobody wrote down what the adviser was supposed to deliver. For an HVAC owner, the fix is a short written scope that answers eight questions. This guide walks through each one, with wording you can adapt, the warning signs of a weak scope and the way to close an engagement cleanly. It applies to any adviser you hire, including us.
Why a written scope matters more for advice than for installs
An install has a physical result you can inspect. Advice doesn't. When an owner pays for a new furnace, everyone can see whether it was installed. When an owner pays for "growth strategy", there is no equivalent inspection, so the scope document has to do that job.
A written scope protects both sides. It stops an adviser from drifting into work you didn't ask for, and it stops the owner from expecting results the engagement was never designed to produce. It also gives you something to measure at the end: did we get what the page said we would get?
The eight parts of a good scope
1. The question
Write the engagement's question in one sentence. "Help us grow" isn't a question. "Why did replacement revenue fall 18% last year while service calls held steady, and what should we change first?" is. If the adviser can't help you write this sentence, the engagement will wander.
2. The deliverables
List what you'll physically receive: a report, a plan, a scorecard, a set of call notes. Give each a rough size and a due date. "A written findings report of 15–25 pages, delivered in week four" is a deliverable. "Strategic insights" isn't.
3. The exclusions
An exclusions list says what the engagement won't do. For an HVAC advisory scope, typical exclusions are:
- running ads, building websites or managing social media
- hiring, firing or managing staff on your behalf
- technical, engineering, mechanical design, inspection or code-compliance work
- legal, tax, accounting or lending advice
Exclusions aren't a sign of an unhelpful adviser. They're a sign of an honest one.
4. The timeline
Give the start date, the end date and the rhythm of contact in between. For a project: weekly milestones. For a retainer: the monthly cycle and the notice period. Avoid starting an engagement in your peak heating or cooling weeks; the business will lose that fight every time.
5. The people
Name who does the work. If the person who sells the engagement isn't the person who delivers it, the scope should say so. If specialists or subcontractors may be involved, the scope should say who, for what, and that you'll agree to them in writing before they start.
6. Decision rights
This is the part most scopes miss. Advice should stay advice: the adviser recommends, and you decide. Write down which decisions stay with you (all of them, normally), what access the adviser has (read-only wherever possible) and who can approve spending. This prevents an adviser from quietly becoming an unpaid manager, or an expensive one.
7. The price and payment terms
State the fee, what it covers, when it is paid and which GST/HST rate applies. For a fixed-fee project, link payments to deliverables. For a monthly retainer, state the monthly amount and the notice period. Any additional costs, such as software the adviser recommends you buy, should be named or excluded.
8. The ending
Write down how the engagement ends and what happens to the work. You should own every report, plan and scorecard. Any accounts set up during the engagement should be in your company's name from the start. A close-out session, where the adviser hands the work back to your team, is worth asking for.
Sample scope wording with placeholders
Here is a short template you can adapt:
Question: Why has [metric] changed by [amount] at [Business name] since [date], and what should we change first? Deliverables: [Document] of about [length], delivered by [date]; [number] review calls. Excluded: [list of exclusions]. People: Led by [Adviser name]. Any other contributors to be agreed in writing in advance. Decisions: All decisions remain with [Owner name]. Access is read-only unless agreed in writing. Fee: [amount] plus GST/HST, paid [schedule]. Ending: Engagement ends on [date] or on delivery of the final report. All work product belongs to [Business name].
Red flags in a proposal
- No question, only activities. A list of tasks without a question means nobody will know when the job is done.
- Promises about results. Be wary of any adviser who promises a fixed number of leads, rankings or revenue. The Competition Bureau treats misleading performance claims seriously, and so should you.
- Account ownership left vague. If an ad account or website would be in the adviser's name, ask for that to change before you sign.
- Requests for passwords by email. Use proper user access with your own administrator in control.
- No ending. An engagement with no end date or notice period is a subscription, whatever it is called.
Data and privacy in an advisory engagement
Advisers often need customer data, such as job histories or call recordings. Canadian private-sector privacy law applies to that information. The Office of the Privacy Commissioner's summary explains which law applies where, including the provincial laws in Alberta, BC and Quebec. As a business practice, ask the adviser to work from exports with customer names removed where possible, and to state in the scope how data is stored and when it is deleted. Confirm the details with your own legal adviser.
A quick test before you sign
Read the scope once more and try to answer three questions without asking the adviser: what will I have in my hands at the end, on what date, and for what total fee? If any answer is unclear, ask for the wording to be tightened before you sign.
How we apply this to our own packages
Every proposal for our Business Diagnostic, 90-Day Growth Plan, Advisory Retainer and Marketing and Vendor Oversight packages follows these eight parts. If you'd like to see how that looks in practice, the pricing page lists what every quote includes, and the contact page explains how to ask for one.
Frequently asked questions
How long should a written scope be?
Usually two to four pages. Shorter than that and something important is missing; much longer and it is probably trying to cover too many projects at once.
Should an adviser ever start before the scope is signed?
A first conversation, yes. Paid work, no. If an adviser wants account access or data before you've agreed a scope, ask why.
What if the problem changes halfway through?
A good scope has a change clause: either side can propose a change in writing, and nothing new is billed until both agree. That keeps a shifting problem from turning into an open-ended bill.
Do I need a lawyer to review an advisory scope?
For large or long engagements, it is sensible to have your own lawyer read it. This guide covers what a scope should contain from a business point of view; it isn't legal advice.