How to Write a Scope of Work On Site

Why this matters

Most disputes at the end of a job are not about the price. They are about the scope: what the customer thought was included and what you thought you were doing. "I assumed that was part of it" is the sentence that eats your afternoon and your goodwill. A scope of work is the short written boundary of the job, agreed before you start. It is not the price sheet and it is not the diagnosis. It is the plain-language answer to one question: what will and will not be done today. Write it on site, in front of the customer, before tools commit.

Step 1: State the outcome, not just the task

A task list ("replace the part, tighten the fitting") tells the customer nothing about whether their problem gets solved. Lead with the result. "When we are done, the system will cool to the setpoint and hold it." "The leak at this joint will be stopped and tested dry." The outcome is what the customer is buying. Naming it sets the standard you will be held to, and it forces you to be honest about whether today's work actually delivers it.

Step 2: Write what is included, specifically

List the work in plain, specific terms. Not "service the unit," which means ten different things to ten customers, but the actual actions: what you will replace, adjust, clean, test, and leave working. Specific inclusions do two jobs at once. They tell the customer exactly what they get, and they draw the line that everything else falls outside of.

• Name the components you will work on.
• Name the tests you will run to prove it works.
• Name the cleanup and the haul-away if it is part of the job.

Step 3: Write what is NOT included

This is the step new techs skip, and it is where the disputes live. The exclusions matter more than the inclusions because they catch the customer's silent assumptions. Write the near-neighbors that a reasonable person might expect but you are not doing:

• Related items you found but are not fixing today.
• Anything the customer mentioned in passing but did not book.
• Pre-existing problems your work will not address.
• Cosmetic restoration (patching, painting, refinishing) if you are not doing it.

You are not being difficult. You are making sure the person who pays knows the edge of the job before it starts, not after.

Step 4: Name the conditions and assumptions

Your scope assumes the job is what it looks like from the outside. Write the conditions that would change it, so a surprise is a known possibility and not a broken promise:

• Access you are counting on (a panel that opens, a shutoff that works, a clear path).
• The assumption that the hidden parts match the visible ones.
• Anything that has to be true for the outcome to hold (correct supply, no unrelated fault upstream).

If a condition touches a real hazard, note the safe action tied to it: if you open the wall and find compromised wiring or active water intrusion, work stops and the scope changes before anyone proceeds.

Step 5: Write the path for "if we find more"

You cannot always see everything before you open it up. Rather than leave that gap to argument, write the rule now: if the work uncovers something outside this scope, you will stop, show the customer, and get a separate agreement before continuing. A customer who agreed to that path up front does not feel ambushed when you use it. This one line prevents the worst mid-job fight in the trade.

Step 6: Read it back and get the acknowledgment

Say the scope out loud, top to bottom, before tools come out. Watch the customer's face on the exclusions, because that is where a mismatch shows. Then get a clear acknowledgment, a signature or a recorded yes, that this is the job. The reading-back is not a formality. It is the last cheap moment to catch the gap between what they expect and what you plan to do, while fixing it still costs nothing.

The judgment to bank

A scope of work is cheap insurance written in plain language. The five minutes you spend drawing the boundary before the job is worth more than any argument you win after it. Inclusions tell them what they get; exclusions keep the job from growing without agreement.

References

• SBA guidance on service agreements, change orders, and managing customer expectations
• Trade-standard practice for on-site scoping and written work authorization
• See related: Presenting Repair vs Replace to a Customer; The Mid-Job Change-Order Price Conversation
• See related: How to Verify the Complaint Before You Start Work