2.4 Float Calculations and Critical-Path Identification

2.4 Float Calculations and Critical-Path Identification

Float describes flexibility in the current schedule model. AACE RP 49R-06 concerns identifying the critical path. Because constraints, calendars, and software rules can affect reported float, critical-path review should combine calculations with a continuous trace of driving relationships to the milestone being analyzed.

Total, free, and interfering float

Under a consistent zero-based convention:

$TF = LS - ES = LF - EF$

Total float is the amount an activity can be delayed from its early dates without moving the applicable late date or completion target in the model. It is a path-related property: several activities can show the same float because delay anywhere along the path consumes shared flexibility.

For a simple zero-lag FS relationship:

$FF = ES_{successor} - EF_{activity}$

Free float is the delay possible without moving the early date of the immediate successor. For SS, FF, multiple successors, lags, and calendars, adapt the endpoint calculation; do not apply the simple FS formula mechanically.

Interfering float is commonly expressed as:

$\text{Interfering Float} = \text{Total Float} - \text{Free Float}$

It is the portion of total float that can be used without delaying the project late date but that would move a successor’s early date.

Example: Activity P has ES 10, EF 16, LS 15, and LF 21. Its FS successor starts early at 19. Total float is 5, free float is 3, and interfering float is 2 under the stated convention.

Critical path

In an unconstrained network whose required finish equals the calculated early finish, the longest path commonly has zero total float. If a finish constraint is earlier than the calculated finish, the controlling path may have negative float. If the required finish is later, the controlling path may have positive float. Therefore “critical equals zero float” is not reliable in every model.

Trace a continuous chain of driving relationships to the relevant milestone. Review longest-path output where available and reconcile it with lowest-float activities, constraints, calendars, and calculation settings. A list of isolated low-float activities is not a path.

Negative float

Negative float indicates that the modeled network cannot meet an imposed date under the current assumptions. If unconstrained completion is 15 November and a required milestone is 31 October, the schedule may show a negative working-day gap on the path controlling that milestone. The precise value depends on calendars and date conventions.

Negative float is a signal, not a recovery plan and not a legal conclusion. Identify the driver, verify the constraint’s source, develop feasible alternatives, and report the current forecast. Responsibility and entitlement require the contract and facts.

Float changes and ownership

Float can change when status, logic, duration, calendars, constraints, scope, or other paths change. Consuming float on one activity can reduce flexibility available to downstream activities. That technical observation does not decide who contractually owns or may use float.

Contracts may expressly allocate float, require notice when it is consumed, or define treatment of concurrent events. In the absence of explicit language, applicable law and project facts still matter. AACE Recommended Practices do not create a universal “project owns float” or “first party to use it owns it” rule.

Review method

For each key milestone:

1. identify the governing calendar and date constraint;
2. trace driving relationships backward to the data date or project start;
3. compare longest path and lowest-float results;
4. inspect alternate near-critical paths;
5. explain constraints and calendar transitions;
6. quantify variance and float consumption; and
7. separate technical findings from contract conclusions.

The purpose is to explain what controls the milestone and how much modeled flexibility remains—not simply to color every zero-float activity red.

Applied review: trace float to the milestone

When a report shows float, identify the finish milestone or constraint against which late dates were calculated. The same activity can have different apparent urgency when analyzed against a contractual completion, an interim turnover, or an unconstrained project finish. Verify that calendars and relationship endpoints are compatible before comparing float across activities.

Test the controlling path by adding a small delay in a schedule copy and observing the milestone effect. If the expected movement does not occur, inspect constraints, alternate paths, resource leveling, open ends, and software longest-path settings. Preserve the test assumptions; a path check is diagnostic evidence, not a contract conclusion.