The super is standing in a master bath that doesn’t match the plans. The tile contractor is holding his phone, scrolling. “You told me Rev B,” he says. The super says, “We moved to Rev C three weeks ago — the change order went through.” Neither of them is lying. Somewhere there’s a change order #14 that swapped the spec’d porcelain for a large-format slab, and somewhere there’s an email approving it, and somewhere there’s a budget line that already absorbed the cost. The problem isn’t that the change didn’t happen. The problem is that nobody in that hallway can prove, right now, what it was, what it cost, or whether anyone with authority said yes.
Change orders are where projects bleed quietly. Not in one dramatic event — in the slow accumulation of small confusions. A field change agreed to verbally and never written up. A price that was “about three grand” in a text, $3,200 in the formal CO, and $4,100 by the time it was installed. An approval that lives in one person’s inbox. A drawing revision three trades are building from and two aren’t. None of these is a catastrophe on its own. Stacked across forty COs on a job, they become the reason the final pay app is a fight and closeout drags into the next quarter.
The good news: change-order confusion is mostly a record-keeping problem wearing a communication problem’s clothes. You can’t make changes stop — changes are the job. But you can make every change unambiguous: what changed, what it cost, who approved it, and what else it touched. That’s four questions. Answer all four, every time, and the confusion has nowhere to live.
The four questions every change order has to answer
A change order isn’t confusing because it’s complicated. It’s confusing because the four things you need to know about it usually live in four different places. The scope is in an RFI response or a marked-up drawing. The cost is in an estimate someone emailed. The approval is in a reply that says “go ahead.” And the impact — the new budget total, the schedule slip, the spec section that now reads differently — is nowhere, because nobody sat down to trace it. When those four answers are scattered, every conversation about the CO starts with archaeology.
Habits that cut the confusion before it starts
Most change-order pain is preventable with discipline that costs minutes, not money. None of this is new — good supers and PMs have done it for decades. The trick is doing it every time, including the small ones, because the small ones are where the ambiguity hides. The $300 change nobody bothered to write up is the one that comes back at the pay app.
- 1
Name it the moment it happens
The instant a change is even discussed, give it a number and a one-line description in writing — “CO #14: substitute large-format slab for spec’d porcelain, master bath.” A change with a name and a number is a thing you can track. A change that’s still a hallway conversation is a thing that will be misremembered.
- 2
Price it before you proceed
No work in the field before there’s a written number tied to the scope — even a rough not-to-exceed. The most expensive change orders are the ones priced after the work is already in, when you’ve lost all leverage and the figure is whatever the sub says it is.
- 3
Get the yes from someone who can give it
Approval has to come from a named person with authority, in writing, against that specific number and scope. “Sounds good” from someone who can’t commit the budget isn’t approval — it’s a future argument about who agreed to what.
- 4
Trace what it touched
Before you close the CO, follow the thread: which drawing revision, which budget line, which schedule activity, which spec section. A change that bumps the tile also moves the finish schedule and the budget, and maybe the substrate or the waterproofing detail under it. Write down every line it moves.
- 5
Push it back to the field
The trades have to be working from the change, not around it. Confirm in writing that the crew installing the work has the current revision. Half of all rework is someone building correctly off the wrong version.
Notice what these habits have in common: every one produces a written artifact, and every artifact is tied to the same change number. The CO number is the string that runs through the scope, the price, the approval, and the impact. When all four are pinned to #14, “what’s the status of fourteen” becomes a question with one answer instead of five.
A change with a name and a number is a thing you can track. A change that’s still a hallway conversation is a thing that will be misremembered.
Why the record falls apart anyway
Here’s the honest part. Even disciplined teams lose the thread, and not because anyone is sloppy. They lose it because the four answers get created in four tools by four people. The scope lands in an RFI log. The price arrives as a PDF attached to an email. The approval is a one-line text from the owner’s rep at 9 p.m. The impact lives in a budget spreadsheet one person maintains. Each piece is fine on its own. The connections between them exist only in someone’s head — and that someone goes on vacation, rolls off the job, or just forgets which of the forty COs the owner was asking about. This is the gap between storing files and keeping a record: a shared drive holds the CO #14 PDF, the estimate, and a folder of drawings, but it doesn’t know they’re the same change, or that the late-night text approving it belongs with them. Storage puts documents next to each other. A record holds them connected. The confusion lives precisely in the connections nobody stored.
Files in a folder
- The CO, the estimate, and the email all exist — separately
- You know a change happened; reconstructing it takes archaeology
- Approvals live in whoever’s inbox caught the reply
- Budget and schedule impact lives only in someone’s memory
- “What’s the status of CO #14?” needs three people to answer
A connected record
- Scope, price, approval, and impact link to the same change
- Ask one question, get one answer with the source attached
- The approval message is part of the change, not a lost reply
- The drawing revision and the budget line are tied to the CO
- Anyone on the team can see the whole change in one look
Where a connected record earns its keep
This is the work BRAD is built for. You already forward the documents and messages that run the job — the change order, the priced estimate, the marked-up drawing, the email approval, the texts between office and field. BRAD reads them, connects the ones that belong to the same change, and keeps that as a record you can question. So when the super texts “what tile are we on for the master bath and was it approved,” the answer comes back over the same thread he’s already in: the spec moved to Rev C under change order #14, priced at $3,200, approved by the owner’s rep on the 9th — with the approval message and the drawing revision cited, so he sees the source instead of taking BRAD’s word for it. That citation is the part that matters: the confusion you’re trying to kill is an evidence problem — two people remembering the same change differently — and an answer with the source attached ends the argument, because nobody is being asked to trust a memory. One honest limit: BRAD doesn’t approve change orders, set the price, or run your contract’s formal CO process; it won’t replace a signed change order, a stamped drawing, or the judgment of the person whose name goes on the approval. What it does is keep the record of that decision — scope, price, approval, impact — connected and findable, with the source one tap away. The decision is still yours. The proof just stops being scattered.
Changes will keep coming — that’s the job, not a flaw in it. The teams that close clean aren’t the ones with the fewest change orders. They’re the ones who can stand in a hallway, pull up #14, and say with certainty what it was, what it cost, who signed off, and what it moved — and show where each answer came from. Get that, and the change order stops being the place the project bleeds.