How to build a project budget, step by step, with a cost breakdown table

What a project budget is (and is not)

A project budget is the approved amount of money for completing the project's scope, broken down by work and by time. It has three layers, and mixing them up causes most budget arguments:

• Cost estimates: the expected cost of each work package, built from quantities, rates and durations.
• Cost baseline: the sum of the estimates plus the contingency reserve for known risks, spread over the schedule. This is the budget the project manager controls and the one earned value measures against. Its total is the budget at completion (BAC).
• Project budget: the cost baseline plus a management reserve for unknown risks. The sponsor usually controls the management reserve, and spending it needs a change.

A budget is not a single number written into a business case. Without the breakdown, you cannot tell which part of the project is overspending until the money runs out.

How to build a project budget in eight steps

1. Fix the scope. Start from a work breakdown structure. Every cost belongs to a work package, and every work package has a budget. Costs with no home in the WBS are how budgets leak.
2. Choose the estimating method per package. Bottom-up (quantities times rates) where the design is clear; analogous (based on a similar past project) or parametric (cost per unit, such as per square meter or per user) where it is not. Use three-point estimates for uncertain items; the three-point estimate calculator does the PERT arithmetic.
3. Estimate each cost type. Labor (hours times rate), materials, equipment, subcontracts, licenses and services, travel, fees.
4. Add indirect costs. Project management, site or office overheads, insurance, and any corporate overhead rate your organization applies.
5. Size the contingency reserve from the risk register. Add up the expected monetary value of the threats you have chosen to accept, or use a percentage only as a first pass and replace it later.
6. Time-phase the baseline. Spread each package's cost over its scheduled dates. This creates the planned value curve and the cash flow forecast.
7. Add the management reserve outside the baseline, agreed with the sponsor.
8. Get approval and freeze the baseline. From then on, the baseline changes only through approved change requests.

Worked example: a cost breakdown table

Take a small systems rollout for a mid-sized office: new hardware, software licenses, configuration and training. Here is the budget, built with the steps above.

Line	Basis	Amount (USD)
Internal labor	1,200 hours × $60	72,000
Contractors	Fixed quote, network setup	18,000
Hardware	Quotes for devices and cabling	25,000
Software licenses	First-year subscription	12,000
Travel and training	Two sessions, trainer fees	5,000
Direct cost subtotal		132,000
Indirect costs	10% of direct	13,200
Total estimate		145,200
Contingency reserve	10% of estimate (first pass)	14,520
Cost baseline (BAC)		159,720
Management reserve	5% of baseline	7,986
Project budget		167,706

Check the arithmetic: 72,000 + 18,000 + 25,000 + 12,000 + 5,000 = 132,000. Indirect costs are 132,000 × 0.10 = 13,200, so the estimate is 145,200. Contingency is 145,200 × 0.10 = 14,520, giving a baseline of 159,720. The management reserve is 159,720 × 0.05 = 7,986, so the approved budget is 167,706.

Now replace the contingency percentage with risk-based numbers. Suppose the risk register holds three accepted threats: a hardware price rise (40% chance, $15,000 impact, EMV $6,000), extra configuration work (50%, $10,000, EMV $5,000) and a delayed training venue (30%, $5,000, EMV $1,500). Their EMV totals $12,500, a little less than the 10% placeholder. You can now defend the contingency line in front of a sponsor, because each dollar traces to a named risk.

Finally, time-phase it. If the rollout runs four months and most hardware is bought in month 2, the planned spend might be $30,000, $65,000, $40,000 and $24,720 by month, which adds back to 159,720. That monthly curve is your planned value.

Common project budget mistakes

• Hiding contingency inside estimates. Padding every line makes the baseline meaningless and the padding gets spent. Keep reserves visible and separate.
• Forgetting internal labor. Staff time costs money even when no invoice arrives. If you leave it out, you cannot compare projects fairly.
• A budget with no time profile. Without monthly phasing you cannot do earned value or forecast cash.
• Budgeting at the top level only. A single line per phase hides where the overrun starts.
• Changing the baseline informally. Every change to scope and money should go through a change request with its budget and date impact recorded.
• Ignoring currency and inflation on long projects or imported items. State the price base date of the estimate.

After approval: tracking against the budget

Once the baseline is frozen, record actual costs against the same work packages every month. Comparing actual cost with the budget alone is misleading: being under budget may just mean you are behind. Earned value fixes this by comparing three numbers: what you planned to spend by now (planned value), the budgeted value of the work actually done (earned value) and what you actually spent (actual cost). The earned value management guide explains the method in full.

How to do this in Critova

In a full project controls project, Critova holds the schedule and the cost side together. Enter cost entries by hand or import them from a spreadsheet, keep baselines (as many as you need), and record scope changes as change requests with their budget and date impact, approved or rejected on the record. Critova then calculates earned value metrics such as CPI, SPI and the EAC family, each shown with its formula, and the cost dashboard shows them across projects. The risk register records cost exposure and EMV per risk, which gives you the numbers for a risk-based contingency. See the cost features.