How to Track Change Orders Without Losing Money

Sound Familiar?

Signs your change order tracking is leaking margin:

• You have verbal change orders you never got written up — but the sub already did the work
• You occasionally 'forget' to send change orders because the client relationship feels awkward
• Your change orders use old markup percentages from a different job's assumptions
• Approved change orders weren't connected to the job budget — so the budget stayed the same while scope grew
• You have a stack of change orders you never sent because the job was already over budget and you didn't want to add more
• You can't tell which active jobs have pending unapproved changes and which ones are clean

What We Found

The 4 Documentation Failures That Cost You the Most on Change Orders

Before building a tracking system, it helps to understand the specific failure modes. In change order tracking, there are four places builders consistently lose money:

1. Verbal agreements with no paper trail

This is the most expensive one. The client says "yes, add that" on a phone call. The sub does the work. Two weeks later the builder sends the change order and the client says "I thought that was included" or "I never agreed to pay extra for that." Without a documented confirmation — email, text, signed form — the builder has no leverage. Best case, they spend time negotiating. Worst case, they absorb the cost.

The rule: any scope addition discussed verbally gets a written confirmation within 24 hours. A simple email — "confirming our conversation about [specific scope change], I'll have a formal change order drafted for your approval" — creates a paper trail without being awkward.

2. Timing: documenting changes days or weeks after they happen

Change order documentation written after the fact is incomplete. When a change is documented immediately, the cost estimate reflects current conditions — current labor rates, current material quotes, current schedule impact. When it's documented later, nobody can reconstruct the actual cost. They estimate it, and estimates always favor the client, not the builder.

The fix isn't a perfect form — it's a habit. Every time someone on the job site does something different from the original scope, it gets documented in the daily log. That's the trigger. If it wasn't in the original scope and it took time or money, it becomes a change order candidate.

3. Pricing changes with wrong or absent markup

I've seen change orders priced at cost with no markup — "the client is already upset, I can't add profit on top." That logic loses money twice: once because the change order is unprofitable on its own, and twice because the client learns that pushing back on change orders gets them better pricing. Every change order is priced with full markup. Always.

The other pricing mistake is applying a blanket "15% admin fee" instead of the correct markup that covers overhead and profit. If your company needs 18% gross margin on a job and your direct costs are 72% of revenue, your markup is 38.9% — not 15%. Change orders priced at 15% are subsidized work.

4. Approved changes not connected to the job budget

The most financially invisible leak: an approved change order for $4,000 gets documented, signed, and filed — but JobTread's budget doesn't get updated. Now the job looks $4,000 under budget when it's actually exactly on budget. When the next change order comes in for $2,000, the builder thinks there's room to absorb it. They're wrong, but the budget report tells them they're right.

Every approved change order updates the budget in JobTread within 48 hours of approval. The budget is the live financial picture of the job. It can't be accurate if it's stale.

The Change Order Tracking System That Actually Works

The tracking system has three components that run in parallel: the log, the workflow, and the budget connection.

Component 1: The Change Order Log

A shared live document — Google Sheet, JobTread if it supports custom fields, or even a simple spreadsheet — that every active job's change orders run through. The log has one row per change order with columns for: CO number (sequential), date originated, date submitted to client, date approved, amount approved, status (pending/submitted/approved/declined), and budget updated (yes/no). The log is visible to the owner, PM, and office team. Every change order goes into the log the day it's originated.

Component 2: The Change Order Workflow

Every scope change follows the same workflow from origination to close-out:

• Day 0: Change is identified. PM or superintendent documents it in the daily log and emails the owner. If it's a verbal client request, a confirmation email goes to the client within 24 hours.
• Day 1-2: PM drafts the change order with line items for labor, materials, sub cost, and markup. If it's a schedule impact, that's documented too.
• Day 2-3: Owner reviews and approves the draft before it goes to the client. Owner signs off on pricing and language.
• Day 3-4: PM sends the formal change order to the client via JobTread or email with a specified approval deadline — typically 5 business days. PM follows up once if no response by day 3.
• Upon approval: PM updates the log, updates the budget in JobTread, and confirms in writing to the sub that the change is approved and work can proceed.

Component 3: The Budget Connection

This is the step that most builders skip and it's the most important one. When a change order is approved, two things happen within 48 hours:

• The approved amount gets added to the job's budget in JobTread as a separate line item
• The log is updated with the approval date and budget updated status

With the budget current, the owner always knows the real projected cost of the job — not the original estimate, but the actual scope the job will be built at. That's the number that matters for financial decisions mid-project.

The Financial Impact of Getting This Right

Industry research from construction financial consultants consistently finds that builders lose 8-15% of gross profit annually to what they call "unbilled scope changes" — work performed under verbal or informal agreements that never resulted in a change order. On a $3M company doing $2M in field work, that's $144,000-$300,000 per year. Most of it is recoverable with a tracking system that documents on the day it happens and connects to the budget.

The other financial impact is subtler but just as real: the builder who has a live budget can make good decisions about which jobs to push and which to pull back on. Without it, they find out a job lost money when it's already closed and there's nothing to do about it.

A change order tracking system isn't administrative overhead. It's the financial visibility tool that lets you manage margin while you can still do something about it.

Frequently Asked Questions