Why Lean Must Be Written Into Construction Contracts

What Happens When You Do Not Put Lean in Your Contracts

Here’s the deal. I hear this claim constantly. You do not have to pay for Lean, and you do not have to put it in the contract. I genuinely disagree, based on real experience, and I want to explain exactly why treating Lean as a free, unwritten expectation causes real, avoidable damage to trade partner relationships.

What Lean in Contracts Actually Means

Putting Lean in a contract is more specific than it might sound. It means answering concrete questions before a trade ever signs. Are foremen going to be interviewed before they are approved for the project? Are foremen or lead persons assigned by geographical area within the zones they will actually be working? Has the afternoon foreman huddle and the morning worker huddle actually been purchased and accounted for? Has the trade been told directly what is expected around safety, cleanliness, and the use of Takt planning? Whatever behavioral expectation you genuinely want from a trade partner has to be bought out explicitly, in writing, rather than assumed.

A Real Story That Proves the Cost Is Real

I once worked as a director at a construction company where we started implementing Lean principles specifically to help a genuinely skilled superintendent get a struggling project back on track. Several trades responded by sending multi-hundred-thousand-dollar change orders, directly tied to new requirements like foreman huddles and worker huddles that had never been part of their original contract.

None of those change orders ever actually got paid. The trades themselves eventually realized they were genuinely more productive working inside the new Lean structure than they had been before. But here is the honest problem. All of that contention, all of that friction, all of that time spent negotiating and calming down understandably upset trade partners, never needed to happen in the first place. It happened specifically because those expectations were never priced or written into the contract from the start. That is genuinely unfair to the trades, and it is completely avoidable.

Notice what actually resolved the situation. It was not a legal argument or a hard negotiating stance. It was the trades themselves discovering, after the fact, that the new structure genuinely made their own work better. That outcome is a lucky one, not a reliable strategy. A trade partner should not have to be talked down from a legitimate grievance before discovering that a change was actually in their own interest. They should have known that going in.

Lean Genuinely Costs Money, and That Is Not a Bad Thing

I want to be direct about something people get wrong constantly. Lean does cost money. Human beings changing how they typically operate costs money, every time, regardless of how beneficial that change ultimately is. Even in cases where Lean genuinely makes a company more money overall through improved productivity and flow, that implementation cost still has to be spent somewhere.

Pretending that cost does not exist does not make it disappear. It simply moves the bill to a later, less predictable point in the project, usually disguised as a dispute rather than a line item anyone actually planned for.

The real choice is not whether that cost exists. It is whether it comes out of pre-construction dollars, planned, budgeted, and contracted for in advance, or out of contingency, unplanned, reactive, and almost always more adversarial. Paying for Lean expectations up front, as part of a genuine negotiation, is a completely different experience for a trade partner than being asked to absorb an unplanned behavioral change mid-project with no warning and no prior agreement.

The Specific Consequences of Skipping This Step

If Lean provisions are missing from your master subcontract agreement, and your work authorization, work order, or contract does not explicitly state, or at minimum reference an exhibit describing, exactly what you expect, several specific consequences follow, and they are predictable rather than occasional.

Watch for these consequences directly tied to skipping Lean provisions in your contracts:

• Trades genuinely surprised by expectations they were never told about in advance.
• The wrong trades potentially selected in the first place, since you were never vetting for the right behaviors during the bidding and selection process.
• Trades arriving without the mindset, plan, or preparation needed, since they had no reason to expect any of it going in.
• Real friction and argument the moment you attempt to introduce these expectations after contracts are already signed.
• Change orders submitted in response, requiring negotiation, relationship repair, or an unplanned payout you never budgeted for.

Why This Is Fundamentally a Fairness Issue

None of this is really about protecting a company’s own interests, even though it genuinely does. It is about doing the right thing for trade partners. Being clear, upfront, and explicit about exactly how a project will be run respects the people you are asking to commit real resources and real crews to that project. Springing new behavioral expectations on someone after they have already signed, with no prior agreement or compensation, is not a small administrative oversight. It is a genuine breach of the trust a contract is supposed to represent.

Addressing the Objection I Hear Most Often

I once heard someone argue that being genuinely clear about how a project will be run will scare trade partners off and drive prices higher. Maybe, since we are dealing with real human beings reacting to real information. That possibility does not change what the right thing to do actually is.

The honest answer to that concern is not vagueness. It is skill. Genuine negotiation ability, solid control estimates, and real competence in planning and pricing a project are what let you communicate clear expectations while still arriving at a fair, competitive price. Hiding expectations to avoid an uncomfortable conversation is not a pricing strategy. It is a decision to pay for that clarity later, through change orders and damaged trust, instead of paying for it up front through honest negotiation.

Building This Into Your Own Contracts

None of this requires a dramatic overhaul of how your organization writes contracts. It requires specifically naming the Lean and Takt expectations you genuinely intend to hold trade partners to, in the master subcontract agreement and again in the specific work authorization for each trade, so nothing about your project’s actual operating rhythm comes as a surprise once work begins.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your organization build these provisions directly into your contract templates, so Lean and Takt expectations are genuinely priced and agreed to up front, rather than introduced later as an unplanned, contentious change.

So here is the challenge. Pull your own current master subcontract agreement and work authorization templates and check honestly whether they actually name your Lean expectations, huddles, Takt planning, foreman interviews, geographic zone assignments, or whether those expectations exist only informally, assumed but never written down. If it is the latter, that gap is exactly where your next unnecessary change order or trade partner conflict is quietly waiting to happen.

Jason Schroeder said it plainly: “The consequences of not having lean behaviors in contracts greatly outweigh having them in there.” Write it down, price it fairly, and the friction that used to be inevitable becomes genuinely avoidable.

On we go.

FAQ

Why do trade partners sometimes submit change orders in response to new Lean requirements?

Because implementing behaviors like huddles, Takt planning, or specific staffing requirements requires trades to change how they typically operate, which genuinely costs them time and resources they did not originally budget for. If those expectations were never included in the original contract, trades have a legitimate basis to request additional compensation for accommodating a change introduced after the agreement was already signed.

Why does the article insist that Lean costs money even when it ultimately improves productivity?

Because the cost of changing established habits and workflows is real and immediate, even if the long term financial benefit of improved flow and productivity eventually outweighs it. The two are not mutually exclusive. Lean can genuinely make a project more profitable overall while still requiring a real, upfront investment in changing how people work, and that investment needs to be planned for rather than assumed away.

What is the practical difference between paying for Lean out of pre-construction dollars versus contingency?

Pre-construction dollars represent planned, budgeted spending negotiated as part of the original contract, generally producing a smoother, more collaborative relationship with trade partners. Contingency spending is unplanned and reactive, typically triggered by disputes or change orders after the fact, and tends to create more friction and less trust between the parties involved, even when the same underlying work ultimately gets done.

How can a company communicate clear Lean expectations without unintentionally driving trade partners away or increasing bid prices significantly?

By pairing clarity with genuine skill in negotiation, cost estimating, and project pricing, rather than avoiding clear communication out of fear that it will scare trades off. A well prepared team can present Lean expectations as a normal, priced-in part of the project rather than an unusual demand, which tends to produce a fair price rather than an inflated one, since the trade partner knows exactly what they are agreeing to from the start.