Schedule Float¶

Scheduling method — instantiates Safety Margin Design

Places deliberate time between the expected completion and a hard deadline, governed by a rule for who may consume it, so ordinary delay doesn't cause deadline failure.

Schedule Float is margin in the time dimension: reserved time between when work is expected to finish and a hard deadline, held as an explicit buffer and consumed only under a rule. The failure boundary is the deadline — a launch window, a regulatory date, a season — past which the work is simply too late. Its defining move, distinct from money reserved in a Budget Contingency, is that the protection is pooled as time at the end of the chain rather than padded into every task, and its consumption is governed so it isn't silently eaten early. It buys time against slippage, not cost against overrun.

Example¶

A satellite must reach the launch site by a fixed date. The launch window is immovable — miss it and the mission waits months for the orbital geometry to return, so the deadline is a hard boundary. The integration-and-test schedule's honest expected finish is about six weeks ahead of that date. Rather than pad every task individually — which invites work to expand to fill the padding (Parkinson's law) and start late anyway (student syndrome) — the team estimates each task at its median duration and pools the protection into a single project buffer at the end of the critical chain: the schedule float. A consumption rule governs it. Routine slips draw the buffer down; when it is, say, half consumed, that crossing triggers escalation and recovery action rather than a shrug. The float is watched as a burn-down, so the team sees the deadline margin shrinking weeks before it would run out.

How it works¶

The distinguishing moves:

Estimate tasks at the median, stripped of hidden per-task padding.
Pool the protection into a shared buffer at the end of the critical chain, rather than scattering it across tasks where it gets wasted.
Govern consumption with a burn rule — banded thresholds (buffer green / yellow / red) that trigger escalation as the float is eaten.
Track the burn-down, so deadline margin is a managed quantity, not a discovery on the last day.

Tuning parameters¶

Buffer size — how much time to pool, as a fraction of the critical chain; the core deadline-vs-cost tradeoff.
Aggregation — per-task padding vs. a single pooled buffer; pooling is more efficient and far more visible.
Burn thresholds — the buffer-consumption levels that trigger escalation; where green becomes yellow becomes red.
Feeding buffers — smaller buffers protecting the critical chain where side-paths merge into it.

When it helps, and when it misleads¶

It helps where the deadline is genuinely hard, task durations are uncertain, and a slip cascades down the chain — a pooled buffer absorbs the variation a single padded task never could. Its failure modes are behavioral: float that is public and unowned gets spent first-come by whoever is behind, and padding hidden inside tasks is quietly wasted (work fills the time). The classic misuse is committing the deadline as if the float were free schedule to give away — promising the buffered date to a customer, so the very first slip is already a breach. The discipline is to pool the buffer, keep its burn-down visible, and govern who may draw it, so it protects the deadline instead of evaporating into optimism.^[1]

How it implements the components¶

Schedule Float fills the reserve-and-governance side of the margin in the time dimension:

normal_operating_range — the expected, median task durations and the planned finish before delay is added.
safety_margin — the pooled time between planned completion and the deadline boundary.
margin_release_rule — the consumption rule and burn thresholds governing who may draw the float and when escalation fires.

It does not reserve funds against cost overrun — that is Budget Contingency — nor hold live throughput (Capacity Headroom), nor display the buffer burn-down, which a Safe Operating Limit Chart would render.

Instantiates: Safety Margin Design — Schedule Float is the margin held as pooled, governed time.
Sibling mechanisms: Budget Contingency · Capacity Headroom · Conservative Estimate · Structural Safety Factor · Reserve Inventory · Risk Capital Buffer · Setback Requirement · Safe Operating Limit Chart · Minimum Reserve Requirement · Stress-Test Margin Check · Premortem Margin Review

References¶

[1] Pooling task-level safety into a single project buffer at the end of the critical chain, rather than padding each task, is the critical chain method — a response to the way per-task padding is wasted by Parkinson's law and student syndrome. ↩