Every task has a little extra time, yet the project still has no clear protection against uncertainty. Project time contingency is an explicit allowance in the schedule for identified uncertainty. Decide what it protects, where it sits and who may consume it rather than quietly padding every estimate.
This is a planning recommendation, not a universal percentage. APM's scheduling guidance provides the underlying logic for dates and float. A contingency allowance is a deliberate management choice; schedule float arises from the activity relationships and constraints in the model.
Photo by Renáta-Adrienn on Unsplash.
Name the uncertainty before adding time
Ask what could move the accepted finish: variable review effort, an uncertain external input or a task whose complexity will only become clear after inspection. Known routine work belongs in the estimate. A forgotten review is missing scope, not an unexpected event.
Do not use contingency to conceal an already infeasible plan. Show the underlying sequence and the allowance separately so the sponsor understands the commitment being proposed.
Build a short allowance record
For each important allowance, note:
Uncertainty and the result exposed to it.
Evidence or scenario supporting the allowance.
Where the time appears in the schedule.
Owner monitoring the condition.
Authority to consume, release or revise it.
Trigger for escalation if protection becomes inadequate.
Check whether several allowances cover the same event. A review task already estimated with a range may overlap with a separate correction allowance. Avoid implying a stronger level of protection by counting one uncertainty twice.
A hypothetical client review window
A project needs an accepted pack before an external event. The team plans the production and agreed review cycle, then identifies uncertainty around a supplier's final input. The sponsor considers holding an additional internal window before the public commitment.
The allowance has an owner and a decision date. If the supplier confirms acceptable material early, the sponsor can decide whether to release the window or retain it for another justified exposure. It does not automatically become space for extra features.
If the input is late enough to exhaust the allowance, the project escalates while alternatives remain. The buffer is not a reason to hide the delay until it has disappeared.
Review consumption and remaining exposure
At a checkpoint, show how much allowance remains, why it has moved and whether the original uncertainty is still relevant. A consumed day is information about the project, not necessarily a failure by the person reporting it.
Avoid displaying the protected finish as certain. Untested assumptions, resource constraints and correlated delays can still exceed an allowance. More complex uncertainty may need specialist scheduling or risk analysis rather than a bigger guessed buffer.
Keep contingency different from spare capacity
A free calendar day is not useful if the required reviewer is unavailable. Confirm the people and operating conditions needed to use the allowance. Time protection and resource protection need to fit together.
The small-team planning guide helps connect the allowance to the wider schedule. For the connected task, read How to Keep a Project Assumptions Log That Changes Decisions. To review whether your deadline has genuine protection, discuss your project requirements.
