Construction Schedule Analysis: The Complete Guide to Methods, Steps & Tools

You have a contractor’s programme in front of you. It’s 800 activities long, full of logic ties you have never seen, and the completion date looks optimistic. Where do you start?

Construction schedule analysis is the discipline of examining a project programme to determine whether it is realistic, logically sound, and capable of delivering the project on time. Whether you are reviewing a baseline submission, assessing a progress update, or preparing for a delay claim, schedule analysis gives you the evidence to make sound decisions.

This guide covers the four core methods of schedule analysis, walks you through a practical seven-step contractor programme review, and explains how schedule analysis connects to extension of time (EOT) claims and delay disputes.

What Is Construction Schedule Analysis?

Construction schedule analysis is the systematic examination of a project schedule to evaluate its quality, logic, and forecast accuracy. It goes beyond simply checking whether the end date looks reasonable; it probes the structure, dependencies, and assumptions built into the programme.

A thorough schedule analysis answers questions like:

• Is the schedule logic complete, or are there open ends that hide real risk?
• Is the critical path genuine, or has it been manipulated with constraints?
• Are resources assigned realistically, or is the schedule resource-loaded in name only?
• Does the programme comply with contractual requirements and industry standards?

Schedule analysis is performed by project managers, project controllers, claims consultants, and owner representatives. The depth of analysis varies. A quick health check before approving a progress update is a different exercise from a forensic analysis for a dispute, but the underlying methods are the same.

Why Schedule Analysis Matters for Construction Projects

Poor scheduling is one of the most common causes of cost overruns and disputes on construction projects. Research by the Construction Industry Institute has consistently shown that projects with poor planning and schedule quality are far more likely to experience cost and time overruns. For wider context, our guide on construction project benchmarking covers how to validate contractor durations against industry data.

The practical consequences of weak schedule analysis include:

• Hidden risks go undetected. Missing logic ties, excessive constraints, and artificial float can mask genuine delays until it is too late to recover.
• EOT claims fail. If your baseline schedule is not logically sound, proving entitlement for an extension of time becomes difficult, sometimes impossible.
• Disputes escalate. Without a resilient schedule to serve as a common reference point, disagreements about delay responsibility quickly become expensive legal arguments.
• Recovery options narrow. By the time a schedule problem becomes visible without analysis, the window for corrective action has usually closed.

Boston’s Big Dig makes the point at scale. The project ran from a $2.8B budget to $14.6B at completion and finished nine years late against its 1998 plan, and the official record traces much of that to programme management that never gave decision-makers an accurate picture of where the schedule actually stood. Schedule analysis is how you keep that picture accurate while there is still time to act on it.

The AACE International Recommended Practice 29R-03 (Forensic Schedule Analysis) and the Society of Construction Law (SCL) Delay and Disruption Protocol both emphasise the importance of a well-constructed, properly analysed schedule as the foundation for any delay assessment.

The 4 Core Methods of Construction Schedule Analysis

Schedule Quality Analysis

Schedule quality analysis examines the structural integrity of the programme itself. Before you can trust any output (critical path, float values, completion dates) you need to know the inputs are sound.

The most widely used framework for schedule quality is the DCMA 14-Point Assessment, developed by the US Defense Contract Management Agency. It checks a schedule against 14 criteria including:

• Missing logic: activities with no predecessors or successors
• Negative float: indicates the schedule is already behind contractual dates
• High duration: activities longer than a set threshold (usually 44 working days) that may be hiding detail
• Invalid dates: activities with dates that contradict their logic
• Lag abuse: excessive use of lag instead of proper logic ties
• Hard constraints: constraints that override network logic and create artificial float

The GAO Schedule Assessment Guide provides another framework, emphasising that a reliable schedule must be well-constructed, appropriately detailed, and realistic in its assumptions.

Running a schedule health check early, ideally at baseline approval, catches problems before they contaminate every subsequent update.

What we found: The DCMA 14-Point thresholds are deliberately conservative: 5% on missing logic, 5% on hard constraints, 5% on high float, and zero on negative float. They describe the floor a working schedule should clear, not an aspirational target.

What it means: A baseline that cannot clear the floor is not a stretch goal that needs encouragement. It is a model the contractor either cannot build to or has not tried to. Approving it commits you to defending a planning instrument that does not function as one, and any delay analysis you later run on it inherits the same defects.

Critical Path Analysis

The critical path is the longest sequence of activities through the schedule network. It determines the project’s earliest possible completion date. Every day of delay on a critical path activity is a day added to the project finish.

For a deeper treatment of how the critical path is identified, validated and monitored across the life of a project, see our guide on the critical path method in construction. Critical path analysis involves:

• Identifying the longest path through the network: is it realistic, or has it been shortened with soft logic or constraints?
• Checking for artificial float: hard constraints and out-of-sequence progress can make non-critical activities appear to have float when they do not.
• Assessing near-critical paths: paths with only a few days of total float can become critical with a single delay. A schedule with multiple near-critical paths carries far more risk than the critical path alone suggests.
• Comparing as-planned vs as-built critical paths: the critical path often shifts during execution. Understanding when and why it shifted is essential for delay analysis.

Critical path (red): Start → A (5d) → C (8d) → Finish = 13 days. Non-critical path (blue): Start → B (3d) → C, with 2 days of total float.

A genuine critical path, derived from proper logic rather than constraints, is the single most important output of any schedule.

Float Analysis

Float (or slack) is the amount of time an activity can be delayed without affecting the project finish date. Understanding float is essential for managing risk and resolving disputes.

The two key types (covered in detail in total float vs free float):

• Total float: the time an activity can slip without delaying the project completion date. This is the float value most scheduling tools display.
• Free float: the time an activity can slip without delaying the early start of any successor activity.

Float analysis becomes particularly important when:

• Tracking float consumption between updates. If an activity had 30 days of float last month and only 10 days this month, something has changed, and you need to understand what.
• Negative float appears. Negative total float means the schedule is forecasting later than the contractual completion date. This is a clear warning sign.
• Disputes arise over float ownership. The SCL Protocol takes the position that float belongs to the project, not to any single party. Understanding how much float exists and where it sits is essential for this debate.

Recovery and Forensic Schedule Analysis

When a project is behind schedule, or when a dispute arises over who is responsible for delay, the more advanced methods of forensic schedule analysis come into play.

For a comparative walk-through of all six recognised delay analysis methods, see our EOT claim analysis guide.

Prospective methods (looking forward from a delay event):

• Time Impact Analysis (TIA): the most widely accepted method for assessing delay as it occurs. You take the schedule as it stood before the delay event, insert the delaying activity, and measure the impact on the critical path. AACE RP 29R-03 and the SCL Protocol both recognise TIA as a preferred method.

Retrospective methods (looking back after the fact):

• As-built delay analysis: reconstructs what actually happened using contemporaneous records to identify the real sequence of events and delays.
• Windows analysis: divides the project into time periods (windows) and analyses delay within each window, making it easier to attribute delay to specific events.
• Collapsed as-built: removes the effects of specific delay events from the as-built schedule to determine what would have happened without them.

The choice of method depends on the contractual framework, available data, and the stage of the project. The CIOB Guide to Good Practice in the Management of Time in Complex Projects provides further guidance on method selection.

Step-by-Step: How to Review a Contractor’s Schedule

Step 1: Verify Schedule Completeness and Scope

Before diving into the logic, check that the schedule actually represents the full scope of work. A schedule that omits material scope is fundamentally unreliable.

• Does the work breakdown structure (WBS) align with the contract scope of works?
• Are all major work packages represented?
• Are milestones consistent with contractual requirements?
• Are handover and commissioning activities included?

If the scope is incomplete, everything that follows (critical path, float, resource analysis) is suspect.

Step 2: Check Logic and Dependencies

Logic is the backbone of the schedule. Without sound logic, the critical path is meaningless and float values are unreliable.

Check for:

• Open ends: activities with no predecessor (other than the project start) or no successor (other than the project finish). Every activity should connect to the network.
• Hard constraints: fixed-date constraints that override logic. They create artificial float by forcing dates regardless of what the network calculates. Most specifications limit hard constraints to contractually required milestones only.
• Redundant logic: duplicate ties that do not change the schedule but can cause confusion.
• Circular logic: where an activity is both a predecessor and successor of the same activity, creating a loop. Scheduling tools typically flag these, but they can appear after data entry errors.

Step 3: Analyse the Critical Path

With logic verified, examine the critical path:

• Does the longest path make sense given the project scope? If the critical path seems surprisingly short, there may be missing logic or excessive constraints hiding delay risk.
• Are there near-critical paths with less than 10 days of total float? These carry real risk.
• Does the critical path pass through activities that make engineering sense? A critical path routed through non-physical activities like submissions or approvals may indicate logic gaps.

Step 4: Review Resource Loading and Levelling

A schedule without realistic resource assignments is a wish list. Check for:

• Activities with no resources assigned where labour or equipment is clearly required
• Over-allocated resources, such as a single team scheduled to work on five activities simultaneously
• Unusually high or low budgeted units per activity
• Whether the schedule has been resource-levelled and, if so, whether the levelling extended the completion date

Step 5: Run Schedule Health Checks

Apply a recognised framework to assess schedule quality. The DCMA 14-Point Assessment is the most common starting point. It identifies problems like:

• Missing logic (open ends)
• Excessive constraints
• Negative float
• Lag exceeding thresholds
• Activities with durations beyond standard limits

You can also create custom quality metrics reflecting specific contractual requirements. Comparing the schedule against industry benchmarks gives you context: a schedule failing 6 of the 14 DCMA points is objectively poor, regardless of the contractor’s explanation.

Step 6: Compare Against Baseline

For progress updates, compare the current schedule against the approved baseline:

• Has the completion date shifted?
• Have activities been added, deleted, or had their durations changed?
• Has the critical path shifted?
• Is progress consistent with the reported percent complete, or are activities showing progress without corresponding resource expenditure?

Variance analysis between the baseline and current schedule reveals whether the project is tracking to plan and highlights where corrective action may be needed.

Step 7: Document Findings and Take Action

The analysis is only useful if it leads to action. Document your findings in a structured review report that covers:

• A summary of schedule quality (pass/fail against key metrics)
• Identified risks and their potential impact
• Specific issues requiring contractor response (missing logic, unrealistic durations, scope gaps)
• Recommendations for corrective action
• Escalation items: issues that cannot be resolved at project level and require management attention

Schedule Analysis for EOT Claims and Delay Disputes

One of the most important, and least understood, applications of schedule analysis is its role in extension of time claims and delay disputes.

The SCL Protocol sets out the core principle: an EOT should be granted where a delay event affects the critical path and causes or is likely to cause completion after the contractual date. This means schedule analysis is not optional for EOT claims; it is the evidentiary foundation. A structured delay analysis report is how that evidence reaches the decision-maker.

Key principles:

• Link the delay event to critical path impact. A delay to a non-critical activity does not entitle the contractor to an EOT, because it does not affect the completion date. You need to demonstrate that the delay event pushed the critical path.
• Address concurrent delay. When both parties are responsible for separate delays occurring at the same time, the analysis becomes more complex. The SCL Protocol takes the approach that concurrent delay should not prevent an EOT being granted where a delay event is on the critical path.
• Use contemporaneous schedules. Retrospective schedules created for the purpose of a claim are treated with caution. The best practice is to analyse the schedule as it stood at the time of the delay event.
• Maintain a proper baseline. You cannot analyse delay without a sound baseline to measure against. This is another reason why schedule quality analysis at baseline approval is so important.

The Holyrood Parliament Building shows what happens when the baseline never holds. The project came in at roughly £431 million against an approximately £40 million initial estimate (Auditor General for Scotland, 2004) and opened around three years late. With the programme shifting underneath everyone, there was no stable reference point left to measure delay against, which is exactly the position a contemporaneous, well-analysed schedule is meant to prevent.

Tools for Construction Schedule Analysis

The right tool depends on the complexity of your project and the depth of analysis required.

If your primary need is to review and analyse contractor schedules rather than create them, a dedicated analysis tool like ScheduleLens can save hours. It automates the health checks, critical path validation, and comparison reports that would otherwise require a long manual pass in P6.

Key Takeaways

• Schedule analysis is not optional. A programme you have not analysed is a programme you cannot trust.
• Start with quality. If the schedule logic is broken, every downstream analysis (critical path, float, delay) is unreliable.
• Use the DCMA 14-Point Assessment as a baseline quality standard. It is widely recognised and provides an objective framework.
• The critical path is king. Most schedule analysis ultimately comes back to understanding what is driving the project finish date.
• Float consumption is a leading indicator. Watch how float changes between updates; it tells you where risk is building.
• Connect analysis to action. Document findings, make recommendations, and escalate issues that cannot be resolved at project level.
• Schedule analysis underpins EOT claims. A sound schedule, analysed at baseline and regularly updated, is your best protection in a dispute.

Ready to stop manually checking schedules and start analysing them properly? Try ScheduleLens for automated DCMA 14-Point assessments, critical path validation, float analysis, and schedule comparison, all from a single XER file upload.