Latest / The Operator's Manual with Fexingo: Daily Decisions, Tactical Wins, and Business Execution / How One Construction Firm Cut Project Overruns 40 Percent With a Single Contract Change
Transcript
- Lucas: You're looking at a commercial construction site in Austin, Texas, about two years ago. Foundation's poured, steel's going up, and then the window subcontractor shows up three weeks late because the framers left the openings out of tolerance. The general contractor has a contractual right to levy a daily penalty — it's in the boilerplate, 'time is of the essence' clause. So they fine the window sub, the window sub pays the fine, but the project is still three weeks behind. Everyone walks away angry and the schedule never recovers. Luna: So the penalty didn't actually solve the delay problem. It just assigned blame. Lucas: Exactly. And that's how most construction contracts operate — they're designed for legal recourse, not operational recovery. But one mid-size firm in Austin decided to change that by rewriting a single contract clause, and the results were dramatic. We're talking a 40 percent reduction in schedule overruns and a 28 percent drop in cost overruns in the first 12 months. Luna: Forty percent — that's huge. What was the change? Lucas: They replaced the standard 'time is of the essence' clause with what they called a 'shared delay risk' framework. Instead of automatically fining the subcontractor for any delay, the new clause required a joint root-cause analysis within 48 hours of a delay being flagged. If the root cause was the subcontractor's fault — say, they understaffed — they still paid a penalty. But if the root cause was a predecessor's work, like the framers' out-of-tolerance openings, the penalty was waived and the responsible party had to cover the mitigation cost. Luna: So it shifted the incentive from hiding blame to actually figuring out what went wrong. That makes sense — but 48 hours is tight. How did they implement that in practice? Lucas: They set up a simple digital log on the project management platform — think of it as a shared spreadsheet — where any foreman or project engineer could flag a delay with a timestamp and a brief description. Then the GC's project manager and the subcontractor's site lead had to meet within 48 hours to fill out a standard root-cause form. The form had just five fields: what was the delay, what was the immediate cause, what was the underlying cause, who was responsible, and what's the corrective action. Luna: And this replaced the old system where the GC would just send a formal notice of delay and start the penalty clock? Lucas: Right. Under the old clause, the GC had no incentive to investigate — they just collected the fine and moved on. The subcontractor had every incentive to hide the delay or blame someone else, because a fine meant lost profit. So you'd get these disputes that dragged on for weeks, sometimes ending up in mediation. Change orders — the formal requests to alter the contract scope — were a huge source of friction. In the year before the change, that company had 42 change order disputes across its projects. The year after, 11. Luna: So the single clause rewrite basically eliminated three-quarters of the disputes. That's the kind of number that makes you wonder why every firm doesn't do this. Lucas: Well, there's a reason it's not standard. The traditional clause is a legal comfort blanket — it's been in every standard form contract from the American Institute of Architects for decades. Lawyers are comfortable with it, and general contractors are used to the income stream from penalties. In fact, some GCs treat delay penalties as a profit center. This firm had to convince its own legal team and its insurance carrier to sign off on the change. Luna: And the subcontractors? I imagine they were initially skeptical that it wasn't a trap. Lucas: Hugely skeptical. The first two projects under the new clause had a lot of hesitation — the subs were used to being blamed for everything, so they were slow to flag delays because they assumed they'd still get fined. But after the first few root-cause analyses where the GC took responsibility for a predecessor's error, trust built quickly. Within six months, the project managers reported that subcontractors were actually self-flagging delays proactively, because they knew they wouldn't be penalized if it wasn't their fault. Luna: That's a complete cultural shift. And it's driven entirely by a contract change — not a training program, not a new software tool, just a different allocation of risk. Lucas: Right. And the data backs up the cultural shift. The company tracked 'delay reporting lag' — how many days between a delay occurring and someone reporting it. Under the old contracts, the average lag was 11 days. Under the new clause, it dropped to 2.3 days. That means problems were being surfaced early enough to actually mitigate them, rather than discovered after the fact when the only option was to argue about fines. Luna: So the 48-hour root-cause meeting became a forcing function. You can't have a meeting about a delay that happened two weeks ago because no one remembers the details. Lucas: Exactly. And the meetings themselves changed the dynamic. Instead of a GC project manager sending a terse email and then a legal notice, you had two people sitting down with a shared log and asking 'What actually happened here?' The form forced them to distinguish between immediate cause — the framers left the openings 3/8 of an inch too narrow — and underlying cause — the framers' foreman didn't have the latest shop drawings because the GC's engineering team uploaded them to the wrong folder. The corrective action then addressed the underlying cause, not just the symptom. Luna: Before we go deeper, I want to mention something. It's a small thing, but a number of listeners chip in monthly at buy me a coffee dot com slash fexingo, and that support is what keeps these conversations ad-free. Lucas: It does. And it's genuinely appreciated. So back to the construction site — one of the most surprising outcomes was the effect on change orders. Change orders are notorious for eating into margins. A typical commercial project might have dozens of them, each one a negotiation. Luna: And with the old clause, a delay often triggered a change order because the subcontractor would claim the delay forced them to work out of sequence, which increased their costs, so they'd submit a change order for extra compensation. Lucas: Right. The old system incentivized turning every delay into a change order. Under the new clause, because the root-cause analysis had to assign responsibility, subcontractors were less likely to submit speculative change orders — they knew the GC would push back with the documented root cause. The number of change order disputes dropped from 42 to 11, as I mentioned, and the total value of change orders decreased by 34 percent year over year. Luna: So the GC saved money on two fronts: fewer schedule overruns and fewer change order payments. Did the subcontractors end up better off too? Lucas: The firm shared some aggregate data. Across all subcontractors on the new contracts, the average markup on change orders actually went up slightly — from 18 percent to 21 percent — because the change orders that did get approved were legitimate and less disputed. But the total change order volume dropped so much that subcontractors' net revenue from change orders fell about 12 percent. However, they also faced fewer penalties. Under the old contracts, the average subcontractor paid about $14,000 in delay fines per project. Under the new, that dropped to about $2,000. So overall, the subs were probably better off by a few thousand dollars per project, plus they had less administrative headache. Luna: That's a win-win, at least on aggregate. But I imagine some subcontractors who were used to gaming the system — submitting inflated change orders, or hiding their own delays — were unhappy. Lucas: Absolutely. The firm actually lost two subcontractors in the first year — both were firms that had a reputation for aggressive change order practices. The GC's project managers said it was a net positive because those subs were high-friction anyway. And the remaining subs reported higher satisfaction in anonymous surveys. One survey question: 'Do you feel the contract treats you fairly?' Under old contracts, 38 percent said yes. Under new, 81 percent. Luna: So the contract change acted as a filter. It attracted and retained subs who were willing to collaborate, and repelled those who preferred to exploit ambiguity. Lucas: Exactly. And the GC didn't even need to market the new clause. Word spread among subcontractor networks in Austin. Within two years, the firm was getting unsolicited bids from subs who specifically wanted to work under the shared delay risk framework. Luna: That's a strong signal. It suggests the old system was costly for everyone, but no one had the power to change it unilaterally until this firm tried. Lucas: Right. And the interesting thing is that the change was almost costless to implement. They rewrote one clause in their standard subcontract, updated the project management software to include the delay log, and trained their project managers on the root-cause form. No expensive ERP overhaul, no new legal retainer. The total implementation cost was maybe $15,000 in training time and software customization. The first year's savings from reduced overruns alone were north of $1.2 million. Luna: That's an 80-to-1 return. And it came from a document that most companies treat as boilerplate, something you just copy from the last project. Lucas: That's the takeaway, I think. The contract is an operating system. Most firms treat it as a legal artifact, something to protect you in court. But it actually shapes behavior on the ground every single day. If your contract incentivizes blame-shifting, you'll get blame-shifting. If it incentivizes root-cause analysis, you'll get that instead. Lucas: Yeah. Look at software development contracts with 'time and materials' clauses — they often incentivize vendors to drag out projects. Or event contracts with 'force majeure' clauses that don't define what counts as a covered disruption, leading to disputes. The same principle applies: the contract creates the incentive structure. Luna: So if a listener is in procurement or contract management, what's the one thing they should try next week? Lucas: Pick one type of recurring delay in your operations. Find the clause in your standard contract that deals with it. Ask yourself: Does this clause encourage the counterparty to surface the problem early and fix it, or to hide it and argue about blame? If it's the latter, rewrite that clause with a shared investigation mechanism. Start with one contract type, pilot it for six months, and measure the change in delay reporting lag and dispute volume. Luna: And don't be afraid of the lawyers pushing back. The Austin firm's legal team eventually became the biggest advocates because they had fewer disputes to litigate. Lucas: Exactly. That's the hidden win: less legal work. So the question is not whether you can afford to change the clause — it's whether you can afford not to.