Protect Margin With a Written Job Scope

A job can look profitable on the calendar and still lose money in the driveway. The leak is rarely the original work. It is the extra request that never made it onto the ticket.

When the scope lives in a phone call and a memory, your crew does unpaid work and your office argues after the fact. A written job scope fixes both problems before the truck leaves.

Why extras sneak in on good jobs

Most homeowners are not trying to cheat you. They see a tech on site and add the next item on their list. A dripping hose bib. A noisy vent. A second bathroom they forgot to mention.

Your tech wants to be helpful. Saying no feels rude. Saying yes without a price feels faster than calling the office. Ten extra minutes turns into forty, and the original job rate no longer covers the day.

That pattern is expensive because it hides. The calendar still shows a completed job. The review may even be good. The margin is gone.

What a useful scope actually includes

A scope is not a legal novel. It is a short, shared picture of the work so the office, the tech, and the customer are looking at the same job.

Keep it to one page and make every line concrete.

• The problem in plain language, not a parts code
• The exact work included today
• What is clearly not included
• The price or price range for the listed work
• How extras will be quoted before they start
• The arrival window and who to text with changes

If a line cannot be checked off at the door, it does not belong on the page.

A Tampa HVAC job that looked fine on paper

A two-person cooling company in Brandon booked a no-cool call in Riverview. The ticket said “AC not cooling, check system, possible capacitor.” The homeowner had already approved a service fee plus parts if needed.

On site the unit needed a capacitor and a dirty filter. Easy win. Then the homeowner pointed to a second air handler in the bonus room. “While you are here, can you look at that one too? It has been weak all summer.”

The tech spent another 50 minutes on a second diagnosis, a clogged drain, and a parts run that was never on the original ticket. The office invoiced the first repair. The second visit became a courtesy. The morning job paid for itself. The extra hour did not.

The next week they added a three-line add-on block to every ticket: extra system, extra area, extra visit. The tech now texts a photo and a price before touching the second unit. Same helpful tone. Paid work instead of a free sequel.

A 6-point check before the truck rolls

Use this before dispatch. If any item is missing, the job is not ready.

1. Can the customer repeat the included work in one sentence?
2. Is the “not included” list written down, not implied?
3. Does the tech know the approved dollar cap without calling you?
4. Is there a clear rule for “while you are here” requests?
5. Does the ticket show photos or notes from the first call?
6. Does the customer know how they will approve extras on the spot?

If you cannot answer yes to all six, you are betting margin on memory.

How to handle extras without killing the relationship

Helpful and free are not the same thing. Train the script so it feels calm, not stiff.

A simple line works: “I can take care of that. It is outside today’s scope, so I will send a quick price before I start.” Then send the price by text with one photo. Wait for a yes.

Most customers agree when they see the number. The ones who do not were never going to pay you later anyway. You just found that out before you donated labor.

Write the extra on the same ticket. Do not open a second mental note. When the work is done, the invoice should match the last approved scope, not the conversation in the garage.

Where verbal scopes break first

Verbal scopes fail in the same three places, week after week.

First, the person who booked the job is not the person at the house. A spouse or property manager adds work the original caller never heard.

Second, the tech changes mid-route. The notes in a text thread do not travel cleanly. The new tech only knows the headline on the calendar.

Third, the job runs long and everyone is tired. Extras get done “real quick” so the crew can get to the next stop. That is how a $189 service call becomes a $189 service call plus an unpaid hour.

A written scope does not need fancy software to beat those three failure points. It needs to exist in one place both sides can see.

Start with one job type, not a new binder

Do not rebuild your whole operation this week. Pick the job that produces the most extras.

For many Tampa Bay shops that is a diagnostic call, a leak visit, or a “clean and check” that turns into repairs. Write one template for that job only. Use it for ten jobs. Count the extras that got priced instead of gifted.

If the template works, copy it to the next job type. If techs ignore it, the template is too long. Cut it until it fits on a phone screen.

The goal is not prettier paperwork. The goal is fewer surprises, cleaner invoices, and a crew that can say yes to extra work without giving it away.

When the scope, the booking details, and the approval trail live in one simple system, extras stop being a debate. Your website and booking flow collect the right details up front. Your techs see the same ticket in the field. Customers approve changes before the wrench turns. That is how a focused tool protects the margin you already earned on the original job.