How to Track Milestones, Variances, Roadblocks, and Procurement in Construction

How to Track Milestones, Variances, Roadblocks, and Procurement in Construction

The most expensive problems on a construction project are the ones nobody saw coming not because the signals were not there, but because nobody was tracking them in a system that made them visible while there was still time to act. A submittal that was sent three weeks ago and has not been returned is not a surprise on the day the trade needs it to enter the zone. It was visible three weeks ago, and two weeks ago, and one week ago and if the procurement log was being reviewed weekly against the production plan, someone would have escalated it before it became a field stop.

The same is true of roadblocks. A roadblock that surfaces in the afternoon foreman huddle two days before the trade enters the zone has very little resolution time left. The same roadblock identified six weeks out in the look-ahead has six weeks to be solved time to pursue the missing information, reroute the delivery, reschedule the inspection, or adjust the sequence before the train of trades arrives at the zone and finds it blocked.

InTakt’s tracking system workflows for procurement and preparation logs, the roadblock log, and milestone variance tracking is built around one idea: make problems visible while they are still cheap to solve. Here is how each of those systems works.

Workflows: A Dynamic Procurement and Preparation Log

In the reports section of InTakt, the Workflows feature provides a fully customizable logging system that functions as a live procurement log, a submittal tracking log, a trade partner preparation process log, or any other sequential tracking system the team needs. Unlike a static spreadsheet or a submittal register in Procore which tracks whether a submittal was sent, not whether the supply chain feeding the production plan is on track InTakt’s workflows are dynamic, tied to the production plan, and visible in real time.

The columns in a workflow log are user-defined. A procurement log might include: trade partner bought out, submittals prepared, submittals reviewed, submittals sent, architect review, resubmission if needed, purchase order released, fabrication, lead time for fabrication and assembly, delivery, supply chain buffer required, and on-job date. Every step gets a planned date, an actual date, and a duration. As each step is completed and verified, it is checked off. The log shows exactly where each item stands in the procurement sequence at any given point in the project.

The critical advantage over a submittal register is that InTakt’s procurement log is tied to the actual production plan. Each procurement log item is linked to the specific task or wagon in the production plan that depends on it. When the log item is displayed in the schedule view, it appears as an activity connected to the production task it feeds so the team can see not just that a submittal is in review, but how the review timeline aligns with the date the trade needs to enter the zone. If the review is taking longer than planned and the delivery date is compressing against the zone start date, the connection to the production plan makes that visible rather than requiring someone to manually compare two separate documents.

Leveling Procurement Work

One feature that distinguishes InTakt’s workflow system from a conventional procurement log is the ability to level the procurement activities and logic-tie them to each other. If two submittals are under review by the same design team resource simultaneously, the stacking of that review work creates a capacity constraint on the design side exactly the kind of constraint that causes one or both submittals to return late. In InTakt, the procurement activities can be dragged and logic-tied in the schedule view so that the design resource is not asked to review two complex submittals in the same week. When the logic is adjusted in the schedule, it automatically updates the procurement log, keeping the two views synchronized.

This is the difference between tracking procurement as an administrative task and managing it as a production input. The procurement schedule is not a separate document from the production plan. It is part of the production plan visible in the same schedule view, subject to the same leveling logic, and tied to the same milestones.

When Something Goes Off Track: Real-Time Procurement Alerts

When a procurement log item is not completed by its planned date when a step slips past the data date without being verified InTakt flags it in red automatically. The team does not need to compare a spreadsheet against the calendar to discover that a critical submittal is behind. The production plan shows it, the procurement log shows it, and the alert prompts immediate escalation.

When a red flag appears, the response is not to update the planned date and move on. The response is to work through the full procurement recovery menu: expedite the submittal review, run a live coordination session with the design team, pursue fabrication at a second production site, take over the shipment, find an in-spec alternate, borrow from another project, or switch vendors. The procurement log that flags the problem also holds the history of the recovery actions taken which builds the defensible record needed if the procurement delay ultimately results in a schedule impact that needs to be documented.

The Roadblock Log: Identify, Discuss, Solve

The roadblock log in InTakt’s reports section is the systematic tool for the make-ready process. Every potential roadblock that surfaces in the look-ahead regardless of how far out it is gets logged here with a title, a description, a countdown to the needed-by date, a responsible person, and a required resolution date.

The dashboard view at the top of the roadblock log shows four numbers at a glance: the oldest open roadblock, how many are past due, how many are within the seven-day critical window, and how many are further out. That summary tells the superintendent immediately whether the roadblock removal process is keeping up with the production plan or falling behind.

The seven-day threshold is the critical boundary. A roadblock that is resolved before it enters the seven-day window before it hits the weekly work plan never becomes a field stop. A roadblock that is still open when the weekly work plan is committed either forces a promise the trade cannot keep or stops the work from being committed at all. The target is always to clear roadblocks long before that window, which is why the look-ahead process needs to be identifying them six weeks out rather than discovering them in the afternoon foreman huddle the day before the zone opens.

The roadblock log is accessible in both the schedule view and the log view, which means it can be displayed on the conference room screen during the trade partner weekly tactical and the afternoon foreman huddle. When a roadblock is resolved, clicking the resolved button automatically updates the dashboard counters at the top of the log. The team can see the resolution happening in real time, which makes the roadblock removal effort visible and gives the person who cleared it immediate recognition for the work.

Milestone Variance: Is the End Date at Risk?

The milestone variance feature in InTakt answers the most important question a superintendent can ask every week: is the end date still intact? With the milestone variance display turned on in the view options, any activity extension that cascades to the phase milestone is immediately visible as a delta between the planned completion and the current projected completion.

This is where the buffer logic becomes critical. When a delay occurs a commissioning activity extends, a zone takes longer than planned, a procurement item slips the first question is whether the delay can be absorbed in the existing buffers. The buffers in a Takt production plan are not float that was forgotten. They were placed deliberately based on the risk analysis, and they exist to absorb exactly this kind of variation. If the milestone variance shows the delay extending into the buffer rather than past the milestone, the system is working as designed. If the variance is pushing past the buffer and threatening the milestone, the team has twelve recovery moves to work through before the delay becomes a schedule impact that needs to be documented.

The milestone variance display, combined with the procurement log alerts and the roadblock dashboard, gives the production team a complete picture of the phase’s health supply chain status, readiness status, and milestone status in one unified system rather than across three separate tracking documents.

What InTakt Makes Possible That Procore Cannot

Procore’s submittal register tracks whether a submittal was submitted and returned. That is a compliance record, not a production management tool. It does not show whether the submittal timeline is compatible with the zone start date in the production plan. It does not alert the team when a step is slipping. It does not level the review workload across the design team. It is not connected to the production plan in any live way.

InTakt’s workflow system is all of those things. It is a procurement log tied to the production plan, alerting the team in real time when something is off track, leveled to prevent overloading any single reviewer, and visible in the same schedule view that shows the train of trades flowing through the building. The supply chain is not managed separately from the production plan. It is managed as part of it.

We are building people who build things. The teams that track procurement, roadblocks, and milestone variance in InTakt that surface problems six weeks out rather than two days before are the teams whose trade partners enter their zones with full kit confirmed, whose milestones hold, and whose buffers are still available when genuine surprises arrive. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow including the procurement and roadblock tracking discipline that keeps the train from stopping.

A Challenge for Builders

Open your current procurement log whether it is in InTakt, a spreadsheet, or a Procore submittal register and find the three items with the earliest needed-by dates that have not been verified complete through every step. For each one: is it tied to a specific zone start date in the production plan? Is there a responsible person assigned to the next unverified step? Is the step on track to be verified before the needed-by date? For any item where the answer to any of those questions is no, assign the owner and the deadline today. The procurement delay that costs the project three weeks of schedule is visible right now in those three items if someone is looking.

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

On we go.

Frequently Asked Questions

What is the difference between InTakt’s procurement workflow and a submittal register in Procore?

A submittal register tracks compliance whether a submittal was sent and returned. InTakt’s procurement workflow tracks the full supply chain sequence against the production plan: every step from buyout through delivery, tied to the specific task that depends on the material, with real-time alerts when any step slips past its planned date. The submittal register tells you what happened.

What does the roadblock log dashboard summary show and why does the seven-day threshold matter?

The dashboard shows four numbers: the oldest open roadblock, the count past due, the count within the seven-day critical window, and the count further out. The seven-day threshold is the boundary between proactive roadblock removal and reactive crisis management. A roadblock resolved before it enters the seven-day window never becomes a field stop. A roadblock still open when the weekly work plan is committed either forces an uncommittable promise or stops the activity from being planned at all.

What should the team do when the milestone variance display shows a delay pushing past the buffer?

Work the twelve Takt recovery moves before accepting the delay as a schedule impact. First, determine whether the delay can be absorbed in any remaining buffer phase buffer, space buffer, or plan buffer. If not, pursue the recovery moves in order from least disruptive to most: line of balance delay recovery, sequence modification, zone isolation, swing capacity from workable backlog, rezoning, design to the work package, bottleneck removal, and the remaining strategies. Document each option considered and the reason it was or was not used. Only when all options are exhausted does the delay become a documentable schedule impact requiring a Time Impact Analysis.