Principles of Schedule Contingency Management
Every schedule gets hit by something — weather, design changes, late deliveries. Schedule contingency is time deliberately reserved to absorb those hits, held as one visible, managed buffer rather than padded invisibly into every activity. Built on AACE 70R-12.
What schedule contingency is
Contingency is the schedule's shock absorber. It's not slack you forgot to remove, and it's not padding you snuck in — it's a deliberate, sized, and visible allowance for the fact that risk is real. Sizing it well usually draws on risk analysis (the kind covered in Track 5), but the management principle is simple: hold it where you can see and control it.
Contingency vs float vs padding
Three things look similar on a Gantt chart but mean very different things. Keeping them straight is half the battle:
- Float — A calculated output of the network — spare time an activity has before it delays the project. You don't create it; CPM computes it. (Lesson 4.)
- Contingency / reserve — Time deliberately added and held to absorb identified risk. It's a managed buffer, owned by someone, drawn down on purpose.
- Padding — Hidden cushion stuffed into individual durations "just in case." Invisible, unmanaged, and the thing contingency is meant to replace.
Managing the reserve
Contingency isn't "set and forget." It's a balance you spend down deliberately as risks materialize, tracking the remaining cushion every period:
Ownership and placement
Where the reserve sits and who controls it shapes behavior. Contingency placed at the very end of the schedule (before the contractual finish) protects the project as a whole; reserve placed before key milestones protects those milestones. Either way, it should be explicitly owned — usually by project management — so it isn't quietly consumed by whoever hits trouble first.
| Placement | Protects |
|---|---|
| End-of-project reserve | The overall completion date |
| Pre-milestone reserve | A specific key milestone or phase handover |
| Feeding buffer (before a merge) | A critical merge point from a risky chain |
Ten things to remember
- Schedule contingency is time deliberately reserved to absorb risk and uncertainty.
- Hold it as one visible reserve — a buffer you can see is one you can manage.
- Float is calculated; contingency is added; padding is hidden — keep them distinct.
- Padding is the enemy — scattered hidden cushion is unmanageable and gets wasted.
- Size it from risk analysis, not gut feel — match the reserve to the real exposure.
- Track the balance like a bank account — each risk event is a withdrawal.
- Burning buffer faster than planned is an early warning — act before it's gone.
- Approve drawdowns deliberately and log them — don't let reserve leak into routine slippage.
- Place reserve to protect what matters — overall finish, a milestone, or a merge point.
- Define ownership and contract treatment up front — it prevents fights over consumed time.
Glossary
- Drawdown
- Deliberately consuming reserve as risks materialize.
- Feeding buffer
- Reserve placed before a critical merge point.
- Float
- Calculated spare time in the network — not contingency.
- Float ownership
- The contractual question of who may use available float.
- Management reserve
- Reserve held by management, outside the working baseline.
- Padding
- Hidden cushion inside durations — the thing to avoid.
- Schedule contingency
- Time reserved to absorb risk and uncertainty.
- Time reserve / buffer
- Another name for managed schedule contingency.