The Regulator's Date: Negative Float on a Transmission-Line Upgrade
A transmission-line upgrade must be energized before the regional peak season on 15 May - a date imposed by the regulator, not derived from the plan. Your CPM schedule, built from the contractor's estimate and a 5-day calendar, calculates a finish on 24 April. Once the schedule is resource-loaded and the subcontractor calendars are applied, the calculated finish moves to 22 May. The project manager's response is to apply a finish-no-later-than constraint of 15 May and instruct the team to 'hold the date.' After the constraint is applied, total float on the tower-erection path shows −7 days and the longest path no longer matches what the software flags as critical. The sponsor asks why the schedule turned red overnight.
1. Explain to the sponsor what the −7 days of total float means and what is actually driving the 15 May risk. What must you avoid doing?
Read the worked answer
What the number means
- A finish-no-later-than constraint makes CPM calculate float against an imposed date rather than the calculated finish. Negative total float of 7 days means: within current logic, durations, calendars and resources, the work cannot reach 15 May - it is 7 working days short.
- The schedule did not 'go red overnight.' The underlying finish date (22 May) was already there; the constraint only made the gap visible.
What is driving it
- Once constraints exist, the software's 'critical' flag and the actual longest (driving) path can diverge. Recovery must be aimed at the longest path, not at whatever is flagged red.
- Before any recovery decision, verify the inputs that produced the 22 May result: calendar assignments (5-day vs 7-day), the 10-day cure durations, resource leveling output, and any soft lags.
What to avoid
- Do not crash the whole schedule, and do not crash activities off the driving path - that buys cost with no date.
- Do not quietly delete the constraint to make the report green; that hides the decision the sponsor actually needs to make.
2. The PM wants to crash the concrete-cure activities by 30% to recover the 7 days. Evaluate that proposal and give a defensible alternative set of options.
Read the worked answer
Evaluate the proposal
- Crashing adds resources to shorten duration. Curing is driven by chemistry and specification, not by crew size, so adding labour does not compress it. The activity is not crashable in the normal sense.
- Check first whether the cure activities are even on the driving path. If tower erection is driven by steel delivery or foundation release, compressing cure recovers nothing.
Defensible options, with the trade each carries
- Accelerate the cure technically - accelerated mix design or heated enclosures. Requires engineering approval, may alter quality hold points and acceptance risk; treat as a technical change, not a schedule trick.
- Fast-track - overlap cure with the successor using a start-to-start relationship plus a deliberate lag, accepting rework risk on the overlapped portion.
- Re-sequence across tower faces - start erection on faces whose foundations are already released; often recovers days with no technical risk.
- Reduce scope or accept the date - descope a non-essential segment, or take the date issue to the regulator as a formal position.
Each option should be presented with days recovered, cost, added risk and confidence - not as a single 'we will crash' answer.
3. What do you put in front of the sponsor, and how does the answer change if the 15 May date turns out to be a soft target rather than a regulatory hard date?
Read the worked answer
If the date is hard
- Present a time-impact analysis: the 7-day gap on the driving path, cause, and 2–3 recovery options with days, cost, risk and confidence.
- State plainly that 15 May is achievable only with a specific combination (e.g., re-sequencing plus accelerated cure), and that the remainder requires a change to scope, cost or the date.
- Frame it as a decision with a deadline, not a status update.
- Any resulting baseline change goes through change control; retain the old baseline and the original finish-date calculation for the record.
If the date is soft
- The constraint was never a hard requirement, so it should not have been modeled as one. Negative float against an arbitrary date is noise that distorts priority-setting.
- Remove or downgrade the constraint, re-run CPM, and report against the calculated finish plus the business driver behind 15 May (peak-season energization value).
- The sponsor still decides whether the commercial benefit justifies acceleration - but the schedule stops manufacturing urgency that the business case does not support.
The judgment being tested: constraints encode requirements, not wishes, and the scheduler's job is to expose the gap, not to absorb it.