A SMALL NETWORK. A VISIBLE ANSWER.
What actually moves
the finish date?
Structure and procurement run in parallel. Installation needs both. Change the procurement duration to see when a late delivery becomes a later project.
Run the experiment
Fixed: structure = 12 days; installation = 3 days. Day zero is the common start. All activities use one continuous working-day calendar.
Orange: driving branch and installation. Blue: other branch.
Procurement can grow by 4 working days before it moves installation. Structure currently drives the finish.
Why these numbers change
The join happens at the later of the two branch finishes. Installation starts there and takes three more days. In this model, procurement float is the join day minus procurement duration. Because procurement leads directly into the common join, its free float and total float are equal here. That equivalence does not hold for every network.
Installation start = max(structure, procurement) Project finish = installation start + 3 Procurement float = installation start − procurement
Three scenarios to discuss with your team
| Procurement | Finish | What changed? |
|---|---|---|
| 8 → 10 days | Day 15 | Two days of float are consumed; completion stays put. |
| 8 → 12 days | Day 15 | Both branches now drive. There is no spare time on either branch. |
| 8 → 17 days | Day 20 | Procurement drives. Its nine-day duration increase moves completion five days. |
What this example leaves out
This is an educational model, not a schedule file analyzer. Real schedules can include multiple calendars, progress, lags, constraints, resource limits, and different calculation settings. A later finish also does not identify who is responsible or whether an extension is due. Preserve the original schedule and examine the governing facts before drawing that conclusion.