Change-Order Approval Capture: Price the Extra Work and Get a Signed Yes Before the Tech Lifts a Finger

The problem this kills

The most expensive words in field service are "while we're here." The tech opens the wall, lifts the panel, pulls the unit — and finds rot, the wrong part, a code violation, or a customer who suddenly wants the extra outlet too. The honest move is to stop, price the extra work, and get a yes before continuing. What actually happens is the tech does the work, scribbles "added 2 hrs + parts" on the back of the ticket, and assumes the office will sort out the billing. The office can't. There's no price, no customer approval, and no proof anybody agreed to anything.

So the invoice goes out with a surprise on it, the customer disputes it, and you either eat the cost or burn a relationship fighting over it. Multiply that across every truck, every day, and unbilled or disputed change orders quietly become one of the biggest leaks in the whole operation. The root problem is that the moment a scope change happens — on the customer's property, with the customer standing right there — is exactly the moment you have zero tooling. The price book is in the office. The approval process is "trust me." The authorization is a memory.

This kills that. The instant scope changes, the tech captures it, the tool prices it from your real price book, a manager gives it a quick sanity check, and the customer signs on the device before a single extra screw goes in. No signature, no work. No surprise invoices, no disputes, no unpaid "while we're here."

What you'll build

A simple internal web app your field techs open on a phone or tablet. A tech picks the original job (which carries the customer, the site, and the existing quote total), describes the scope change — extra parts, added labor, an unforeseen condition — and adds line items. The tool prices each line from your price book and assembles a clean, numbered change order that shows the original total, the added amount, and the new revised total.

Before any customer sees a price, a manager reviews the draft — catching a fat-fingered quantity or a line that should've been warranty. Then the customer reviews the priced change order on the device and signs, and the tool captures the signature and timestamp as the authorization. Only then is the change order marked authorized, linked back to the work order with a revised total, and the tech is cleared to proceed. Authorized change orders export as a clean CSV in the exact columns your invoicing or ERP system expects.

What's inside the Implementation Plan

The downloadable plan is a step-by-step file you paste into an AI coding agent. It opens by interviewing you about your business — how your jobs and quotes are identified, how your price book is shaped (part numbers, labor rates, markups, tax), who's allowed to approve what dollar amount, how you number change orders, and the messy real-world cases (warranty vs billable, verbal-only approvals, a customer who wants the work but won't sign, multi-day jobs with several changes). It reads a short tailored spec back to you and waits for your thumbs-up before building anything — so the tool matches how your jobs and pricing actually work, not a generic template.

From there it walks the agent through the data model, the price-book lookup and pricing math, the change-order builder, the manager review gate, the on-device signature capture, linking the revised total back to the work order, and the CSV export. Every step ends with a ready-to-copy prompt. There's a full "No API yet?" path that uses Google Sheet / CSV imports for your jobs and price book and produces a clean CSV of authorized change orders — so you can build and run the whole thing this afternoon, even with no connection to your existing field-service or accounting system.

The governance it includes (this is the point)

A change order is a binding agreement to charge a customer more money, so the controls aren't optional. The plan builds in login so only your team can create change orders, row-level security so each branch or franchise sees only its own jobs and change orders, a complete audit trail of who logged, priced, reviewed, signed, and authorized every change and when, a hard human approval gate — manager review and a captured customer signature — before a change order is authorized and the tech proceeds, and duplicate guards keyed on (work order + change number) so the same change can't be logged or billed twice. Nothing is authorized on a memory; it's authorized on a signature with a timestamp.

Who it's for

Technicians, project coordinators, and service managers at any field-service operation where scope changes on site — HVAC, plumbing, electrical, restoration, remodeling, installs, commercial maintenance, property services. If you can describe your price book and who's allowed to approve a change, you can build this.

You've got this — start with the plan, paste the first prompt, and answer the interview. You'll be capturing a signed, priced yes before any extra work starts by the end of the afternoon.