Critical Path Analysis for Interim Milestones: Why Positive Project Float Can Mislead

A monthly CPM update can report a project finish that remains within the contractual completion window while an important interim phase is already forecast late. For an owner or general contractor, that distinction can determine whether to ask for routine monitoring, a documented recovery plan, or an immediate discussion about access, handoffs, and the governing milestone requirement. Critical path analysis must therefore examine the paths to significant interim milestones as well as the longest path to final completion.

A positive float figure at project completion is useful information, but it does not assure that every contract milestone can be met. The practical response is to compare consecutive schedule updates, trace the work controlling each exposed milestone, validate the field and procurement status, and require an explanation of any forecast movement. This is especially important on long-duration infrastructure and phased construction programs where work streams may have separate completion obligations.

Why overall completion float can hide an interim miss

Total float is the calculated flexibility for an activity or milestone under the schedule’s current logic, constraints, calendars, and scheduling settings. It is not a reserve of time that can automatically be transferred from one project phase to another. An interim milestone can have negative total float because its forecast falls beyond a constrained or required date, while later milestones retain positive float against their own requirements. Their governing paths and available windows are different.

Consider an illustrative project with a required equipment-readiness milestone on September 1 and an unrestricted project-completion date several months later. If the readiness work is now forecast for September 20, the interim obligation warrants attention even if the overall completion forecast has not passed its deadline. The nineteen calendar days between those dates are not necessarily nineteen schedule days of negative float, because calendars, time-of-day settings, and constraints affect that calculation. The owner must also establish whether September 1 is a contractual requirement, a management target, or an assumed planning date.

This is why CPM scheduling services and baseline schedule development should establish the controlling milestones, phase boundaries, and logic connections before the first progress update. Once construction is underway, the same distinctions should remain visible in monthly schedule updates. A sound schedule compliance review tests the submitted forecast against the actual contract requirements rather than assuming a displayed constraint is legally controlling.

Critical path analysis that follows each milestone

Check the date, data date, and float basis

Start with a milestone register that lists the governing required date, current forecast, prior forecast, variance in calendar days, total float in the scheduling software’s units, and the source of the required date. Verify the update’s data date, not merely the day the file was issued. A review performed in November on a September data date describes the September schedule condition unless later evidence is separately incorporated. Compare like with like. A previous accepted update is preferable, and if only a courtesy copy is available, identify that limitation.

Next examine the calendars, imposed constraints, remaining durations, and scheduling options. Primavera P6 scheduling services and Microsoft Project scheduling services can both support credible network analysis, but a PDF bar chart alone will rarely show the assumptions needed to explain a disputed float result. Native files allow reviewers to inspect logic and recalculate the forecast. Formal schedule health checks can flag open ends, inconsistent status, unexplained constraints, or actual dates beyond the data date; none of those flags alone determines whether construction is achievable.

Follow the driving relationships, including closeout

A project’s displayed longest path usually leads to final completion, but a separate milestone may be controlled by a different, more constrained branch. In Primavera P6, multiple float-path analysis can be directed to a selected ending activity, commonly a milestone. That helps a reviewer identify the chain governing a phase date instead of relying on a single project-wide critical filter. The relevant branch may include fabrication, inspection, shipment, site receipt, installation, testing, documentation, and release for the next workfront. Oracle documents multiple float-path calculations for this purpose.

Use critical path analysis to examine actual drivers and near-critical alternatives, rather than simply counting activities with negative float. If two paths are constrained by different milestones, their float values should not be added together. Likewise, a longer forecast duration for a future work package does not prove that a contractor can or cannot achieve it. The question is whether the remaining plan has logical ties, supportable production assumptions, and traceable external interfaces.

A real review of a phased hydroelectric rehabilitation

On a long-duration hydroelectric rehabilitation, Leopard Project Controls performed an owner-side review of a contractor’s monthly schedule update against the prior period’s file. The submitted update forecast one major phase milestone later than the prior forecast and beyond the required date recorded in the contractor’s schedule. Later phases and final project completion still showed positive total float against their separate requirements.

The contractor’s schedule identified rework in a major equipment sequence as a leading driver of the reported longest path. Leopard Project Controls examined the activity’s recorded start, physical completion, original and remaining durations, and connections to downstream work. Its written review asked the contractor to substantiate the remaining-work plan, reconcile differing shipment and receipt descriptions, correct specific status and logic defects, and explain the relationship between the phase movement and the overall completion movement. Those were documented review findings and requests, not proof that a claimed delay had been caused by any particular party.

The contractor prepared and submitted the update, and Leopard Project Controls supplied the technical review and comments for the project team. The record does not establish that the requested corrections were accepted, that recovery was achieved, or that any time extension was approved. The lesson is narrower and more useful: a reviewer who stops at positive final-completion float may overlook a separate milestone exposure that requires an immediate and specific response.

Turn a negative-float warning into a management decision

Separate schedule defects from actual execution risk

A reviewer should first decide whether the apparent milestone miss is a credible forecast or partly a modeling problem. Some active activities may show 100 percent physical completion yet retain meaningful work durations, for example, if reported progress is inconsistent or incomplete. A finish milestone may lack the relationship that should carry its completion into subsequent work. Such conditions demand corrections and an explanation of any resulting date movement. Schedule narrative reports should reconcile forecast dates, identify what changed, and distinguish work actually performed from future assumptions.

The review should also test the measurement basis. Cost and resource loading can improve reporting, but a cost-loaded percentage is not equivalent to physical completion. Earned value management requires defined rules for measuring earned work; it should not be inferred from cumulative spending or the presence of cost assignments. An executive can use these signals together, but should never treat a single percentage as validation of the remaining critical sequence.

Require a response that leads to action

For a credible interim shortfall, request a contractor response showing the affected activity chain, responsible work packages, current vendor and access commitments, and the options available to protect the milestone. Lookahead schedules should translate that plan into near-term field commitments. If the forecast depends on additional shifts, different handoffs, or parallel crews, recovery scheduling should model those choices with realistic resources, calendars, safety constraints, and approval windows. A dated mitigation proposal is a plan, not an achieved recovery.

If the contractor attributes movement to an owner instruction, review period, changed condition, or other event, the schedule should identify the affected activities and provide contemporaneous records. Construction delay analysis and a Time Impact Analysis (TIA) may be appropriate where required by the contract and suited to the timing of the event. Construction claims support can organize schedule evidence, but technical analysis does not itself establish legal entitlement, compensability, or responsibility. The contract and applicable law control those determinations. AACE’s schedule update review recommended practice emphasizes changes in progress, logic, constraints, and resources from one period to the next rather than treating the updated finish date in isolation.

The useful executive decision comes down to a few questions. Is the reported shortfall technically credible? What work or decision controls the exposed date? What response, supporting documentation, and next review date are required? Answering them turns a schedule update review into an operating decision rather than an exercise in collecting red flags.

How Leopard Project Controls supports milestone oversight

Leopard Project Controls provides construction scheduling consulting for contractors and independent schedule review for owners. As an owner’s scheduling consultant, the company can examine native schedules, compare updates, trace constrained milestone paths, review narrative consistency, and document required clarifications. Its broader owner’s representative services can support coordination where schedule issues affect owner decisions and project interfaces. For contractor teams, the company also provides progress update support, schedule development, and technical review of proposed recovery or change effects.

The expected product of such work is a clear schedule review or update package identifying the data date, milestone exposure, driving activities, material assumptions, recommended actions, and items still requiring confirmation. To discuss a phase-milestone concern or request a review of a current CPM file, contact Leopard Project Controls.

The decision to make before the next update

A schedule with positive final-completion float can still contain a serious interim obligation at risk. Owners should not automatically reject the update, and contractors should not dismiss the concern because the last milestone still appears safe. Determine which date governs, validate the network and progress record, and require a documented response tied to the actual controlling work. The earlier that distinction is made, the more useful the next field coordination meeting becomes.

Frequently asked questions

Can a milestone have negative float while the project finish has positive float?

Yes. A milestone can be constrained to an earlier required date and forecast late while final completion remains before a separate deadline. Different logic paths and milestone requirements produce different float conditions. Review the native schedule, constraints, calendars, and milestone definitions before interpreting the numbers or deciding whether a contract obligation is affected.

Is the project’s longest path always the path to the most urgent milestone?

No. The displayed project longest path commonly relates to final completion. A phase milestone can have a different driving sequence, particularly when its required date is constrained. The scheduler should calculate or trace paths ending at the interim milestone and examine procurement, access, testing, and turnover dependencies that may not appear on the project-wide path.

Does negative float prove the contractor caused a delay?

No. Negative float describes the calculated schedule condition; it does not identify cause, responsibility, or entitlement. The reviewer needs reliable actual dates, contemporaneous records, prior updates, applicable milestones, and analysis of relevant changes. Technical conclusions should remain separate from contractual or legal determinations.

Should the owner reject every update containing negative float?

Not automatically. An accurate update may properly disclose a late forecast. The response should depend on contract requirements and whether status, logic, forecast dates, and explanations are supportable. Require corrections for specific technical defects, request an actionable response to the exposed milestone, and document acceptance or other review treatment according to the contract.

What should a contractor submit when an interim milestone is forecast late?

A useful package includes the updated native CPM file, a comparison with the prior update, the affected milestone path, supporting field and vendor records, a clear narrative of changes, and a realistic mitigation plan where warranted. When an extension is asserted, include the notices and schedule analysis required by the contract. The owner can then distinguish a forecast concern from a substantiated time request.