Build a clear change-order tracking process that connects scope, approval, job costs, billing, and cash for active construction projects.
Back to contractor finance →Why Change-Order Tracking Protects Job Margin
A change order is usually a business event before it becomes an accounting entry. Someone asks for a different finish, an unforeseen condition changes the work, a plan is revised, or a subcontractor discovers extra scope.
The field team has to decide what to do next while the office has to preserve the trail: what changed, who requested it, what it will cost, whether time moves, and whether the customer has agreed to pay.
Without a shared process, the work can happen before the price, approval, cost coding, and invoice catch up. That is how a contractor can complete real extra work while the job report still treats the cost as an unexplained overrun. The opposite error is just as dangerous: putting every requested change into projected revenue before approval makes a job look healthier than it is.
Construction contract rules vary by project, owner, and jurisdiction. Still, the core records are consistent. California's construction guidance, for example, calls for a clear description of the work, its location, time effect, and compensation method, while Texas guidance emphasizes approval before changed work begins except where documented verbal direction is permitted. Use your own contract as the final authority, and have counsel resolve a disputed or unclear clause.
The finance goal is simpler: give the business owner an honest view of the base contract, approved additions, pending exposure, change costs, billings, and cash timing. That view helps you protect margin while the job is active, not just explain it after closeout.
- CaptureRecord the request, source, scope, and affected job area.
- PriceBuild a cost and time view before treating it as revenue.
- AuthorizeStore the approval path and status required by the contract.
- Code and billTrack actual cost, invoice timing, and collection separately.
What Belongs in a Change-Order Log
A change-order log does not need to be fancy. It needs to be complete enough that a project manager, bookkeeper, and owner can open the same record and arrive at the same answer.
A spreadsheet can work for a small team if someone owns it and updates it promptly. Construction software can work well too, provided its approvals, cost codes, billing records, and accounting handoff are kept aligned.
Give every change a unique identifier. Do not rely on a supplier invoice description, a text message, or a verbal memory to identify it later. Then keep the original request and the decision trail with that identifier.
| Field | Why it matters | Example of a useful entry |
|---|---|---|
| Change ID and job | Keeps records, costs, and billing tied to one project event | Job 24-018, CO-07 |
| Requested by and date | Shows where the request began and how long it has waited | Owner request, May 12 |
| Scope and location | Prevents a vague label from hiding what was actually changed | Replace specified flooring in second-floor corridor |
| Status | Separates requested, priced, approved, directed, declined, and billed work | Priced, awaiting written approval |
| Price and cost basis | Supports margin review and commercial discussions | Lump sum based on labor, material, and subcontractor quote |
| Time impact | Prevents schedule exposure from disappearing behind the dollar amount | Three working days requested, pending approval |
| Cost codes and billing reference | Connects actual costs and the invoice to the same change | Finish carpentry, materials, invoice 1142 |
Attach supporting records where your process allows: marked plans, photos, emails, field notes, subcontractor quotes, supplier pricing, time records, and the signed form.
The log is the index. The source records are the support for what happened. Keep the description factual. "Customer requested additional cabinet run at west wall" is more useful than "extra kitchen work."
Most importantly, use statuses that mean something. A request, a proposal, a verbal direction, a signed approval, completed work, an issued invoice, and collected cash are different states. Combining them into one column called "change order" causes false confidence.
Use a status that the owner can trust
A Change-Order Workflow That Keeps Up With the Work
The best workflow follows the speed of the field without pretending that every urgent request is fully resolved.
Assign a clear owner for each handoff. On a small contractor team, that may be the owner or project manager. On a larger team, estimating, project management, operations, and accounting may each touch the record. The key is that no handoff becomes invisible.
- Capture the change when it is discovered. Record the request date, job, location, requester, and a factual description. Add photos or marked plans where they clarify the scope.
- Check the contract path. Identify the notice, approval, pricing, documentation, and time provisions that apply. If the record is unclear or the issue is disputed, get appropriate professional advice before treating it as settled.
- Build the price from the work. Separate expected labor hours, materials, equipment, subcontractor costs, permits, disposal, and any relevant overhead or markup approach used by the business. Do not copy a prior change price without checking current cost and scope.
- Get the required direction or approval. Store who authorized the work, the date, and what was agreed or deferred. A verbal instruction should not be allowed to vanish into a job note.
- Open the right cost buckets. Let payroll, purchase orders, supplier invoices, and subcontractor bills land against the change or a distinct phase where practical.
- Update the forecast and billing list. Approved value may affect revised contract value. Pending items belong in a separate risk view until the contract supports inclusion.
- Review until cash is collected. A signed change can still be unbilled, short-paid, disputed, or delayed. Keep the item open until the financial path is complete.
This workflow creates the same discipline that makes progress billing more dependable: the scope, supporting records, billable amount, and customer-facing documentation must agree before you expect cash.
Price the Change Without Hiding the Risk
Change pricing is not only a markup exercise. The number has to reflect what the contractor can support, the contract method, and what is known at the time. When the scope is incomplete, distinguish between a firm price, a unit-price extension, an allowance, a not-to-exceed amount, and work directed before final price. Your contract language controls the options available.
For management purposes, separate three numbers: the estimated cost to perform the change, the approved or requested selling price, and the actual cost as work proceeds. That comparison tells you whether the change itself is holding its margin. It also keeps a base-job overrun from being disguised as a change cost, or vice versa.
| Illustrative item | Expected cost | Approved price | Actual cost to date | What to review |
|---|---|---|---|---|
| Added millwork | $4,800 | $6,200 | $3,400 | Remaining labor, delivery, and installation risk |
| Unforeseen repair | $2,100 | Pending | $900 | Authorization and whether work can continue |
| Deleted scope | -$1,500 | -$2,000 | -$1,200 | Credits, restocking, and released labor |
These figures are illustrative, not a recommended pricing formula. A contractor should use the cost definition and margin approach that fits its business, trade, contract, and risk.
The important management habit is to update the expected cost when new facts arrive. A change that began with a sensible estimate can still lose money if supplier costs rise, labor takes longer, access changes, or rework appears.
For labor, compare actual crew hours to the allowance, not only payroll dollars. Our labor-cost guide explains why crew hours, burden, and productivity need to tell the same story. For materials, retain quotes, receipts, returns, and credits so the actual change cost is not overstated or understated.
Connect Approved Changes to Job Costs and Billing
Once work is authorized, the finance system needs a clean connection between the field record and the books. If the job-cost report shows only a single project total, it cannot answer whether the original estimate missed the work or whether a separate approved change performed poorly.
Create a change-specific phase, cost code, or tracking tag where the system can support it. At minimum, retain the change ID on the invoice, supplier documentation, and project file.
Keep the original contract value, approved changes, pending changes, and revised forecast visible as separate lines. The revised contract value should only include items that meet the business's policy and contractual support for recognition. A bookkeeper should not be asked to infer approval from an invoice or a project manager's note.
Then link the approved value to the billing schedule. Some projects bill changes on the next progress application. Others need a separate invoice, a specific owner form, backup documents, or a period of review before billing.
A delay between approval and billing can create a cash squeeze even when the change is profitable. Use the same cash-flow forecast discipline for changes that you use for base contract billings.
Weekly Review and Closeout
A short weekly change-order review is more useful than a frantic cleanup at the end of a job. Review every open item with the people who can move it forward. Sort by dollar exposure, age, work already performed, schedule impact, and billing status. An old $500 request may matter less than a $25,000 directed change with no final price and several weeks of labor already spent.
- Open exposure: Which requested or priced changes have work underway without final approval?
- Forecast: Which approved changes need an updated cost to finish or time view?
- Billing: Which approved changes are missing from the next invoice or payment application?
- Collections: Which billed changes are past the expected payment date?
- Closeout: Which completed changes need final cost review, documentation, or a lesson for the next estimate?
At project closeout, reconcile the log against the executed documents, job-cost report, customer billings, and cash received. Look for:
- Items marked approved that were never invoiced.
- Invoices without clear support.
- Costs posted to the base job that belong to a change.
- Credits that were not reflected.
This is also the right time to feed lessons into estimating. If the same scope change appears on several projects, decide whether the original scope, customer communication, allowance, or estimating assumptions need work.
Clear change-order tracking is not paperwork for its own sake. It gives contractors a more reliable line from a field decision to job margin, billing, and cash. When that line is visible, business owners can act while there is still time to protect the job.
Need a clearer job-finance rhythm? Golden Bookkeeping helps contractors connect job costs, billing records, cash planning, and useful reporting so the numbers support decisions before closeout. Book a Profit Review.
Frequently asked questions
What is change-order tracking in construction?
Change-order tracking is the process of recording a requested scope change, its approval status, estimated and actual cost, time effect, job-cost coding, and billing status. A useful log lets the owner see which changes are approved, pending, disputed, or completed without treating all of them as revenue.
Should a contractor start changed work before a change order is approved?
The contract and local requirements control. In many cases, the safest practice is to get written authorization before starting changed work. If immediate direction is given, document who directed it, when, what work was affected, and the contract path for resolving price and time. A bookkeeping record does not replace contract or legal advice.
How do change orders affect job costing?
Each approved change needs a consistent job, phase, and cost code so labor, materials, subcontractor costs, and equipment can be compared with the change budget. Keep original-scope costs separate from change costs when practical, otherwise an overrun can look like poor original estimating or an approved scope change can disappear into the base job.
What is the difference between a change order and a change directive?
The names and legal effect depend on the contract. Broadly, a change order often records an agreed change in scope, price, and sometimes time, while a directive may instruct work before all commercial terms are settled. Read the contract and keep the log status specific rather than assuming every request is approved revenue.



