A change order approval workflow is the path an extra takes from the crew that discovers it to a countersigned record both parties can produce later. Most contractors run it on a verbal go-ahead and a T&M ticket signed on a tailgate. A system captures the change where it is found, prices it as structured data, routes it through the approval the contract actually requires, and rolls the executed version into the contract sum.
How an extra becomes a dispute
Work starts on a nod
The superintendent gets a verbal go-ahead from the owner’s rep and puts a crew on the change Monday morning. By the time paperwork catches up, the scope has grown and the hours are spent. The only record of the authorization is somebody’s memory of a parking lot conversation.
The T&M ticket never becomes a change order
Field crews write time and material tickets daily and somebody signs them. Then they ride around in a truck, get photographed, get emailed, and never become a priced change against the contract sum. At closeout you are billing work with no approved change behind it.
Pricing and approval live in different places
The estimator prices the change in a spreadsheet. The PM emails the owner a PDF. The owner replies “proceed” in the thread. Three systems, and no single record of what was approved, at what price, on what date.
Nobody agrees on the current contract sum
Original contract, eight executed changes, two pending, one rejected. Ask three people what the contract is worth today and you get three numbers. The pay application carries whichever number accounting was told last.
Approval authority is assumed rather than defined
A project manager approves a change the contract says needs the owner’s written signature. Or the owner’s construction manager approves something outside their own limit. Neither is caught until the change is challenged, and by then the work is in place.
The approval chain and the nine fields that survive a dispute
Two things decide whether a change order holds up: who touched it in what order, and whether the document carries enough to answer questions later. Top rows are the chain; the rest is the field list we build the form to.
| Part | Item | Owner or source | What it establishes |
|---|---|---|---|
| Chain | 1. Field ticket raised at discovery | Foreman or superintendent | The date found and who found it |
| Chain | 2. Scope written and priced | PM or estimator | Labor, material, equipment, sub quotes, markup, time impact |
| Chain | 3. Internal approval against a dollar threshold | PM or operations lead | That the number was checked in-house first |
| Chain | 4. Owner, architect, or CM signature | The rep the contract names | Authorization from someone with authority to give it |
| Chain | 5. Countersigned record filed against the contract | System of record | Both signatures, both dates, one version |
| Field | Sequential change order number, per job | Assigned on creation | That the log is complete |
| Field | Discovery date, separate from the date written | Field ticket | When the condition arose, the date notice turns on |
| Field | Originating reference: RFI, field ticket, ASI, or owner directive | Whoever raised it | That it traces to a document, not a conversation |
| Field | Scope in the trade’s own words, never “per attached” | PM or estimator | What was agreed, readable by an outsider |
| Field | Cost breakdown: labor hours and rate, material, equipment, sub quotes, markup, shown separately | Estimator | That the price checks line by line |
| Field | Basis of pricing: lump sum, unit price, allowance, or T&M with a not-to-exceed | Estimator | How the number settles if quantities move |
| Field | Schedule impact in calendar days, stated even when it is none | PM with the scheduler | That time was addressed, not left open |
| Field | Signature block: printed name, title, authority held | Both parties | That the signer could bind their party |
| Field | Revised contract sum and revised contract time | Calculated | The total the next pay application must match |
The chain, as we build it
Capture where the condition is found
A mobile form the foreman completes on site: photos, the condition, the affected area, the date. It creates the change record before anyone has priced anything, so the discovery date is recorded rather than reconstructed three weeks later.
Pricing as structured fields, not an attachment
Labor hours and rate, material, equipment, sub quotes, and markup are entered as fields. The total calculates and the breakdown stays queryable. A spreadsheet PDF can still go to the owner, but the numbers live in the record.
Thresholds decide the route
The approval authority your contracts set is encoded per job. Under a stated dollar amount the PM approves. Over it, the owner’s signature is required before work is released, and a change cannot skip a required signature.
Signature collected through the contract's own channel
The e-signature request goes to the named representative with the priced change attached. The executed document returns into the same record with its timestamp. Nobody files a separate PDF, and there is no question which copy is signed.
Contract sum recalculated on execution
Executed changes roll into the running contract sum and the change order log that goes with the next pay application. Pending and rejected changes stay visible but out of the total, which keeps billing and the field aligned.
The systems on either side of a change
- contract workflow automation — The executed change attaches to the prime contract record with the revised sum rather than to a separate folder.
- e-signature routing with DocuSign — Signature requests go to the named owner's representative and the countersigned copy returns to the change record.
- QuickBooks automation for job billing — Approved changes raise the job's contract value so progress billing reads from a current number.
Is this a fit for your business?
A good fit when
- Your jobs regularly carry more than a handful of changes
- Field crews start extra work before any paperwork exists
- You bill on AIA forms and the change order log must reconcile
- More than one person can approve, and the limits sit in the contract
Probably not a fit when
- You run fixed-price residential work where changes are one conversation
- You need full scheduling and cost control, not the approval path
- You want someone to negotiate change order pricing with owners
What to have ready
- Your current change order form, even if it is a Word document
- The approval thresholds your prime contracts set, by owner type
- A recent job’s change order log, including rejected changes
Questions we get asked
Can the field crew start work before the owner signs?
That is a contract question and the answer differs by owner. The system makes the choice explicit: a change can be marked released to proceed under a construction change directive with the signature still pending, and that state shows on the log. What it prevents is work starting with nothing recorded.
How do T&M tickets fit in?
A T&M ticket is evidence, not authorization. We treat daily tickets as children of a change record, so hours and material logged in the field roll up against the change they belong to. When the change is priced, the tickets are already attached.
What happens to changes the owner rejects?
They stay in the log with their rejection date and reason, and out of the contract sum. Rejected changes matter at closeout, because a rejected change with work already performed is the shape most claims take. Deleting them removes the record you need.
Does this handle changes we issue down to our subcontractors?
Yes, and it should. An owner change usually creates one or more subcontract changes, and the two need linking so a sub is not asked to hold a price you never got approved upstream. The subcontract change carries its own number, scope, and signature.
Related
- daily field reports and job site photo capture
- progress billing and AIA pay application workflow
- contract workflow automation services
- workflow automation for construction companies
Tell us what the process looks like now and we will map what a system would need to do. No obligation, and you keep the map either way.