If someone wanted to constrain a project's end date so that any project slippage would cause negative float, they would do so by using

To create a condition where project slippage results in negative float, a "Finish-No-Later-Than" (FNLT) constraint must be applied to the final activity or project milestone. This constraint imposes a hard deadline. The scheduling software uses this date as the starting point for the backward pass calculation to determine late dates. If the forward pass calculation results in an early finish date that is later than this constrained late finish date, the total float (Late Finish - Early Finish) becomes negative, indicating a schedule overrun against the deadline.

A: A finish-no-earlier constraint on the first activity would only delay the project's start; it would not create a cap on the end date. B: A finish-no-earlier constraint on the last activity sets a target to finish after, not a deadline to finish before, and would not generate negative float. D: A start-no-later constraint on the first activity restricts the project start but does not directly control the project's overall completion deadline.

1. AACE International

Recommended Practice No. 29R-03

"Forensic Schedule Analysis

" (April 25

2011)

Section 1.4.C.3

p. 14. Discusses constraints and their effect on float calculations

noting that late constraints can result in negative float.

2. AACE International

Recommended Practice No. 10S-90

"Cost Engineering Terminology

" (June 18

2019)

p. 82. Defines "Negative Float" as occurring when the "late start or finish date is earlier than the early start or finish date

" a condition created by a late constraint.