Brad for builders: protect margin, catch scope, track every change order

Margin does not vanish on a job. It leaks. A substitution nobody priced. A directive the architect issued by email that never made it onto a change order. A spec revision that conflicts with a sheet still in the field. Each one is small. Together they are the difference between the number you bid and the number you keep. The information that would have caught them was always in the project. It was never connected, which on a busy job is the same as not having it.

This is not a margin-of-error problem you can manage with more attention. The data tells on itself. Bad project data caused roughly $88.7 billion of rework in 2020, about fourteen percent of all rework that year.^[1] And the rework is not random: across a wide set of projects, productivity beat plan on about sixty percent of jobs when change stayed at or under five percent of contract value, and never once when change ran past twenty percent.^[2] Scope is the variable a GC has the most leverage over, and the one that does the most damage when it moves unwatched.

Brad reads the job you already run

A GC carries a project as one connected thing: the plan set, the contract, the open change orders, who approved the substitution, the schedule of values, and the two dozen decisions made over text and email since last Tuesday. That works until the person holding it takes a week off, or rolls to the next job, and the picture leaves with them. Brad gives that running memory a home. It reads the plans, the specs, the contract, the change orders, the invoices, the field photos, and the conversations around all of it, and links them into one knowledge base built from the documents your job already produces.

You ask in plain language and get an answer from your actual project, not a generic model that has never seen your set. “Which detail is current at grid line 7?” “What did the owner agree to on the canopy substitution, and is it on a CO yet?” “What's still open against the schedule of values?” The answer comes back with the source attached, over the email and text your team already uses. There is no new system to key everything into, and no dashboard that sits half-used by August. The point is to take the digging out, not hand the crew another chore. The average construction pro already loses about 5.5 hours a week just looking for data; an answer that assembles itself is time the schedule gets back.^[3]

Every change order, tied back to the schedule of values

Change orders are where margin lives or dies, and they fail in a predictable way: the work happens, the paper lags, and by the time anyone reconciles it the cost is already yours. Brad tracks each change order from the moment it starts as an RFI answer, a field directive, or an owner email, and ties it to the plans it touches, the contract terms that govern it, the cost it carries, and the line in the schedule of values it belongs against. The approval and the impact stay visible together instead of one living in a thread and the other in a spreadsheet someone last touched in April.

That linkage is what catches scope creep early, while you can still write the change order, instead of at closeout when it has hardened into a fight. The MacLeamy curve makes the stakes plain: your ability to influence cost falls steadily as the project moves forward, while the cost of making a change rises.^[4] A directive caught the day it is issued is a priced change order. The same directive caught at closeout is an argument, and arguments are expensive: the most common cause of construction disputes is a party failing to understand or comply with its contract obligations, which is exactly what an untracked change becomes.^[5]

Catch the quiet scope before it becomes rework

The expensive changes are rarely the ones with a directive attached. They are the quiet ones. A superseded sheet still in the field. A finish where the plans and the spec disagree. An ASI that changed a detail nobody pushed out to the framers. A substitution everyone assumed was approved that never closed. Because Brad holds the whole set connected, it can see when two documents contradict each other and flag the conflict rather than waiting for the field to build the wrong one.

When the documents genuinely disagree, Brad does not paper over it with a confident guess. It points at both sources and surfaces the discrepancy, because reconciling a conflict between the drawings and the spec is the project team's call. The value is timing. Catching a superseded detail before the crew frames to it is a five-minute correction. Catching it after is a rework line, and rework is the single biggest avoidable cost on most jobs.

Draw packages and closeout that assemble themselves

Because invoices, approvals, lien waivers, COIs, and change orders are already connected to the work they belong to, assembling a draw package or a closeout binder is pulling what Brad has organized, not reconstructing it by hand the night before it is due. Ask for what backs a given pay application against the schedule of values and Brad returns the invoices, the approvals, and the change orders behind each line, with the source on every one.

The same thread protects you long after the job. Six months out, when memory has gone soft and the paperwork is all you have, someone asks why a detail got built the way it did, or whether the added cost was ever authorized. The RFI, its cited answer, and the change order it triggered are already sitting together. No archaeology through old inboxes, and no room full of people saying they think it was around April. A sourced, dated record is the difference between a defensible position and a guess, and on a disputed change that difference is the money.

Where Brad stops and your team starts

Brad is document intelligence and project records pointed at the way a GC actually runs a job. It reads, connects, and surfaces from your project's documents and messages, and it answers with the source attached. What it is not: a stand-in for licensed professional judgment, your contract's notice and change-order requirements, or your accounting system of record. It does not approve a change order or sign a pay application. It connects the plans, the contract, the costs, and the conversations so the people making those calls are working from the full picture instead of a partial one. Your project's content stays yours, every workspace is walled off from every other one, and if you have specific requirements about how your data is handled or retained, ask us and we will walk you through exactly how it works.

You will not stop a job from generating change. You can change whether each one gets priced while you still have leverage or discovered at closeout when you do not. Margin leaks one untracked change at a time. Brad is how you see them while they are still small.