Contingency is a protected reserve of time or budget kept inside a project plan to absorb unexpected complexity within the original scope.
What is contingency?
Contingency is different from a change request. It is not meant for new scope. Instead, it covers risks that belong to the agreed work but could not be estimated with full confidence.
Why contingency matters
- It protects fixed-price delivery from technical surprises.
- It reduces the need for reactive contract renegotiation.
- It gives the team a safer risk margin.
- It supports more realistic planning under uncertainty.
Example
If an integration with a legacy ERP system is estimated at 100 hours, the team may add a 15 percent contingency because the data quality and documentation are unclear.
Contingency vs. change request
- Contingency: Covers uncertainty inside the original scope.
- Change request: Covers new or modified work outside the original scope.
How Apropo supports contingency planning
Apropo supports contingency planning through native buffer controls and through later comparison between planned and actual work.
- Project and item buffers give teams a practical way to represent contingency inside the estimate workflow.
- Named buffer entries make it easier to separate different risk sources instead of hiding them in one opaque number.
- Versioned estimates help teams compare alternative contingency assumptions during review.
- Shareable outputs make it easier to explain current contingency logic to stakeholders.
How Apropo helps refine contingency assumptions
Contingency planning improves when teams can compare their original assumptions with what happened in delivery.
- Budget tracking helps compare quoted work with actual spent work over time.
- Profitability views show how contingency decisions interact with the final commercial outcome.
- Jira sync helps connect delivery tracking back to the estimate structure.
- Revision history helps teams adjust contingency logic without losing prior estimate states.