How to Manage Handoffs, Progress Updates, Delays, and the Lockline in Takt Planning

How to Manage Handoffs, Progress Updates, Delays, and the Lock Line in Takt Planning

A Takt production plan that never gets updated is not a production management tool. It is a historical artifact a record of what the team planned before reality arrived. Every construction project encounters delays, missed promises, prerequisite work that was not ready, and activities that took longer than the Takt time allowed. The question is not whether those things will happen. The question is whether the team tracks them, learns from them, and recovers systematically or whether they absorb the impact silently until the buffer is gone and the milestone is at risk.

InTakt’s tracking and reporting features are where the Takt Production System becomes a steering and control mechanism rather than just a scheduling format. The lock line defines the commitment window. Handoffs track the critical promises between trade partners. Variance logging captures what went wrong and why. The reporting suite makes the patterns visible. And the recovery logic gives the team a menu of options for pulling the plan back without stacking trades or burdening anyone. Here is how each of those elements works.

The Lock Line: The Boundary of Commitment

The lock line is one of the most important concepts in Takt Steering and Control. In InTakt, the lock line is a visible boundary on the production plan that defines the committed window the activities that trade partners have confirmed they will execute in the current planning cycle. Once the lock line is set, everything within that window is no longer a plan. It is a commitment.

This is standard Last Planner theory applied to the visual production plan. The look-ahead identifies and removes roadblocks. The weekly work plan converts ready activities into specific commitments. The lock line is the moment when the production plan shifts from planning mode to commitment mode and from that point forward, any activity within the locked window that is not completed as promised becomes a variance that must be tracked, root-caused, and learned from.

When the lock line is moved forward as it is every planning cycle the window shifts, and InTakt begins tracking variances for the activities that were committed and not kept. A promise made in the previous cycle that was not delivered shows up as a variance requiring a root cause. That tracking is what drives the continuous improvement loop: plan, do, check, adjust. Not just the plan. Not just the do. The check and the adjust, which require knowing specifically what went wrong and why.

Handoffs: The Critical Promises Between Trades

Inside the committed window, handoffs are the most important tracking item. A handoff is a specific promise from one trade partner to the next the predecessor committing to have their scope complete in a specific zone by a specific date so that the successor can enter. These are not informal understandings. They are the promises that connect the whole train of trades, and when one handoff is missed, every wagon behind it feels it.

InTakt tracks handoffs explicitly within the production plan. Trade partners commit to handoffs in the weekly work plan, and those commitments are visible as connection points between activities in the plan. Whether each handoff was kept or not is tracked and reported separately from general activity completion because a handoff is categorically more important than an individual activity that has no immediate downstream consequence.

This is why Perfect Handoff Percentage is a more important KPI than Percent Plan Complete. Percent Plan Complete tracks all activities equally a completed task with no downstream dependency counts the same as a critical handoff. Perfect Handoff Percentage tracks only the commitments that directly affect the next trade’s ability to enter the zone. On a phase with high PPC but low PHP, the team is completing a lot of non-critical work while consistently missing the handoffs that protect flow. The PHP reveals that. The PPC masks it.

The target for Perfect Handoff Percentage is above 80%. Below that, the production system has a systemic problem that needs to be diagnosed not just tracked.

Statusing Activities: Done, Received, and Approved

Marking activities complete in InTakt uses three distinct status levels: done, received, and approved. Each represents a different verification step for the work’s completion.

Done means the trade has completed their scope in the zone. Received means the successor trade has checked the handoff condition and confirmed the zone is ready for them to enter. Approved means the GC, the inspection authority, or the quality standard has been verified against the conditions of satisfaction established in the precon meeting. All three can be tracked independently, which means the production plan knows not just that work happened, but that the work was handed off properly and met the required standard.

To status an activity in InTakt, click on the activity in the production plan. The properties panel appears on the right, with the tracking options visible. Select done, received, or approved as appropriate. The activity updates immediately in the plan, and the status is logged with the user who marked it and the timestamp of the update. That log creates the verification trail that any handoff or quality dispute will eventually require.

When a Promise Is Not Kept: Variance Tracking

When an activity is not completed as promised when what was committed in the lock line window was not delivered InTakt opens a variance dialogue that asks for two things: the new expected completion and the reason for the variance.

The reason categories align with the standard roadblock taxonomy: prerequisite work not complete, design information not in hand, materials not on site, equipment not available, layout not ready, weather, inspection failure, and others. Selecting the category assigns a root cause to the variance. Adding a specific note “substrate was not ready” or “RFI still open” makes the root cause actionable rather than just categorized.

This is the PDCA cycle made systematic. Plan: the commitment was made. Do: the work was attempted. Check: the variance was identified with a root cause. Adjust: the root cause drives a specific corrective action before the next cycle. Without the check step without capturing specifically what went wrong and why the team is planning and doing but never actually improving. The variance log is the institutional memory that turns a missed promise into a lesson the whole project learns from.

Trade Stacking and Trade Burdening Are Never the Answer

When an activity slips and the cascade shows trades running into each other, the instinct is to compress the plan push the delayed trade to finish faster, overlap the successor into the zone before the predecessor is done, or stack multiple trades into the same area to make up time. All of those responses are trade stacking or trade burdening, and they are never recovery strategies. They are the cause of the problem, applied again.

Trade stacking means too many trades in one area simultaneously more than the space and the coordination capacity can manage safely or effectively. Trade burdening means expecting one trade to be in multiple areas when their crew size and production rate cannot support that. Both increase Work in Progress above the capacity of the resources to complete it, which is the definition of the downward productivity spiral.

The Takt Production System has twelve recovery moves, and none of them involve trade stacking or trade burdening. They range from absorbing the delay in the existing buffers to resequencing around the delayed zone, isolating the delayed wagon onto a separate pull plan, rezoning the successor activities, pulling in swing capacity from workable backlog, or optimizing the phase through the Velaga Method. CPM’s recovery option is crashing adding resources to the critical path, which reliably makes the situation worse. The twelve Takt recovery moves are available in the description of the InTakt onboarding video for reference.

What the Reports Show

The variance data logged through activity statusing flows automatically into InTakt’s reporting suite. The variance report shows every missed promise: when it happened, which task it affected, which phase and area it was in, and the root cause that was logged. The report can be filtered by task, by trade, by phase, or by root cause category, and it can be exported to PowerBI for integration with project reporting dashboards. A pie chart view of variance categories makes the systemic patterns visible if prerequisite work not complete is accounting for sixty percent of all variances, the look-ahead system has a gap in identifying and clearing that category of roadblock.

The handoff report shows weekly and cumulative Perfect Handoff Percentage. The weekly view shows whether the PHP is trending up or down across planning cycles. The cumulative view shows the running average across the phase. The report also lists every handoff that was not made: the task, the phase, the area, what was not delivered, and the dates. This is the document that drives the trade partner accountability conversation not as a blame exercise, but as a systemic identification of where the train of trades is consistently breaking down and what needs to change.

We are building people who build things. The production teams that use InTakt’s tracking and reporting tools the way they were designed locking commitments with the lock line, tracking handoffs as the primary KPI, logging variances with honest root causes, and using the twelve recovery moves to pull the plan back without hurting anyone are the teams that turn the Takt production plan into a learning system that gets better with every 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 Takt Steering and Control discipline that keeps the production plan honest from the first zone to the last.

A Challenge for Builders

At the end of this week’s planning cycle, pull the handoff report for your current phase. Find the three handoffs that were missed most recently. For each one, ask: was the root cause logged at the time? Was a specific corrective action assigned and followed up on? Has the same root cause appeared more than once? If any of those answers is no, the variance tracking loop is incomplete. Close each gap this week log the root cause, assign the corrective action, and check whether the same issue shows up in next week’s handoff report. The Perfect Handoff Percentage improvement that follows is the measure of whether the system is actually learning.

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

On we go.

Frequently Asked Questions

What is the lock line in InTakt and why does it matter for Last Planner implementation?

The lock line is the visible boundary on the production plan that defines the committed window the activities that trade partners have confirmed they will execute in the current planning cycle. Once the lock line is set, everything within that window is a commitment, not a plan. When the lock line moves forward each cycle, InTakt begins tracking variances for any activity within the previous window that was not completed as promised. This is what converts the weekly work plan from an informal list into a trackable commitment system.

Why is Perfect Handoff Percentage more important than Percent Plan Complete?

Percent Plan Complete tracks all activities equally a completed task with no downstream consequence counts the same as a critical handoff. Perfect Handoff Percentage tracks only the commitments that directly affect the next trade’s ability to enter the zone. A phase with high PPC but low PHP is completing non-critical work while consistently missing the handoffs that protect flow a pattern that PPC masks and PHP reveals. The target is above 80%, and below that, there is a systemic production problem that needs diagnosis.

What should happen when an activity is not completed as promised within the lock line window?

Open the variance dialogue in InTakt and select the root cause category prerequisite work not complete, materials not on site, design information missing, or another applicable reason. Add a specific note describing exactly what was missing. That root cause drives the PDCA cycle: the check step identifies what went wrong, and the adjust step produces a specific corrective action before the next planning cycle. Without logging the root cause at the moment of the variance, the team is planning and doing but never actually improving.