Who Performs Impact Analysis In Project Management?

Who Performs an Impact Analysis and How to Do It Right

Every construction project will take an impact. That is not a pessimistic statement. It is a production reality. Design changes, supply chain disruptions, weather events, owner decisions, and dozens of other variables will hit the schedule at some point. The question is never whether an impact will happen. The question is whether the production system sees it early enough to respond intelligently, documents it accurately enough to protect everyone involved, and recovers from it in a way that actually works instead of making the project worse.

There are two frameworks for handling this. One is CPM-based. One is Takt-based. They produce very different outcomes, and understanding the difference is one of the most practically valuable things a PM, superintendent, or scheduler can carry into any project.

Why CPM Creates an Impact-React Cycle

The CPM system narrows every project onto a critical path the longest path through the schedule with no buffers or float where any delayed activity delays the whole project. When an impact hits that path, the contractually specified response is a time impact analysis inserted as a fragment into the CPM software. The format shows the original baseline, the documented impact, the recovery strategy, who is at fault, and what is needed to recover. That structure sounds reasonable until you look at what actually gets recommended inside it.

The typical CPM recovery options are adding labor, working overtime, adding crews, rushing trades, crashing activities, trade stacking putting too many trades into one area or trade burdening, making trades work in too many areas simultaneously. Every one of those responses adds cost, adds stress on the crews, and usually makes the production system worse rather than better. The CPM framework produces an impact-react, impact-react, impact-react cycle that constantly changes the baseline, constantly generates approval requests, and constantly struggles to find a recovery strategy that isn’t just pushing people harder against a schedule that was already broken.

There is also a dimension to the CPM preference that most people in the field have never been told directly. Research on why CPM is more prevalent than CCPM Critical Chain Project Management found that financial institutions and legal institutions preferred it because its complexity gave lawyers more ability to assign blame and gave financial institutions muddier water to operate in. A production plan that serves the project is not the same thing as a legal instrument designed to manage liability exposure. CPM often serves the second purpose while being sold as the first.

What a Takt-Based Impact Analysis Actually Looks Like

In a Takt Production System paired with the Last Planner System and the Kanban method, the impact analysis works fundamentally differently because the system is designed to see impacts early and absorb them systematically rather than reactively.

The first difference is visibility. In a CPM environment, a problem may not surface in the schedule analysis until a week or a month after it happens sometimes longer. In a Takt system, the impact is visible daily. The production board shows where the train of trades is relative to where it should be, and any deviation from the path of critical flow is identifiable before it compounds.

When an impact is identified in a Takt system, the analysis follows a structured path. The team identifies what happened, maps how it affects the path of critical flow meaning the activities, durations, logic ties, sequence, buffers, and trade flow and then evaluates at least twelve positive, production-minded recovery options before making a recommendation. The output of that analysis is a clear picture of the strategic baseline, the documented impact, the available options, the recommended path, what the chosen option does to the buffers and the overall project, and the root cause entry into the buffer log. That is a production conversation, not a legal one.

The Buffer Log: Where the Takt System Protects Everyone

One of the most important features of a Takt-based impact process is the buffer log. Every time a buffer is used, the reason is recorded. That log is not overhead. It is the running record of what happened to the schedule, when it happened, and why. If the project runs past the end date, the buffer log makes it possible to do an honest analysis of who is responsible the owner, the contractor, or a combination based on a verifiable, timestamped record of every buffer consumption event.

That stands in sharp contrast to the CPM baseline change cycle, where the baseline keeps moving and accountability becomes a legal argument about whose version of the schedule was accurate. In a Takt system, the sequence is verifiable through the pull plan. The speed and line of balance are verifiable through the pull plan. The buffers are verifiable through the pull plan based on the original risk analysis. Everything from beginning to end is mathematically and scientifically justifiable. Recovery options can be selected from a production mindset rather than from a legal defense posture.

Warning Signs That the Impact Analysis Process Is Broken

Before a project’s impact cycle compounds into a legal dispute, watch for these signals that the process is not functioning correctly:

• Impacts are being discovered a week or more after they occur, because there is no daily production visibility system in place to surface deviations early.
• The recovery plan defaults to overtime, trade stacking, or crashing activities all of which add cost and typically make the production system worse.
• The baseline keeps shifting with each impact analysis, making it impossible to establish an honest comparison between planned and actual production.
• Buffer consumption is not being logged with root causes, meaning nobody can verify who is responsible for schedule slippage when it matters.
• The impact analysis is being prepared primarily by schedulers and lawyers rather than by the superintendent and PM who understand the production logic.

Any one of those signals means the system is reacting instead of controlling. Multiple signals together mean the project has lost its ability to recover predictably.

Who Owns the Impact Analysis

In a proper format, the superintendent and PM own the impact analysis. They are the primary parties responsible for identifying the impact, understanding how it affects the production system, evaluating recovery options, and framing the recommendation. The scheduler is the secondary party brought in to support the technical documentation and format requirements. Legal counsel is looped in when the situation has escalated to arbitration or legal proceedings, or when the complexity of the contract provisions makes their involvement necessary to protect the analysis properly.

This ownership structure matters. An impact analysis written primarily by a scheduler and filtered through legal from the start is a legal document disguised as a production document. An impact analysis written by the superintendent and PM, grounded in production logic and supported by verifiable Takt data, is a real recovery tool. The difference is not just procedural. It determines whether the output actually helps the project or just manages the paper trail around a project that keeps falling further behind.

Recovery Options That Actually Work

The production-minded recovery framework in a Takt system starts with the options that protect the train of trades before reaching for the ones that burden people. The preferred first option is to delay the line of balance slow the Takt time to give the system room to absorb the impact without stacking trades. The second option is to isolate and decouple the affected work from the main train, so the rest of the system can keep flowing while the problem gets resolved. The third option is recovering with additional resources, applied surgically rather than broadcast across the whole project.

What this framework never recommends as a first response is overtime, trade stacking, or crashing. Those are last resorts after the production options have been exhausted, because they introduce overburden that damages the people doing the work and often produces defects and rework that extend the schedule further than the original impact did. If the plan requires burnout to succeed, the plan is broken, not the people. A recovery plan that resolves an impact by overburdening the crew is not a recovery plan. It is a transfer of the impact onto the workforce, which shows up in quality, safety, and turnover.

What Good Documentation Makes Possible

The impact analysis is only as strong as the documentation behind it. A strategic baseline the original production plan showing the planned sequence and pace is what makes any impact analysis credible. Without a baseline, every conversation with the owner is a trust-me conversation. With a baseline, it is an evidence-based conversation grounded in the production plan from day one, compared honestly against what actually happened and why.

This is where daily production tracking, buffer logs, pull plan records, and material procurement logs do their most important work. Not as administrative overhead, but as the verifiable foundation that transforms an impact claim from an assertion into a documented, mathematically supportable analysis. It is also what protects the project team when the conversation with the owner gets difficult. A team that can show exactly what the plan was, exactly what happened, exactly when buffers were consumed and why, and exactly what recovery options were evaluated is a team that can have an intelligent, professional conversation about a new milestone rather than a legal argument about who is to blame.

A Challenge for Builders

Walk your current project this week and ask one honest question: if an impact hit the schedule tomorrow, what would your analysis look like? Do you have a strategic baseline? Is your buffer log current? Can you trace every buffer consumption event back to its root cause? Is the superintendent and PM positioned to lead the analysis, or is it being delegated entirely to schedulers? If the answers are weak, the fix starts with the production system, not with the legal team. Build the Takt plan. Keep the buffer log. Run the pull plan. Do it every week, not just when the impact arrives.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow including the production control discipline that makes impact analysis a routine tool instead of a crisis response.

As Taiichi Ohno said, “Where there is no standard, there can be no improvement.”

On we go.

Frequently Asked Questions

What is a time impact analysis and when is it required?

A time impact analysis documents the original baseline, the specific impact event, the effect on the schedule, and the proposed recovery strategy. In CPM contracts it is typically required whenever an impact extends the critical path, and it is submitted in whatever format the contract specifies.

Why is a Takt-based impact analysis more effective than a CPM-based one?

Because Takt sees impacts daily rather than weekly or monthly, keeps a verifiable buffer log that documents root causes in real time, and evaluates production-minded recovery options before resorting to overtime or trade stacking all of which protect both the schedule and the people executing it.

Who is primarily responsible for conducting the impact analysis on a project?

The superintendent and PM own it. They understand the production logic and the field conditions. The scheduler provides technical support, and legal counsel is brought in only when the situation escalates to arbitration or requires contract-level interpretation.