Contingency Budget: What It Is and How to Calculate It

What is a contingency budget?

A contingency budget is a reserved amount of money — built into your project estimate — that covers unexpected costs. It’s not padding. It’s a calculated response to risk.

Every project has two types of uncertainty:

• Known unknowns — risks you can identify but can’t price exactly. A subcontractor might charge more than quoted. Materials might increase in price. The client might request a revision round you didn’t plan for.
• Unknown unknowns — risks you can’t predict at all. A regulatory change, a key team member leaving, a supply chain disruption.

Contingency covers the first type. The second type is handled by management reserve — a separate bucket that sits above the project budget.

Management reserve vs. contingency reserve

These are often confused, but they serve different purposes and are managed by different people.

	Contingency Reserve	Management Reserve
Covers	Known unknowns (identified risks)	Unknown unknowns (unforeseeable events)
Owned by	Project manager	Senior management / sponsor
Part of project baseline?	Yes	No — sits above the baseline
Typical range	5–15% of project cost	3–10% on top of total budget
Approval to use	Project manager decides	Requires sponsor approval

For freelancers and small businesses, you usually only need contingency reserve. Management reserve matters more on large, multi-team projects.

How to calculate contingency percentage

There’s no single formula — the right percentage depends on how much risk the project carries. Consider these factors:

• Project complexity — more moving parts means more things that can go wrong. A simple brochure site needs less buffer than a custom SaaS build.
• Scope clarity — if the brief is vague or the client hasn’t finalized requirements, add more buffer.
• Client history — repeat clients with predictable feedback need less contingency than new clients with unclear expectations.
• External dependencies — subcontractors, third-party APIs, permits, approvals — anything outside your control adds risk.
• Timeline pressure — tight deadlines leave no room for recovery. Compressed schedules need higher contingency.

A common starting point: 10% for well-defined projects, 15–20% for projects with significant unknowns. Adjust up or down based on the factors above.

How to present contingency in a proposal

This is where most people get nervous. Clients see “contingency” and think you’re inflating the price. Here’s how to handle it:

• Name it clearly. Don’t hide it inside line items. A separate “Risk Buffer” or “Contingency” line shows transparency, not weakness.
• Explain what it covers. “This 10% buffer covers scope adjustments, revision rounds beyond the agreed limit, and minor unforeseen technical issues.”
• Set a rule for unused funds. “Any unused contingency is returned to you at project close.” This removes the fear that you’re pocketing extra money.
• Frame it as protection for both sides. Without a buffer, every surprise becomes a change order — which is slower, more expensive, and more frustrating for both parties.

The goal is to make the client feel safer, not more suspicious. A well-explained contingency line actually increases trust.