Burn Rate
Burn rate is the speed at which a project consumes its budget — spend per week or per month. It is used to project when funds will run out and to compare actual consumption against plan. On its own it says nothing about progress: a project can burn exactly to plan while delivering nothing.
What it contains
Burn rate is derived rather than recorded. It needs actual cost by period, which on most IT projects means timesheets or resource allocations at agreed rates, plus vendor invoices, licences and infrastructure. The rate is total spend for the period divided by the number of periods, or more usefully, plotted per period so the shape is visible.
Three related figures usually travel with it. Cumulative spend to date against the approved budget. Remaining budget divided by current burn rate, giving the number of weeks of funding left. And forecast at completion, which is spend to date plus the estimated cost of the work remaining — the figure that actually matters at a steering committee, and the one the budget tracker is built to produce rather than leaving it as a mental calculation.
How it is used
Burn rate answers a funding question, not a delivery question. If a project is burning ninety thousand a month with four hundred thousand left, it has roughly four and a half months of runway at current staffing. Whether that is enough depends entirely on how much work remains.
The comparison that carries information is planned burn against actual burn. Underspending early is common and usually means mobilisation is slower than assumed — roles unfilled, contracts unsigned, environments not ready. That underspend is not a saving; it is deferred cost, and it typically reappears as a spike later.
Burn is also the figure that makes staffing decisions concrete. Adding two contractors changes the monthly rate immediately and the completion date only maybe. Presenting both together — the steering committee pack usually shows burn beside milestone progress for this reason — is what stops the two being discussed separately.
Where it goes wrong
The classic error is reading burn as progress. A project fifty per cent through its budget is not fifty per cent complete, and the two figures diverge most in exactly the situations where you would want a warning. Burn tracks input consumption. Milestone completion tracks output. Both belong in the same report.
The second is burn calculated on invoices received rather than work performed. Vendor invoicing lags, often by a month or more, so reported spend understates committed spend. Accrual — recording what has been consumed but not yet billed — is what makes burn honest, and it is the step most often skipped.
The third is a burn rate that ignores committed future cost. Signed statements of work, licence renewals and contracted notice periods are already spent in every sense except the ledger. A runway calculation that excludes them is optimistic by the size of the commitments.
The fourth: burn measured against the original budget after scope has changed. Every approved change request should move the baseline, which is why the change log and the budget need to reconcile. Comparing today's spend to a superseded baseline produces a variance that is arithmetic rather than a signal.
Related terms
Cost variance is the difference between planned and actual cost for the work performed. Forecast at completion is the projected total cost including remaining work. Accrual is cost recognised before it is invoiced. Run rate is the recurring cost per period, often used interchangeably with burn rate. Contingency is the budget held back for identified risk, and whether it is included in burn should be stated explicitly.
Questions
Is burn rate the same as run rate?
In practice they are used interchangeably. Run rate more often describes ongoing operational cost per period; burn rate more often describes consumption of a fixed budget.
How often should burn rate be reported?
Monthly suits most projects because that matches finance cycles. Weekly reporting adds noise unless the project is short or under close funding scrutiny.
Why does reported burn understate real spend?
Because vendor invoices arrive late. Without accruals for work performed but not yet billed, reported spend trails actual commitment by weeks.
Does burn rate indicate whether a project is on track?
No. It measures how quickly money is being consumed. It only becomes a track indicator when read alongside milestone completion or earned value.