The Difference Between a Scope and a Promise
Why this matters
Two shops quote the same job. One writes what it will do. The other writes what the customer will get. Both are honest, both are competent, and only one of them has taken on every unknown in the building. The difference is a grammar problem with a money consequence: a scope is a list of your actions, and a promise is a claim about a result. The moment you write the result, you have agreed to be measured against a system you did not design, in a building you did not build, for a customer whose expectations you cannot see.
Neither form is wrong. Selling results is often the better business. But you have to know which one you just sold, because they fail in completely different ways.
Two sentences, two contracts
Scope form: replace the unit, connect it to the existing distribution, commission it to the manufacturer's start-up procedure, and verify operation at the equipment.
Promise form: make the back bedroom comfortable.
The scope form is satisfied when the listed operations are complete and correct. If the room is still uncomfortable, that is a new conversation about a different problem, and you can charge for investigating it.
The promise form is satisfied only when the room is comfortable. If your work is flawless and the room is still wrong because the duct serving it is undersized, you are not done. You did not undertake to install equipment. You undertook to deliver an outcome, and every unknown between your equipment and that outcome is now inside your price.
The test that separates them
Read the deliverable sentence and ask: can this be verified without the customer's opinion?
- "Static pressure measured at the values on the attached sheet" - verifiable. Scope.
- "Drain flows freely under a two-minute full-flow test" - verifiable. Scope with a stated acceptance test, which is the strongest form.
- "No more noise" - not verifiable. Promise, and an unbounded one.
- "System operates per the design intent" - not verifiable unless a design document is attached and named. Promise wearing a scope's clothes.
The third and fourth are the dangerous ones because they read like technical language. Anything that requires the customer to agree that it is good enough is a promise, however many nouns it uses.
Why the promise form is not just a mistake
Plenty of good shops sell promises deliberately, and they charge for it. A homeowner does not want a list of operations. They want the room to work. A shop that will stand behind the outcome can charge a premium over a shop that will only stand behind its actions, and on repeat residential work that premium is often the whole difference in margin.
What separates a profitable promise from a ruinous one is bounding. A promise can be bounded three ways, and a promise with none of the three is the ruinous kind:
- By condition. The outcome is promised provided a stated condition holds. "Provided the existing distribution to that room measures within the range on the attached sheet."
- By remedy. The outcome is promised, and if it is not achieved, the stated remedy is a defined action, not an open-ended obligation. Define the remedy narrowly and in writing.
- By investigation. The outcome is promised only after a paid investigation establishes it is achievable. This is the honest answer when you genuinely do not know, and it converts a bet into a service you get paid for.
Field key: how each form fails
| Scope form | Promise form | |
|---|---|---|
| Satisfied when | The listed operations are done and correct | The stated result exists |
| Who carries an unknown in the surrounding system | The customer, as new work | You |
| Typical dispute | "I thought that was included" | "It still does not work" |
| Strongest defence | The written list and a signed acceptance of the listed items | A pre-work measurement record showing the starting condition |
| What makes it profitable | Tight boundaries and a clean change process | A bounding condition and a defined remedy |
| Failure mode | Nickel-and-diming a customer through a series of small change items until they stop trusting you | Working unpaid until the result appears or the relationship ends |
Notice that the failure modes are opposites. Scope form fails by eroding trust in small increments. Promise form fails in one large uncompensated block. A shop that has been burned by one usually overcorrects into the other.
One condition, two jobs, opposite answers
Take a single sentence and run it against two real jobs. The sentence is a bounded promise: the treated area will meet the acceptance test on the attached sheet, provided the enclosure is intact at the points marked on the sheet. One gate, two outcomes.
Job one. Pre-work walk finds the enclosure intact at all 9 marked points. The photographs go on the sheet, the customer signs it, work proceeds. Post-work test fails at 2 of 9 points. Because the gate was checked and recorded as met, the failure is inside the promise: the shop returns, finds its own installation defect at one point and an under-sized component at the other, and fixes both at its own cost. That is 6.0 hours of unsold return time on a job that sold 22.0 hours, so about 27 percent of the sold hours came back as unpaid rework. Painful and correct. The shop promised the result, the gate held, the result did not appear, the shop owns it.
Job two. Same sentence, different building. Pre-work walk finds the enclosure compromised at 3 of 9 marked points, all three photographed and noted on the sheet before any work starts. The customer is told in writing, before the work is scheduled, that the promise cannot attach at those three points and is offered two paths: repair the enclosure first as a separate quoted item, or accept the work with the promise limited to the 6 intact points. They choose the limited promise and sign the sheet naming the three excluded points.
Post-work test fails at 2 points, and both are among the 3 excluded. The shop returns, confirms the failures are at excluded points, and quotes the enclosure repair as new work. No unpaid rework. The conversation is straightforward because the customer already saw the photographs of those three points before they spent a cent.
Same sentence, opposite outcomes, and the difference is entirely in what was recorded before the work started. Job two's shop did not have better luck. It had 9 photographs and a signature. The gate did the allocating, and the gate only worked because someone walked it and wrote down the answer while the evidence was still visible.
Read across the two jobs and the arithmetic is stark: job one absorbed 6.0 unsold hours out of 22.0 sold. Job two absorbed none and converted the same physical condition into a quoted item. Identical technical situation, identical promise language, and the whole difference sits in a pre-work record that took under an hour to produce.
Where shops get the grammar wrong without noticing
Three habits convert a scope into a promise by accident:
The reassuring sentence in the email. The quote is a clean scope. The follow-up email says "this will take care of that noise for you." That sentence is now part of what was represented, and in a dispute the customer will print it. Whatever you write in the quote, do not undo it in the thread.
The verbal walkthrough. Standing in the room saying "when we are done you will not have this problem" is a promise made by the person the customer trusts most. Train for this. The right phrasing names the action and the expected effect separately: "we are replacing the unit and rebalancing the two branches, which should reduce it noticeably, and if it does not, the next thing to look at is the return path."
The word "properly." "The system will operate properly" is a promise with no test, and it appears in an enormous number of otherwise careful scope lists. Cut it or attach a measurement.
What changes the answer
Commercial buyers with their own specification. When the customer supplies a performance specification, you are in promise form whether you like it or not, and the bounding has to come from your exceptions to their spec, taken at bid time. Exceptions taken after award are usually worthless.
Work required to satisfy a code official. If the deliverable is an approved inspection, that is a result, not an action list, and the authority having jurisdiction decides when it is met. Price the possibility of a re-inspection into the job rather than treating a correction notice as a change order, because the customer will not read it as one.
How to verify you got this right
Take your last three quotes and highlight every sentence describing an end state rather than an action. For each highlight, answer: what is the test, who runs it, and what happens if it fails? A highlight with no test is an unbounded promise, and you own every unknown behind it. Either add the test, add a condition, or rewrite the sentence as an action. Three quotes is enough to find the pattern, because the loose sentence is almost always the same sentence, copied forward for years.
References
- Contract interpretation, implied warranties and remedies vary by state and differ for consumer and commercial customers; have your own attorney review your standard scope language
- U.S. Small Business Administration (SBA), guidance on contracting for small businesses
- See related: What You Are Actually Promising When You Quote a Price; The Difference Between an Estimate, a Quote and a Contract; Negotiating Scope, Not Just Price