What to Expect From Your Third-Party CxA

Posted on June 30, 2026June 30, 2026 by Danny Jiménez⁩

Read 24 min

What to Expect from Your Third-Party Commissioning Agent

There is a version of commissioning that happens too late, managed too loosely, with a commissioning agent who was not engaged until the interiors were half done and the controls contractor had not started designing their graphics. In that version, the final third of the project becomes a scramble testing conflicts with fire alarm verification, the preliminary balancing report is not ready when the occupancy application needs it, and the yellow brick road to substantial completion is a map the team is drawing while they are walking it. That version costs time, money, and the owner’s trust in the delivery team.

The alternative is a commissioning partnership that starts on Day 1, builds a relationship before there is pressure, and creates a coordinated schedule that maps every testing milestone, every inspection, and every report from the first pre-functional checklist through the final acceptance to a specific day on the calendar. That version lands the plane. This guide covers what to expect from your commissioning agent at each stage of the project and how to build the partnership that makes the commissioning process run rather than scramble.

Day 1: Find Out Who They Are

Most field teams make first contact with the commissioning agent somewhere in the middle third of the project around the time the interiors are underway and the mechanical and electrical systems are beginning to take shape. That timing is too late. By the time the commissioning agent is brought into active coordination, the controls contractor may have already begun designing building automation graphics without CxA input, pre-functional checklists may not have been prepared for the equipment that is already being installed, and the kickoff that should have established the commissioning schedule months earlier is being held under time pressure.

On Day 1 during dirt work, before structure, before anything that looks like commissioning is remotely close to being relevant find out who the commissioning agent is. Read their scope. Get their contact information. And then go meet them. Not a formal meeting. Lunch. A site visit. A conversation that establishes a relationship before there is anything to fight about or coordinate under pressure. The commissioning partnership that works at the end of the project is the one that was built at the beginning.

The reason this matters is that commissioning is not a service the agent performs on the building at the end of construction. It is a parallel process that runs alongside the entire project and must be integrated with the production plan from the first day. An agent who is connected to the project from Day 1 has months of context when the critical testing sequences arrive. An agent who is brought in at month twelve is starting from scratch during the most time-sensitive period on the project.

The One-Third Point: Plan, Team, and Kickoff

By the one-third point of the project when the structure is substantially complete or topping out and the interiors are beginning the commissioning plan and schedule should be in hand and the team should be fully assembled and oriented. This is the target date for the initial kickoff and expectations meeting for the overall commissioning process.

The commissioning plan is the document that governs the entire commissioning effort: the systems to be commissioned, the sequence of verification activities, the roles and responsibilities of each party, the documentation requirements, and the schedule of events from the first pre-functional checklist through final acceptance testing. It should be based on the Owner’s Project Requirements and the Basis of Design the foundational documents that define what the building is supposed to do and how it is supposed to do it. If the commissioning agent does not have a fully developed commissioning plan by the one-third point, that is the conversation to have now while there is still time to build the commissioning sequence into the production plan before the interiors phase accelerates.

The controls contractor deserves specific attention at this stage. The controls contractor designs and installs the building automation system the brain of the building that will eventually coordinate every mechanical, electrical, and life safety system into one integrated control network. BAS graphics take months to design, program, and commission. The sequence of operations must be tested and verified before functional performance testing can begin. If the controls contractor is not on board, actively designing their graphics, and connected to the commissioning agent by the one-third point, the commissioning schedule has a gap in it that will surface at the worst possible moment.

The kickoff meeting at or before the one-third mark should align the commissioning agent, the controls contractor, the GC’s project delivery team, and the owner’s representative on the commissioning schedule. When does the pre-functional checklist phase begin for each system? When do the BAS graphics need to be complete? When does the small black box the DDC controller that is the physical brain of the building automation system need to be installed and configured? When does the sequence of operations testing begin? When does test and balance start, and how does it sequence around fire alarm testing to avoid the fire smoke damper conflict that derails so many commissioning schedules?

A Note on Exterior Commissioning

The exterior skin consultant the specialist who verifies waterproofing, window performance, and curtain wall integrity needs to be engaged significantly earlier than the general commissioning kickoff. Performance mockups for curtain wall, metal panels, and exterior glazing systems have nine-to-eighteen-month lead times for materials. A performance mockup that is built and tested early enough to influence specification and installation decisions is a quality management tool. A performance mockup built after the materials are already on site is a documentation exercise.

The exterior skin commissioning process waterproofing reviews, window and glazing performance testing, air and water infiltration testing runs throughout the exterior installation phase. The exterior commissioning agent needs to be doing inspections continuously during this phase, not reviewing completed work after the fact. Every exterior component that is concealed during installation and later found to be deficient requires remediation that is far more expensive and disruptive than catching it during installation. Getting the exterior skin commissioning agent into the field during exterior installation is one of the highest-return investments the project team can make.

The Middle Third: Reports, Feedback, and Meetings

Once the commissioning plan is in place, the kickoff has aligned the team, and the pre-functional checklists are running alongside the installation, the commissioning effort settles into a rhythm: reports, feedback, and meetings. The commissioning agent is in the field verifying installations, issuing pre-functional checklists for trade sign-off, collecting completed checklists, and generating reports that track the state of each system against the commissioning plan’s requirements.

Pre-functional checklists are the critical quality gate in this phase. Each one verifies that a specific piece of equipment or system component is installed correctly, accessible for testing, powered up safely, and ready to proceed to startup. Getting pre-functional checklists kicked off during the rough-in phase not waiting until equipment startup is imminent is what gives the commissioning process its runway. If the PFC process is running while the interiors are still being built, the equipment is being verified incrementally rather than all at once under time pressure. When startup begins, the team already knows which systems are ready and which ones have open items.

The controls contractor’s work runs in parallel. BAS graphics must be complete before functional performance testing can begin on any system that the building automation controls. Sequence of operations must be reviewed and approved against the Basis of Design. Point-to-point testing verifying that every sensor, actuator, and control signal is correctly mapped in the BAS must be complete before the functional performance tests can confirm that the system behaves as designed. Each of those activities has a lead time, and the commissioning agent’s reports are the visibility tool that tells the team whether those lead times are being honored.

The Final Third: The Yellow Brick Road

The final third of the project is where the commissioning partnership either pays off or falls apart. Every system test, every inspection, every report, and every sign-off has a specific date and a specific sequence, and managing those events without a detailed calendar is how teams discover at the moment they need the certificate of occupancy that something required was not planned for.

The yellow brick road document is the tool for this phase. Not a schedule summary or a milestone list a month-by-month, day-by-day calendar that maps every commissioning event to a specific date. Elevator testing. Engineers’ walks. Fire alarm testing per floor. Building-wide fire alarm testing. Fire alarm testing with fire smoke dampers. Test and balance. Fire sprinkler walk and inspection. State elevator inspection. Functional performance testing for each system. Integrated systems testing. Final acceptance testing. Owner training sessions by system.

Each of those events has prerequisites, lead times, and coordination requirements that make sequencing them on a calendar a non-trivial exercise. Fire alarm testing and fire smoke damper testing must be sequenced carefully relative to test and balance if test and balance is running while fire alarm testing activates the fire smoke dampers, the air flow measurements will not reflect the building’s normal operating condition, and the balancing report will need to be repeated. The state elevator inspection in most jurisdictions requires advance scheduling that can be weeks out. Engineer walks need to be calendared with the engineers of record and the commissioning agent simultaneously.

What the commissioning agent should be providing in this phase and what to ask for explicitly if it is not being offered is active partnership on building and maintaining the yellow brick road document. One document, per critical system, mapping every event to a specific date and tracking its completion. Posted in the conference room. Reviewed in every weekly commissioning coordination meeting. Updated in real time as events are completed or rescheduled. This is the document that tells the team, on any given day in the final third of the project, exactly where they are on the path to substantial completion and what is at risk.

We are building people who build things. The project teams that build a genuine partnership with their commissioning agent from Day 1 who have the commissioning plan before the one-third mark, who start pre-functional checklists during rough-in, who build the yellow brick road document for the final third, and who partner with the controls contractor and the exterior skin consultant throughout are the teams whose substantial completion dates hold. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow including the commissioning partnership discipline that turns the final third of the project into a controlled landing.

A Challenge for Builders

On your current project, answer three questions today. First: have you met the commissioning agent not emailed, met and do you have a relationship with them that would make a difficult conversation easy? Second: is the commissioning plan in hand and connected to the production plan as a named section with its own schedule of events? Third: is there a yellow brick road document for the final third that maps every testing and inspection milestone to a specific day? For any of those gaps, close them this week. The commissioning partnership that lands the plane is built over months, not assembled in the final three weeks.

As Jason says, “Plan it first, build it right, finish as you go.”

On we go.

Frequently Asked Questions

Why should the commissioning agent be identified and engaged on Day 1 of the project?

Because commissioning is not an end-of-project service it is a parallel process that must be integrated with the production plan from the beginning. An agent engaged from Day 1 has months of context when the critical testing sequences arrive. They can influence pre-functional checklist design during rough-in, coordinate with the controls contractor before BAS graphics are already behind schedule, and build a commissioning schedule that is integrated into the production plan rather than bolted on at the end when there is no time to accommodate it.

What is the yellow brick road document and why is it essential in the final third?

The yellow brick road is a month-by-month, day-by-day calendar that maps every commissioning event every inspection, test, walk, and sign-off to a specific date in the final third of the project. It is the single source of truth for the path to substantial completion, reviewed weekly in commissioning coordination meetings and updated in real time. Without it, the team discovers conflicts fire alarm testing overlapping with test and balance, state elevator inspection unscheduled, engineers’ walks not calendared at the moment those events are needed, when there is no schedule flexibility left to accommodate them.

Why must fire alarm testing and test and balance be carefully sequenced relative to each other?

Because fire alarm activation triggers fire smoke dampers, which change the airflow patterns throughout the building. If test and balance is running measuring and adjusting air flows to match design values at the same time that fire alarm testing activates smoke dampers and changes those flows, the balancing report will not reflect the building’s normal operating condition and will need to be repeated. Sequencing fire alarm testing to be either complete before test and balance begins or held until test and balance is fully documented is a commissioning schedule requirement that needs to be established in the yellow brick road document before either activity starts.

If you want to learn more we have:

-Takt Virtual Training: (Click here)
-Check out our Youtube channel for more info: (Click here)
-Listen to the Elevate Construction podcast: (Click here)
-Check out our training programs and certifications: (Click here)
-The Takt Book: (Click here)

Discover Jason’s Expertise:

Meet Jason Schroeder, the driving force behind Elevate Construction IST. As the company’s owner and principal consultant, he’s dedicated to taking construction to new heights. With a wealth of industry experience, he’s crafted the Field Engineer Boot Camp and Superintendent Boot Camp – intensive training programs engineered to cultivate top-tier leaders capable of steering their teams towards success. Jason’s vision? To expand his training initiatives across the nation, empowering construction firms to soar to unprecedented levels of excellence.

Substantial Completion vs Final Completion Explained

Posted on June 30, 2026June 30, 2026 by Danny Jiménez⁩

Read 21 min

Substantial Completion vs. Final Completion: What Every Builder Needs to Know

Most construction projects reach the end of the field work without a clear, shared understanding of what substantial completion actually requires. The team has been focused on getting the building built the interiors done, the site work finished, the systems installed. And then the commissioning sequence arrives, the owner starts asking about the occupancy date, and it becomes clear that nobody defined the finish line precisely enough to know whether they are going to cross it on time.

That gap between finishing the work and achieving the legal and operational conditions that allow a building to be occupied is where projects lose weeks they did not budget for. Understanding what substantial completion requires, what the gap between substantial and final completion looks like, and what can happen in that window is not closeout knowledge. It is project planning knowledge, and it needs to be established and tracked from the beginning of the project, not discovered in the final month.

What Substantial Completion Actually Means

Substantial completion means the building is substantially done ready to be used for its intended purpose, in a condition where the occupant can safely occupy it. That definition has specific operational requirements that must all be true before a temporary certificate of occupancy can be issued, and each one has its own predecessor sequence that needs to be planned for rather than discovered at the end.

Life safety systems must be fully operational. The fire sprinkler system must be up and running, inspected, and certified. The fire alarm system must be functional and tested. Egress paths must be clear, compliant, and signed. ADA requirements must be fully met accessible routes, compliant hardware, appropriate signage, and any other element that governs the safe movement of occupants through the building. Elevators must be operational and have passed their state elevator inspection, which in many jurisdictions requires scheduling with a state inspector months in advance.

The architect must have issued the punch list. The engineers of record must have provided their sign-offs. The inspector’s green tags must be in hand for every system and space that required inspection. And the preliminary balancing report the HVAC and controls team’s documentation that the building’s air and water systems are balanced within design tolerances must be complete and submitted.

That last item deserves particular attention because it is the one that most often surprises teams who have not planned for it. Getting a preliminary balancing report typically takes anywhere from two to eight weeks after the systems are running and ready to test. That is a two-to-eight-week window that does not compress no matter how much urgency is applied, because the balancing process requires the systems to be stable and the testing to be thorough enough to be defensible. If that window has not been built into the commissioning schedule if the team is discovering it when they think they are two weeks from substantial completion the occupancy date is already slipping before anyone has acknowledged it.

The Window Between Substantial and Final Completion

Substantial completion is not the end of the project. It is the point at which the owner can occupy and use the building while the remaining work is completed. The window between substantial completion and final completion typically measured in weeks, though it can stretch to months on complex projects is where several specific activities need to happen in a defined sequence.

The punch list is the most visible work in this window. Every item identified by the architect, the commissioning agent, the owner, and the building department is tracked, assigned, completed, and verified before final completion can be declared. Punch list management in this window is a production activity, not an afterthought each item needs an owner, a completion date, and a verification step, and the whole list needs to be organized and moving before substantial completion rather than compiled in a rush the week after it.

Building flush is a requirement on many project types, particularly healthcare, laboratory, and educational facilities where indoor air quality standards are stringent. Flushing the building means running the HVAC system at a high air exchange rate for a defined period of time to remove from the air the volatile organic compounds, particulates, and chemical off-gassing from new materials, adhesives, paints, and finishes. The duration of building flush is specified by the design or by the standard the owner is building to, and it needs to be scheduled to fit within the substantial-to-final-completion window without compressing it or overshoot it. A team that does not plan for building flush duration discovers it when the owner’s move-in date is already fixed.

Functional performance testing the structured testing of how each system performs across its full range of operating conditions may have remaining items in this window. Some FPT activities can only be completed after the building is occupied, or after certain predecessor conditions are met that were not achievable before substantial completion. These need to be identified, sequenced, and scheduled into the final completion window rather than left as open items with no plan.

Why This Needs to Be Known at the Beginning, Not the End

Here is the problem with discovering the requirements for substantial completion in the final month of a project: by then, the schedule does not have enough flexibility to accommodate the prerequisites that were not planned for. The preliminary balancing report needs six weeks of HVAC system operation before testing can begin. The state elevator inspection needs to be scheduled months in advance in some jurisdictions. The building flush needs a specific duration that cannot be compressed. Each of those requirements has a lead time, and lead times that are not factored into the production plan early become schedule impacts that are factored in late.

The solution is to define substantial completion and final completion at the beginning of the project not as contractual abstractions, but as operational definitions that specify exactly what conditions must be true for each milestone to be achieved. What are the life safety systems that must be operational? What is the required completion status for each one? What inspections are required and who schedules them? What is the estimated timeline for the preliminary balancing report given the specific HVAC system on this project? What is the building flush duration required by the specification? What is the typical timing for architect punch list issuance on projects of this type?

Those questions answered at the beginning of the project produce a commissioning schedule that works backward from the substantial completion date with realistic predecessor durations. That commissioning schedule, built into the Takt production plan from Day 1 as a named section with its own wagons and milestones, is what gives the team visibility into the path to substantial completion months before they need to be on it. A pull plan that details out how the conditions of substantial completion will be met with a buffer before the deadline is the difference between a controlled landing and a crash.

Using Takt to Protect the Path to Substantial Completion

A CPM-managed closeout will crash, stack, and burden at the end. There is no other outcome when the final activities are compressed together in a schedule that has no production logic and no buffers, being executed by a team that is discovering prerequisites they did not plan for. The path to substantial completion on a CPM-managed closeout is managed by urgency rather than by sequence, and urgency at that stage costs money, damages quality, and produces a building that is delivered late and imperfectly.

A Takt-managed closeout has a visible path to substantial completion that was planned before the trades started the final third of the project. The building interiors, the exterior, and the site work are all on a production plan. The commissioning sequence is detailed out in the norm-level production plan with a day-by-day map for the final months. The preliminary balancing report is on the plan with a confirmed start date and a realistic completion date. The elevator inspection is scheduled. The building flush duration is in the plan. The architect punch list walk is calendared. The buffer before the substantial completion deadline is visible.

That buffer is not extra time the team is carrying to pad the schedule. It is the protection that allows the team to land the plane without crashing it to absorb the variation that will inevitably appear in the final commissioning sequence without that variation becoming a missed occupancy date. We are building people who build things. The project teams that define substantial and final completion early, build the commissioning path into the Takt production plan from Day 1, and track the conditions of substantial completion as rigorously as they track the production plan will be the teams whose buildings turn over on time with systems that work. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow including the commissioning scheduling discipline that protects the substantial completion milestone.

A Challenge for Builders

On your current project, answer three questions this week. First: has substantial completion been defined operationally not just as a contractual date, but as a specific list of conditions that must all be true? Second: does the commissioning schedule account for the preliminary balancing report timeline, and is that timeline specific to the HVAC system on this project rather than a generic estimate? Third: is there a buffer between the last planned commissioning activity and the substantial completion deadline and is that buffer visible on the production plan? If any of those answers is no, close the gap this week. The substantial completion deadline is decided by what is planned today, not by what is scrambled in the final month.

As Jason says, “Plan it first, build it right, finish as you go.”

On we go.

Frequently Asked Questions

What is the difference between substantial completion and final completion?

Substantial completion means the building is ready for its intended use and safe for occupancy life safety systems operational, elevators inspected and certified, fire sprinklers and alarms functional, ADA compliance confirmed, egress clear and signed, preliminary balancing report complete, punch list issued, engineer sign-offs in hand, and inspector green tags obtained. Final completion means the punch list is done, building flush is complete, all remaining functional performance testing is finished, and the building is fully turned over. The gap between them is typically weeks to a few months.

Why does the preliminary balancing report deserve special attention in commissioning planning?

Because it takes two to eight weeks to complete after the HVAC and controls systems are running and ready to test, and that window cannot be compressed by urgency. If the balancing report timeline is not built into the commissioning schedule with a confirmed start date based on system readiness, it will appear as a surprise in the final month of the project when there is no schedule flexibility left to absorb it. It is also a required predecessor to the temporary certificate of occupancy in most jurisdictions, which means a late balancing report directly delays occupancy.

Why should the definitions of substantial and final completion be established at the beginning of the project rather than the end?

Because the prerequisites for substantial completion have lead times elevator inspection scheduling, HVAC system operation required before balancing, building flush duration specified by contract or standard, FPT activities with their own predecessor sequences and those lead times need to be built into the production plan early to protect the milestone. Discovering them in the final month means they have already become schedule impacts. Knowing them at the start means they can be planned for, sequenced into the commissioning schedule, and tracked as production milestones from the beginning.

If you want to learn more we have:

Discover Jason’s Expertise:

How to Speak with Power as a Construction Superintendent

Posted on June 30, 2026June 30, 2026 by Danny Jiménez⁩

Read 20 min

Stop Saying Um, Ah, and Weak Filler Words: How Field Leaders Communicate With Power

Most superintendents and project managers do not think of themselves as professional communicators. They think of themselves as builders. And that is true but when was the last time a superintendent drove a nail or turned a screw? What they actually do all day is short-interval production planning, foreman conversations, trade partner coordination, owner updates, and safety briefings. Every one of those activities is professional communication. The building gets built because the communication works. When the communication is weak full of filler words, lacking confidence, missing the point the building feels it.

The builder identity is real and it matters. But it does not excuse communication that loses the room. A superintendent who cannot hold the owner’s attention in an update meeting, who cannot communicate a critical milestone problem in one sentence, or who loses the foreman’s engagement in the morning worker huddle is a superintendent who is leaving production capacity on the table. Communication is not separate from the work. It is the work.

What Filler Words Actually Do

An occasional um or ah is forgivable in any conversation. Nobody is listening to communication at that level of precision. What is not forgivable and what does damage to a leader’s credibility and effectiveness over time is a communication pattern that is dominated by filler words, trailing sentences, weak presence, and a lack of confidence in delivery. When a leader says “well, like, you know, I kind of, um, well, the thing is” before getting to the actual point, the people in the room spend more mental energy tracking the filler than absorbing the content. By the time the point arrives, the room has partially checked out.

People think four times faster than any speaker can speak. In a world where most listeners are consuming podcast content at two or three times the normal speed, patience for filler words is even lower than it has ever been. The filler words are not just a stylistic problem. They are a throughput problem they slow the transfer of information below the rate the listener can absorb it, which means attention drifts.

The Feedback Loop That Fixes It

The fastest way to reduce filler words is to hear yourself use them. That means creating a feedback loop, and there are several practical ways to do it. Recording a podcast, a meeting recap, or even a voice memo and listening back is one of the most powerful. The first hundred times you hear yourself say “like” three times in one sentence or trail off into “um” while searching for a word, the correction becomes urgent in a way that theoretical advice never achieves. Listen. Notice. Correct. Listen again. Repeat.

For leaders who are not producing recorded content, the equivalent is asking a trusted colleague for one piece of specific feedback after every significant meeting or presentation. Not general feedback one thing. “Did I have too many filler words?” “Was my delivery confident?” “Did I pause well when I needed time to think, or did I fill the pause with noise?” One specific question, one specific answer, one specific correction for the next time. That is the Plan-Do-Check-Adjust cycle applied to communication the same production thinking that governs the rest of the work, applied to the skill that makes the rest of the work possible.

The correction for most filler words is not eliminating them with willpower in the moment. It is learning to replace them with a pause. A pause is not weakness. A pause is confidence the willingness to let the room wait for a moment while a clear, complete thought forms before it is spoken. Most filler words exist to fill the silence that would otherwise exist between thoughts, and most listeners experience that silence as more comfortable than the filler words that replace it. Embrace the pause. Let the thought form. Then speak it.

Speaking in Soundbites

One of the most transferable communication skills for field leaders is the ability to speak in soundbites to compress a complex situation into one clear, complete sentence rather than narrating the whole chain of events that produced the situation.

Here is the contrast. An owner asks what the biggest problem with the schedule is. Option one: “Well, the thing didn’t ship on the thing and I talked to Larry and they said that they could do the other thing and this and then I called the supplier and…” The owner has stopped listening by the third clause. Option two: “The material vendor for this application said it will be four weeks until they can get that material to us, which is two weeks late, and there are no other options.” One sentence. The situation, the impact, and the constraint clear, complete, and actionable.

That is a soundbite. It is not a performance skill. It is a thinking discipline. Before speaking, answer these three questions internally: what is the situation, what is the impact, and what does the listener need to know to make a decision or take action? Compress those three things into one or two sentences. Then say them. Everything else is context that can be provided if the listener asks for it and if they ask, they are engaged, which is exactly where a good communicator wants their audience.

Tailoring Communication to the Hearer

Every person in every meeting is operating from a different context, a different vocabulary, and a different set of priorities. The communication that works perfectly in a foreman huddle does not work in an owner update meeting. The communication that works in a scheduling review does not work in a conversation with a designer who has never been on a construction site.

Tailoring communication to the hearer not to the speaker means consciously asking what the person in front of you needs to know, in what language they understand it, and at what level of detail they can act on it. A technical explanation of how the path of critical flow is affected by a delayed trade is the right communication for a superintendent or a PM. It is not the right communication for a designer who is hearing “path of critical flow” for the first time. For the designer, the right communication is: “That design deliverable, which is tracking late right now, will push the back end of the schedule out by a month. We want to find an option where you get the time you need without that impact.” Same situation. Different audience. Different language.

This is not dumbing information down. It is amplifying the listener’s ability to engage with it. The best communication meets the listener where they are and moves them where they need to go which is exactly the definition of coaching. A coach does not transfer information. A coach moves people forward. Every conversation a field leader has is either moving someone forward or not, and the difference between the two is usually how well the communication was tailored to who was in the room.

Confidence, Presence, and Physical Delivery

None of the above matters if the physical delivery undermines it. Shoulders back. Eye contact held, not avoided. Voice projected out to the whole group, not directed at the floor. A pace that is deliberate rather than rushed. Confidence is not an attitude. It is a posture, a vocal projection level, and a willingness to hold the room’s attention without apology.

The real-time feedback loop for physical presence does not require a recording or a colleague’s input. It requires watching the room. Are people engaged? Are they leaning in, making eye contact, nodding? Or are they checking phones, losing focus, and starting to disengage? The moment attention starts to drift is feedback, and it is immediate. Something in the delivery changed a drop in energy, a cluster of filler words, a sentence that went on past its natural endpoint. The correction is equally immediate: change the pace, increase the energy, end the sentence, ask a question, redirect to the person who is drifting. Professional communicators watch the room as carefully as they watch the plan.

We are building people who build things. The superintendents and project managers who invest in their communication who practice speaking in soundbites, who build feedback loops into their daily interactions, who tailor their language to the person in front of them, and who project confidence through their presence rather than just their title are the leaders whose meetings move people forward, whose trade partners stay engaged, and whose projects benefit from communication that actually works. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow including the communication discipline that makes every conversation more effective.

A Challenge for Builders

In your next significant meeting or foreman huddle, ask one trusted person afterward: what is one thing I could have done better? Write the answer down. Make one specific correction before the next meeting. Then ask again. Three meetings. Three corrections. Three improvements. That is the feedback loop that builds a professional communicator out of a builder who communicates and the difference between the two is the difference between a meeting that moves people forward and one that everyone leaves without knowing what to do next.

As the Stoic philosopher Epictetus wrote, “First say to yourself what you would be; and then do what you have to do.”

On we go.

Frequently Asked Questions

What is the fastest way to reduce filler words in professional communication?

Create a feedback loop by recording yourself a meeting recap, a voice memo, or a video and listening back. Hearing your own filler words is more motivating than any theoretical advice. Alternatively, ask a trusted colleague for one specific piece of feedback after each meeting. The correction for most filler words is replacing them with a deliberate pause rather than eliminating them with willpower. A pause communicates confidence. A filler word communicates the absence of it.

What does speaking in soundbites mean for a construction field leader?

It means compressing a complex situation into one or two clear, complete sentences before opening your mouth. Identify the situation, the impact, and what the listener needs to know to act then say those three things in the shortest possible form. Everything else is context that can be provided if the listener asks. Leaders who speak in soundbites hold attention. Leaders who narrate the full chain of events lose it before they reach the point.

How do you tailor communication to someone who does not have a construction background?

Replace technical terminology with outcomes the listener understands. A designer does not need to hear about the path of critical flow and buffer depletion. They need to hear that a specific deliverable is tracking late and will push the project end date by a specific amount of time, and that the team is looking for options that protect both the design quality and the schedule. Same situation, same urgency communicated in language the listener can engage with and act on.

If you want to learn more we have:

Discover Jason’s Expertise:

Functional Performance Testing: The Complete Guide

Posted on June 30, 2026June 30, 2026 by Danny Jiménez⁩

Read 20 min

Functional Performance Testing: What Every Superintendent Needs to Know to Enable Commissioning

Most superintendents understand the broad shape of commissioning: systems get tested, problems get fixed, the building eventually passes its inspections and the owner moves in. What most of them underestimate is the specific role the field team plays during functional performance testing, the phase where active testing of all building systems under varying operating modes either validates everything the team built or surfaces every problem that was never fully resolved. This phase is not the commissioning agent’s responsibility to manage alone. It is a daily clearing operation that the superintendent owns, and the pace at which the team clears deficiencies and enables the next test determines whether the project finishes on time or absorbs weeks of additional schedule that nobody budgeted for.

The Pain That Shows Up Too Late

The pattern on projects that struggle through commissioning is consistent. The mechanical, electrical, and plumbing rough-in is complete. The controls contractor finished their cable pulls. The test and balance is in progress. Everyone believes commissioning is close. And then the commissioning agent starts asking questions that reveal how much prerequisite work was never actually verified: the building automation system does not have vertical connectivity throughout the building, the air handlers are not ready to be sequenced, the filters have not been installed, several areas of the building are not clean enough to start the process, and the documentation for half the systems is incomplete. The schedule assumed commissioning would begin in week forty. It is now week forty-two and the commissioning agent is still saying no to every question.

The System That Produced the Delay

The schedule that put commissioning at week forty was built on the assumption that the prerequisites would be complete. The prerequisites were never tracked as a daily deliverable with the same urgency as the production work on the floors. Nobody assigned ownership for each prerequisite item. Nobody tracked the controls contractor’s BAS connectivity progress against the commissioning start date. Nobody confirmed with the mechanical trade partner that the air handlers were in a condition to receive filters and be sequenced. The commissioning agent was not engaged early enough to surface the full list of what would be required before testing could begin. The project team discovered the gap when the commissioning agent arrived and started saying no, and by then the schedule had already absorbed the consequence of the delay before anyone understood why it was happening.

What Functional Performance Testing Actually Requires

Functional performance testing is exactly what the name describes: active testing of building systems under various operating modes to verify that they perform per the Owner’s Project Requirements, the Basis of Design, and the Sequence of Operations. That sounds technical, and it is, but the superintendent’s role in it is not technical. The superintendent’s role is to clear every roadblock between the current condition and the commissioning agent’s ability to run the next test.

Before testing can begin, several prerequisite conditions must be in place. Permanent power to the building must be established and stable. The building must be enclosed and clean to the standard the commissioning agent requires. The controls contractor must have completed the building automation system to the point of vertical connectivity throughout the building, meaning signals can travel from devices on each floor up through the backbone to the BAS software and graphics. The pre-functional checklists for each system must be complete. Test and balance must be sufficiently advanced for the mechanical systems to be commissioned in sequence. And any additional prerequisites that the commissioning agent, the mechanical trade partner, and the electrical trade partner identify must be addressed before testing is authorized to begin.

Every Question Will Get a No, and That Is Useful

Here is something worth preparing for: during the prerequisites phase and throughout functional performance testing, the answer to almost every question the superintendent asks the commissioning team will be no. Can we start the air handlers? No. Can we sequence it this way? No. Can we put filters in now? No. Can we do the pre-functional checklist on this system? No. The building is clean enough on floors three through eight but you need to finish two before we start up there. No.

Every one of those nos is useful information. Each no identifies a specific condition that needs to be resolved before the next step can happen. The superintendent’s job is to take each no, convert it into a specific action item, assign an owner, put it on a visual strategy document, and track it to completion. The no is not an obstacle to forward progress. It is a roadmap of exactly what forward progress requires. The teams that treat the commissioning agent’s nos as problems to be argued with fall further behind. The teams that treat each no as a task to be cleared move through prerequisites faster and start functional performance testing sooner.

What Daily Management Looks Like During Testing

Once functional performance testing begins, the superintendent’s primary focus shifts from prerequisites to daily responsiveness. The commissioning agent is running tests. Every failed test produces a deficiency: a piece of equipment that did not respond correctly, a controls point that did not communicate, a graphics update that was not made, a procedure in the sequence of operations that did not execute as designed. Each deficiency needs to be tracked, assigned to the responsible party, and cleared before the commissioning agent can retest that system and move it toward acceptance.

The discipline that makes this work is daily communication with the commissioning agent and daily tracking of every open deficiency. Not weekly. Not whenever there is a site meeting. Daily. The commissioning agent needs to know that the team heard the deficiency list from yesterday, knows who is working on each item, and can confirm when each fix will be ready for retest. The superintendent needs to know what tests are scheduled for today and what conditions need to be in place before each one can run. That daily communication loop is what prevents deficiencies from aging, which is the single most common reason functional performance testing extends beyond its scheduled window.

The Parallel Track That Cannot Wait

While functional performance testing is running on the mechanical, electrical, and plumbing systems, several other critical systems are tracking toward their own inspection and acceptance milestones. These cannot wait until functional performance testing is complete:

Elevator inspections require coordination with the local authority having jurisdiction and have lead times that do not bend to the project schedule
Fire alarm testing requires point-to-point verification throughout the entire system, and that testing cannot happen simultaneously with HVAC test and balance
Fire sprinkler inspections require their own coordination and sign-off sequence
Pressurization and egress systems have specific testing requirements that need to be completed and documented before the certificate of occupancy can be issued

The superintendent who is managing functional performance testing without also tracking all of these parallel systems toward their own completion dates will find that the functional performance testing finishes and the project is still not ready for occupancy because the elevator is not inspected, the fire alarm has open points, and the pressurization test was never scheduled. All of those tracks need to be visible on the same daily management view, moving simultaneously toward the same end date.

Enable the Commissioning Agent. That Is the Job.

The frame that clarifies everything about the superintendent’s role in this phase is simple: your job is to enable the commissioning agent to do their job. Every prerequisite you clear is an enablement. Every deficiency you track and close is an enablement. Every trade partner you coordinate to be in the right place for the right test at the right time is an enablement. The commissioning agent cannot pass systems that are not ready to be tested. The field team builds the readiness. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Functional Performance Testing Flows When the Prerequisites Were Done Right

The projects that move through functional performance testing efficiently are the ones that treated prerequisites as a production deliverable from the beginning of the commissioning phase. They tracked BAS connectivity daily. They confirmed filter installation with the mechanical trade before the commissioning agent arrived. They engaged the controls contractor early enough to know whether the software and graphics would be ready when testing was scheduled to begin. They had a pre-functional checklist tracking system that showed, in real time, which systems were ready and which were not. The commissioning phase is not where those decisions get made. It is where they get revealed. As W. Edwards Deming taught: quality is built in, not inspected in. The quality of the commissioning outcome is built in the weeks of prerequisite work that happen before the commissioning agent runs the first test. Do that work with the same discipline you bring to production, track it with the same daily accountability you bring to the weekly work plan, and the commissioning phase will flow the way the rest of the project is supposed to flow.

On we go.

Frequently Asked Questions

What is functional performance testing and why does it matter to the field superintendent?

Functional performance testing is the active testing of building systems under various operating modes to verify they perform according to the Owner’s Project Requirements, Basis of Design, and Sequence of Operations. It matters to the superintendent because the pace at which deficiencies are cleared during testing directly determines when the project can achieve substantial completion and occupancy. The commissioning agent can only move as fast as the field team enables them to, which means every failed test that goes unresolved for days costs the schedule exactly that many days.

What are the most common prerequisites that delay the start of functional performance testing?

The most frequent delays come from incomplete building automation system connectivity, meaning the controls contractor has not established full vertical signal connectivity from devices on each floor through the backbone to the BAS software. Incomplete pre-functional checklists, areas of the building that have not been cleaned to the commissioning agent’s standard, unavailability of permanent power, and air handling units that are not in a condition to be started or filtered also appear regularly as prerequisites that were assumed to be on track but were never actively verified.

Why does the commissioning agent say no to so many requests and how should the superintendent respond?

The commissioning agent says no because each no represents a specific condition that has not yet been met, and testing a system before its prerequisites are in place produces unreliable results and can damage equipment. The correct superintendent response is to treat each no as a specific task: document the condition that is not met, assign it to the right trade partner or contractor, establish a completion date, and track it daily until it is resolved and the commissioning agent can be asked again. The no is a roadmap, not a dead end.

If you want to learn more we have:

Discover Jason’s Expertise:

Improvements to the Last Planner System

Posted on June 27, 2026June 27, 2026 by Danny Jiménez⁩

Read 23 min

Enhancements to the Last Planner System That Will Change How You Run Projects

The Last Planner System is one of the most valuable tools in construction. It gave the industry huddles, collaborative planning, short-interval commitments, and a language for connecting foremen to the schedule. It is the foundation for how crews make and keep promises, and it has helped countless projects find a rhythm that CPM scheduling alone could never produce.

But here is the deal. The Last Planner System, as it is commonly taught and practiced, has gaps. Some of those gaps are producing outcomes that directly contradict what the system is supposed to achieve. They are punishing trade partners for behaving well, rewarding fragile plans, and prioritizing a lagging metric over the leading indicators that actually predict project success. Those gaps need to be addressed, and that is exactly what this post is about.

The Pain That Motivated These Enhancements

Here is a scenario that plays out constantly on construction projects across the country. A trade partner works hard, plans well, and finishes their scope slightly ahead of the committed date. In a healthy system, that would be celebrated. That is the sign of a prepared crew, a realistic plan, and a trade that respected the process. Instead, under how the Last Planner System is often applied, that trade gets marked red. They are penalized for finishing early, flagged as a deviation, and in some versions of the meeting, have their schedule accelerated to squeeze out the remaining buffer.

The message that sends is devastating. It says that finishing ahead of schedule is a problem. It says that having breathing room at the end of a task is waste. It says that the system rewards pushing every trade to the edge of their capacity with no margin for quality control, inspection, cleanup, training, or transition. And then the same system wonders why punch lists are enormous, why trades demobilize sloppily, and why the last three months of every project become a disaster. The system produced those results. The trades did not fail the system. The system failed to protect them.

Why Buffers Are Not Sandbagging

Let’s settle this argument definitively. A buffer at the end of a task is not sandbagging. It is production realism. It is the same principle that makes every reliable manufacturing operation work, and it is the reason that “no schedule should ever be made without buffers.” Wagons have buffers. Zones have buffers. Sequences have buffers. Trains have buffers. And individual trade activities need buffers because the work that happens at the tail end of a task matters enormously.

Think about what a trade partner actually needs to do when their installation work is complete. They need to clean up the zone. They need to do a final quality control walk and correct any deficiencies before the next trade arrives. They need to complete the final sign-off and inspection. They need to demobilize their tools and materials without creating chaos in the next crew’s workspace. They need to transition mentally and physically to the next activity and prepare their team for what comes next. None of that happens if every second of the allotted time has been packed with installation work and there is no room left to breathe.

The analogy is a university student who finishes their assignment early and uses the remaining time to review their notes, improve their submissions, prepare for the next assignment, and maintain their wellbeing. If the professor immediately moved the next assignment earlier the moment the student turned in their work, the student would learn one thing: never finish early again. That is exactly what many Last Planner implementations are teaching trade partners on construction projects today.

What Needs to Change in the Last Planner System

These are the specific enhancements that make the Last Planner System more aligned with Lean principles, Takt Production System logic, and the reality of how flow actually works in the field. The first change is around percent plan complete (PPC) and what counts as green. A task that is completed on time or reasonably early should be marked green, not flagged as a deviation. The system should only mark tasks red when they are not complete by the committed date. Finishing ahead of schedule is not a problem. It is a signal that the plan was realistic, the trade was prepared, and the buffer did its job. Targeting 100% PPC with good trade flow is the goal, not something to be suspicious of.

The second major change is to shift the primary metric from PPC to roadblock removal. PPC is a lagging indicator. It tells you what already happened. Roadblock removal is a leading indicator. It predicts whether the work can actually flow two to three weeks out. A project that is removing roadblocks aggressively and consistently is far more likely to hit its milestones than a project that is chasing a PPC number while roadblocks pile up upstream. Leaders should not even begin tracking PPC as a primary performance signal until they have established a consistent roadblock removal discipline at least two to three weeks in advance.

The third enhancement is around the language of “constraints.” The Last Planner System uses the word constraint to describe anything that could impede a task. But a constraint and a roadblock are fundamentally different things, and mixing them up causes teams to treat everything the same way when they actually require different actions. A roadblock is a solvable blocker. Go remove it. A constraint is a limiting condition that must be planned around. Manage it. When teams call everything a constraint, they debate endlessly about whether it can be removed instead of just removing what can be removed and designing around what cannot.

How Takt Planning Enhances What the Last Planner System Does

One of the most important upgrades is understanding that the Last Planner System cannot stand alone as a planning methodology. It was never designed to. It is a short-interval commitment system, not a production design tool. When it is paired with a Takt Production System, the results are dramatically different because the Takt plan provides something the Last Planner System cannot: a visual, time-and-location plan that makes trade flow, zone sequencing, and buffer placement visible before the work begins.

With a Takt plan in place, you can see whether pull plans in one zone are accidentally stacking trades in adjacent zones. That is one of the most common and costly errors in Last Planner practice. A team will do a pull plan for Zone A, feel confident about it, and then realize too late that the same trade has been committed to Zone B and Zone C in overlapping windows. Pull plans must always be compared across all active zones. If you are only looking at one zone at a time, you are flying partially blind, and the stacking will show up as chaos in the field.

The Takt plan also allows the project team to plan in meaningful detail well in advance, rather than defaulting to the Last Planner principle that you plan in greater detail only as you get closer to doing the work. That principle makes sense when you are using a CPM schedule as your only planning tool, because CPM does not give you enough granularity or reliability to plan far out. But with a Takt plan built on real quantities, historical production data, and collaborative pull planning with trade partners, you can have a high-confidence plan that reaches all the way to project completion, and then refine sequences as each trade mobilizes.

The Behaviors the System Must Stop Rewarding

These are the patterns that current Last Planner practice inadvertently reinforces, and that need to be actively addressed at the leadership level.

Marking a task red when it was completed early instead of on time, which trains trades to hold work artificially and never finish ahead of the committed date.
Accepting pull plans that push trades faster than they can maintain quality, finish as they go, or transition cleanly between zones.
Tracking PPC as the primary success metric before establishing roadblock removal as the foundational discipline.
Running pull planning sessions for individual zones without cross-referencing other zones to check for trade stacking.
Treating “finishing as you go” as a nice-to-have rather than a non-negotiable that requires end-of-activity buffers to make possible.

When a project does not finish as it goes, the punch list grows until it becomes a project within a project. The last three months of a build consumed by rework, touch-up, and inspection are not an inevitability. They are the predictable outcome of a system that never gave trades the buffer they needed to finish correctly the first time. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

What the Enhanced System Looks Like

The Last Planner System, when enhanced with these principles, becomes something that genuinely protects trade partners and produces reliable flow rather than just measuring how often commitments were missed. The daily afternoon huddle becomes the primary rhythm for surfacing roadblocks and confirming next-day readiness. Roadblock removal becomes the most important conversation in every coordination meeting. PPC becomes a learning tool, not a performance weapon, used to diagnose what broke and trace it back to its root cause in the First Planner, the Takt plan, or the coordination system. Trade partners are asked to commit to plans that meet milestones and maintain flow, not plans that push them to the edge of their capacity with no margin left.

The goal is a system where honest commitments are made, buffers are honored, quality work is finished in the zone before anyone moves on, and the whole team is advancing together in a stable rhythm. That is what Lean construction is supposed to produce. That is what the Takt Production System and the Last Planner System, working together as part of the Integrated Production Control System, can deliver when they are implemented correctly. “No schedule should ever be made without buffers. Wagons have buffers, sequences have buffers, trains have buffers, zones have buffers, phases have buffers, and the project itself has a buffer.” On we go.

Frequently Asked Questions

Why is finishing a task early sometimes marked as a problem in the Last Planner System?

Because some practitioners interpret early completion as evidence that the original commitment was not aggressive enough, meaning the trade sandbagged their estimate. But this interpretation ignores the legitimate value of end-of-activity buffers for quality control, cleanup, inspection, and transition. A trade that finishes slightly early and uses that time to do the work right is behaving exactly as a well-run production system should encourage. The system should mark that green and celebrate it, not penalize it.

What is the difference between a roadblock and a constraint, and why does the distinction matter?

A roadblock is a solvable blocker: something in the environment that is in the way and can be removed with the right action. A constraint is a limiting condition that cannot be easily changed and must be planned around. When teams treat everything as a constraint, they spend time debating whether it can be fixed instead of just fixing what can be fixed. When teams understand the distinction, they remove roadblocks fast and design their plans intelligently around true constraints.

Why should roadblock removal be prioritized over percent plan complete?

PPC is a lagging indicator. It tells you what already went wrong after the fact. Roadblock removal is a leading indicator. It predicts whether work can flow smoothly two to three weeks out. A project focused on removing roadblocks ahead of the train is actively preventing schedule failure. A project focused on PPC is measuring schedule failure after it happens and calling that control.

How does the Takt Production System enhance the Last Planner System?

The Takt plan provides the visual, time-and-location production design that gives the Last Planner System a reliable foundation to operate from. Without it, pull plans are often built against a CPM schedule that cannot accurately predict trade flow or zone sequencing. With it, teams can see buffer placement, trade movement across zones, and potential stacking conflicts before they become field problems.

What does “finish as you go” actually require from the planning system?

It requires that end-of-activity buffers be built into every task so that the trade partner has time to clean up, inspect, quality-control, sign off, and demobilize cleanly before the next crew arrives. Without those buffers, trades are forced to leave unfinished work behind as they rush to meet the next commitment, and that unfinished work accumulates into the massive punch list that consumes the final months of the project.

If you want to learn more we have:

Discover Jason’s Expertise:

The Honeybadger

Posted on June 27, 2026June 27, 2026 by Danny Jiménez⁩

Read 20 min

Be the Honey Badger: The Construction Mindset That Changes Everything

Most of the losses in this industry are not caused by bad projects. They are not caused by bad locations, bad weather, bad owners, or bad timing. Most of the losses in construction come from mentality. From leaders who stop at the obstacle instead of going through it. From field engineers who wait to be told what to do instead of figuring it out. From project teams that let circumstance become excuse.

The antidote to all of that has a name, and it is not a system or a software or a training module. It is an animal. It is a honey badger. And once you understand what a honey badger actually is, you will never look at leadership, problem-solving, or performance the same way again.

The Pain That Keeps Projects Stuck

Walk a struggling project and you will find the same pattern. The field engineer is waiting on information that no one has delivered. The foreman is standing around because materials were not staged. The superintendent is firefighting the same problem for the third time this week. And somewhere above all of that, a project manager is writing a report about why the schedule slipped instead of going into the field and doing something about it.

The common thread is not incompetence. These are often talented, hard-working people. The common thread is passivity in the face of friction. The mindset that says, “This is hard, so I will wait for someone to fix it.” That mindset is everywhere in construction, and it is costing companies hundreds of thousands of dollars per project in delay, rework, miscommunication, and lost momentum. The system has trained people to document problems instead of destroy them.

The System Created the Pattern

Here is what needs to be said clearly. The passivity that shows up in construction teams is not a character defect. It is a learned behavior, and the system taught it. When leaders consistently punish people for making decisions without permission, when there is no psychological safety to act boldly and be wrong, when the project culture rewards caution over initiative, people stop going after problems. They start managing their exposure instead of solving the issue. The system failed to create an environment where tenacity is rewarded, and then it blames individuals for lacking it.

That is the failure pattern. And the solution is not to demand more from people without changing the environment. The solution is to develop the honey badger mindset at the individual level while simultaneously building the systems and culture that reward it.

What a Honey Badger Actually Is

The honey badger is a mammal found across Africa, Southwest Asia, and India, and it is one of the most remarkable animals on earth. It has thick skin, ferocious defensive capabilities, and very few natural predators. It will go after a cobra, get bitten, absorb the venom, recover, and then finish the job. It will push through a beehive, get stung repeatedly, and keep going because it is not deterred by discomfort.

In captivity, honey badgers have been documented opening gates, stacking objects to build escape routes, and solving problems that should be far beyond their capability. They are fearless, resourceful, independent when they need to be, and collaborative when the situation calls for it. They have large brains relative to their size. They waste nothing. They eat everything they pursue, down to the bone. And they have one of the longest lifespans of any animal their size because they are built to last. That is not just a fun animal fact. That is a blueprint for leadership in construction.

The Honey Badger in the Field

At Elevate Construction and in the Field Engineer Boot Camp, the honey badger is the official mascot of the field engineer role. The credit for that connection goes to Steve Snedeker, who first made the association, and it is one of the most accurate and useful mascots in the entire program. Because what does a great field engineer actually do? They figure things out. They absorb chaos so that the crews behind them can have stability. They remove friction before it becomes a problem. They get into hard spaces, find the information that does not exist, create the answer that was not provided, and deliver it to the people who need it without being asked twice.

That is the honey badger in practice. Not reckless. Not chaotic. Tenacious, intelligent, nimble, and utterly committed to getting it done regardless of what is in the way.

What the Honey Badger Mindset Looks Like in Practice

This is not just for field engineers. The honey badger mindset applies to every leadership role on a construction project, from foreman to project executive. Here is how it shows up across the work.

A honey badger field engineer does not wait for the information to arrive. They go find it, verify it, and get it into the hands of the crew before the crew needs it. A honey badger foreman does not accept that the zone is not ready. They make it ready, get the obstacles removed, and protect their crew from friction.
A honey badger superintendent does not manage the schedule on paper from the trailer. They go to the zone, see what is actually happening, identify the real constraints, and attack the biggest problem first.
A honey badger project manager does not blame the trade partner for the delay. They get into the coordination, find the root cause, and remove it. The pattern in each case is the same: go toward the problem with intelligence, tenacity, and the expectation that you will get it done. If the task bites you, sleep it off and go back after it. The cobra is still there waiting.

Why Mentality Determines Outcomes

Here is the foundational truth behind all of this. Construction projects do not fail because of circumstances. They fail because of the mentality of the people leading them. A clean, safe, well-organized project with all the right tools and systems in place can still fall apart if the leaders do not have the mindset to drive it. And a difficult project, with all the obstacles and dysfunction and chaos that come with it, can still be stabilized and delivered when the right mentality is present.

Mentality sets the standard. It determines how far a leader will go before they stop. It determines whether an obstacle becomes an excuse or a problem to solve. Core Framework Concept 85 describes this as the mental setpoint: the internal thermostat that governs what conditions a leader is willing to accept. If the setpoint is low, the project will drift to low. If the setpoint is honey badger, the project will be held to a different standard entirely, because the leader in the zone will not stop until it is right.

Most of what holds people back in construction is not external. It is internal. Learning a new scheduling tool looks like a cobra. Building a Takt plan for the first time looks like a cobra. Having a hard conversation with a trade partner looks like a cobra. The question is not whether the cobra is real. The question is whether you are going to go get it. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Building a Team of Honey Badgers

The goal is not to find one honey badger and put them in charge of everything. The goal is to build a team where every person has been trained to operate with this mindset, where the culture rewards tenacity and problem-solving, and where people feel safe enough to act boldly without waiting for permission at every step.

That requires two things working together. First, individual development. People have to be trained in the honey badger attributes: tenacity, fearlessness, resourcefulness, intelligence, nimbleness, and the willingness to not waste what they have been given. Second, the system has to support it. Psychological safety has to exist so that people who go after the cobra and get bitten do not get punished for trying. They need a team and a culture that says, “Good. Sleep it off. Go back out.” When both are present, the results are extraordinary.

The workers and the leaders who thrive in construction are not the ones who had the easiest projects. They are the ones who went through the hardest ones and came back stronger. They built their setpoint by going after cobras and surviving. They became the honey badger through repetition, training, and an environment that expected that level of them and supported them in achieving it.

“We have got to figure out how to not throw people away going forward.” That means building them up. Training them well. Creating conditions where they can develop the mentality and the skills to be the honey badger. That is the work of Elevate Construction, Jason Schroeder, and LeanTakt, and it is the work of every construction leader who is serious about building people who build things. On we go.

Frequently Asked Questions

What is the honey badger mindset in construction?

It is the combination of tenacity, fearlessness, resourcefulness, and intelligence that allows a leader to go after problems instead of waiting for someone else to solve them. It means absorbing difficulty without being stopped by it, recovering from setbacks without losing momentum, and treating every obstacle as something to be defeated rather than avoided.

Why is the honey badger the mascot for field engineers?

Because the field engineer role is fundamentally about removing friction before it reaches the crew. Great field engineers do not wait for information to arrive. They go find it, verify it, and deliver it before anyone needs to ask. That requires exactly the traits the honey badger embodies: independence, resourcefulness, intelligence, and relentless follow-through.

Is the honey badger mindset something you can train?

Absolutely. Mentality is not fixed. It is developed through training, repetition, and exposure to environments that expect and reward tenacity. The Field Engineer Boot Camp at Elevate Construction specifically trains this mindset alongside the technical skills required for the role. People grow into the honey badger through coached experience, not just encouragement.

What is the difference between being a honey badger and being reckless?

A honey badger is fearless but not thoughtless. The animal has a large brain relative to its size, and it uses it. Being a honey badger in construction means going after problems with intelligence and preparation, not just aggression. It means figuring it out before charging in, being nimble when the situation changes, and being strategic about which cobras to go after first.

How do leaders create a team culture where the honey badger mindset thrives?

By rewarding tenacity, providing psychological safety, and making it clear that going after problems is expected and supported. When leaders punish people for acting without permission or for failing while trying, they train passivity. When leaders celebrate the person who identified the roadblock and removed it before anyone else knew it existed, they build a team of honey badgers.

If you want to learn more we have:

Discover Jason’s Expertise:

Maslow’s Hierarchy of Needs

Posted on June 27, 2026June 27, 2026 by Danny Jiménez⁩

Read 22 min

What Maslow’s Hierarchy of Needs Has to Do With Your Construction Project

You want total participation from your workforce. You want workers who show up engaged, who care about quality, who raise problems instead of hiding them, who feel a sense of ownership in the work they are doing. You want the kind of culture where every person on the project is giving their best every single day. That is a worthy goal. It is the right goal.

But here is the problem. You cannot get to total participation if the rungs underneath it have not been built. You cannot skip the foundation. And most jobsites in this country are trying to demand high-level engagement from people whose most basic needs are not being met in the field. That is not a worker problem. That is a system problem, and it starts with leadership.

The Pain We Keep Ignoring

Walk any major project in the country right now and you will find the same pattern. Leadership is frustrated that workers are disengaged. Foremen are complaining that the crew does not care. Superintendents are baffled that safety behavior is inconsistent and that continuous improvement ideas never come from the field. And nobody is asking the right question: have we actually provided the conditions that make engagement possible?

Most construction companies spend significant time and money on culture initiatives, lean training, engagement programs, and recognition efforts. Those are all valuable. But if the bathrooms are filthy, if there is no clean place to eat lunch, if workers do not feel physically safe or psychologically secure, then no culture program in the world is going to unlock the level of participation that leadership is looking for. You cannot build the upper floors of a building without laying the foundation first. The same principle governs people.

The System Did Not Support Them

The reason this gap exists is not that workers are unwilling. The reason is that the system has not been designed to meet their needs at each level. Leaders talk about accountability and performance without first asking whether the environment they have created is one where performance is even possible. That is the real failure pattern here, and it shows up on projects of every size.

A worker who does not know whether their job is secure next week is not going to raise a continuous improvement idea in the morning huddle. A worker who has no clean place to eat lunch and no decent bathroom is not going to feel a sense of pride in the project. A worker who has never had someone walk up and shake their hand, say their name, or ask how they are doing is not going to feel the sense of belonging that drives commitment. The system failed to create those conditions, and then it blames the worker for the results.

A Story Worth Telling

There was a point in Jason’s career when he was an area superintendent at a large company, highly skilled, deeply loyal, having given fourteen years to an organization he genuinely believed in. The work was good. The projects were meaningful. But at a local Walmart, standing in the grocery aisle counting change to make sure the bank account had enough to cover $4.35 in food for a family of eight, something broke.

It was not anger. It was clarity. The most foundational need, the ability to provide food for his family, was not being met. Not because of poor leadership or poor effort, but because the compensation system had never caught up with the value being delivered. And once that foundational need was unmet, no amount of loyalty, pride, or organizational identity could hold things together. He took his skills to a different company, received a raise of roughly thirty percent, and within a few years saw his salary grow by more than a hundred thousand dollars. The people who remained at the original company still say it was the biggest mistake they ever made. That is what happens when you do not take care of the foundational rungs for your people.

Teaching the Framework: Maslow on the Jobsite

Maslow’s Hierarchy of Needs identifies five levels of human motivation, arranged in a pyramid: physiological needs at the base, then safety needs, then belonging, then esteem, and finally self-actualization at the top. The insight is that people do not move naturally up the pyramid unless each lower level is reasonably met first. And while Maslow developed this framework in a psychological context, it maps directly and practically onto what construction workers experience on the jobsite every day.

Physiological needs are food, water, warmth, and rest. On a construction project, this means a clean place to eat, access to drinking water, somewhere to wash their hands, a functioning bathroom, shade or heat depending on the season, and scheduled breaks that allow the body to recover. These are not luxuries. They are the baseline. And if they are not provided, workers are already starting their day in a state of deficit that no amount of engagement strategy can overcome.

Safety needs are next, and in construction this means two things: physical safety and psychological safety. Workers need to know that the site is genuinely safe to work in, that hazards are addressed instead of tolerated, and that following the safety rules is the norm, not the exception. But they also need psychological safety, the assurance that they can speak up, raise a problem, admit a mistake, or ask a question without being humiliated, dismissed, or threatened. When psychological safety is absent, problems stay hidden until they become catastrophic. The system fails to surface what it needs to see.

Belonging is the middle of the pyramid, and this rung is one that construction consistently underinvests in. Do workers feel connected to a social group on the project? Does the morning huddle actually create a sense of team, or is it a five-minute checklist that nobody pays attention to? Do people know each other’s names? Does the most remote worker on the jobsite feel like they are part of something, or like an anonymous body filling a slot in a schedule? Connection is not soft. It is a production strategy. People work harder, communicate more, and stay safer when they feel they belong.

Signs Your Jobsite Is Not Meeting the Needs

Before moving to the upper rungs, it is worth doing an honest audit of whether the foundation is actually in place. These are the signals that something is missing. Workers eat lunch in their trucks or on the ground because there is no designated, dignified space for a meal.

The bathrooms are rarely cleaned and are treated as a reflection of how leadership values the workforce.
No one from leadership has approached the most remote worker on the project in the last week to ask how they are doing. Workers do not know what winning looks like for the day, the week, or the project overall.
People feel afraid to raise problems because they have seen what happens to those who do. If any of those land, the foundation is not as solid as the engagement program assumes. And until those things are addressed, the upper rungs will always underperform.

Esteem and Self-Actualization Are Within Reach

Here is where it gets exciting. When the lower rungs are in place, the upper two become genuinely achievable on a construction project, and they drive the kind of results that transform a team. Esteem needs, the sense of prestige and accomplishment, can be met in ways that cost almost nothing. Tours with the owner or facilities manager where workers are asked to show off what they built. A short video of a worker or crew posted to social media highlighting the quality of the installation. A handshake and a thank you from a superintendent who actually means it. These are not gestures. They are signals to a person that they matter, that their work matters, and that the organization sees them as more than a unit of labor.

Self-actualization is the top of the pyramid, and it is the level where continuous improvement ideas come from, where workers engage creatively and bring their full capability to the project. When workers feel safe, connected, valued, and proud, they start looking for ways to make the work better. They shoot improvement videos. They flag inefficiencies. They offer ideas in the huddle. They drive their families past the building on weekends and say, “I built that.” That is not a soft outcome. That is the highest expression of a production system that was designed to serve the people in it. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Building the Whole Pyramid

The vision at Elevate Construction, and the mission that drives Jason Schroeder’s work across the industry, is that every worker on every project reaches that top rung from a work standpoint. Not just a few high performers. Every single person on the crew. That means they are achieving their full potential, contributing their creative ideas, and doing work they feel genuinely proud of.

That outcome is not achieved through a poster on the trailer wall or an annual safety banquet. It is achieved by leaders who take seriously their responsibility to design a system that provides for people at every level of the pyramid. Clean bathrooms. Good water. A morning huddle that actually connects people. Psychological safety that makes problems visible. Recognition that makes workers feel seen. Opportunities that make them feel capable.

Chaos at work becomes chaos at home. When a worker’s needs are not met in the field, they carry that home to their family. When a worker’s needs are met and they feel a genuine sense of belonging, esteem, and purpose, that flows home too. Protecting flow is always a family protection strategy. And building the full hierarchy of needs into your project system is one of the most powerful ways to honor the people who show up every day and build the things that matter. “I would love it if each worker received 15 minutes, even 5 minutes, of training from the crew leader every day. Workers aren’t just going to figure everything out. Everyone needs training.” On we go.

Frequently Asked Questions

What does Maslow’s Hierarchy of Needs have to do with a construction jobsite?

It maps directly to what workers experience every day. Each rung of the pyramid, from physiological needs to self-actualization, has a concrete equivalent in the field, from clean bathrooms and drinking water all the way to recognition, belonging, and the chance to contribute ideas that improve the work. Leaders who understand the hierarchy can design a system that unlocks genuine engagement rather than demanding it without creating the conditions for it.

Why is psychological safety so important in construction?

When workers do not feel safe raising problems, problems stay hidden. Hidden problems become expensive surprises. Psychological safety is what allows a crew to surface roadblocks, flag quality concerns, and communicate honestly with foremen and superintendents before small issues become catastrophic ones. It is not a soft concept. It is a production strategy.

How can a superintendent create a sense of belonging on a large project?

The morning worker huddle is the most powerful tool available. Done well, it creates a social group, communicates the plan, and gives every worker a sense of connection to the project. Beyond that, learning names, conducting brief check-ins with the most isolated workers, and inviting owners or facilities managers to tour the work so workers can show off what they built all contribute significantly to that sense of belonging.

What does self-actualization look like on a construction project?

It looks like a worker who brings a continuous improvement idea to the morning huddle. It looks like a crew that shoots a before-and-after video of a process they improved. It looks like a worker who drives their family past the finished building and says they built that. Self-actualization is not an abstract concept on a jobsite. It is the natural result of a system that took care of everything below it.

What is the first step a leader can take to start meeting the hierarchy on their project?

Walk the project and ask an honest question at each rung: are workers’ physiological needs met, do they feel safe physically and psychologically, do they feel connected to a social group, are they being recognized, and are they being given a chance to contribute. The answers will reveal exactly where the gaps are and where to start.

If you want to learn more we have:

Discover Jason’s Expertise:

Straining at Gnats and Swallowing Camels

Posted on June 27, 2026June 27, 2026 by Danny Jiménez⁩

Read 22 min

Stop Straining Gnats and Swallowing Camels: The Construction Leader’s Problem-Weighting Crisis

There is a trap that catches experienced construction leaders all the time. It is not laziness. It is not incompetence. It is not even bad intentions. It is something far more subtle and far more expensive: the inability to tell the difference between a small problem you can see clearly and a massive problem you cannot see at all.

That gap in perception is costing the industry hundreds of thousands of dollars per project, burning out teams, keeping crews away from their families, and driving good superintendents out of the business. And the painful part is that it is entirely preventable.

There is a passage in Matthew 23 that captures this perfectly: “Ye blind guides, which strain at a gnat, and swallow a camel.” The idea is to fuss about trifles while ignoring the more serious matters. It is an ancient observation about human nature, and it plays out on jobsites and in company offices every single week. The gnat is easy to see, easy to grab, easy to feel productive about. The camel is enormous, but somehow invisible until it is already inside you.

The Story That Started This Conversation

Here is a real situation that illustrates this precisely. A large construction company was in trouble on a major project. Liquidated damages were a real threat. Craft turnover was hurting productivity. Self-perform work was suffering. The schedule was slipping, and the pressure was mounting on everyone from the superintendent to the project executive. The company needed focused, practical help, and they needed it fast.

A training and coaching engagement was put together for their superintendent team. Not a generic seminar. A real site audit, a Takt planning effort, system development, meeting observation, the whole package. The price was roughly half of the normal consulting rate for that scope of work, roughly $4,000 to get started, and the kind of daily consulting investment that typically runs four to eight thousand dollars per site visit at minimum.

The project manager received the invoice and shut the whole thing down because it was coded to the wrong budget line. The training never happened. The coaching engagement was canceled over a coding problem. Meanwhile, the project continued losing hundreds of thousands of dollars in poor performance, the team continued working brutal hours, and the families of those workers continued absorbing the chaos that flowed from an unstable jobsite. They strained at the gnat of a $4,000 invoice and swallowed a camel made of overtime, rework, stress, and schedule loss.

Why This Keeps Happening

The reason this pattern repeats itself across companies of all sizes is not a character flaw in any individual leader. The system is set up to make gnats visible and camels invisible. That is the real diagnosis here.

Most project managers are only given direct visibility into general conditions and general requirements budgets. That means they can see what was spent on office supplies, internet service, and portable toilets. They can scrutinize a $4,000 consulting invoice and feel like they are doing their job by pushing back on it. But they typically do not have direct line-of-sight into the overall contingency, labor productivity gains, or the compounding downstream cost of a superintendent team that has never been trained on how to stabilize production flow. The financial system is designed to surface the gnat while hiding the camel. Leaders manage what they can see, and then the things they cannot see eat them alive.

This is the core of the problem: too many leaders are too focused on visible things that are not urgent or important, and not focused enough on things that are urgent and important but are not visible. The budget line is visible. The craft turnover trend is not. The toilet paper order is visible. The root cause of schedule slippage is not. And so the organization keeps optimizing for the wrong things, not because people do not care, but because the system is not designed to surface what matters most.

Signs You Are Straining Gnats

Watch your own patterns this week. Here are the signals that your attention has drifted toward the wrong problems.

You are debating truck specifications or hard hat colors while your schedule reliability is below fifty percent and nobody has identified the root cause.
You are frustrated about a software subscription cost while your foremen have never received a day of structured training on how to plan their zone.
You are managing the general conditions budget line by line while the overall contingency is eroding and no one in the room is asking why.
You are in a two-hour meeting about office supply spending while your superintendents are working sixty-hour weeks trying to recover a schedule that was never stabilized to begin with.

If any of those land close to home, the system is not serving you. The system failed to surface what actually matters, and that is what needs to change.

What Good Problem-Weighting Looks Like

A legendary general superintendent who spent decades at one of the country’s most respected construction firms used to say that when he arrived on a project, he would immediately go find the most difficult area and attack it first. He would own that space. He would not spend his early days on the easy wins or the comfortable tasks. He went straight for the hardest problem on the board and took it down while his energy was high and his team was fresh.

That is Core Framework Concept 97 in practice: tackle the biggest problem first. Start with the most complex area while energy is high, and the rest becomes manageable. It sounds simple, but it runs completely counter to how most leaders naturally behave. Natural human tendency is to start with what is easy to see and easy to resolve. The satisfaction of closing small items is real. But the impact is minimal, and while we are celebrating the closed gnats, the camels are multiplying.

Good problem-weighting requires leaders to actively seek out what is invisible. You cannot wait for the camel to become visible, because by then it has already been swallowed. The question every construction leader needs to ask at the start of every week is this: what is the most important problem I am not currently looking at? That question requires discipline. It requires getting off the inbox and onto the jobsite. It requires standing in the middle of a zone and watching until you see what you were not looking for. It requires financial literacy that goes well beyond general conditions. And it requires the courage to run toward the hard problems instead of the comfortable ones.

Run Toward the Camels

There is a phrase that has stayed with Jason Schroeder from a leader he deeply respected: run to your work, not away from it. That is the antidote to gnat-straining. It is an act of discipline to run toward the most difficult, most uncomfortable, most invisible problems on your project or in your company. It is far easier to run toward things that feel urgent, that produce visible outputs, that make you look busy and productive.

The gnats are everywhere and they will always be waiting for your attention. But the camels require you to go find them. For construction companies specifically, this means being willing to invest in training when the project is struggling, not after it has fully collapsed. It means looking hard at labor productivity, not just labor cost. It means examining the root cause of why your best superintendents are burning out rather than accepting turnover as an industry norm. Planning is a moral responsibility, and poor planning steals evenings and weekends from people with families depending on them to come home in a good frame of mind.

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

The Camels You Cannot Afford to Miss

Here is the other side of this conversation. Once you know what to look for, the camels become recognizable. They are hiding in plain sight, just outside the edges of what the system currently shows you.

Is your company genuinely profitable, or are you chasing more volume to cover for margin problems that have never been addressed?
Does your project have healthy cash flow, or are you managing collections and pay applications reactively because no one owns that proactively?
What is actually going wrong with your Takt plan in the field, and have you stood in the zone long enough to see the root cause?
Are your superintendents developing week over week, or are they repeating the same firefighting patterns on every project because training was never prioritized?
Are you dealing with the actual people problems on your team, or are you hoping they resolve themselves while the morale quietly erodes?

These are the camels. They are not easy to see. They require you to dig, to ask better questions, to invest in things that do not show up as a line item. But they are the ones that determine whether your project succeeds or fails, whether your team stays together or falls apart, and whether the people on your crew go home whole or broken.

The Families Behind Every Camel

Here is the part of this conversation that does not show up in a budget report. When a project spirals into overtime and chaos because the leadership team was straining at gnats, the people absorbing that pain are not just the crew. They are the families. They are the spouses sitting up late wondering when their partner will get home. They are the kids who have learned not to ask if Dad can make it to the game. They are the relationships slowly eroding under the weight of a project that never had to be this hard.

Chaos at work becomes chaos at home. That is not a soft observation. It is a system truth. When production is unstable, the people delivering that production carry the instability home with them. Protecting flow is not just a production strategy. It is a people strategy. It is a family protection strategy. And every time a leader chooses to ignore the real problems in favor of the easy ones, they are making a choice that ripples well beyond the jobsite.

Every leader in construction right now should be asking: what is the most important problem I am not looking at? Where am I spending energy on the visible while the invisible is quietly costing me hundreds of thousands of dollars, burning out my team, and pulling good people away from their families? Find the biggest problem in the room and take it down first. That is not reckless. That is what real leadership looks like. “Run to your work, not away from it.” On we go.

Frequently Asked Questions

What does it mean to “strain at gnats and swallow camels” in a construction context?

It means spending leadership energy on small, visible, easy-to-resolve problems while ignoring the large, difficult, invisible problems that are actually eroding the project. The budget line is the gnat. The root cause of craft turnover is the camel.

Why do leaders naturally focus on visible problems rather than invisible ones?

Because visible problems produce a measurable sense of resolution when addressed. The system rewards that behavior with outputs you can point to. The invisible problems require discipline and courage to surface, and most organizations have not built the habits to go find them.

How can a company build a culture of focusing on the most important problems?

It starts with making the invisible visible. Create systems that regularly surface financial health, production reliability, labor stability, and superintendent readiness. Then model the behavior from the top: leaders who run toward hard problems train their teams to do the same.

What is the real cost of straining a gnat instead of addressing a camel?

The direct financial loss is significant, but the deeper cost is the overtime absorbed by the team, the craft workers who leave for steadier environments, and the families that carry the weight of an unstable project long after the workday ends.

What is the first step a leader can take to stop straining at gnats?

Ask a different question at the start of every week: what is the most important problem I am currently not looking at? That single shift in attention consistently surfaces what matters most before it becomes catastrophic.

If you want to learn more we have:

Discover Jason’s Expertise:

Mistakes vs. Negligence

Posted on June 27, 2026June 27, 2026 by Danny Jiménez⁩

Read 22 min

The Difference Between a Mistake and Negligence: What Every Construction Leader Must Understand

There is a moment on construction projects that every leader eventually faces. Someone produces seriously deficient work, a layout error that costs two months and hundreds of thousands of dollars, a quality failure that cascades into something that changes the project’s trajectory entirely. The leader holds the person accountable. And almost immediately, someone in the organization asks the uncomfortable question: are we creating a culture where people get punished for making mistakes? That question sounds principled. It sounds like the kind of thing a good leader should take seriously. The answer is that nobody should face consequences for an honest mistake. But the premise of the question is wrong, because what just happened was not a mistake. And until leaders can make that distinction consistently and precisely, quality culture in construction will continue to drift in exactly the direction that nobody intends.

The Pattern That Keeps Repeating

Walk any construction company long enough and you will find quality failures that were not surprises. The person who produced them had a history. The type of error was predictable. People around the situation could have told you it was coming before it happened, because the behaviors that produce that kind of failure had been visible for months. And yet when the failure occurs, it gets labeled a mistake, handled with a coaching conversation, and within a few weeks everyone is waiting for the next one. The project absorbs the cost. The team absorbs the frustration. The pattern continues because nobody changed anything, and nobody changed anything because the failure was framed as a mistake rather than what it actually was.

The System That Created the Confusion

The lean construction movement, which Jason Schroeder fully endorses, has correctly established that systems should be examined before people are blamed, that workers should not be scapegoated for outcomes produced by bad processes, and that psychological safety requires an environment where people can surface problems without fear of retribution. All of that is right. The gap is that the system-first framing can be misapplied to situations where the process is sound, the culture is clear, the standards have been communicated, and the failure is happening because a person is choosing not to follow them. At that point, the failure is behavioral rather than systemic. It has a different name and it requires a different response from the leader.

The Story That Forces the Distinction

Jason Schroeder describes overseeing a surveyor who was technically sophisticated in every measurable way. This person understood automatic levels, total stations, and GPS equipment. They could discuss the principles of accurate survey work with authority. They were professionally credentialed, genuinely knowledgeable, and personally pleasant to work with. They also produced massive layout mistakes repeatedly, errors that changed jobs, caused months of delay, and cost hundreds of thousands of dollars. These were not the stumbles of someone learning an unfamiliar task. They were the predictable output of someone who did not believe they needed to double-check their work, did not take adequate field notes, and did not follow the verification procedures the survey department had established.

When the surveyor made another significant error, Jason sent him home for three days without pay and initiated a performance improvement plan. The pushback came quickly from others in the organization. Was this the culture they wanted to create, where people were marginalized for making mistakes? Jason’s response was precise: that was not a mistake. The behaviors that produced it had been observable for a long time. The process gaps in the survey department had already been identified and corrected. The standards had been clearly communicated. What remained was a person whose behavior was not aligned with those standards, not because of ignorance or inexperience, but because of a habitual pattern of not caring enough to follow the process. That is negligence. And negligence requires a different response than a mistake, not because punishment is the goal, but because the failure to distinguish between them builds the wrong culture.

When a Mistake Is Actually a Mistake

Before any leader can respond correctly to negligence, they have to know what a genuine mistake looks like. Jason describes asking a group exactly that question: when would it be acceptable for someone to make a mistake? The answers were specific and worth internalizing. The task is genuinely new to the person, and they are doing their best with the knowledge currently available to them. The person consistently asks for help when uncertain. They care about the quality of their work and demonstrate it through their behavior and habits. They are honest when something goes wrong and admit it without concealing it. They use the quality checklist and the verification processes the team has established. They participate in pre-activity meetings and plan their work before executing it. They have a known habit of checking their work, and people around them would describe them as conscientious.

When all of those things are true and a failure still occurs, something in the system did not catch what it should have caught. The process needs to be examined. The training may have a gap. The tools may need improvement. The right response is to lean into the problem alongside the person, support them through the correction, understand what the system missed, and fix it. There is no consequence for the person because there is nothing at the behavioral level to correct. The person did everything they were supposed to do. The system failed them. That is the accurate diagnosis, and it points to the accurate response.

What Negligence Actually Looks Like

Negligence looks like the inverse of everything that defines a genuine mistake. These are the signals that separate a behavioral failure from a systemic one:

The checklist and verification processes exist, are clearly communicated, and the person consistently does not use them
The proper tools are available and required, and the person does not use them even knowing they should
Pre-activity meetings are scheduled and expected, and the person does not genuinely prepare or participate
When something goes wrong, the person attempts to hide it or minimize it rather than surfacing it immediately
The person has a known pattern of not asking for help when uncertain and not double-checking completed work
The failure is predictable to anyone familiar with the person’s habits, not a genuine surprise

When those conditions describe the quality failure, the word mistake is inaccurate. The accurate word is negligence. Not as a judgment of the person’s character or worth as a human being, but as a precise description of what actually occurred. A negligent failure is one where the person knew what they were supposed to do, had the process and the tools available to do it, and chose not to.

The Organizational Immune System

Jason describes two medical analogies that clarify what happens when a system fails to recognize and respond to a threat within itself. Cancer cells carry surface receptors that make them appear normal to the body’s immune system. The body does not recognize them as enemies, does not fight them, and the cancer grows unchecked because the mechanism that should address it is not activated. Leprosy damages the nervous system, removing the body’s ability to feel pain. Injuries that would normally trigger immune response and repair go undetected, and tissue degrades without the body knowing to intervene. In both cases, the damage results not just from the disease itself but from the failure of the body’s recognition and response system.

A construction team that cannot distinguish negligence from mistakes is exhibiting the same failure mode. The harmful behavior is present. The organizational immune system does not recognize it as something requiring a response. The damage accumulates quietly. And every day the leader allows the negligence to continue without consequence, they are not simply tolerating it. They are authorizing it. Authorized behavior becomes normal behavior. Normal behavior becomes culture. Culture becomes process. At that point, the three variables that could have been addressed independently, the process, the culture, and the behavior, are locked in alignment around the wrong standard.

What This Means for the Team That Is Doing It Right

The people on the team who are using the checklist, double-checking their work, asking for help when uncertain, and caring about the quality of their output watch every day to see how the organization responds to the people who are not. When the answer is nothing, the signal they receive is that the effort they are putting in does not matter, that the standard they are holding themselves to is not actually the standard, and that the people around them can produce negligent work without consequence. Over time, that signal degrades the behavior of the people who were doing the right things. The standard does not just fail to improve. It actively pulls the whole team down toward the lowest tolerated behavior, and every conscientious worker on that team bears the cost of a standard the leader chose not to enforce.

Respect for the workers who are doing the work correctly requires that their standard actually be enforced as the standard. That is not separate from the lean construction principle of dignity and respect for people. It is an expression of it. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

The Standard You Set Is the Standard You Get

The closing point from this episode belongs to the leader. If negligent behavior exists on a team and has not been addressed, that is not the negligent person’s culture. It is the leader’s culture. The choice to allow the behavior, made through inaction, is the choice to build a culture where that behavior is within the range of what is accepted. When the behavior continues, it is not because the person decided independently to be negligent. It is because the culture communicated, through the leader’s consistent non-response, that negligent behavior is permitted. As Eric Thomas put it directly: if you let people treat you any kind of way, it becomes a culture. What you permit, you promote. What you promote becomes the standard. Know the difference between a mistake and negligence, respond correctly to each one, and build a culture where the workers doing the work right can trust that the standard they are holding themselves to is the actual standard of the organization.

On we go.

FAQ

What is the most reliable way to tell the difference between a mistake and negligence on a construction project?

Examine the behavior pattern surrounding the failure rather than the failure itself. If the person used their process, asked for help, checked their work, and the error still happened, it was a mistake. If the failure was predictable because those behaviors were consistently absent, it was negligence.

Why is it harmful to treat negligence as a mistake when responding to a quality failure?

It removes the consequence the behavior requires and signals to the entire team that the behavior is within the range of acceptable conduct. Over time, that signal becomes the culture, and the culture pulls the standard down toward the lowest tolerated behavior.

How does the system-first principle of lean construction apply when negligent behavior is present?

System-first means examining whether the process, training, and standards were in place before concluding a failure is behavioral. Once those conditions are verified to be sound, a failure that occurs because the person chose not to follow the process is a behavior problem, not a system problem.

What is the difference between a consequence and a punishment in this context?

A consequence is corrective in intent: it signals clearly that a behavior produced an unacceptable result and creates a strong incentive for change, delivered with clarity and respect. A punishment is inflicted to cause suffering as retribution, which is not the goal and not what accountability in a healthy organization looks like.

What should a leader do when they realize negligent behavior has been tolerated without consequence?

Stop allowing it immediately, communicate the actual standard clearly, and begin enforcing it consistently from that point forward. The discomfort of the transition is real, but continuing to authorize negligent behavior through non-response is not a leadership choice that serves the team or the workers who have been doing the work correctly all along.

If you want to learn more we have:

Discover Jason’s Expertise:

What Is Takt Planning? Beginner’s Guide to Construction Scheduling

Posted on June 26, 2026June 26, 2026 by Danny Jiménez⁩

Read 20 min

What Is Takt Planning? A Beginner’s Guide to Construction Scheduling

Most construction scheduling tells you what needs to happen and when. It gives you a list of activities, a set of dates, and a bar chart that is technically accurate and practically inaccessible to the people who need to build from it. The superintendent cannot see the train of trades in a CPM bar chart. The foreman cannot see where their crew goes next. The project manager cannot see trade stacking until the trades are already stacked. The format hides the most important thing a production plan needs to show: motion.

Motion is the word that unlocks what Takt planning is. A construction project is not a static list of deliverables. It is a sequence of people moving through a building crews entering zones, completing work, handing off to the next trade, and flowing to the next zone while a successor crew enters behind them. That movement is the production system. And a scheduling format that cannot show movement cannot manage production. It can only report on it after the fact, when the damage is already done.

Takt planning shows motion. That is the foundational difference, and everything else follows from it.

Four Dimensions: Why Time-by-Location Is the Right Format

Think about the difference between a photograph and a video. A photograph captures X, Y, and Z the three spatial dimensions that describe where something is. A video adds T time and that fourth dimension is what turns a static image into something that shows motion. The same logic applies to construction scheduling.

A time-by-deliverable CPM schedule captures what needs to be delivered and when two dimensions of information organized around contract milestones. It does not capture where the work is happening or how the crews are moving through the building. There is no motion visible. The schedule is a static picture that requires the reader to mentally reconstruct the movement it describes, which is why CPM schedules are accurate documents that field teams cannot navigate from.

A time-by-location format adds the spatial dimension. Time runs across the top the horizontal axis, showing the project timeline from left to right. Location runs down the left the vertical axis, showing the zones and areas where the work happens. An activity on a Takt plan is not just a bar with a start date and an end date. It is a bar that shows when a trade is in a specific zone, and when the next bar for that trade shifts down and to the right, the diagonal line that connects them is the motion the trade moving from one zone to the next over time.

That diagonal trade flow is what you look for on a Takt plan. Not bar charts. Diagonals. Each diagonal line represents a trade flowing continuously through the building entering Zone A, completing their scope, entering Zone B, completing their scope, and continuing through every zone in the phase without stopping, restarting, or being asked to be in two places at once. When the diagonals are clean and parallel, the production system is flowing. When they cross or overlap, trades are stacking. When they go flat, a trade has stalled. The format makes the production system’s health immediately visible without requiring a schedule health analysis.

What Takt Planning Is Actually Based On

Here is the most important clarification for anyone new to Takt planning: the system is not Takt-time based. It is flow-based. That distinction matters because it is the source of the most common misunderstanding the idea that Takt planning requires a single, uniform Takt time applied to every trade in every zone across the entire project.

That is not correct. Different trains of trades can run at different Takt times within the same phase. A fast trade and a slow trade running on separate trains at their natural rhythms, with the trains properly offset from each other, is a Takt plan. A phase where some sections of the building require a longer Takt time because of density or complexity, while other sections move at a faster rhythm, is a Takt plan. The defining characteristic is not the uniformity of the Takt time. It is the presence of three things: a time-by-location format, diagonal trade flow that protects every trade from stacking and overburdening, and buffers in the system that absorb variation and protect the milestone.

If those three things are present the format, the flow, and the buffers the system is Takt planning, steering, and control, regardless of whether every trade is on the same Takt time. If they are absent, the schedule is not a Takt plan, regardless of what it is called.

The Production Plan: Everything Fits

One more foundational concept before going into what the plan looks like in practice: everything fits on the Takt production plan. There is no pre-Takt. There is no out-of-Takt. There is no non-Takt area of the project that requires a different format. High schools, airports, bridges, civil infrastructure, medical office buildings, data centers, multi-family housing all of it fits into the time-by-location format. The Takt Production System is not a niche tool for repetitive building types. It is a production planning format that works for any type of project because the format is organized around how crews move through space over time, which is universal to construction regardless of what is being built.

When the production plan is the single reference for the whole project not a master schedule for the owner, a pull plan for the trades, a look-ahead for the field, and a CPM schedule for the contract office, all maintained as separate documents the whole delivery team can see as a group, know as a group, and act as a group. The production plan replaces the collection of disconnected planning documents with one coherent picture of the project from start to finish.

What a Takt Plan Looks Like: Reading the Format

Looking at a Takt production plan in InTakt, the layout follows the same structure every time. Time runs across the top in the macro view, week by week; in the norm view, day by day; in the micro view, hour by hour or even minute by minute for the most detailed production tracking. The specific timescale depends on which planning horizon is being addressed. The macro is strategic. The norm is operational. The micro is for precision control in phases where the production rhythm is tight enough to track at that level of resolution.

Location runs down the left the phases, the areas within each phase, and the zones within each area. The hierarchy makes it easy to navigate: click into a phase to see the areas, click into an area to see the zones, and the zones are the production units where the work is actually managed. The train of trades flows through those zones from left to right and top to bottom simultaneously each activity moving one zone to the right as time passes and one row down as the trade advances through the building.

The diagonal trade flow rhythm is the signature visual of a correctly formatted Takt plan. Each trade has a color, and each colored bar flows diagonally through the zone grid entering Zone 1 on day one of the Takt time, completing and entering Zone 2 on day six, completing and entering Zone 3 on day eleven. The stagger between trades the gap between one colored diagonal and the next is the buffer. When that stagger is consistent and the diagonals are parallel, every trade has the space, time, and clear zone it needs to work in one-process flow: plan, build, finish, move, plan, build, finish.

That diagonal rhythm is what enables every other Lean concept to function. One-process flow requires it. Goldratt’s rules of flow require it. The Last Planner System requires it as a base to filter the look-ahead and weekly work plan from. The pull plan produces it. The Takt calculator optimizes it. Everything in the production system depends on the diagonal trade flow being protected and the time-by-location format is what makes protecting it visible.

We are building people who build things. The field leaders who learn to read a Takt production plan who can look at a diagonal trade flow and immediately know whether the production system is healthy or whether something needs to be addressed are the leaders whose projects produce the flow that protects their trade partners, their workers, and their families. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow including the Takt planning literacy and InTakt implementation that turns the production plan into a tool the whole team can navigate from.

A Challenge for Builders

Find a CPM bar chart for a current project and compare it to a Takt production plan for the same phase either one you have built in InTakt or one from a comparable project. Ask three questions. Can you see where each trade is in the building at any given point in the schedule? Can you see which trades are active simultaneously in the same zone? Can you see the stagger between trades that represents the buffer protecting each one from the one behind it? If any of those answers is no in the CPM chart and yes in the Takt plan, you are looking at the difference between a schedule and a production plan. That difference is where projects are won or lost.

As Jason says, “Flow over busyness.”

On we go.

Frequently Asked Questions

What does “time-by-location” mean and why does it matter for construction scheduling?
Time-by-location means the schedule is organized with time on the horizontal axis and physical location zones, areas, phases on the vertical axis. This format makes the motion of trades through the building visible as diagonal lines flowing from zone to zone over time. A time-by-deliverable format like CPM organizes activities around what needs to be delivered by when, which hides the spatial sequence and makes trade stacking and overburdening invisible until they are already causing damage.

Does Takt planning require a single uniform Takt time across the whole project?
No. Takt planning is flow-based, not Takt-time-based. Different trains of trades can run at different Takt times within the same phase. Different sections of the building can operate at different rhythms based on work density. The defining requirements are the time-by-location format, diagonal trade flow that protects every trade from stacking and overburdening, and buffers in the system.

What is the diagonal trade flow and why is it the most important visual on a Takt plan?
The diagonal trade flow is the visual pattern produced when a trade moves from zone to zone over time entering a zone, completing their scope, and advancing to the next zone while a successor trade enters behind them. On a time-by-location plan, this movement appears as a diagonal line descending from upper left to lower right. When the diagonals for all trades are clean, parallel, and consistently staggered, the production system is flowing.

If you want to learn more we have:

Discover Jason’s Expertise:

General Offerings

Company Offerings

Systems

Subscribe Now !

Sign Up & Start Learning

The Foundation of Construction Excellence

© 2026 elevate constructionist LLC. All Rights Reserved. |

SUBSCRIBE NOW !

Subscribe to our newsletters and stay updated!

Related Books

The First Planner System: The Project Planning System for Executives, Project Managers, and Superintendents in Pre-construction - Book 2

Pull Planning For Builders: How to Pull Plan Right, Respect People, and Gain Time (The Art of the Builder)

The Ten Improvements to Production Planning: What Lean Builders Can Do To Improve Short Interval Planning (The Art of the Builder)

Related Books

The First Planner System: The Project Planning System for Executives, Project Managers, and Superintendents in Pre-construction - Book 2

Built to Fail: Why Construction Projects Take So Long, Cost Too Much, And How to Fix It

Related Books

The First Planner System: The Project Planning System for Executives, Project Managers, and Superintendents in Pre-construction - Book 2

The 10 Myths of CPM: How The Critical Path Method Systematizes Disrespect for People

Calumet "K"

faq

General Training Overview

Superintendent / PM Boot Camp

Takt Production System® Virtual Training

Onsite Takt Simulation

Foreman & Field Engineer Training

Testimonials

Testimonials

agenda

Day 1

Foundations & Macro Planning

day2

Norm Planning & Flow Optimization

day3

Advanced Tools & Comparisons

day4

Buffers, Controls & Finalization

day5

Control Systems & Presentations

faq

UNDERSTANDING THE TRAINING

VALUE AND RESULTS

PLANNING AND SCHEDULING TOPICS

APPLICATION & TEAM ADOPTION

VIRTUAL FORMAT & ACCESSIBILITY

faq

GENERAL FAQS

CURRICULUM & OUTCOMES

LOGISTICS & FORMAT

PRICING & VALUE

SEO-BASED / HIGH-INTENT SEARCH QUESTIONS