Are You Contracting What You Want or Hoping Trades Comply?

You implement Takt planning. You create beautiful zone maps and schedules. You establish daily huddle systems, just-in-time delivery requirements, and zero-tolerance policies. Then trades push back. They didn’t bid for daily huddles. They weren’t told about just-in-time staging requirements. They threaten change orders for behaviors you’re now requiring. And you have no leverage because nothing was in their contracts. You hoped trades would comply with your systems. But hope isn’t a strategy. And compliance without contractual obligation is voluntary. So trades do what’s easiest for them, not what’s best for the project. Your systems fail not because they’re bad but because you never bought what you wanted.

Here’s the principle most teams miss. All systems you plan to implement must be included in contracts. This creates clarity for budget, schedule, and operational systems. You cannot surprise trade partners with requirements they didn’t bid for. You cannot expect to hold people accountable to systems unless those systems are contractually tied to their work. When you fail to contract what you want, you lose the right to require it. Trades can ignore your huddle systems. They can deliver materials in bulk instead of just-in-time by zone. They can refuse to assign foremen geographically or use your QC checklists. And when you try to enforce these behaviors, they levy change orders because you’re asking for work they didn’t bid. The solution isn’t better implementation techniques. It’s better contracting that buys the behaviors you need before work begins.

The deeper problem is that teams assume Lean will magically fall out of the sky and work. They think if they just explain the benefits, trades will happily adopt huddles, just-in-time deliveries, and zone-based staging. But construction doesn’t work that way. Trades optimize for their own efficiency, not project flow. They deliver in bulk because it’s easier for them. They skip huddles because it’s faster. They ignore your systems unless those systems are contractual requirements backed by payment terms and accountability mechanisms. Lean implemented like butter and honey and rainbows doesn’t exist. You have to sign people up. And signing people up means contracting what you want before work begins.

The Real Pain: Systems Failing Because They’re Not Contracted

Walk any project struggling with Lean implementation and you’ll see the pattern. The superintendent runs daily huddles but foremen don’t attend consistently. Why? Because huddle attendance wasn’t in their contracts. It’s a nice suggestion, not a requirement. The Takt plan shows just-in-time material deliveries by zone. But trades deliver in bulk anyway because their contracts don’t require zone-based staging. The project has zero-tolerance policies for safety and quality. But trades don’t take them seriously because contracts don’t tie violations to payment consequences. Every system exists on paper while the field ignores it because nothing was contractually required.

The pain compounds when trades levy change orders for behaviors you’re requiring. You ask for daily 25-minute crew preparation huddles. Trades say this wasn’t in the bid and demand payment for the additional time. You require just-in-time deliveries staged by zone instead of bulk drops. Trades say this increases their logistics costs and submit change orders. You want foremen assigned geographically to attend the right huddle systems. Trades say this wasn’t bid and costs extra. And you have no defense because they’re right. You’re requiring behaviors they didn’t bid for. The change orders are legitimate because you failed to contract what you wanted upfront.

The worst part is losing the ability to hold trades accountable. You implement zero-tolerance for cleanliness violations. A trade leaves their area messy. You want to enforce consequences. But their contract doesn’t specify cleanliness standards or enforcement mechanisms. So you clean it yourself or escalate to conflict without contractual backing. You want foremen using iPads with QC checklists and submitting inspections daily. But contracts don’t require this, so foremen ignore it. And you can’t enforce what you didn’t buy. Accountability without contractual foundation is wishful thinking. And wishful thinking doesn’t create compliant behavior on construction projects where every requirement faces resistance without contractual weight.

The Failure Pattern: Hoping for Compliance Instead of Contracting Requirements

Here’s what teams keep doing wrong. They create beautiful systems, then send bid packages without including those systems in the contracts. The Takt plan shows rhythm and flow. The site logistics plan shows staging areas. The basis of schedule describes the operational approach. But work authorizations and subcontract agreements don’t require trades to follow any of it. So trades bid based on traditional stick-built methods, bulk deliveries, and independent scheduling. Then when the project starts and you require different behaviors, they push back or demand change orders because you’re asking for work they didn’t bid.

They also assume explaining benefits will create compliance. If we just show trades how Takt planning helps them, they’ll adopt it. If we explain how daily huddles improve coordination, they’ll attend. But trades don’t adopt behaviors because they’re beneficial. They adopt behaviors because they’re required and enforced. Without contractual obligation, beneficial behaviors compete with easier traditional methods. And easier wins when there’s no requirement forcing change. So teams explain benefits while watching trades ignore systems that would help them because compliance is voluntary.

The failure deepens when they don’t include operational specifics in contracts. Contracts mention schedule but don’t detail the Takt rhythm, zone assignments, or just-in-time delivery requirements. Contracts mention quality but don’t specify QC checklists, foreman inspections, or zero-tolerance enforcement. Contracts mention meetings but don’t require daily huddles, crew preparation time, or geographic foreman assignments. So trades interpret requirements using traditional assumptions. And traditional assumptions contradict Lean systems. Without specific operational inclusions, contracts support the old methods you’re trying to change.

The System Failed You

Let’s be clear. When trades resist your Lean systems or levy change orders for required behaviors, it’s not because they’re difficult or resistant to improvement. It’s because you failed to contract what you wanted. You created systems without including them in bid packages and contracts. So trades bid traditional work and now you’re requiring different behaviors they didn’t price. The change orders are legitimate. The resistance is justified. You’re asking for work they didn’t bid. And that’s not their failure. It’s yours for not contracting what you wanted before work began.

The system fails because it doesn’t teach that contracting comes before implementation. Teams focus on creating great Takt plans and Lean systems. They invest in training and visual boards and coordination. But they skip the contracting step that makes implementation possible. So they have beautiful systems with no contractual foundation requiring compliance. And systems without contractual requirements are suggestions, not standards. Suggestions get ignored when they’re inconvenient. Standards backed by contracts get followed because non-compliance has consequences tied to payment and accountability.

The system also fails by treating Lean like it will magically work if you just believe hard enough. Some consultants promise that Lean implemented correctly will win hearts and minds creating voluntary compliance. But construction doesn’t work that way. Trades are businesses optimizing for profit. They’ll adopt behaviors that save them money if those behaviors are easy. But they won’t adopt behaviors that require effort, coordination, or change unless contracts require it. Lean needs believers. But it also needs contracts. And contracts matter more than beliefs when trades are deciding whether to comply with systems that require them to work differently.

What Lean in Contracts Looks Like

Picture this. Before sending bid packages, the project team prepares comprehensive contract inclusions. The basis of schedule details assumptions, exclusions, risks, opportunities, and key schedule considerations. It explains anything that cannot be interpreted from the Takt plan, zone maps, and site logistics plan. This eliminates ambiguity about how the project will operate.

General operational inclusions specify required behaviors:

Cleanliness standards with zero-tolerance enforcement. Just-in-time deliveries staged by Takt zone instead of bulk drops. Daily afternoon foreman huddles with required attendance. Twenty-five-minute daily crew preparation huddles before work begins. QC checklists and inspections by foremen using iPads. Zero-tolerance systems for safety and quality with enforcement tied to payment. Project management team approval of all foremen before they work on site. Foremen assigned geographically by area to attend the right huddle systems.

System-specific inclusions detail Takt planning, Last Planner, and any other operational systems. At BSRL, contracts bought out priority walls, room kitting, lean behaviors, huddle systems, zero-tolerance, bathroom use standards, no composite cleanup crews, delivery methods, crew operation requirements, and orientation systems. Every behavior the project wanted was contracted before work began. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

The contracts go into work authorizations, subcontract agreements, and work orders. Some requirements go into the company’s master subcontract agreement approved by legal. This ensures every trade on every project understands the operational standards. And enforcement becomes straightforward because non-compliance violates contracts, not just preferences.

If this increases bid prices slightly, reduce contingency on the back end. The project will spend less from construction contingency doing it right than fixing problems created by doing it wrong. And the overall budget stays the same while operational excellence becomes contractually required instead of hoped for.

How to Contract What You Want

Prepare before sending bid packages. Create the Takt plan, zone maps, and site logistics plan first. Complete division one spec and prime agreement research. Conduct risk analysis and fresh eyes reviews. Identify estimating inclusions ensuring the right general conditions, general requirements, and team size. Don’t send bid packages based on traditional assumptions, then try to implement Lean systems after. Contract the systems first.

Write a comprehensive basis of schedule detailing assumptions, exclusions, risks, opportunities, and key considerations affecting costs and schedule. Include anything that cannot be interpreted from Takt plans and zone maps. Eliminate ambiguity about operational approach so trades bid correctly.

Include general operational requirements in contracts. Cleanliness standards. Just-in-time delivery by zone. Daily huddles with required attendance. Crew preparation time. QC checklists and foreman inspections. iPads for foremen. Zero-tolerance enforcement mechanisms. Foreman approval processes. Geographic assignments. Every behavior you want must be specified and required.

Detail system-specific inclusions. If using Takt planning, explain rhythm, zones, and coordination requirements. If using Last Planner, detail weekly work planning and commitment expectations. If using Scrum or other systems, include their requirements. Don’t assume trades will figure it out. Contract what you want specifically.

Put requirements in work authorizations, subcontract agreements, and work orders. Consider including foundational requirements in master subcontract agreements for company-wide consistency. Have legal review to ensure enforceability. Make compliance contractual, not voluntary.

The Challenge

Here’s your assignment. Audit your current contracting approach. Do work authorizations and subcontract agreements include your operational systems? Are Takt requirements, huddle attendance, just-in-time deliveries, and zero-tolerance enforcement detailed in contracts? Or are you hoping trades will comply with systems they never agreed to?

Prepare comprehensive contract inclusions before your next bid package. Create basis of schedule, Takt plan, zone maps, and site logistics plan first. Then write contracts requiring the behaviors those systems need.

Include general operational requirements. Cleanliness, just-in-time deliveries, daily huddles, crew preparation time, QC processes, zero-tolerance enforcement, and foreman approval processes. Every behavior you want must be contracted.

Detail system-specific inclusions. Don’t just mention Takt or Last Planner. Explain what these systems require from trades and include those requirements in contracts.

Stop hoping for compliance. Contract what you want. If you want daily huddles, contract them. If you want just-in-time deliveries, contract them. If you want zero-tolerance enforcement, contract it. Compliance without contractual obligation is voluntary. And voluntary compliance fails when it’s inconvenient.

If you want it, buy it. Put it in contracts. Then enforce what you bought.

Current condition: we don’t contract what we want, so we don’t get it. Change that. Contract what you want before work begins. Then get what you paid for.

On we go.

FAQ

What should a basis of schedule include?

Assumptions, exclusions, risks, opportunities, and key schedule considerations affecting costs. Include anything that cannot be interpreted from Takt plans, zone maps, and site logistics plans. Eliminate ambiguity about operational approach so trades bid correctly understanding how the project will actually run.

What are general operational inclusions that should be in every contract?

Cleanliness standards with zero-tolerance enforcement. Just-in-time deliveries staged by Takt zone. Daily afternoon foreman huddles with required attendance. Twenty-five-minute crew preparation huddles. QC checklists and foreman inspections using iPads. Zero-tolerance systems tied to payment. Project management team approval of foremen. Geographic foreman assignments for huddle systems.

How do you handle trades pushing back on Lean requirements?

Include them in contracts before bidding. When requirements are contractual, pushback becomes non-compliance with payment consequences. When requirements aren’t contracted, pushback is legitimate because you’re asking for work they didn’t bid. Contract first, then enforce.

What if including Lean requirements increases bid prices?

Reduce contingency on the back end. Projects doing it right spend less from construction contingency than projects fixing problems created by doing it wrong. Overall budget stays the same while operational excellence becomes required instead of hoped for. Small upfront increases prevent large downstream waste.

Where should Lean requirements be documented?

Work authorizations, subcontract agreements, work orders, and potentially master subcontract agreements for company-wide consistency. Have legal review for enforceability. Make compliance contractual in every document governing trade work so there’s no ambiguity about requirements.