Change Order Logs
Change order logs that maintain themselves.
We encode each contract’s change-order rules against the job data you already keep, so the log maintains itself and every approved change reaches billing.
Built with the leading AI platforms
The broken Friday
The field said yes. The pay app never heard.
From contractors we have sat with: general contractors and specialty subs between $10M and $100M, not shopping for software — drowning between the field approval and the billing cycle.
Approved in the field, missing from the pay app
The work got a verbal yes and it is done, but the change order never reached the schedule of values. The money sits unbilled until someone reconciles the log against the pay application — which is to say, eventually.
The log and the pay app don’t reconcile
The change-order log and the pay application have to reconcile every cycle — and they don’t. The gap between approved and billed widens, and nobody owns the difference.
Notice windows missed before anyone saw them
The contract required written notice within days of the field change. It went out late or never — a legitimate change became a negotiation or a giveaway.
Priced from memory, not the contract
The contract sets the markup on change-order work, but pricing happens from memory — labor, material, and equipment each with their own rate, consistent only while somebody remembers.
The rules walked out the door
Which owner wants change orders as separate lines — it lived in one person’s head. She left, and nobody has systematically checked a change order against the contract since.
What manual costs
Unbilled change orders are a line item, not a feeling.
What the manual way looks like at a contractor running its log in a spreadsheet and its rules in someone’s head. Your numbers will differ — the first job we reconcile puts figures on yours before anything gets built.
From anonymized engagements — general contractors and specialty subs, $10–100M in revenue
How it works
We encode your exceptions.
No new system for your team to learn. The change-order rules your best person carries in their head become the log.
- 01
Reconcile one job’s log
We reconcile one job’s change-order log against the last three pay applications — approved in the field, priced, billed. That gap is where the rule set starts.
- 02
Encode the contract’s change-order rules
Notice window, signature chain, pricing and markup, when the change enters the schedule of values — documented end-to-end against the job data you already keep, yours to keep.
- 03
The log maintains itself
Field approvals feed the log; priced, approved changes sequence into the schedule of values. Anything approved but unbilled lands in an exception queue your team reviews each cycle.
A template logs the change order. It can’t get it onto the pay app.
The spreadsheet template is the real incumbent for the mid-market GC. A template logs the change order — it cannot get it approved, priced, or onto the pay application, which is where the money is.
The construction software holds the job data; change-order software sells another system to adopt. Neither holds your approval rules — the notice windows, the markup, the sequencing your PM negotiated. We encode those; our AI reads each approved change against them, every cycle.
Questions
Asked by GC controllers and owners.
The straight answers, before you book anything.
What’s holding your business back?
A workflow ready for automation. An AI product you want to build. A problem that has sat on the roadmap for years. Let’s talk about what it would take to solve it.
Talk to Zaigo

