Day in the Life of a Project Engineer (What Really Happens on the Job)

Posted on May 18, 2026May 18, 2026 by Jason Schroeder

Read 11 min

Day in the Life of a Project Engineer: The Rhythm That Keeps the Field Moving

The project engineer who arrives to work without a plan for the day will spend the day managing someone else’s plan. Emails accumulate. Field questions arrive faster than they get answered. A pay application sits half-finished because two coordination fires got in the way. By three in the afternoon, the most important work of the day the submittal that the trade needs reviewed before their crew mobilizes next week, the RFI that is blocking the electrical sequence is still sitting untouched. And by Friday, the PE is behind on things that should have been done Monday.

This is not a talent problem. It is a structure problem. The PE role carries enormous responsibility for field productivity, supply chain health, trade partner readiness, and project financial integrity all simultaneously. Without a rhythm that organizes those responsibilities across the month, the week, and the day, the role defaults to reactive firefighting that always costs more time than the fires are worth. With a rhythm, the PE is consistently ahead of the field’s needs, consistently enabling the trades, and consistently contributing to flow instead of disrupting it.

Why the PE Role Is Harder Than It Looks

The office-based perception of the PE role submit RFIs, track submittals, process pay apps does not capture what it actually takes to do the job well. A PE who is doing the role correctly is simultaneously managing dozens of open procurement items against the Takt plan, preparing multiple trade partners through different stages of the preparation process, coordinating design conflicts before they reach the field, building and maintaining installation work packages for active scopes, and attending a cadence of meetings that, if unmanaged, will consume the entire day.

The difficulty is that all of those responsibilities have different time horizons. A monthly pay application deadline is predictable and planned. A field RFI question that just arrived from a foreman mid-installation is urgent and unplanned. A long-lead submittal that needs to be in the architect’s hands by Thursday to protect the procurement schedule is important but not yet urgent. Without a rhythm that separates those categories and creates protected time for each of them, the urgent always beats the important and the important things are almost always the ones that protect flow.

The Monthly Rhythm: Recurring Commitments That Cannot Slip

At the monthly level, the PE carries a set of recurring commitments that need to be sequenced intelligently rather than handled reactively as their deadlines arrive. Insurance verifications for new and continuing trade partners need to be tracked and renewed. New trade partner onboarding buyout, contracting, pre-mobilization meetings, pre-construction meetings needs to be sequenced against the production plan so trades are fully prepared before they arrive on site. Pay applications need to be submitted, reviewed, and processed on time, because trade partners who are not paid are not resourced, and trade partners who are not resourced cannot sustain the production the project depends on.

The monthly owner narrative and schedule update is also the PE’s opportunity to tell the project’s story professionally where the project stands against the production plan, what is being tracked in the supply chain, and where risks are being managed proactively. A PE who treats the monthly owner update as a formality rather than a communication tool is missing one of the most important trust-building moments in the owner relationship. These monthly rhythms are predictable. Planning for them at the beginning of the month rather than scrambling at the deadline is what separates a PE who is in control from a PE who is always behind.

The Weekly Rhythm: Alignment, Supply Chain, and Coordination

At the weekly level, the PE’s calendar follows a pattern that concentrates meetings on Monday, Tuesday, and Thursday and protects Wednesday and Friday as high-production, no-meeting days. The logic is straightforward: meetings generate action items, and action items need focused time to complete. A calendar where every day is fragmented by meetings is a calendar where the most important work never gets done.

Monday and Tuesday carry the team weekly tactical, where the project delivery team creates coverage for the week and confirms alignment on priorities. The strategic planning and procurement meeting follows, reviewing the supply chain against the Takt plan, confirming buffers are intact, and activating recovery for any items showing risk. Tuesday is also a good time for the OAC meeting with the owner. Thursday carries the coordination meetings BIM sessions, trade partner preparation process meetings, and any additional coordination with designers or specific trade scopes. Wednesday and Friday are production days: no meetings, full focus, the work that requires uninterrupted blocks of time to do well.

Time blocking the weekly calendar at the start of the week rather than responding to meeting requests as they arrive is one of the highest-leverage habits a PE can build. A weekly calendar that is designed rather than assembled by accident is a weekly calendar where the important work actually gets done.

The Daily Rhythm: Morning Routine Through End-of-Day Setup

At the daily level, the PE’s day follows a structured sequence that begins before the first meeting starts. A morning routine that includes physical movement, something that challenges the brain a book, a podcast, a reflection and a written plan for the day on paper is the foundation. Not because these are soft habits, but because a PE who arrives mentally prepared, with a clear picture of what the day needs to accomplish, makes better decisions from the first minute to the last. The brain organized before the day starts is a brain that can triage effectively when the unexpected arrives.

The daily team standup at around eight or nine in the morning is where the PE, PM, superintendent, and field engineers align around the scrum board or Kanban board. This meeting is brief ten to fifteen minutes and its purpose is sharp: review what the office team is working on, hear what the superintendent is seeing from the morning zone walks, and make any adjustments to the sprint backlog that better support the field’s immediate needs. This meeting is the daily recalibration that keeps the office team pointed at the field rather than at their own to-do lists.

From eight until ten, the PE handles any urgent field-focused items the fires that could not wait, the field questions that need immediate answers, the coordination issues that surfaced in the standup. From ten until lunch, the work shifts to focused, high-quality output: the installation work package that needs updating, the RFI that needs a well-written proposed solution, the submittal review that requires careful reading. The hours from ten to eleven are often the sharpest production hours of the morning, and protecting them from interruption is worth defending.

The afternoon is where the bulk of PE production happens. After any scheduled meetings are cleared, the window from roughly one to three-thirty is the most valuable sustained working time in the day. Trade partner preparation work, pay application processing, procurement log updates, BIM coordination follow-up, RFI tracking, submittal management all of this gets done in the afternoon production block. The PE who fills that window with reactive work and informal conversations is a PE who perpetually feels behind.

Warning Signs That the Daily Structure Is Breaking Down

Before the lack of structure compounds into a field impact, watch for these signals in the PE’s day:

Urgent field questions are arriving faster than they can be answered, because the PE has not gotten ahead of known needs through the morning planning process.
The afternoon production block is being consumed by meetings that could have been handled with an email or that belong on a meeting day rather than a production day.
Pay applications, submittal reviews, and procurement log updates are piling up because they keep getting deferred in favor of whatever feels most urgent in the moment.
The PE is leaving at the end of the day without having written down the open items and made a plan for the following morning, which means tomorrow’s day starts reactive rather than planned.

Any one of those signals is a structure problem, not a workload problem. The fix is a deliberate daily plan, built the night before, executed against the standup alignment each morning.

The Afternoon Foreman Huddle and End-of-Day Setup

The afternoon foreman huddle is a production meeting where the trades plan the following day’s work. The PE should be present not as an active participant in every conversation, but as an accessible resource. When a foreman surfaces an RFI issue, a submittal problem, or a material concern during that huddle, the PE is there to pick it up immediately rather than hearing about it secondhand the next morning after the problem has already ripened.

After the foreman huddle, the PE’s end-of-day routine is the setup for the next day. Write down everything that surfaced the open items, the promised deliverables, the follow-ups and build the next day’s plan on paper before leaving the desk. A PE who ends the day with a clear written plan for the next morning is a PE who hits the standup ready to execute, not ready to figure out what to do.

We are building people who build things. The project engineer who runs a structured day built on a monthly, weekly, and daily rhythm is building the operational discipline that protects the field, the supply chain, and the trade partners who depend on the office being ahead of their needs. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow including the PE scheduling discipline that keeps every level of the project supported and in rhythm.

A Challenge for Builders

Look at your current weekly calendar as a PE and count the meeting-free production blocks. If Wednesday and Friday are not protected from meetings, the structure is already eroding. Design the calendar this week. Block production time deliberately. End today with a written plan for tomorrow. Hit the standup prepared. Refine it. Execute. Refine it. Execute. That rhythm, built into daily practice, is what separates a PE who is always behind from a PE who is always enabling.

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

On we go.

Frequently Asked Questions

Why should a project engineer protect certain days from meetings each week?

Because meetings generate action items that require focused, uninterrupted time to complete. A calendar fragmented by daily meetings never produces the quality work that trade preparation, supply chain management, and coordination require. Protecting Wednesday and Friday as production days ensures the important work the kind that protects field flow actually gets done.

What is the purpose of the daily team standup for a PE?

To align the office team’s sprint backlog to what the field actually needs that day, based on intelligence from the superintendent’s morning zone walks and the previous day’s foreman huddle. It is a ten-to-fifteen-minute recalibration that keeps the PE pointed at the field’s real needs rather than working from assumptions about what matters most.

How does end-of-day planning make the next day more productive?

Because it moves open items, follow-ups, and priorities out of the brain and onto paper before leaving the desk, so the next morning starts with a written plan rather than a reactive scramble. A PE who plans the day the night before can hit the standup ready to execute rather than ready to figure out where to start.

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.

Field Support for Project Engineers (How to Actually Help the Jobsite Succeed)

Posted on May 15, 2026May 15, 2026 by Jason Schroeder

Read 11 min

Field Support for Project Engineers: How to Measure Success by Flow, Not Paperwork

There is a version of the project engineer role that produces a lot of documentation and very little field productivity. Logs are current. Emails are answered. The project management platform is organized. And out in the field, trades are waiting on information that should have been in their hands last week, superintendents are fielding drawing questions they should not have to answer, and field engineers are being pulled away from layout to chase RFI responses that a PE should own.

The PE who measures their success by the quality of their paperwork is measuring the wrong thing. The PE who measures success by whether the trades have full kit, whether roadblocks are cleared before they reach the zone, and whether the field is flowing without stopping to ask for information that should already be there that PE is doing the actual job. The difference between those two versions of the role is not work ethic. It is orientation. One is pointed at the office. The other is pointed at the field.

What the Meeting Cycle Actually Does

The system that keeps the PE oriented toward the field is a meeting cycle that connects the office team to the field team every single day. Understanding how that cycle works and where the PE fits in it is what makes the difference between a PE who feels disconnected from the site and a PE who is genuinely aligned with what the field needs in real time.

The week starts with the full team PM, superintendent, PE, field engineer, and any other project delivery staff meeting to review coverage for the week and ensure the overall strategic plan is aligned with the supply chains in the strategic planning and procurement meeting. The superintendent then takes the last planners through the lookahead and weekly work planning process in the trade partner weekly tactical. The following day brings the afternoon foreman huddle, where the next day’s plan gets built. The morning worker huddle communicates that plan to the crews and connects the site as one social group. Zone control walks give the superintendent and field leads visibility into what is actually happening in each zone versus what was planned.

After all of that after the superintendent has been through day planning, the morning huddle, and the zone walks the PE and PM join them in a daily standup. Ten to fifteen minutes. The whole team, including the superintendent who now has three distinct information sources about what the field needs: the day plan from the afternoon before, the morning worker huddle, and the zone control walk. They bring all of that into one room where the office team’s work queue the sprint backlog, the in-progress items, the completed actions is visible on a scrum board or Kanban board.

The superintendent says: these are the roadblocks we are hitting. These are the things we need. Can we reorder the sprint backlog to make sure those come first? The PE and PM align their work to what the field actually needs most, right now. That alignment is not a metaphor. It is a physical adjustment of priorities on a visible board, made in real time, based on field intelligence. That is how you prevent the field-office disconnect from forming.

The PE’s Role in the Daily Rhythm

The daily standup is where the PE gets their marching orders from the field. Not from the project management software. Not from an email chain. From the superintendent who has just walked the zones, run the huddle, and knows exactly where the production system is strong and where it is at risk.

The PE leaves that standup knowing which trades are within days of needing information or materials that may not be ready, which coordination questions have surfaced from the field that need to be resolved before they become stops, which submittals or RFIs are on the critical path for the week, and which supply chain items are at risk of missing their required-on-job date in the window ahead. That intelligence drives the PE’s day. The sprint backlog gets organized around it. The procurement follow-up calls happen against it. The coordination work gets prioritized to it.

This is what it means for the office to support the field: not physically being in the field all day, but being so closely aligned with the field’s needs that the work the PE is doing in the office is directly protecting the field’s ability to perform tomorrow and next week.

Protecting the Superintendent and Field Engineer from Office Work

Here is one of the most costly patterns on struggling projects, and it happens without anyone planning it. A drawing question comes in from a trade partner. Instead of routing it to the PE, it goes to the superintendent because the superintendent was nearby. The superintendent stops what they were doing to answer it. Then another drawing question. Then a coordination question about a conflict between two trades. Then a detail question from a foreman who could not find the spec section. An hour later, the superintendent is sitting in the office pulling drawings instead of walking zones, managing handoffs, and enabling the production system.

The field engineer version is the same. A PE is unavailable, a trade has a detail question, and the field engineer whose job is layout control, lift drawings, and spatial accuracy gets pulled into answering RFI questions. An hour of field engineer time lost to drawing interpretation is an hour where nobody is checking the layout that prevents expensive rework.

The PE’s role in field support is to be the buffer that prevents this. Drawing questions, spec questions, coordination questions, RFI responses all of that should route to the PE. Not because the superintendent and field engineer do not know the answers, but because answering those questions is the PE’s job and enabling the field is theirs. Stand where you are and lift where you stand. The superintendent enables from the field. The PE enables from the information and materials side. Both are necessary. Neither should be doing the other’s job at the expense of their own.

The Eight Principles of PE Field Support

The guidelines that define what PE field support actually looks like in practice come down to eight disciplines:

First, every trade has full kit information, materials, and permissions before they start, because the PE ensures nothing missing from their needs reaches the zone as a stop. Second, the PE is always identifying, discussing, and solving roadblocks with trade partners that would impact the trade’s work always, not occasionally. Third, the PE ensures information and materials are where they are needed, for the trade that needs them, when they need them the timing is as important as the provision. Fourth, the PE is present on site when possible, not absent in the office. Presence creates trust, surfaces field intelligence earlier, and signals to the field that the office is not a separate world. Fifth, the PE builds genuine relationships with foremen, so foremen trust the PE as a real resource rather than treating them as a bureaucratic obstacle.

Sixth, the PE has a quick problem-solving mindset. When a field question arrives, the goal is resolution, not process navigation. Seventh, the PE learns from the trades they support learning the craft, respecting the expertise that the trade partner brings, and understanding that enabling trades is not a support function layered on top of the real job. It is the real job. Eighth, and most important: the PE does not measure success by paperwork and administration. They measure success by field productivity and flow. A PE whose logs are perfect but whose trades keep stopping for missing information has not done their job. A PE whose logs are rough but whose trades are flowing cleanly has.

Warning Signs That the Field-Office Gap Is Opening

Before the disconnect becomes a production problem, watch for these signals that the PE’s field support has drifted:

Superintendents are regularly answering drawing and spec questions from trade partners rather than routing those to the PE.
Field engineers are being pulled into coordination questions that belong to the PE, reducing the time they spend on layout and lift drawings.
The daily standup is not happening consistently, so the PE is working from last week’s understanding of what the field needs rather than today’s.
Trades are stopping in their zones for information that should have been in their installation work package.
The PE’s daily activity is primarily reactive responding to what the field is asking for rather than getting ahead of what the field will need next week.

Every one of those signals means the PE has drifted from a proactive field-support orientation toward a reactive document-management orientation. The fix starts with the standup getting back in that room with the superintendent daily, aligning the sprint backlog to what the field actually needs, and rebuilding the habit of having the information ready before the question arrives.

We are building people who build things. The PE who masters field support is building the operational bridge between the office and the site ensuring that every trade partner, foreman, and worker has what they need, when they need it, without pulling the superintendent or the field engineer away from the production work that only they can do. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow including the PE field support discipline that keeps the production system moving without the field-office friction that slows most projects down.

A Challenge for Builders

Walk your project tomorrow and watch where drawing and spec questions are going. Are they routing to the PE where they belong or are they landing on the superintendent and field engineer because the PE is not close enough to the field’s daily reality to intercept them first? If the second answer is more accurate, the fix is the daily standup. Start it this week. Ten minutes. The whole team. Align the sprint to the field’s needs. Do it every day. The gap between field and office closes when the meeting makes both parties visible to each other in real time.

As Jason says, “Flow over busyness.”

On we go.

Frequently Asked Questions

What is the daily standup meeting for project engineers and why does it matter?

It is a ten-to-fifteen-minute huddle between the PE, PM, and superintendent after the morning worker huddle and zone walks, where the superintendent brings field roadblocks and needs to the office team, and the PE and PM align their sprint backlog to address those needs in priority order. It is the daily mechanism that prevents the field-office disconnect from forming.

Why shouldn’t superintendents and field engineers answer drawing questions?

Because every hour a superintendent spends answering drawing and spec questions is an hour not spent enabling the production system walking zones, managing handoffs, clearing roadblocks, and holding the site standard. The PE exists specifically to field those questions and protect the superintendent’s focus on field execution. Routing questions to the wrong person hobbles the field.

How should a PE measure their own success?

By field productivity and flow whether trades have full kit, whether roadblocks are cleared before they reach the zone, and whether the production system is moving without information stops. Not by the quality of their documentation, the organization of the project management platform, or the number of emails processed. Those are inputs. Field flow is the output.

If you want to learn more we have:

Discover Jason’s Expertise:

Change Management for Project Engineers (RFIs, Change Orders, and Cost Control)

Posted on May 14, 2026May 14, 2026 by Jason Schroeder

Read 11 min

Change Management, RFIs, and Change Orders: The System That Protects Everyone on the Project

Change is inevitable on every commercial construction project. The owner requests a modification. The design has a gap that the field cannot resolve without a drawing revision. An unforeseen condition requires a scope adjustment. None of these events are failures they are the natural reality of building complex structures in an imperfect world. What determines whether change events damage a project or get absorbed cleanly is not whether they happen. It is whether the team has a system for managing them.

The project engineer sits at the center of that system. RFIs, potential change orders, executed change orders, documentation, posting to drawings, trade partner notification all of it flows through the PE. A PE with a disciplined change management process protects the project’s budget, the schedule, the trade partners who need to be paid for extra work, and the contractual integrity that governs every decision. A PE without one finds themselves six months into a project with untracked exposures, unpriced changes, trade partners doing work outside their contract without financial approval, and a change order reconciliation that will take months to untangle.

What an RFI Actually Is

An RFI request for information is the formal mechanism for modifying the contract documents when something is unclear, missing, or inconsistent. That definition matters because it shapes how the PE should think about the RFI process. You do not design through submittals. You do not design through field sketches, verbal agreements, or email conversations. If something on the drawings or specs needs to change, it changes through an RFI a formal, documented, traceable request that produces an official answer tied to the contract.

This matters for two reasons. First, because the contract documents govern the project, and any deviation from them that is not formally documented creates risk for the party who deviated. A trade partner who installs to a verbal instruction rather than a posted RFI response has installed outside the contract documents, and their protection in a dispute is thin. Second, because the fewer RFIs on a project, the better the design. RFIs are, in a very real sense, rework for information they represent gaps that should have been resolved in the design phase rather than pushed into the construction phase for the field team to navigate. A streamlined RFI process simple, clear, frictionless, with only the information actually needed honors that reality rather than creating administrative overhead that obscures it.

The goal for any RFI is the same: propose a clear solution, describe the issue with enough specificity that the designer can answer it correctly on the first response, and submit it early enough that the answer arrives before the construction sequence needs it. A well-written RFI with a recommended solution gets answered faster and more accurately than a vague question that leaves interpretation to the reviewer. The PE who writes RFIs with that discipline is protecting the schedule as much as they are resolving a design gap.

The Trigger Rule: Log It the Moment You Know

Here is the rule that protects more projects from financial surprises than almost anything else in change management. The moment any event occurs that might cost money or time, it becomes a potential change order with an assigned number. Not when the price is confirmed. Not when the owner approves it. Not when the work is complete and someone asks what it cost. The moment the trigger happens.

This principle keeps nothing forgotten. A potential change order log that is current in real time with every triggered event numbered, described, and tracked is the difference between a project whose financial projections reflect reality and a project where half the exposures are invisible until they surface as disputes at closeout. If an event is triggered on a Tuesday morning, it is on the log by Tuesday afternoon. If it eventually gets resolved without a cost impact, it gets closed off the log. If it becomes an executed change order, the log tracks that evolution.

The downstream effect of this discipline is also significant. When the PM is reviewing financial projections and contingency exposure, the potential change order log is what makes those projections honest. A project that appears to have consumed only a third of its contingency budget might actually have consumed 75% once every tracked potential change order is accounted for. Without the log, that reality is invisible until it is too late to take corrective action. With the log, the picture is clear every week at the strategic planning meeting, and corrective action is available when it is still relatively cheap.

The Phase Gate Process: Do Not Proceed Without Financial Approval

The single most important rule in change order management is this: do not authorize work outside the contract scope until financial approval has been obtained. Not tentative approval, not a verbal from the owner, not a hand wave in a meeting that someone interprets as a go-ahead. A documented approval written confirmation that the rough order of magnitude cost, or the final lump-sum cost, has been accepted by the owner and the work can proceed.

This sounds obvious. In practice, schedule pressure and relationship dynamics push teams across this line constantly. A change is needed urgently. The owner says “just go, we’ll work out the price later.” The team proceeds, the work gets done, and then the price conversation becomes a negotiation over work that has already been installed. The leverage has shifted entirely to the owner’s favor. The trade partner who did the work may or may not get paid for it at what it actually cost them. And the PE who authorized the work without written approval is holding a difficult conversation with very little documentation to support the project’s position.

The phase gate model prevents this. Each step in the change order process the RFI, the design response, the rough order of magnitude pricing, the owner’s written approval, the final pricing, the executed change order has a clear gate. Work at the next step does not begin until the gate is cleared. It feels slower. It is actually faster, because it eliminates the disputes, the reconciliation effort, and the relationship damage that unauthorized work creates.

Posting to Drawings Only After Approval

Once an RFI is answered and the change is approved, the updated information needs to be posted to the drawings in the field. This step is as important as the approval itself, because a trade partner who is still working from a superseded drawing after an approved RFI has been answered is working from wrong information and the quality consequences of that belong to the change management system, not to the trade.

The PE’s discipline here is simple: post the bulletin or the RFI response to the current drawing set immediately after approval, before releasing the trade to act on the change. Current, relevant, accurately marked drawings are the protection. Unmarked drawings with verbal instructions are a dispute waiting to happen.

When changes are concentrated in a specific scope or area, they should be handled by a dedicated resource a separate engineer or office PE focused on pricing and processing the change orders rather than diverting the main project team from contract work. A project team that gets overwhelmed by change order processing and loses focus on the contract scope will deliver neither the contract work nor the change work at an acceptable standard. Keeping those tracks separate when volume demands it is a management decision the PE and PM need to make proactively, not reactively when both tracks are already behind.

Warning Signs That Change Management Is Breaking Down

Before the financial exposure becomes unmanageable, watch for these signals that the change management system needs a reset:

Potential change order events are being tracked in someone’s memory or a personal spreadsheet rather than in the formal log with assigned numbers.
Work outside the contract scope is being performed based on verbal approvals because the formal process feels too slow for the schedule pressure.
Updated RFI responses have been answered but not posted to the field drawing set, meaning some trades are still working from superseded information.
The contingency budget appears healthy on the cost report, but the potential change order log if it exists shows exposures that have not yet been moved to the contingency calculation.
Change orders from months ago are sitting unexecuted because the pricing and documentation were never finalized.

Every one of those signals is a financial exposure that is growing invisibly. The system, run correctly, makes every exposure visible from the moment it is triggered. That visibility is what allows the PM and owner to make informed decisions rather than being surprised.

The Eight-Point Summary That Protects Every Project

The complete change management framework distills to eight disciplines that every PE should treat as non-negotiable:

Log every triggered change immediately with an assigned number.
Process the RFI correctly clear, descriptive, with a recommended solution.
Obtain pricing, negotiation, and written approval before executing any work.
Track both time and cost impacts for every potential change from the moment it is triggered.
Document properly to protect the project backup, vendor pricing, owner authorization.
Avoid scope gaps by closing every interface between contract scope and change scope before either progresses.
Track changes systematically using phase gates so no step proceeds without the required approval.
Prevent change order overload from derailing contract work by separating the tracks when volume demands it.

We are building people who build things. The PE who masters change management is building the financial integrity of the project ensuring that every extra dollar spent is authorized, every trade partner gets paid for their work, and every change is traceable from trigger to execution. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow including the change management discipline that protects the project’s budget and the people who build it.

A Challenge for Builders

Open your current project’s potential change order log this week or create one if it does not exist and account for every event that has been triggered since the project started that might have a cost or time impact. For each one: has it been numbered? Has it been priced? Has written approval been obtained before any work proceeded? Has the approved change been posted to the drawings? If any of those steps are missing for any item, close the gap this week. The longer a potential change order sits untracked, the harder it becomes to reconstruct and the more it costs in reconciliation effort and relationship damage at closeout.

As W. Edwards Deming said, “Manage the cause, not the result.”

On we go.

Frequently Asked Questions

When should a potential change order be logged?

The moment any event is triggered that might have a cost or time impact not when the price is confirmed, not when the work is done, but at the moment the trigger occurs. Immediate logging with an assigned number ensures nothing gets forgotten and every exposure is visible in the financial projections from day one.

Why is written financial approval required before proceeding with change order work?

Because performing work outside the contract scope without written approval shifts all negotiating leverage to the owner after the work is already installed. Written approval whether a rough order of magnitude or a final lump-sum protects the project, the trade partner who performs the work, and the GC who authorized it. Verbal approvals are disputes waiting to happen.

What does “phase gates” mean in change management?

Each step in the change order process RFI submission, design response, pricing, owner approval, execution, drawing posting has a clear gate that must be cleared before the next step begins. No work proceeds to the field without passing through the approval gate. This structure prevents the unauthorized work and unresolved pricing that create the most expensive change order disputes.

If you want to learn more we have:

Discover Jason’s Expertise:

Project Engineer Coordination: How to Align Trades and Keep Projects Moving

Posted on May 13, 2026May 13, 2026 by Jason Schroeder

Read 11 min

Coordination and Aligning Trades: Why This Is the Project Engineer’s Most Important Work

Walk the interiors of a laboratory, a hospital, or any complex commercial building and look at what the installation actually requires. The electrician needs to know where the HVAC ductwork runs before they can route their conduit. The plumber needs to know where the lab equipment connections land before they can rough in the supply and waste. The HVAC contractor needs to know where the architectural ceiling drops before they can design the layout of their distribution. And none of those design disciplines, in the current industry model, have designed their work in direct coordination with the others. Every set of drawings was produced independently, and the job of reconciling them lands in the field unless a project engineer does it first.

This is not a peripheral responsibility. Coordination is one of the project engineer’s most central duties on any commercial project. The general contractor is there to provide the environment, the rhythm, the information, and the materials that allow trades to flow through zones cleanly. None of that happens if the drawing sets are uncoordinated, if the interfaces between scopes are undefined, if the routing conflicts are discovered at the point of installation rather than in the office. Coordination is what prevents all of that. And when it is done well, the field does not have to fight the design.

Why Design Does Not Come Coordinated

The ideal construction process starts with design teams thinking in systems during concept and schematic design, developing those systems with construction execution in mind during design development, and producing drawing packages that are organized around production units zone-sized batches that align with how the work will actually be built. In that world, a 8,000 square foot zone would have a drawing set that shows every design discipline structural, architectural, mechanical, electrical, plumbing, and lab equipment coordinated in one complete package for that zone. A PE could pick up the zone package and have everything needed to create the installation work package without reconciling six different drawing sets that were never designed to be read together.

The construction industry is not in that world yet. What actually arrives on the project site is a set of architectural drawings, a set of structural drawings, a separate set of mechanical drawings, a separate set of electrical drawings, a separate plumbing set, and any specialty drawings for equipment or systems all developed independently, organized by visual convenience rather than production sequence, and frequently containing conflicts that nobody caught because nobody was looking at all of them simultaneously. Every contractor, trade partner, and field team has experienced this reality. The building in the drawings and the building that can actually be built are not always the same building.

In the absence of a coordinated design system, the PE is the person who builds the coordination that the design process did not produce. That is not an addendum to the role. It is the role.

The Coordination Chain: From Drawings to Zone

When a PE is assigned responsibility for a specific area of a project say, Building One, or the interiors of one wing the coordination work starts with the documents and flows through every subsequent touchpoint until the trade is in the zone with full kit.

The first step is coordinating the drawings and specs themselves. The PE reviews the drawing sets for the assigned scope and identifies every gap, conflict, and unresolved interface. Where the electrician’s conduit path conflicts with the HVAC duct routing, that conflict needs to be resolved before either trade mobilizes. Where the plumbing rough-in connects to the lab equipment, the point of connection needs to be defined and agreed upon by both responsible parties in their respective contracts. Where the architectural reflected ceiling plan shows a height that the mechanical system cannot achieve, that discrepancy needs to be resolved in the design, not in the ceiling above a foreman who is trying to figure out why nothing fits.

This is also where the PE coordinates scope interfaces contractually. The electrician’s scope ends somewhere. The HVAC contractor’s scope begins somewhere. Where those scopes meet, the interface needs to be owned by a specific party in a specific contract. Gaps in contractual coverage become change orders, disputes, and field delays. A PE who closes those gaps before the trades mobilize is protecting the project from some of the most expensive friction in commercial construction.

Submittals, Shaft Drawings, and RFIs as Coordination Tools

Beyond the drawing set itself, several additional documents require active PE coordination before the trade can work cleanly.

Submittals are the trade partner’s documentation that the products they intend to use meet the specification requirements. They need to be initiated early enough to move through the review cycle before the material is needed on site meaning the PE is managing the submittal timeline against the procurement log and the Takt plan simultaneously. When a submittal gets returned with comments, the PE coordinates the response between the designer and the trade partner so the issue is resolved without consuming the buffer.

Shaft drawings are required wherever multiple trades need to coordinate their routing through a shared vertical space. An elevator shaft, a mechanical chase, a plumbing riser zone in all of those spaces, the routing of every trade needs to be modeled and agreed upon before anyone starts installing. A PE who coordinates the shaft drawing process ensures that the routing decisions are made before they become physical conflicts in the field, not after.

RFIs address the missing information that the drawings and specs did not resolve. A well-managed RFI is submitted early, clearly describes the gap or conflict, provides the project team’s recommended solution where possible, and receives a response before the construction sequence reaches the point where the answer is needed. A PE who coordinates RFIs proactively writing them clearly, submitting them at the right time against the production sequence, and tracking the response timeline is closing information gaps before they become stops.

The Pull Plan and Pre-Construction Meeting as Coordination Events

Coordination does not end with the documents. It continues through the production planning process and the trade partner preparation meetings that set every trade up to flow through their scope cleanly.

In the pull plan, the PE assists the superintendent and PM in bringing the trades into the sequence so that every trade understands where they fit relative to the others. The pull plan is a coordination event in the most literal sense it is where the trades see each other’s timelines, negotiate their handoffs, and commit to the sequence that will allow the whole train to move without stacking or burdening. A PE who is actively engaged in the pull planning process not just observing but helping coordinate the sequence, surfacing conflicts in the planned handoffs, and making sure the timeline reflects the actual coordination requirements is contributing directly to the quality of the production plan.

The pre-construction meeting is where all of that coordination comes together for the trade in one document. By the time the trade sits down in that meeting, the drawings for their scope should be coordinated, the conflicts resolved, the interfaces defined, and the RFIs that affect their scope answered. The PE’s job in the pre-con meeting is to consolidate all of that into a single installation work package one visual document that the foreman can carry into the zone so that the trade leaves knowing exactly what they are building, to what standard, in what sequence, with what material specifications.

Warning Signs That Coordination Is Falling Behind

Before a coordination gap becomes a field stop, watch for these signals that the PE’s coordination system needs to catch up:

Trades are discovering routing conflicts at the point of installation because the shaft drawing was never coordinated across disciplines.
Scope interface disputes are surfacing during construction because the contractual points of connection were never defined in the pre-mobilization or pre-construction process.
RFIs are being submitted from the field rather than from the office, which means the gaps were not identified and closed before the trade arrived on site.
The pre-construction meeting produced a promise to send information later rather than a completed installation work package.
BIM coordination sessions are happening reactively resolving conflicts that showed up in the model after the trade had already started working rather than proactively clearing the path before mobilization.

Every one of those signals is a coordination failure that is more expensive to resolve in the field than it would have been in the office.

BIM as the Coordination Environment

Building information modeling is the most powerful coordination tool available to the project engineer, and its primary value is not visualization. It is conflict identification and resolution before construction begins. A well-managed BIM process surfaces routing conflicts between trades in three dimensions, allows the trades and the design team to negotiate routing solutions in the model, and produces a coordinated design that the field can actually build without stopping to resolve physical conflicts.

The PE who coordinates the BIM process for their assigned scope is ensuring that the virtual model reflects the decisions that have been made every routing agreement, every interface resolution, every scope definition so that the field work is an execution of a coordinated plan rather than an improvisation around unresolved conflicts.

We are building people who build things. The PE who masters coordination is building the environment in which every trade can perform at their best because the drawing is right, the interfaces are defined, the routing is clear, and the installation work package is ready before the crew steps into the zone. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow including the PE coordination discipline that protects trades from the uncoordinated design environment they should never have to fight.

A Challenge for Builders

Pick one trade on your current project that has not yet mobilized. Trace their coordination chain forward from the current date. Are the drawing conflicts in their scope resolved? Are the scope interfaces defined contractually? Are the submittals submitted and tracking against the procurement log? Is the shaft drawing coordinated? Are the outstanding RFIs submitted and tracking toward a response before the construction sequence needs the answer? And does the pre-construction meeting have a specific date with a planned IWP? If any of those are weak, the coordination gap will show up as a field stop. Close it now, while it is still cheap.

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

On we go.

Frequently Asked Questions

Why is coordination considered one of the project engineer’s most important responsibilities?

Because design drawings are produced independently by discipline and almost always contain routing conflicts, scope gaps, and undefined interfaces that nobody resolved before the drawings were issued for construction. The PE’s coordination work is what bridges the gap between the design that was delivered and the building that can actually be built without field stops and rework.

What is the ideal output of a pre-construction meeting from a coordination standpoint?

A single installation work package in the trade partner’s hands one visual document that consolidates every coordination decision, drawing reference, RFI answer, spec requirement, and scope definition relevant to their work. The trade should leave knowing exactly what they are building, with no outstanding coordination gaps that will stop them in the zone.

How does BIM coordination relate to the PE’s coordination responsibilities?

BIM surfaces the routing conflicts between trades in three dimensions so they can be resolved in the model before construction begins. The PE coordinates the BIM process for their assigned scope, ensuring the model reflects every routing agreement and scope decision, so the field executes a coordinated plan rather than discovering physical conflicts during installation.

If you want to learn more we have:

Discover Jason’s Expertise:

In Sync

Posted on May 13, 2026May 13, 2026 by Jason Schroeder

Read 14 min

Getting in Sync: Why Flow Happens When Trades Focus on Each Other, Not Just Their Tasks

There is a moment in every Takt simulation when the group stops struggling and something clicks. The work that was chaotic and colliding becomes smooth. The rhythm that was absent becomes palpable. And every time it happens, the shift is not in the tasks. The tasks are the same. The shift is in where people are looking. They stopped watching their own work and started watching each other. They stopped processing the activity and started anticipating the person. That moment, in a simulation in Germany, or in a church activity room, or on the floor of a construction project, is what flow actually feels like. And it is entirely available to every trade partner on every project, the moment the system is designed to make it possible.

The Problem That Nobody Names Correctly

The construction industry has been trying to improve production for decades by focusing on the tasks. Better CPM schedules. More detailed look-aheads. More frequent planning meetings. More detailed procurement logs. These are all task-focused interventions, and they all produce marginal results because they are solving the wrong problem. The problem is not that the tasks are poorly tracked. The problem is that the trades are not in sync with each other. They are executing their individual scopes in isolation, handing off to the next trade when their work is nominally complete, and moving on without any real awareness of whether the people behind them are ready to receive what was left for them. That is not a scheduling failure. It is a system design failure.

The Failure Pattern

The failure pattern is predictable. A trade gets into an area, executes their scope, finishes when the schedule says to finish or when the work runs out, and moves to the next area. What they leave behind may or may not be ready for the next trade. Punch list items remain in the space. Materials from the previous scope are still staged in the way. The connection points between scopes have not been inspected. The area has not been cleaned. And because the next trade’s start date was set by the schedule and not by the actual state of the space, they begin work in an environment that is not fully ready. They lose time in the first day getting set up, resolving leftover conditions, and figuring out what the previous trade intended. The first day of every Takt cycle becomes a recovery day rather than a productive one. And the project never gets into flow because the conditions for flow are never fully established before the next cycle begins.

The System Failed, Not the Trade

This is not a failure of professionalism. Trades who leave areas unprepared for the next crew are not careless. They are responding rationally to a system that measures task completion, not handoff quality. If the metric is whether the drywall is installed, the drywall installer will install drywall. Whether the space is properly prepared for the painter who comes next is not their measured responsibility under most scheduling systems. The system never encoded that expectation. The system never protected the time needed to fulfill it. And so the behavior that produces poor handoffs persists, not because people do not care, but because the system never gave them the time, the expectation, or the model for something better.

What the Clapping Game Taught Jason About Flow

Jason Schroeder describes a team activity from a church setting that became one of the clearest analogies he has found for how Takt planning and trade coordination are supposed to work. In the activity, participants stand in a group and pass a clap from person to person around the circle. When people are focused on the task of clapping, they are thinking about when to clap and where to send it. The rhythm is inconsistent. Some passes are too fast, some too slow, and the group stays out of sync regardless of how hard everyone is trying.

Then something shifts. Someone makes eye contact with their partner before the clap arrives. They begin to anticipate. They can see, from the other person’s posture and timing, when the clap is coming. They are ready. They receive it smoothly and send it on in the same rhythm. When that behavior spreads around the circle, the group stops being a collection of individuals doing individual tasks and becomes a team producing a shared rhythm. The clapping is not harder or faster. It is in sync. And in sync is what flow feels like.

In construction, every trade is either focused on the task or focused on the team. A drywall crew focused only on the task installs drywall and moves to the next area. A drywall crew focused on the team installs drywall, QCs the work before demobilizing, cleans the space, removes their gang boxes, completes the punch list in that area, stages materials for themselves in the next space, and leaves the area in a condition that the painter can enter and be immediately productive. They passed the clap properly. And the painter, who knew what to expect because the system is designed that way, arrives ready to receive it.

Takt First, Then Pull: Getting the Sequence Right

One of the foundational insights this episode clarifies is that the construction industry has the system sequence backwards. Pull planning and the Last Planner System are excellent tools. They are not, however, the primary production system. They are what pulls to the primary production system, which is Takt.

Taiichi Ohno at Toyota set the car assembly line on a Takt time, meaning a governed rhythm. Everything else, the motor delivery, the seat installation, the parts supply, was pulled to that rhythm. Nobody talked about pull planning as the main event. Pull was what made the Takt system function. The Takt rhythm was the backbone.

In construction, the equivalent is a Takt plan that governs the pace and zone sequence of the project. Last Planner pull planning, Scrum for the office team, weekly work plans: all of these pull to the Takt backbone. When a project runs only on Last Planner without a Takt backbone, it is the equivalent of designing a parts delivery system without first designing the assembly line. The parts might arrive. They will not arrive in sync with a rhythm that produces flow because no rhythm was established.

What Buffers Are Actually For

The most important practical insight in this episode is what buffer time in a Takt cycle is designed to do. Most people think of buffers as time set aside in case something goes wrong. That is part of the function. But the deeper function of the buffer is preparation and quality.

When a trade finishes their scope in a Takt cycle before the end of the cycle, the correct response is not to push into the next zone early. The correct response is to use the remaining time to QC the current work thoroughly, punch list the area, clean and demobilize, stage materials for the next cycle, prepare layout, train the crew on what is coming, coordinate with the trade behind them, and walk the next area to confirm it will be ready. All of that is buffer use. All of that is what makes the next cycle start on time, in a ready space, with a crew that is prepared rather than scrambling.

In the simulation with Janos and Marco in Germany, when the batch sizes were optimized and the Takt time was right, Jason found himself finishing his work package with five to seven seconds left in the 40-second cycle. Instead of pushing into the next area, he staged materials for the trade behind him. He QC’d his own work. He prepared his materials for the next cycle. And the whole simulation ran smoother because every participant was doing the same. The buffer was not idle time. It was production time directed at making the next cycle succeed rather than pushing more work into the current one.

Here Is What Being in Sync Looks Like in Practice

Before every Takt cycle ends, a trade that is in sync with the system is asking:

Have we QC’d the completed work and resolved all open punch list items in this area?
Is the space clean and demobilized, with our materials and equipment removed or staged correctly?
Have we walked the next area to confirm it is ready to receive us at the start of the next cycle?
Have we staged the materials and equipment we need for the next cycle so we can hit the ground running on day one rather than spending day one getting set up?
Have we communicated with the trade behind us to make sure they know what they are walking into and what we are leaving for them?
Have we looked the next trade in the eyes, metaphorically or literally, and confirmed that the handoff is ready?

When those questions are answered yes before the cycle ends, the next cycle begins in a condition that allows flow. When they are not answered, the next cycle begins in recovery mode and the project never finds its rhythm.

Built for Trade Partners Who Want to Win Together

The opposing squares game that Jason describes at the close of this episode makes the team dimension of this clear. A group of people trying to navigate past each other in opposite directions will fail every time if they are each figuring it out individually. They will fail if they silo into small groups. They will fail if they focus on their own movement without coordinating with the whole. They only succeed when they appoint a leader, gather information collectively, make a shared plan, communicate it to everyone, execute together, and adapt as a group. That is not a team-building exercise. It is a description of how a Takt system functions when it works. Trades following a common rhythm, anticipating each other, preparing for each other, and measuring success not by whether they finished their own task but by whether the team produced flow. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Get in Sync and Stay There

The question that closes this episode is the right one to carry back to every project: are the trade partners on your site focused on their individual tasks, or are they focused on each other? Are they anticipating the needs of the teams ahead of and behind them? Are they using the buffer time in their Takt cycles for preparation and quality rather than pushing more work? Are they treating the trades behind them as customers whose success depends on how well the handoff is made? When the answer to those questions is yes, flow is present. When the answer is no, the project is a collection of siloed tasks that happen to be in the same building. As Jason closes with the image of the clapping circle: only when people look each other in the eyes and anticipate the rhythm does the group get in sync. That is how flow is created. Focus on the people, not the task.

On we go.

FAQ

Why is Takt planning the primary production system rather than pull planning?

Because pull planning is a coordination mechanism, not a rhythm system. Pull planning works best when it is coordinating commitments to a governing rhythm, which is what Takt provides. Toyota used Takt time as the backbone of their assembly line and pulled materials and components to that rhythm. The construction industry adopted pull planning through the Last Planner System and, in many cases, implemented it without a Takt backbone to pull toward. The result is a coordination system that produces collaborative commitments without a governing pace. Those commitments tend to drift into push behavior when variation hits because there is no rhythm to hold the sequence in place. Takt first, then Last Planner pulling to it, is the correct sequence.

What should a trade do with buffer time at the end of a Takt cycle?

Use it for preparation and quality, not for pushing work into the next cycle. When a trade finishes their scope before the Takt time ends, the productive use of the remaining time is to QC the completed work, punch list the area, clean and demobilize, stage materials and equipment for the next cycle, walk the next area to confirm it is ready, coordinate with the downstream trade, and prepare the crew mentally and physically for what comes next. All of those activities are high-value uses of buffer time that directly contribute to the next cycle starting in flow conditions. Pushing into the next area early breaks the rhythm and often creates conditions that force the downstream trade to start before their area is ready.

What does “focus on the people, not the task” mean for a foreman?

It means the foreman’s primary orientation in a Takt system is not to the completion of their own work package but to the success of the handoff between their crew and the trades around them. It means knowing what condition the downstream trade needs the space in and ensuring it is delivered in that condition. It means communicating with the upstream trade when something is preventing a clean start. It means being aware of the rhythm across the whole zone, not just within the area of current work. The clapping game analogy captures it directly: the person focused only on passing the clap stays out of sync; the person focused on the eyes and energy of their partner produces flow. A foreman focused only on finishing their scope will hand off a space that is not truly ready. A foreman focused on their trade partners will hand off a space that the next crew can enter immediately and productively.

How does Kingman’s formula relate to the idea of buffer time for preparation?

Kingman’s formula describes the relationship between utilization, variation, and delay. When a Takt cycle is packed to full utilization with no buffer, any variation produces delay that cascades into the next cycle. The buffer time that Kingman’s formula requires is not empty time. It is time that absorbs variation and, when variation has not occurred, gets used for preparation and quality. Jason describes the moment in the BMW simulation when he realized that the buffer between Takt times is where the production system actually improves: not during the active cycle, where the crew is executing the standard, but in the preparation before and after, where the conditions for the next cycle are established. The buffer is where finishing as you go happens. It is where the system learns and gets better.

What is the opposing squares game and what does it demonstrate about construction teams?

The opposing squares game is a team activity where two groups face each other across a sequence of spaces and must navigate past each other to reach the opposite side, following specific rules about who can pass whom. Every time a team plays the game without coordinating as a group, they fail. They silo into pairs. They focus on their own movement. They talk to the person next to them but not to the whole team. They lose sight of the plan. The only way to win is to appoint a leader, gather information from everyone, build a shared plan, communicate that plan to every member of the team, execute together, and regroup and adapt as conditions change. That five-step process, appoint a leader, gather information, make a plan, communicate the plan, execute and adapt, is the same process that makes a Takt system function when trade partners are treating each other as a team rather than as independent contractors who happen to share a building.

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

Personal Buffers, Feat. Brandon Montero

Posted on May 13, 2026May 13, 2026 by Jason Schroeder

Read 12 min

Are You Creating Capacity? Why Buffers in Your Week Are the Foundation of Personal Excellence

There are people in the construction industry right now who started something remarkable. They began an improvement effort, a lean initiative, a leadership development journey, a genuine attempt to run their projects better and lead their teams more effectively. They had real momentum. And then their employer piled on more work without adding more support, and the improvement effort quietly died. Not because they stopped caring. Because they ran out of capacity. The overburdened version of a talented leader is a marginal version of what they could be. And the tragedy is that nobody intended it. The work just kept coming, the buffers disappeared, and the energy and excitement and capability that made those improvement efforts possible went with them.

The Pain That Does Not Get Named

Construction is an industry that celebrates running hard. Long hours are treated as evidence of commitment. A packed calendar signals that someone is important and in demand. The leader who has no margin in their week is often the leader who gets praised for working so hard, while the slow, quiet erosion of their capacity goes unnoticed until it shows up as mediocre results, stalled initiatives, and a person who used to be on fire and now just shows up. That erosion is not weakness. It is physics. You cannot run a production system at 100% utilization without variation destroying it. You cannot run a human being at 100% utilization without variation destroying them. The same law applies.

The Failure Pattern

The pattern is recognizable to anyone who has watched it happen. A high performer gets promoted or takes on a more demanding role. The workload grows faster than the support structure. They start carrying tasks that should belong to others, either because delegation has not been set up properly or because the people below them are not yet trained to take those tasks on. They stop exercising because there is no time. They stop reading because the week is too full. They stop reflecting because reflection feels like a luxury they cannot afford. The improvement effort stalls. The creative thinking stops. The energy that made them exceptional gets consumed entirely by the urgent, leaving nothing for the important. They settle into a maintenance mode that everyone around them accepts as their new normal.

The System Did Not Support Them

This is not a story about discipline. The people who end up overburdened and marginal did not get there because they lacked grit or determination. They got there because nobody designed a system around their capacity. Nobody asked whether the workload was sustainable. Nobody built in the buffers that would have protected their thinking time, their energy, and their improvement efforts. The system created the conditions for decline and then watched it happen. That is a leadership failure at the organizational level, not a personal failure at the individual level.

What Jason, Brandon, and Effie Noticed in Mexico

This episode was recorded in a car outside Guadalajara, with Jason Schroeder, his daughter Effie, and Brandon Montero, a construction professional and close colleague. The conversation the previous day had been about people they both know well, people who had started genuinely exciting improvement efforts and whose momentum had stalled because their employers had overburdened them without providing the support those efforts required. Neither Jason nor Brandon was criticizing the people. They were lamenting the system. And out of that conversation came the question that this episode answers: what does it actually look like to have capacity, and what does a person do with it when they have it?

Effie was playing ukulele and listening to music. Brandon was making custom frames and refinishing furniture, the kind of focused, tactile, single-problem work that clears the mind and brings genuine restoration. Jason was going through old Apple Notes and flagged emails, reconnecting with ideas he had captured weeks earlier, finding inspiration he had not yet acted on. In a different mode, he was jogging in the morning, stopping at the park to do box breathing, walking in silence without music or podcasts, and returning home to kneel and think. These were not indulgences. These were the activities that made showing up at 100% possible. And every single one of them required time that had to be protected rather than filled.

What Kingman’s Formula Says About Your Week

The production law that governs this is the same one that governs every Takt wagon on every construction project: cycle time alone is not enough. You need cycle time plus a buffer for variation plus a buffer for capacity. If a drywall crew needs five full days to complete a zone and the schedule allocates exactly five days, the first interruption turns five days into six and they are working Saturday. The buffer was never there. The same logic applies to a person’s week. If every hour from 7 a.m. to 6 p.m. is committed to something, the first urgent email, unexpected call, or emotional challenge that requires a human response turns a functional day into an exhausting one. And the next day begins already behind.

The U.S. military studied this directly. Research found that soldiers could march 50 to 100% farther when they took a 10-minute break every hour than when they did not. The break was not wasted time. It was the mechanism that made the sustained performance possible. The worker who takes 10 minutes to reflect between tasks is not less productive than the one who pushes through. They are more productive, more focused, and more capable of sustaining that performance across the full day. The buffer is the thing that protects the output.

Three Things That Building Capacity Actually Requires

The first thing capacity requires is an honest assessment of current utilization. If the week is full and there is no time for exercise, reflection, meaningful relationships, thinking time, or the activities that restore energy, the week is overfull. That is not a calendar problem. It is a system design problem. And just as the solution to an overpacked Takt wagon is not to work faster but to right-size the load, the solution to an overfull week is not to be more disciplined but to redesign the schedule so the buffer exists.

The second thing capacity requires is a clear answer to the delegation question. Brandon Montero frames this precisely: there is a difference between what the people around you can do and what they should do. Tasks that belong to others but have not been transferred yet because the training has not happened represent a training priority, not a permanent responsibility. The time investment in training someone to own a task is the investment that eventually creates the capacity buffer. Leaders who hold on to tasks because they are not ready to delegate are not protecting quality. They are consuming capacity they cannot afford to lose.

The third thing capacity requires is protecting the activities that make excellence possible. These are different for every person. For Jason, it is morning exercise and reflection, thinking time, and the practice of reviewing past notes for uninvested inspiration. For Brandon, it is creative work with his hands and deep, intentional time with the people who matter to him. For Effie, it is music and the simple restoration of rest. The specific activities are not what matters. What matters is that they exist, that they are protected in the schedule, and that they are understood as production inputs rather than indulgences. You cannot help people from a depleted state. As Effie says plainly in this episode: you cannot help people if you do not have the help you need.

Here Is Where to Start on Your Calendar This Week

Before the next week begins, run through these questions:

What percentage of your waking hours are genuinely committed to active output? If the answer is above 80%, you are carrying no buffer.
Is there protected time in your week for exercise, reflection, or the activities that restore your energy? If not, that time needs to be scheduled before other commitments fill it.
Are there tasks on your plate that belong to someone else but have not been transferred because the training has not happened? That is this week’s first priority, not the task itself.
When was the last time you had genuine thinking time, uninterrupted, without inputs, to work through a real problem or capture real insights? If you cannot remember, the schedule needs to create that space.
Are you excited about your work? If the answer is no, the most likely cause is not the work itself. It is that there is no capacity left to bring energy to it.

Built for People, Not Just Projects

The North Star of Elevate Construction has always been to build people who build things. That means building people who are healthy, energized, growing, and capable of showing up at their best. A construction leader who is running at 100% utilization with no buffer is not serving their project or their crew at the level they are capable of. They are surviving rather than thriving, and the people who depend on them feel the difference. Creating capacity is not a personal preference. It is a performance strategy. Protect the buffer. Protect the thinking time. Protect the activities that make a remarkable life possible. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Plan the Buffer Before the Week Fills Up

The challenge from this episode is not complicated: go back to your calendar and plan the buffers before everything else takes the space. Protect the exercise. Protect the reflection. Protect the time with the people who help you grow. And if the calendar is already full, look honestly at what is there that belongs to someone else, train that person this week, and take the task off your plate permanently. As Keith Cunningham writes in The Road Less Stupid: the quality of your thinking determines the quality of your outcomes. You cannot think well when you are buried. You cannot lead well when you are depleted. Build the buffer and watch what comes back.

On we go.

FAQ

Why do high performers become marginal over time when their workload increases without support?

Because performance requires capacity, and capacity requires buffers. Kingman’s formula describes this mathematically: when utilization is high and variation is present, delay compounds. A person operating at 100% utilization has no response capability when variation hits, and variation always hits. The first unexpected demand consumes whatever margin existed. The second one pushes the person into reactive mode. Over time, the energy and initiative that produced improvement efforts, creative thinking, and genuine leadership get fully consumed by immediate demands. The person is still working hard. The output is marginal because the system was never designed to protect the conditions that excellent performance requires.

What is the connection between Kingman’s formula and personal capacity management?

Kingman’s formula says that the time required to complete work is not just the cycle time. It is the cycle time plus a buffer for variation plus a buffer for being near full utilization. Applied to a person’s week, it means the time required to perform excellently is not just the time the tasks take. It is that time plus margin for unexpected demands plus time for the thinking, reflection, and restoration that make sustained high performance possible. A week with no buffer is a week where the first disruption breaks the system. A week with intentional buffer is a week where disruptions are absorbed and performance stays high.

What does it mean to delegate what people should do rather than what they can do?

Brandon Montero introduces this distinction clearly. Sometimes a task stays on a leader’s plate not because they are the only one qualified to do it but because the person who should own it has not yet been trained. The leader looks at the task, concludes that the team member is not ready, and does the task themselves. That is a temporary solution that becomes permanent. The training priority is to invest time in developing the team member’s capability so the task can be transferred. Every task that is successfully transferred is a buffer permanently added to the leader’s capacity. Delegation is not just time management. It is a training strategy.

How do you protect thinking time when the week is already full?

Schedule it before anything else occupies the space. Jason Schroeder describes the experience of driving through northern Arizona with a quiet car and capturing 35 significant business ideas because there was nothing else competing for that mental space. Thinking time does not require a retreat or a dedicated day. It requires a protected 30 to 60 minutes where no input is competing for attention. That might be a morning walk, a drive without a podcast, a blocked calendar appointment that nobody can schedule over, or the 10 minutes between tasks that the military found doubles endurance. The specific format does not matter. The protection of the time does.

How does building personal capacity connect to leadership performance on a construction project?

Directly and measurably. A leader who is depleted cannot remove roadblocks with the speed and clarity the field needs. A leader who has no thinking time cannot see around corners or anticipate coordination problems before they become delays. A leader who is not exercising, reflecting, or maintaining relationships cannot sustain the energy and judgment that field leadership requires day after day. The superintendent who protects their buffer is the superintendent whose crew notices that their leader always has bandwidth for a real conversation, always has a clear answer, and always shows up ready. That is not a personality trait. It is a capacity management outcome.

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

Supers, Foremen, & Takt Control

Posted on May 13, 2026May 13, 2026 by Jason Schroeder

Read 13 min

What Is Takt Control? The Short Interval Planning Standard Every Foreman and Superintendent Needs

There is a generation of foremen and assistant superintendents on construction projects right now who cannot create a three-week schedule on their own. Not in the Last Planner System. Not in Excel. Not on graph paper. They were promoted because they were good at the work. They were put in charge of crews before anyone invested in the planning capability they needed. And the superintendents above them, who do know how to schedule, are overwhelmed managing larger scopes and trying to train upward and downward simultaneously. The result is a field leadership layer that is executing from memory and instinct rather than from a plan. This is not a character failure. It is a training gap that the industry created and now has to solve.

The Problem Nobody Wants to Name

Most construction projects in the United States do not have a functional short interval planning system at the foreman and assistant superintendent level. The master schedule exists somewhere. The project superintendent may have a loose look-ahead. But the people who are closest to the daily execution of work, the foremen who lead crews and the assistant superintendents who support them, are planning their work in their heads, improvising their sequences, and restarting from scratch every Monday. There is no standard. There is no template that repeats. There is no cycle to improve. Every week is a new round of figuring it out, which means every week carries the same variation as the last. The project never gets better. It just continues.

The Failure Pattern

The failure pattern has a specific history. Before the Last Planner System, superintendents would take the CPM schedule, break it into one to six week look-aheads, and hand those to trade partners. It was a push system. The trades had no input into the sequence and no ownership of the commitments. But at least there was a written plan. Then the Last Planner System introduced pull planning, six-week make-ready look-aheads, weekly work plans built collaboratively with the trades, and a percent plan complete metric to measure execution reliability. That was better. The trades had voice in the plan. Commitments were made with genuine input.

But here is what happened over time. The people who knew how to run the Last Planner System got promoted or moved on. The next generation of foremen and assistant superintendents did not receive the training. And now, on many projects, even the collaborative work plan creation has disappeared. The weekly meeting happens. People say what they think they will work on. Nobody checks whether it aligns with the master schedule. The percent plan complete gets tracked but nobody investigates why tasks fail. And the plan, such as it is, gets rebuilt from scratch the following Monday. The system cannot improve because it never repeats anything long enough to get better at it.

What Good, Better, and Best Actually Look Like

Before defining Takt Control, it helps to be honest about where most projects sit on the capability spectrum.

Good means the superintendent creates a three-week look-ahead schedule in Excel and distributes it to the trades. That is better than running without any written short-interval plan. It is still a push system because the trades did not build it, but it at least makes the upcoming work visible and creates a reference point for daily decisions.

Better means the project has a functioning Last Planner System. The trades participate in pull planning. A six-week make-ready look-ahead tracks what needs to be ready and who is responsible for making it ready. Weekly work plans are built collaboratively and the team targets above 80% plan complete. Trade partners have genuine input and the plan reflects real commitments.

Best is Takt Control. Every Takt wagon, meaning every work package that moves through each zone on a defined Takt time, has a standard sequence of work steps mapped out for each day of the cycle. A four-day Takt time means day one, day two, day three, and day four are each defined. The trades participate in building that standard template once, during the initial pull planning process. Then that template repeats through every zone, floor, or area of the building, up to fifty or more repetitions on a large project. The foreman and the assistant superintendent do not recreate the weekly work plan from scratch each Monday. They execute the standard, track whether it is flowing, identify where the cycle time can be reduced, and refine the template as they go. That is the plan-do-check-act cycle applied to production.

What Takt Control Means in Practice

Takt Control is the practice of managing the work steps within each Takt wagon to create flow. The project superintendent or senior superintendent manages the overall Takt plan: the zone sequence, the train of trades, the buffer system, the overall rhythm. The assistant superintendent and foreman manage what happens inside each wagon: are the work steps being executed in sequence, are the cycle times matching the plan, is the crew appropriately loaded or being overutilized, is there a small buffer at the end of each cycle that confirms the wagon is not overpacked?

The target inside a Takt wagon is not 80% plan complete. It is 100%. The difference matters. A percent plan complete target at the weekly work plan level acknowledges that some tasks will not get done and measures how many did. A Takt Control target at the wagon level says that within this four-day cycle, in this zone, all of the work steps must complete. If they do not, the flow breaks. The next zone starts at a disadvantage. The sequence degrades. The standard is not a suggestion; it is the minimum acceptable outcome for that cycle.

When the foreman and assistant superintendent are on the floor watching the work flow through the cycle, they are answering three questions continuously. Is the work following the standard sequence? Is the cycle time matching the plan or is it running long? Is the crew at the right utilization level, meaning not so loaded that any variation pushes them into overburden? The answers to those three questions drive the adjustments that make each subsequent cycle faster, more reliable, and better buffered than the previous one.

Why This Matters More Than Last Planner Alone

The Last Planner System is excellent at what it does: creating collaborative commitments and surfacing coordination problems early. What it does not provide on its own is a standard that repeats and can be improved. When a trade partner is asked every week, from scratch, what they think they should be doing this week, two problems occur. First, the answer may not align with the Takt rhythm or the master schedule because it is being generated independently without reference to a repeating standard. Second, the cognitive load of recreating the weekly work plan from scratch every week consumes capacity that should be going into execution and improvement.

Compare that to a foreman who has a standard four-day sequence template for their scope of work. Once the template is created, the weekly planning meeting is not about invention. It is about confirmation and refinement. Did the last cycle match the template? Where did variation come from? What can be adjusted to make the next cycle more reliable? That conversation is faster, more specific, and more productive than starting from a blank page every Monday. And because the template repeats, every improvement sticks. The work gets better over time in a way that new-from-scratch weekly planning never enables.

The Minimum Standard and What Comes Next

Every foreman and every superintendent must be able to schedule. That is not negotiable. The minimum acceptable standard is a hand-drawn Gantt chart on graph paper if no computer is available, though every foreman and assistant superintendent should be able to use Excel for this purpose. The inability to schedule is not a technology problem. It is a training gap that needs to be closed, and it needs to be closed before someone is put in charge of a crew.

Once the scheduling capability exists, the path is clear: build the Takt plan at the project level, pull plan the standard work sequences with the trades for each Takt wagon, document the day-by-day work steps within each cycle, and then execute, track, and refine that standard through every repetition. The foreman and assistant superintendent are the people who live inside that cycle. Their job is not to manage paperwork. Their job is to stand on the floor, watch the work flow, and make it better every time it repeats.

Takt Control is what happens when all of that comes together. Flow is the measure that tells you whether it is working. If work is moving steadily through each zone, finishing the wagon on time, and starting the next zone without trades stacking, the system is functioning. If wagons are colliding, cycle times are running long, and every week feels like the first week, the standard is not yet working. Fix the standard. Improve the standard. Repeat.

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

The Industry’s Next Step

The construction industry has the tools it needs to run production-level field operations. Takt planning provides the rhythm. Last Planner provides the collaborative commitment framework. Takt Control provides the standard work loop that makes improvement possible through repetition. What is missing is the training and the culture that makes all three of those function at the foreman and assistant superintendent level. As Jason closes this episode from a hotel room in Guadalajara, the ask is direct: get your foremen and assistant superintendents scheduling. Get the standard work steps into each Takt wagon. Get them on the floor watching the cycle and making it better every time. That is how this industry builds the manufacturing-level consistency it has always been capable of but never quite achieved.

On we go.

FAQ

What is the difference between the Last Planner System and Takt Control?

The Last Planner System is a collaborative commitment system where trade partners pull plan to milestones, identify make-ready requirements in a six-week look-ahead, and build weekly work plans together. It measures execution reliability through percent plan complete and targets above 80%. Takt Control operates at a more granular level: within each Takt wagon, a standard sequence of work steps is defined for each day of the cycle. That standard repeats through every zone of the building and gets refined with each repetition. Where Last Planner asks trades to commit to what they will do this week, Takt Control defines what right looks like in advance and then measures whether the cycle achieved it. The two systems are complementary: Last Planner coordinates commitments between trades at the project level, and Takt Control optimizes the execution within each wagon at the floor level.

Why must every foreman and superintendent know how to schedule?

Because a foreman or superintendent who cannot create a schedule cannot see the future. They cannot identify what preparation needs to happen before the crew arrives. They cannot communicate commitments with precision. They cannot align their work with the trades ahead of and behind them. Scheduling is not a clerical function. It is the mechanism through which field leadership converts the plan into executable daily direction. The minimum standard is a Gantt chart on graph paper. The practical standard is an Excel-based short-interval schedule. The aspirational standard is a Takt wagon with documented work steps that are tracked and improved every cycle. None of those are possible for someone who has not developed the capability to schedule.

What does it mean to target 100% plan complete inside a Takt wagon?

It means that the standard for execution within a Takt cycle is completion, not a percentage of completion. When a Last Planner weekly work plan targets above 80% plan complete, it acknowledges that some tasks will not get done and measures the proportion that did. Inside a Takt wagon, the wagon must complete. All the work steps assigned to that zone in that cycle need to finish, because the next trade is entering that zone at the start of the next cycle. If 80% of the tasks complete, the next trade enters a zone that is not ready, the sequence breaks, and the trades begin to stack. The 100% target is not about being harder on people. It is about protecting the sequence that makes flow possible.

How does Takt Control apply the plan-do-check-act cycle?

The Takt wagon standard is the plan. Executing the work steps within the cycle is the do. Measuring whether the cycle time matched the plan, whether variation was absorbed within the cycle, and whether the crew was appropriately loaded is the check. Adjusting the standard, reducing a step that was taking longer than expected, resequencing two activities that were interfering with each other, or right-sizing the crew for the actual work content, is the act. Because the wagon repeats through every zone of the building, every improvement made in one cycle carries forward into the next. Over twelve to fifty repetitions, the cycle time decreases, variation reduces, and the crew develops a reliable rhythm that produces the flow the project needs.

What should the assistant superintendent be doing in a Takt Control system?

The assistant superintendent’s job is to live inside the Takt wagon. That means being on the floor where the work is happening, watching the sequence unfold against the standard, identifying where cycle times are running long or variation is entering the system, and working with the foreman to adjust the sequence, the crew loading, or the material delivery timing to make the next cycle better. The assistant superintendent is not managing paperwork. They are the quality control mechanism for the production rhythm. They are the person who notices that a particular work step is consistently taking six hours instead of the planned four, investigates why, fixes the input condition, and carries that fix forward into every subsequent repetition. That is Takt Control.

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

Why Your 5 Day Takt Time Isn’t Working…

Posted on May 13, 2026May 13, 2026 by Jason Schroeder

Read 12 min

Why Your Five-Day Takt Time Is Probably Working Against You

About 75% of the people who have tried Takt planning come away as raving fans. The project moved better. The trades coordinated more reliably. The schedule became a real tool rather than a document. That is the overwhelming experience. The other 25% say they tried it and it did not work. And in almost every case where it did not work, the diagnosis is the same: they locked themselves into a five-day Takt time, forced it to run between Monday and Saturday, and never escaped the constraints that created. The tool did not fail them. The way they used it did. This episode, recorded in Guadalajara, Mexico before a Takt training session at LCI Mexico, addresses that directly.

The Problem Nobody Names

The five-day Takt time has become the default setting for almost everyone who learns Takt planning. It makes intuitive sense: the workweek is five days, the weekend provides a natural buffer, and organizing everything into weekly rhythms feels clean and manageable. The problem is that defaulting to five days without asking whether five is the right number for the project produces a schedule that is not optimized. It produces a schedule that happens to fit a calendar rather than one that is calculated to fit the production system. And a schedule that fits the calendar rather than the production system will eventually descend into a push scenario when the inevitable interruption hits.

The Failure Pattern

The failure mode is specific and predictable. A team adopts Takt planning with a five-day rhythm locked between Monday and Saturday. They pack their Takt wagons, the work packages that move through each zone, at or near full capacity for the five-day window. Everything looks structured and intentional. Then a delay hits. A material shortage on Tuesday. A rain day. An inspection that does not get scheduled in time. The interruption eats into the five-day cycle and the work for that wagon does not finish by Saturday. The superintendent, trained to keep the project moving, starts the next wagon on Monday anyway, because that is when it was scheduled to start. Now two wagons are in the same zone at the same time. The trades are stacked. The flow is gone. What looked like Takt planning has become a push system dressed in Takt language, and the team concludes that Takt planning does not work.

The System Did Not Fail. The Buffer Did.

The buffer capacity was there. But because the schedule was locked between Monday and Saturday in five-day increments, the only way to eat into a buffer was to delay the entire sequence by a full five days, which nobody was willing to do for a one-day interruption. So instead of shifting the phase by one day to maintain the sequence, the superintendent pushed through. The wagons collided. The chaos followed.

Jason Schroeder used a five-day Takt time for the majority of his construction career without running into this problem, and the reason is instructive. His wagons were never packed above 80% of the five-day capacity. The cycle time inside each wagon was closer to four to four and a half days, not five. That slack inside the wagon was enough to absorb the routine variation that every project generates. When the wagon was not overpacked and the schedule was not rigidly locked to calendar weeks, small delays did not cascade. The system could breathe. But that approach required discipline about not filling every available moment with planned work, and most teams using Takt today are not applying that discipline.

Two Different Jobs for the Five-Day Takt Time

Here is the critical distinction that this episode makes clear: the five-day Takt time has a legitimate and valuable role in preconstruction, and a different and more complicated role once the project moves to detailed planning.

At the macro level, meaning during schematic design, design development, and the proposal phase, a five-day Takt time is the right tool for establishing an honest overall project duration. When you plan a project at the macro level in five-day increments, blocking out holidays and mapping the flow at a high level, you build natural buffers into the system. The result is a project duration that is typically within 5% of what it actually takes to build. Compare that to CPM schedules, which in Jason’s tracked experience undercut the actual project duration by approximately 20% on average. That 15-percentage-point gap represents projects that were promised at durations they could never achieve, which is why teams end up pushing, crashing, and spending more than the budget to try to hit a date that was unrealistic from the beginning.

So at the macro level: use the five-day Takt time. It calibrates the overall duration honestly. It protects the general conditions and general requirements budget from being consumed by design scope that the project could not afford. It gives the owner and the team a realistic target from the beginning.

At the norm level, which is where the detailed day-by-day production plan lives, the five-day Takt time needs to be questioned and potentially replaced with whatever Takt time actually optimizes the project.

How to Find the Right Takt Time for Your Project

The optimization process works like this. You break the building into Takt zones, pull plan a representative zone to establish the work sequence, package that sequence into a Takt wagon, and then use Little’s Law to calculate the project duration: Takt wagons plus Takt zones minus one, multiplied by the Takt time, equals the phase duration. You then vary the number of zones and the Takt time to find the combination that gives you the most buffers within the target project duration.

If you start with a five-day Takt time and run the optimization, you may find that a three-day or four-day Takt time with a different number of zones produces 35 additional buffer days. Or 60. Or 120. Those buffer days are available to you, but only if you allow the Takt time to be something other than five. If you lock yourself into five before you run the optimization, you never discover the alternative. You leave those buffers on the table and run the project tighter than it needs to be.

Here Is What to Apply on Your Next Project

Before you finalize your Takt plan at the norm level, work through these questions:

Have you run the optimization to find the Takt time and zone count that produces the most buffer days within the needed project duration, or did you default to five?
Are your Takt wagons packed to 100% of the Takt time, or is there room inside each cycle to absorb routine variation without cascading?
Is your schedule locked between Monday and Saturday in a way that prevents you from shifting the phase by one or two days when an interruption hits?
Do you have a defined method for eating into buffers, shifting the entire phase by days rather than pushing wagons into each other when a delay occurs?
Does each Takt wagon have standard work steps documented so that the team can track whether the sequence is flowing and improving?

If most of those answers reveal a locked five-day system, the production plan has an optimization problem that will show up as either wasted time or a push scenario, and usually both.

What the Assistant Superintendent’s Job Actually Is Inside a Takt System

Jason closes this episode with a role definition that is worth stating directly. Each Takt plan needs wagons with documented work packages and work steps. The assistant superintendent’s job is to know, within each wagon, how the sequence flows for every trade in every zone. Not in a general sense. Specifically. And then to help each trade get faster and better at that sequence every cycle. The feedback loop of standard work, plan-do-check-act, improving cycle time through repetition and observation: that is where Takt planning delivers its manufacturing-level consistency. That is how a construction project gets faster over time rather than slower. And none of it is available if the Takt time was never optimized in the first place.

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

Open Your Mind to a Different Number

The invitation is simple. Stop assuming five is the answer before you have asked the question. Use five at the macro level in preconstruction because it builds honest buffers into your overall duration estimate. Then, when you move into norm-level planning, run the optimization. Let the math tell you whether the right Takt time is two, three, or four. Build your buffers into the plan. And when delays come, which they will, shift the entire phase by days to protect the sequence rather than pushing wagons into each other to protect the Monday start date. As Hal Macomber observed in the previous episode: Takt is a countermeasure to variation. A five-day Takt time locked to the calendar is a system that cannot countermeasure variation because it has no room to flex. Give the system room. Give the trades room. And watch what happens when the plan finally has enough buffer to absorb the reality of the field.

On we go.

FAQ

What is the difference between a macro-level and a norm-level Takt plan?

The macro level is the high-altitude view used in preconstruction, schematic design, and the proposal phase. At this level, a five-day Takt time is appropriate because it builds natural buffers into the overall project duration estimate. When planned this way, the project duration comes in within about 5% of what the project actually takes, compared to CPM schedules that typically undercut by around 20%. The norm level is the detailed day-by-day production plan where the actual Takt time and zone count are optimized using Little’s Law. At this level, defaulting to five days without running the optimization leaves buffer days on the table and can lead to a push scenario when interruptions occur.

Why does a locked five-day Takt time prevent you from eating into buffers properly?

Because eating into a buffer in a five-day system locked between Monday and Saturday requires delaying the entire sequence by a full five days, which teams almost never do for a one or two day interruption. Instead, they push the next wagon into the zone on Monday as scheduled, even though the previous wagon has not finished. The wagons collide, the trades stack, and what was Takt planning becomes a push system. If the Takt time is three or four days, and the schedule is not locked to the calendar week, the team can shift the entire phase by one or two days when a delay hits, maintain the sequence, and absorb the interruption without stacking trades.

How do you optimize a Takt plan to find the right Takt time for a project?

The process starts with breaking the building into Takt zones, pull planning a representative zone to establish the work sequence, and packaging that sequence into a Takt wagon with documented work steps. Then you apply Little’s Law: Takt wagons plus Takt zones minus one, multiplied by the Takt time, equals the phase duration. By varying the number of zones and the Takt time, you find the combination that produces the most buffer days within the needed overall project duration. The Takt time that results from that optimization might be two, three, or four days rather than five. Accepting whatever the math produces is what gives you the buffer to absorb variation without pushing.

What happens when Takt wagons are overpacked in a five-day system?

When wagons are packed to full capacity for five days and a delay occurs on Tuesday, the work for that cycle does not finish by Saturday. If the superintendent starts the next cycle on Monday because that is what the schedule says, two cycles are now occupying the same zone at the same time. The trades are stacked. The flow breaks. The system is now a push system. Jason’s practice for most of his career was to pack wagons to no more than 80% of the five-day capacity, which left a natural cushion inside each cycle. The internal cycle time was closer to four days, which meant small delays were absorbed without cascading. That discipline, which most teams do not apply when they are defaulting to five days, is what kept the system from decomposing.

What is the assistant superintendent’s role within a Takt production system?

The assistant superintendent’s specific job is to know the standard work sequence within each Takt wagon for every trade in every zone, and then to help each trade execute that sequence faster and more reliably with each repetition. This is where the plan-do-check-act improvement cycle lives in Takt planning. By tracking whether the sequence is being followed, identifying where the cycle time is longer than planned, and working with the trade to find a faster sequence, the assistant superintendent is the person who drives the continuous improvement that Takt planning makes possible. This function only works when the Takt time is right, the wagons are not overpacked, and the trades have room to improve rather than just survive.

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

The Jack in the Box Effect

Posted on May 13, 2026May 13, 2026 by Jason Schroeder

Read 12 min

The Jack in the Box Effect: Why Leadership Decisions Made in a Silo Always Backfire

Somewhere inside Jack in the Box headquarters, someone made a decision that seemed entirely reasonable. Set a timer. Measure how long each car waits in the drive-thru. Create accountability for speed. Deliver the food faster. Take better care of customers. The logic is clean and the intention is good. The result is that employees at Jack in the Box locations across the country now ask customers, mid-transaction, to put their cars in reverse and back up two car lengths so that a timer resets and the metric looks better. The food is no slower. The customer is no happier. The experience is now worse because the customer has been inconvenienced, possibly put at risk from the car behind them, and left with the distinct impression that something strange just happened. The strategy produced the opposite of its intended effect. That is not bad luck. That is what happens when you try to fix a culture problem with a policy.

The Pain on Every Jobsite

The same dynamic plays out on construction projects constantly. A company decides to measure something: safety incidents, PPC scores, schedule adherence, self-perform costs. A metric is defined. Accountability is attached. The people being measured respond not by improving the underlying behavior, but by adapting to the metric in ways that make the number look better without changing the reality. Safety incidents get underreported. PPC scores get inflated by superintendents who put things on the weekly plan they know will get done regardless. Schedule dates get managed by adjusting logic rather than executing work. Self-perform gets avoided to keep safety numbers clean. The measurement system produces behavior that is exactly opposite to what it was designed to produce.

The Failure Pattern

The pattern is consistent and it starts in a conference room. A leadership team or a continuous improvement team or a development group identifies a problem, designs a solution, defines a metric, and issues a policy without going to the place where the work actually happens and asking the people who do it whether the solution will work. The people who receive the policy understand immediately whether it is grounded in field reality or not. They can see the loopholes. They know what the workaround looks like. And because they were not part of the design, they do not feel ownership of the outcome. When a policy imposes accountability without providing influence, the people affected will find ways to look compliant without actually changing anything. That is not a character problem. That is a rational response to a bad system.

Leadership Teams Are Often the Last to Know

Here is the uncomfortable truth that this episode names directly: leadership teams are frequently unqualified to make the decisions they are making, not because they are unintelligent, but because they do not have the information that only exists at the place of work. A continuous improvement team that designs a safety program without ever consulting a foreman, a superintendent, or a field engineer does not know what problems that program will create in the field. A company that grades superintendents on self-perform safety outcomes they have no authority over has created a system where the metric and the authority are disconnected, which means the metric will be gamed and the outcome will be the opposite of what was intended. Superintendents who have no control over how self-perform crews are composed, trained, or managed will respond to safety accountability by doing everything they can to keep self-perform off their projects. The company loses the margin that self-perform provides. The intended safety improvement never materializes. The Jack in the Box effect.

What Happened at the Drive-Thru and What It Means

Jason Schroeder went to Jack in the Box after donating blood, ordered food for himself and his kids, and was asked by the drive-thru attendant to back up two car lengths. The attendant did not explain why. Jason had to guess. The car behind him did not know he was coming. He backed up, saw a hand gesture telling him to stay, waited, then was waved forward. The food came. He was annoyed. He has had this happen six or seven times. He still goes to In-N-Out and Culver’s instead of Jack in the Box by default.

The drive-thru timer was supposed to improve customer service. It made the service measurably worse for customers who encountered it. The employees were not trying to create a bad experience. They were responding to a metric that their culture had not prepared them to treat as meaningful. When the culture does not genuinely care about customer experience, a timer does not create that care. It creates a workaround. And the workaround produces the Jack in the Box effect.

You cannot multiply negatives. If the food is not good and the service adds friction, those are not two separate problems with separate solutions. They compound. Two negatives multiplied make the situation worse, not better. A policy that adds a third negative, the annoyance of being asked to back up your car mid-transaction, does not cancel out the others. It deepens the hole.

What Culture Actually Is and Why Strategy Cannot Fix It

Culture is not a mission statement or a set of values on a conference room wall. Culture is the story a team actually lives by, the behaviors that get reinforced and the ones that get tolerated, and the beliefs that shape how every individual responds when nobody is watching and no policy is being enforced. Peter Drucker’s observation that culture eats strategy for breakfast is not hyperbole. It is a description of what happens when a strategic decision meets a culture that was not built to support it. The decision does not change the culture. The culture absorbs the decision and converts it into something consistent with existing behavior.

Jack in the Box did not have a culture built around genuine customer care. When they added a timer, the culture responded by finding the fastest way to manage the timer rather than the fastest way to genuinely serve the customer. The timer was a strategy. The culture was the reality. The culture won.

In construction, this plays out in every company that has tried to implement lean tools, scheduling systems, or quality programs without first building the culture that makes those tools meaningful. The Takt plan becomes a document the field ignores. The Last Planner system becomes a PPC exercise that nobody believes reflects real commitments. The 5S initiative runs for three weeks and then the site returns to its previous condition. Not because the tools are wrong. Because the culture was not built to support them.

Here Is What Total Participation Actually Requires

Before any policy, metric, program, or system is implemented, ask these questions honestly:

Have the people who will be directly affected by this decision been asked for their input before the decision was made?
Do the people being held accountable to this metric have genuine influence over the outcome it measures?
Has anyone gone to the place of work and observed what actually happens there before designing a solution?
Are there loopholes or workarounds in this policy that, if used by someone not committed to the culture, would produce the opposite of the intended result?
Is the leadership team that is making this decision living under the same rules they are implementing?

If any of those answers is no, the Jack in the Box effect is a real risk. The solution is not to refine the policy in the conference room. It is to go to the field and ask the people who will implement it whether it will work.

What Good Looks Like

Ryan Schmidt and Lauren Atwell of Petty Coach Smith Civil Contractors in Florida provide the counterexample. Every job visit involves them being present. Every training deployment involves them being there. Every consultation includes pulling in the superintendents and subject matter experts who are closest to the work. When decisions are made that affect the field, the field is part of making them. The organizational transformation work they are doing with Elevate Construction includes the people who will have to implement it from day one. That is not a soft cultural preference. It is a production strategy. When people have input into the decisions that affect their work, they own the outcomes of those decisions. When they do not have input, they manage the metrics while the underlying problem continues.

The goal at Elevate Construction is a construction industry where decisions about how work is done are made with the people who do the work, not for them. That is the only approach that produces outcomes that are durable rather than gamed. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Stop Managing From a Distance and Start Leading From the Work

The closing challenge from this episode is direct: stop making decisions in a silo and expecting them to change a culture. Leadership does not produce culture through policy. It produces culture through presence, participation, and consistency. If you would not want to live under a rule yourself, you should not implement it without understanding how the people who will live under it will respond. If you are grading someone on an outcome they cannot control, you are setting up a system that will produce exactly what Jack in the Box produced: people gaming a metric to avoid consequences, with results that are worse than if the metric had never been introduced. As W. Edwards Deming put it: every system is perfectly designed to get the results it gets. Design the system with the people inside it, and the results will be what you actually want.

On we go.

FAQ

What is the Jack in the Box effect and how does it apply to construction?

The Jack in the Box effect is what happens when a leadership decision made without frontline input produces the opposite of its intended result. At Jack in the Box, a drive-thru timer designed to improve customer service led employees to ask customers to back up their cars and reset the clock, which worsened the customer experience. In construction, the equivalent is any policy, metric, or system implemented from a conference room without field input that causes the people affected to find workarounds that make the measurement look better without improving the underlying condition. Self-perform safety programs that grade superintendents on outcomes they cannot control, scheduling metrics that get managed by adjusting logic rather than executing work, and quality programs that get documented but not followed are all versions of the same effect.

Why does culture eat strategy for breakfast in construction?

Because the people doing the work respond to the culture they are embedded in, not to the strategy that was written above them. A strategy that says to implement Takt planning does not produce Takt planning in a culture that does not believe in it. A policy that says to report safety incidents does not produce honest reporting in a culture where reporting is associated with punishment rather than system improvement. Strategy defines what the organization wants. Culture defines what the organization actually does. When they are misaligned, culture wins. The only way to make strategy effective is to build the culture that makes following the strategy feel like the natural and right thing to do.

How do you avoid the Jack in the Box effect when implementing a new policy or system?

Go to the place of work before the decision is finalized. Ask the people who will be most affected by the decision what they think will happen when it is implemented. Ask specifically whether there are ways the policy could be gamed or worked around that would produce results worse than the current condition. Give those people genuine influence over the design of the policy, not just an opportunity to provide feedback that gets ignored. And do not hold people accountable for outcomes they have no authority over. If any of those conditions cannot be met, the implementation should be delayed until they can.

What does it mean to hold someone accountable to something they have no influence over?

It means creating a metric that measures an outcome the person cannot meaningfully affect, and then attaching consequences to their performance on that metric. The superintendent who is graded on self-perform safety in a company where self-perform crews are independently managed, composed, and trained cannot improve that metric by doing their job better. They can only avoid the consequence by keeping self-perform off their project entirely, which is exactly what happens. The metric produces the opposite of the intended outcome. Accountability is only meaningful when the person being held accountable has genuine authority over the inputs that produce the outcome being measured. Otherwise it is punishment disguised as management.

What is total participation and why does it matter for organizational change?

Total participation means that the people who will be affected by a decision, at every level of the organization, have genuine input into that decision before it is made. Not a survey after the fact. Not a town hall where the decision has already been made and the purpose is to explain it. Genuine involvement in designing the solution. Hal Macomber described this principle in the previous episode: the expertise and experience of the whole workforce, including the people handling material and using physical tools, is required to improve flow. Jason extends that principle to organizational decisions: if the decision affects the field, the field must be part of making it. Companies that operate this way, like Ryan Schmidt and Lauren Atwell’s organization, build cultures where people own the outcomes of decisions rather than managing around them.

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

General Offerings

Company Offerings

Systems

Month: May 2026

Day in the Life of a Project Engineer (What Really Happens on the Job)

Field Support for Project Engineers (How to Actually Help the Jobsite Succeed)

Change Management for Project Engineers (RFIs, Change Orders, and Cost Control)

Project Engineer Coordination: How to Align Trades and Keep Projects Moving

In Sync

Personal Buffers, Feat. Brandon Montero

Supers, Foremen, & Takt Control

Why Your 5 Day Takt Time Isn’t Working…

The Jack in the Box Effect

Subscribe Now

Our Office

Get In Touch

Company

Follow Us

General Offerings

Company Offerings

Systems

SUBSCRIBE NOW !

Subscribe to our newsletters and stay updated!