Budget Burn / Burn Rate

Budget burn is the portion of a project’s allocated budget consumed to date. Burn rate is the speed of that consumption, expressed as cost or hours per week. Together they are the primary tools for detecting cost overruns in real time rather than at project close.

The core calculations

Budget burn (%) = Actual cost to date / Total budget × 100

Burn rate (weekly) = Actual cost to date / Weeks elapsed

Planned burn rate = Total budget / Total planned weeks

A project with a $200,000 budget planned over 10 weeks has a planned burn rate of $20,000 per week. If the team has spent $90,000 in week 4, the actual burn rate is $22,500 per week, running 12.5% above plan.

Burn vs. completion: the key comparison

Budget burn is meaningful only when compared against project completion percentage:

• Burn % equals completion %: spending is in line with progress
• Burn % exceeds completion %: overspending relative to progress, overrun risk
• Burn % trails completion %: underspending relative to progress, possible delays or under-staffing

A project that is 70% through its budget but only 50% delivered is on track to overrun. The estimate at completion (EAC) calculation quantifies how large that overrun will be if current rates hold.

Why burn rate matters more than point-in-time burn

A single burn number shows where the project stands today. Burn rate shows where it is heading. If burn rate is accelerating in the second half of a project, a delivery problem is compounding. If burn rate is slowing unexpectedly, the team is likely blocked or the project is shedding scope.

Tracking trend, not just position, is what allows a project manager to act before the budget is exhausted. A change order to increase budget or reduce scope has to be negotiated before the funds run out, not after.

Hours burn vs. dollar burn

Tracking only dollar burn obscures where overspend originates. A project can run over budget because:

• The team is working more hours than planned (a volume problem)
• The staffing mix is more senior than the estimate assumed (a rate problem)
• Both

Separating hours burn from dollar burn identifies which problem is at work. If hours are on plan but cost is over, the issue is rate. If hours are over plan, the team is working harder than the estimate projected, which points to a scope or estimation gap.

Common pitfalls

• Not resetting the planned burn rate after an approved scope change. Once a change order is signed, the baseline changes and the comparison becomes meaningless if the denominator stays fixed.
• Reporting burn at month-end instead of weekly. A monthly cycle delays the warning signal by up to four weeks, often past the point where corrective action is cheap.
• Conflating budget burn with WIP (work in progress). Burn tracks spending against budget; WIP tracks unbilled effort against revenue. Both matter, but they answer different questions.

The Fixed-Fee Pricing Calculator can help establish planned burn baselines when structuring fixed-fee engagements.