Implementing BIM Part 1 Feat. Greg Low

BIM on Real Projects: How to Get Buy-In, Start at the Right Time, Run Kickoffs, and Stop “Figure It Out in the Field”

A lot of teams talk about BIM like it’s a “nice to have.” Something you do on the big jobs. Something you do when you’ve got extra time. Something you do when the trade partners are already into it. That mindset is exactly why BIM fails. This episode is a listener Q&A with Greg Lowe, and the theme is practical: BIM is not a fancy add-on. BIM is a field advantage when you treat it like an execution system. If you treat it like a side project, it becomes an argument about fees. If you treat it like a system that protects flow, safety, and schedule, it becomes non-negotiable.

The real issue isn’t software. The issue is leadership. And the quote that anchors this entire conversation is a leadership habit every PM and superintendent needs: “The number one question a PM should learn is: what do you need?”

The Hook: Why BIM Keeps Turning Into Drama

Most BIM drama starts the same way. A job is awarded. The schedule is tight. The design is incomplete. Trades mobilize fast. Someone says, “We should do BIM.” Another person says, “That’s an alternate.” Another says, “We’ll figure it out in the field.” And then the project pays for that decision in rework, clashes, delays, and stress. The pain isn’t just technical. It’s human. Crews get stuck with conflicts they didn’t create. Foremen spend their days solving design problems instead of building. Leaders become referees. The job goes reactive. The system failed them; they didn’t fail the system. If the project didn’t set up coordination early with clear expectations, the field gets punished for it later. BIM is one of the best ways to prevent that if it’s done with discipline.

BIM Isn’t a Fancy Add-On: It’s a Field Advantage When It’s Done Right

Greg and Jason both reinforce the same truth: BIM’s value is not in the model. BIM’s value is in the decisions the model forces early before the job is stacked, before the ceilings are closed, before the schedule is bleeding. BIM becomes powerful when it’s tied to constructability and prefabrication, when it reduces variation, and when it stabilizes handoffs. That’s why it fits so naturally with Lean thinking and LeanTakt systems. Flow doesn’t happen by wishing. Flow happens by removing conflicts before crews hit them. If BIM is set up as a production tool, it protects the workforce. If BIM is set up as a design exercise, it becomes overhead that people resent.

The First Question: How Do You Get Trade Partner Buy-In Without “BIM as an Alternate”?

The trade partner buy-in question is real. Many subs have been burned by BIM being treated as “extra work” without clear scope, clear leadership, or clear return. That’s why you can’t sell BIM with vague promises. You sell BIM with clarity. Buy-in comes from a BIM execution plan that answers: What’s the purpose? Who owns what? What level of detail is required? What’s the schedule cadence? What decisions will be made with the model? What’s the clash process? What are the deliverables? When trade partners see that BIM will reduce rework and stabilize field production, buy-in increases. When they see BIM as ambiguous coordination meetings that never end, buy-in disappears.

Confidence Comes From the Plan: Why the BIM Execution Plan Is the Whole Game

This episode makes the execution plan the centerpiece, and for good reason. A BIM execution plan is not paperwork. It’s the operating agreement for coordination. It creates control.

Without it, the project will suffer from:

• unclear expectations,
• unclear model responsibility,
• unclear LOD,
• mismatched file naming and version control,
• slow responses,
• and coordination meetings that produce noise instead of resolution.

With it, BIM becomes a disciplined production system. That’s why Greg and Jason keep pushing back on the idea of “we’ll sort it out as we go.” Sorting it out later is exactly what creates the field pain.

“Death Ground” Scheduling: When Prefab Is Non-Negotiable and the Data Proves It

A key idea in the episode is the moment when the schedule makes prefabrication unavoidable. If you’re on “death ground”—no buffer, tight milestones, high complexitythe only way through is to reduce field variability. Prefab is one of the strongest ways to do that, but prefab without BIM is risky. BIM gives you the confidence to prefab. It lets you spool and assemble offsite with fewer surprises. It reduces exposure time in the field. It turns installation into production rather than improvisation. That’s not theoretical. It shows up in the field story about prefabricated underground racks—spooled, color-coded, and installed fast because coordination happened early and clearly.

When Do You Start BIM on Hard-Bid Jobs? The Truth: You’re Already Late

One of the sharpest lessons in this Q&A is about timing. On hard-bid jobs, teams often wait until after award to “consider BIM.” By that time, you’re already behind. You’re already mobilizing. You’re already buying materials. You’re already scheduling rough-in.The “empty shopping cart” analogy lands because it highlights urgency: if you’re trying to coordinate after the job is already underway, you’re shopping after the shelves are empty. You don’t have choices. You’re reacting. Hard-bid doesn’t mean “no BIM.” Hard-bid means you must decide fast and set expectations immediately, or the field will coordinate with saws and hammers.

When Do You Start on Design-Build? Get In During Design

Design-build is where BIM can deliver the biggest value because you can influence decisions before they’re locked. You can shape layouts, resolve major conflicts, and reduce constructability misses while there is still time to change the plan cheaply. This is not a software decision. It’s a risk decision. If you wait until late design or early construction, you lose the best opportunity: preventing problems instead of reacting to them.

Align BIM to the Rhythm: Using Takt to Time the Last-Level Coordination

This is where the conversation ties beautifully into production. BIM coordination must be aligned to the project rhythm. If you’re running Takt zones, you don’t coordinate “whenever.” You coordinate to the upcoming zones. You create last planner-style make-ready through BIM. You resolve clashes before the zone is active. This prevents a common failure: re-coordinating the same area multiple times because the schedule keeps shifting. When BIM is aligned to Takt, the team knows what must be ready and when. It creates a cadence for coordination, not a never-ending loop.

The First Meeting Agenda: Roles, LOD, Naming, Clash Process, Ownership

The kickoff meeting is where BIM either becomes real or becomes a mess. This episode emphasizes practical agenda items: define roles, define LOD expectations, define naming and file control, define the clash detection process, define meeting frequency, and define what “done” looks like. BIM meetings must produce decisions. If meetings become status updates with no resolution, the model will drift and the field will suffer.

A strong kickoff is the difference between:

• a coordinated install,
• and “we’ll figure it out in the field.”

Fast Signals Your BIM Effort Will Stall

• The BIM execution plan is vague or missing, so expectations are unclear from day one.
• Coordination meetings happen, but decisions don’t get made and ownership isn’t assigned.
• You start BIM late on a hard-bid job, after procurement and mobilization have already begun.
• Trade partners are asked to model without clear LOD, naming standards, or deliverables.
• Someone is still relying on “we’ll figure it out in the field” as the default strategy.

Meeting Frequency and Communication: Why “We’ll Talk Next Week” Breaks Coordination

One practical point that matters: BIM coordination needs a cadence that matches the work. If your zones are turning every week, then a slow coordination response time becomes a schedule risk. Waiting a week to answer a clash question is a week of exposure. That exposure shows up later as rework. Communication speed is part of production. This is why leaders must treat BIM like an operational system: fast feedback, clear ownership, and reliable commitments.

The 2D Holdout Problem: What to Do When Someone Says “We’ll Figure It Out in the Field”

Greg and Jason talk about the 2D holdout someone who refuses to participate in coordination and expects the field to solve it. The response cannot be aggression toward people. It must be system clarity. You make expectations explicit. You define required deliverables. You tie coordination participation to schedule risk. You escalate appropriately when needed, but you do it with facts. And you keep returning to the production truth: field coordination is expensive. Early coordination is cheaper.When a partner truly can’t model, you still need a plan: who models for them, how information is captured, and how their conflicts are resolved before installation.

The PM Question That Changes Everything: “What Do You Need?”

This quote is the leadership hinge. When PMs ask “what do you need?” they stop managing from assumptions. They start supporting production. They uncover constraints early. They build trust with trade partners. They turn coordination into collaboration. That question belongs everywhere: in BIM kickoff, in weekly coordination, in field huddles. It is a system-first mindset, and it’s how you prevent people from getting set up to fail.

A Practical BIM Playbook for PMs and Supers

• Build and publish a BIM execution plan early, with clear scope, LOD expectations, and ownership.
• Run a disciplined kickoff meeting that defines naming, clash process, meeting cadence, and “done.”
• Start BIM immediately on hard-bid jobs and during design on design-build jobs to prevent late pain.
• Align coordination to Takt or zone rhythm so the next areas are ready before crews arrive.
• Handle 2D holdouts with clear expectations, defined support, and facts about risk—not blame.

Connect to Mission

At Elevate Construction, the goal is stability teams that can plan, schedule, and flow without burnout. LeanTakt supports that stability by reducing variation and making work ready before it starts. BIM, when executed properly, is a major weapon against variation. It prevents conflicts from landing on the field. It protects foremen and crews from constant restarts. Jason Schroeder’s system-first lens is consistent: don’t blame the workforce for design conflicts. Fix the system early.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Conclusion

BIM is not about being fancy. It’s about refusing to “figure it out in the field.” It’s about reducing waste and variation by making decisions early with the right people in the room. If you want BIM to work, stop treating it like a side project. Build the execution plan. Start early. Run kickoffs with discipline. Align coordination to the zone rhythm. And lead with the most important question a PM can learn:

“The number one question a PM should learn is: what do you need?”Ask it. Mean it. Build the system around the answer. 

Frequently Asked Questions:

What is a BIM execution plan and why does it matter?
It’s the operating agreement for coordination defining roles, deliverables, LOD expectations, meeting cadence, file naming, and clash resolution. Without it, BIM becomes noise instead of control.

When should a team start BIM on a hard-bid job?
Immediately. Waiting until after mobilization increases schedule risk and forces the field to solve conflicts during installation.

How does BIM connect to Takt and LeanTakt?
Takt relies on stable zones and predictable handoffs. BIM supports make-ready by resolving clashes ahead of the zone work, reducing variation and protecting flow.

How do you get subcontractor buy-in for BIM?
Provide clarity: scope, expectations, deliverables, and how BIM will reduce rework and protect production. Buy-in increases when BIM is a system, not an undefined extra.

What do you do when someone refuses to participate and wants to “figure it out in the field”?
Set clear expectations, define who will model or coordinate the missing scope, tie the risk to schedule and cost with facts, and keep the focus on protecting the workforce from rework not blaming people.