Approve Extra Work Before the Tech Leaves

Extra work should be good news. The tech is already on site. The problem is visible. The customer already trusts you enough to let you in the door. Then the job stalls because nobody can get a yes in the next ten minutes.

That pause is expensive. The truck sits. The next stop slides. The extra work often never happens because the moment passed. A clear mid-job approval path turns found work into finished work instead of a parked van and a vague "we'll follow up."

Why extra work turns into a parked truck

Most service businesses treat extra work like a special event. The tech finds a second problem, calls the office, the office calls the customer, and everyone waits. If the customer is at work or in a meeting, that loop can eat 20 to 40 minutes.

The tech is not lazy. The process is. Nobody decided in advance who can approve what, how the price gets shown, or what happens if the customer does not answer. So the default is sit and hope.

Hope is not a dispatch plan. In a Tampa Bay summer, an HVAC tech waiting in a driveway is burning the coolest part of the afternoon on a job that may still end as a "maybe later."

What the mid-job approval loop actually looks like

Walk through a normal Tuesday. A cooling company in Brandon sends a tech for a no-cool call. The capacitor is shot. That repair is straightforward. While the panel is open, the tech sees a rusted disconnect and a drain line that is already sludged.

Now four people need to talk.

The tech needs a price and a green light.
The office needs the details and photos.
The owner wants to protect margin and the customer relationship.
The homeowner wants to know if this is urgent or optional.

If those four conversations happen by phone, the extra work becomes a project. The original repair gets done. The extra items land on a crumpled note. By Thursday there is no clean quote, and the competitor who texted a photo and a price range wins the next call.

The cost is bigger than one lost add-on

One stalled approval looks small. Across a week it is not. A crew that finds extra work on three jobs a day and converts none of it is leaving real revenue in the driveway. Worse, the schedule behind those jobs gets sloppy.

Late arrivals create reviews you cannot buy your way out of. Techs start skipping the extra inspection because "it just slows us down." You train the team to finish the ticket, not to finish the house.

A five-step rule that keeps the truck moving

You do not need a giant playbook. You need one rule the whole team can run without calling the owner every time.

Capture the finding in one place. Photo, short note, and the recommended next step. No group text thread.
Price from a short menu. Common add-ons get a range or a set price before the tech leaves the shop.
Send the ask to the customer immediately. Text or a simple approval link beats a voicemail.
Set a time box. If there is no answer in 15 minutes, finish the original job and book a return window.
Record the yes or no before the wheels move. Approved work stays on today's ticket. Declined work becomes a dated follow-up, not a memory.

That sequence is the difference between "we mentioned it" and "we either did it or scheduled it." Mentioning it is not a system.

What the customer needs in that moment

Customers rarely reject extra work because they enjoy broken equipment. They reject it because the ask is fuzzy. A phone call that starts with "so we found a few things" feels like an open tab. A short message with a photo, a plain-language risk, and a price range feels like a decision.

Keep the ask small and specific.

What you found, in one sentence.
What happens if they wait.
What it costs, or the range if parts vary.
How long it adds to today's visit.
A clear yes, no, or schedule-for-later choice.

Do not bury them in options. Two choices beat five. If the work is truly urgent, say why in plain words. "This drain is already backing up into the closet" is clearer than "we recommend addressing the condensate path."

Give techs a lane, not a lecture

Owners hang onto approvals because a bad quote can wipe out the job. That fear is fair. The fix is not to approve every washer by text. The fix is a lane.

Set three buckets before the week starts.

Do it now. Safety issues and cheap, obvious add-ons under a dollar cap the tech can sell from a card.
Ask and wait 15 minutes. Mid-size work with a photo and a set range.
Quote and return. Big replacements, insurance questions, or anything that needs the owner.

Write the dollar cap down. A $250 cap in writing beats a $0 cap that secretly becomes a 30-minute call on every job. Review the cap monthly. Raise it for techs who price cleanly. Lower it if quotes get sloppy.

How this looks on a real Tampa Bay job

Picture a landscaping crew in Pinellas County finishing a weekly maintenance stop. The lead notices an irrigation zone flooding the driveway. Old process: take a photo, text the owner, wait, leave a note on the invoice, hope someone calls Friday.

New process: the lead snaps two photos, picks "irrigation zone repair" from a short list, and sends the customer a message with a $180 to $260 range and a same-day add-on of 45 minutes. The customer taps yes while still at the office. The crew fixes the zone before they trailer out.

Same finding. Different system. One version creates a callback and a wet driveway. The other creates a paid hour and a customer who feels taken care of.

A quick diagnostic for your current process

If you are not sure whether mid-job approvals are leaking money, check last week's tickets against this list.

How many jobs had extra findings written in notes but not quoted?
How often did a tech wait more than 15 minutes for a yes or no?
How many "we'll follow up" items still have no date on the calendar?
Can a tech send a photo and a price without calling the owner?
Does the customer get a written record of what they approved?
When the customer says later, does a return visit get booked before the truck leaves?

Three or more weak answers means the problem is not "customers don't want extra work." The problem is that extra work has no path.

Some jobs still need the owner. A full system replacement or a tense customer should not close from a price card. Route those exceptions to a person. Route the common case to a simple flow so a $90 drain flush does not wait on a 2:15 p.m. text.

Mid-job approvals fail when the finding lives in someone's head and the price lives in someone else's pocket. Give the tech a way to capture the issue, show a clear price, and get a yes before the wheels turn. That can live on a better booking flow, a simple approval page, or a small internal tool that replaces the group chat. The format matters less than the rule: extra work gets a decision while you are still on site.