Why change orders and final invoices leak money
Extra work is where good jobs lose margin. The crew finds rot under the old tub, a corroded shutoff or a duct that won’t reach. The homeowner asks for one more outlet while the electrician is there. Someone says “sure, we’ll take care of it,” and the work gets done.
Then the trail goes cold. The okay was a conversation in the driveway. The price was in a text to the estimator. The photos are on the crew lead’s phone. The office builds the final invoice from the original contract, because that is the only version in the system.
Money leaks at each of those steps. Work done without a written approval is hard to bill and easy to dispute. A signed change order that never reaches billing is free work. A final invoice that waits a week for paperwork is a week of your cash sitting with the customer. An invoice with no follow-up schedule ages until someone has time for an awkward call.
Example only: one forgotten $400 change order a month is $4,800 a year of work done for free. Your numbers will be different. The leak is usually small per job and steady over time, which is why nobody sees it.
The fix is a record that follows the change from the moment someone spots it to the moment it is paid.
Worked example: a fictional repipe with two changes
This job is fictional, and so are the prices. A plumbing company is doing a whole-house PEX repipe. The contract is $9,800 with a $2,000 deposit paid. The company uses a field service CRM for jobs and QuickBooks Online for accounting. Crews report from their phones.
Monday, 10:20 AM. The crew lead closes the main shutoff to start, and it won’t fully close. The valve is corroded and wasn’t in the scope. The crew lead takes two photos and opens a change order from the phone: “Replace main shutoff with a 1-inch full-port ball valve.”
Monday, 10:25 AM. The workflow attaches the photos to the job, creates CO-1 with the status “needs price” and notifies the estimator. The rest of the repipe keeps going.
Monday, 10:40 AM. The estimator prices CO-1 at $385 from the price book and approves the draft. The homeowner gets a text with the description, the photos, the price and a link to sign.
Monday, 10:58 AM. The homeowner signs on the phone. The record now shows who approved, how and when. The crew lead gets “CO-1 approved, go ahead.” A $385 line is added to the job’s billing list with the change order number.
Monday, 2:15 PM. The homeowner asks the crew lead about adding a hose bib on the back patio. The crew lead says the office will send a price and logs the request in the same form. CO-2 is created with the reason “customer request.”
Monday, 3:30 PM. The estimator prices CO-2 at $640 and sends it. The crew lead sees CO-2 as “awaiting approval,” which means don’t start it.
Tuesday, 8:00 AM. CO-2 is still unsigned. The homeowner gets one reminder, and the estimator gets a note. At 9:05 AM the homeowner signs. The crew installs the hose bib that afternoon and adds two photos of the finished work.
Wednesday, 3:40 PM. The crew marks the job complete with completion photos and the pressure test result. Before drafting the invoice, the workflow checks three things. Every approved change order has an invoice line. No change order is still open. Every change order has photos. All three pass.
Wednesday, 3:45 PM. The workflow drafts the final invoice: the $9,800 contract, CO-1 at $385 and CO-2 at $640, minus the $2,000 deposit, for a balance of $8,825. The office manager reviews it and sends it at 4:20 PM with a payment link.
Thursday, 9:10 AM. The homeowner texts: “What is the $385?” The office manager replies within minutes with the signed CO-1 and the photo of the corroded valve, both already on the invoice record.
The following Monday, 9:00 AM. The balance is still open, so the first scheduled reminder goes out. The homeowner pays by card that evening. The payment lands in QuickBooks, the job shows paid, reminders stop and a review request goes out the next day.
Nothing here needed a new idea. Each step put the same few facts in the same place, so the office never had to rebuild the story from texts.
Checklist: what a change order record needs
A change order is a small contract. Treat it like one. Whatever tool holds it, each record should answer these questions without anyone calling the crew.
The same list works in every trade. On a kitchen remodel it is the upgraded hinges or the moved outlet. On a roof it is the rotted decking found under the old shingles. On an HVAC change-out it is the new return the old ductwork couldn’t support.
- Job link: the job ID in your CRM, not only the customer name. One customer can have two jobs.
- Number and status: CO-1, CO-2 and so on, with a status like requested, priced, sent, approved, declined, invoiced or paid.
- Description: what is added, removed or changed, and where, in words the homeowner will still understand in a month.
- Reason: customer request, hidden condition, code requirement or design change.
- Price: the amount, how it was priced, and any credit for removed work. Note tax if it applies.
- Schedule impact: days added, if any, and whether the completion date moves.
- Who asked and who priced it: the crew lead, the homeowner, the estimator.
- Who approved: the customer’s name, and confirmation they can approve for the property, like both owners if your contract requires it.
- How and when: e-signature, signed paper or written reply, with the date and time. A verbal okay gets a written confirmation the same day.
- Photos: the condition that caused the change, and the finished work.
- Documents: the signed change order, plus any revised drawing or product sheet.
- Invoice line: the line on the progress or final invoice that bills it, with the change order number in the description.
- Payment status: due with the final invoice, billed now, or financed.
Failure modes and the check that catches each one
Each of these happens in good companies with honest people. A check turns a memory task into a routine one. Every alert should name the job, the change order and the person who fixes it.
Run each check against a few past jobs before you rely on it. Include a clean job too. A complete, correctly billed job should pass without a single alert.
- Work done on a verbal okay. Check: the crew sees “go” only after approval is recorded, and a daily check flags change-order work logged without one.
- Approved change never reaches the invoice. Check: before a final invoice is sent, compare approved change orders with invoice lines. A missing line blocks sending.
- Credit for removed work never applied. Check: the same comparison, run for change orders that reduce the price.
- Change order stuck waiting for a signature. Check: after 24 hours in “sent,” the customer gets one reminder and the estimator gets a note.
- Change attached to the wrong job. Check: match on job ID, not name. A customer with two jobs, or a property manager with ten addresses, goes to review when the match is unclear.
- The same change billed twice. Check: flag invoice lines that repeat a change order number or match another line’s amount and description.
- Job complete, no invoice. Check: if no invoice is drafted within one business day of completion, the office gets an alert.
- Invoice ages with no follow-up. Check: reminders on the schedule you set, and anything past the age you choose goes to a person.
- Reminder sent after payment. Check: confirm the balance in accounting right before each reminder goes out.
- Customer disputes a charge. Check: a dispute pauses reminders and goes to a person with the signed change order and photos attached.
- Supplier bill for change-order material arrives without a job. Check: match it by PO or job number, and send anything unmatched to a review list instead of the first similar address.
- A resent supplier email becomes a second bill. Check: keep the supplier invoice number and skip any bill already recorded.
What to automate and what to keep human
Automate the paperwork and the follow-through. Creating the draft change order from the crew’s report. Attaching photos to the job. Sending the approval request and one reminder. Comparing approved changes with the invoice. Drafting the final invoice when the job is marked complete. Sending payment reminders and stopping them when the balance hits zero.
Keep people on price and on anything that could damage the relationship. A person sets or approves every change order price. A person decides whether a hidden condition is billable or a cost of doing business. A person handles disputes, discounts and write-offs, and decides when a past-due account needs a phone call instead of another text.
Pick a threshold for a live conversation. For example, any change over $1,000, or any change that adds days, gets a call from the estimator before the signature request goes out. A link is fine for a $385 valve. It is a poor way to tell someone their project grew by a third.
Leave legal steps to people and professionals. Notice and lien rules vary by state. If late payments might lead there, ask your attorney what your process needs, and don’t let an automation send anything that reads like a legal demand.
Review drafted invoices by hand for at least the first month before any go out on their own. Many owners keep that review for good, and that is a reasonable choice.
How it looks in JobNimbus, Jobber, Housecall Pro, ServiceTitan and QuickBooks
Features differ by plan and change often. Check your account before building anything, and use what the tool already does well. Whatever tool you use, put the change order number on the invoice line. That one habit makes every bill traceable.
JobNimbus. Estimates, invoices and documents live on the job, and estimates can typically be signed electronically. Many teams write a change order as an additional estimate or document on the job; check whether your account has a dedicated change order type. QuickBooks sync is available on plans that include it.
Jobber. Clients can approve quotes online through the client hub. Extra work can go on the job as new line items or out as a separate quote for approval, and invoices are built from the job’s line items. Jobber syncs with QuickBooks Online. Check your plan for automatic invoice reminders.
Housecall Pro. Customers can approve estimates online, line items can be added to the job before invoicing, and invoices can carry an online payment link. QuickBooks sync and automatic invoice reminders are available on many plans. Check yours.
ServiceTitan. Extra work is often sold as another estimate on the same job, and sold items can be carried to the invoice. Accounting integrations, including QuickBooks on many setups, depend on your configuration. Confirm how your pricebook and invoice settings handle add-on work before building around it.
QuickBooks. This is usually where the invoice and payment end up. In QuickBooks Online, estimates can be turned into invoices, and some plans add projects and progress invoicing. Whether you track a change order as its own estimate or as a line on the final invoice, keep the job reference so the books and the job record agree.
If your field tool and QuickBooks both let people edit invoices, decide which one owns the invoice. With two editable copies, a correction made in one place leaves a wrong amount in the other.
What to measure each month
Take a baseline from your last 30 completed jobs, then check these monthly. The first number on the list should be zero. If it isn’t, that is money you can still collect.
Look at change orders by reason, too. If one trade keeps finding the same hidden condition, the estimate may need an allowance for it. Pricing it up front beats a surprise in the middle of the job.
- Approved change orders not yet on an invoice.
- Change-order work done before approval was recorded.
- Change orders created, approved and declined, and their total as a share of contract value by job type.
- Days from job complete to invoice sent.
- Days from invoice sent to paid, as a median.
- Open invoices by age: 0–30, 31–60, 61–90 and over 90 days.
- Disputed charges and the reason for each.
- Discounts and write-offs given to settle a dispute.
Build it or buy it off the shelf
Your field service tool or CRM probably already handles the change order document and the signature. Use that. Your accounting software already handles invoices and payments. Use that too.
An off-the-shelf billing or collections tool can be a good buy when your invoices already live cleanly in accounting. Its weak spot is the job. A tool that only sees accounting can’t know a change order was approved on site yesterday, or that the crew marked the job complete this afternoon.
A custom workflow makes sense when the gap runs between tools: crew report to office pricing, pricing to customer approval, approval to invoice, invoice to QuickBooks and payment back to the job. That path crosses three or four systems, and none of them owns all of it.
A custom app makes sense when the homeowner needs a better place to act. A portal where a remodel customer sees every change, approves it and pays is one example. Start with one screen.
Whatever you choose, start with one job type and one approval path. Run a few real past jobs through it on paper first. You will find the exceptions faster that way than from a diagram.
Where GoodHandoff fits
We connect the change order to the invoice and the invoice to the payment, inside the CRM and accounting tools you already use. A person still sets prices and handles disputes. See /services/change-orders-invoices for what it covers.
Workflow builds are $1,500–$5,000, depending on your accounting setup and payment methods. Custom apps, like a customer approval portal, are quoted to scope. Optional monthly plans are Care at $1,500 a month and Partner at $3,500 a month. A $500 assessment maps where your billing leaks, and the fee is credited toward the build. Pricing is at pricing.