Project Burn Rate: How to Calculate and Control It

How do you calculate project burn rate?

Burn rate is total cash out during a period divided by the number of periods. Use cash actually leaving the account, not costs recognised in the ledger, and use a period long enough to smooth routine timing noise.

Gross burn = total cash out in the period ÷ number of periods

Net burn = (total cash out − cash in) ÷ number of periods

A project with $384,000 of expenditure over six months has a gross burn of $64,000 a month. If it also received $90,000 from a client milestone in that window, net burn is ($384,000 − $90,000) ÷ 6 = $49,000 a month.

Three choices determine whether the number is useful:

Cash, not accrual. An invoice dated 28 March but paid on 15 April belongs to April for burn purposes. A prepaid annual licence is cash out on day one, even though the accountant spreads it over twelve months. Burn rate is a treasury view: it exists to predict the bank balance.

A period that matches the spend pattern. Monthly is standard, but if payments cluster — quarterly VAT, annual insurance, milestone invoices — a single month will mislead you in both directions. Use a rolling three-month average and report the individual months beside it.

Consistent scope. If the calculation includes a group function one month and excludes it the next, the trend is meaningless. Write down what is in the number.

What is the difference between gross burn and net burn?

Gross burn is what leaves the account. Net burn is what leaves after money arrives. The gap matters enormously on projects with milestone payments, licence resales, or partial client funding.

The trap with net burn is optimism. A project that depends on a client paying on the 30th can look comfortable for eleven months and insolvent in week 52, because one late payment turns net burn back into gross burn. Report both, and state which receipts are confirmed.

Why is runway the number that actually forces decisions?

Because runway converts a rate into a date, and dates create urgency that percentages never do. “Burn is 12% above plan” invites discussion. “We cannot pay salaries after 14 August” ends it.

Runway has a simple formula and an important qualifier:

Runway (months) = cash available to the project ÷ net burn per month

The qualifier is what “cash available” means. It is not the approved budget. Approved budget is permission to spend; cash on hand is the ability to spend. Many projects have a healthy budget and a thin bank balance, because funding is released in tranches, tied to gates, or shared with the rest of the organisation.

Three runway variants are worth tracking on any cash-constrained project: gross runway (cash ÷ gross burn, the pessimistic case where no receipts arrive), net runway (cash ÷ net burn, assuming receipts land as planned), and committed runway (cash ÷ (net burn + committed step-ups), the realistic case once approved hires and signed contracts land).

If the three numbers are far apart, the project has a collections risk disguised as a healthy forecast.

Example 1: on budget and three weeks from an empty account

A nine-month programme has a $600,000 budget, planned to burn evenly at $66,700 a month. At the end of month 4, $268,000 is spent — almost exactly the $266,800 planned. By any budget measure, it is on track.

Now the cash view. Funding is released in three tranches, and tranche two arrives at the month-5 gate. Cash on hand is $58,000.

Runway = $58,000 ÷ $67,000 = 0.87 months, or about 26 days.

The gate is 30 days away. The project is on budget and four days short of payroll.

Nothing in the budget report warned anyone, because the budget report did not know about tranche timing. The fix is not a cost cut; it is a conversation with finance about releasing tranche two early, a short bridge, or re-sequencing a $40,000 vendor payment. All three are cheap. Discovering the gap on day 27 is not.

This is the most common burn-rate failure, and it has nothing to do with overspending.

Example 2: how net burn changes the runway story

A client-funded project spends $95,000 a month: $45,000 on staff, $40,000 on subcontractors, $10,000 on tools and hosting. It invoices the client in monthly milestones averaging $30,000.

Gross burn = $95,000. Net burn = $95,000 − $30,000 = $65,000.

With $390,000 in the project account:

• Gross-burn runway = 390,000 ÷ 95,000 = 4.1 months
• Net-burn runway = 390,000 ÷ 65,000 = 6.0 months

Which number is real? Both, depending on whether the client pays. If one milestone slips a month, that month’s net burn reverts to $95,000 and runway compresses immediately.

The honest presentation is a range: “six months if receipts land on schedule, 4.1 months if they stop.” That is more useful to a steering group than either number.

What is burn multiple and when should you use it?

Burn multiple is net burn divided by net new value added in the same period. It answers a question burn rate cannot: how much cash did it take to produce one unit of new, recurring value?

Burn multiple = net burn ÷ net new ARR (for a revenue-generating product)

A company that burned $1.8 million over twelve months and added $1.2 million of net new annual recurring revenue has a burn multiple of 1.8 ÷ 1.2 = 1.5x. It spent $1.50 for every $1.00 of new recurring revenue.

The metric was popularised by David Sacks at Craft Ventures. The commonly cited scale is:

For non-revenue projects, use delivered value as the denominator. A cost-reduction programme that burns $400,000 for $1.1 million of annual savings scores 0.36x; a rewrite that burns $2 million to remove $300,000 of maintenance cost scores 6.7x and needs an argument beyond “the old system is messy.”

The trade-off is real. Burn multiple punishes investment that takes more than a year to pay back, and some strategically necessary work looks terrible on it. Use it as a lens on the portfolio, not as a veto on individual projects.

How does burn rate differ from CPI, SPI and budget variance?

Burn rate measures the pace of cash consumption. CPI and SPI measure the relationship between value earned, money spent, and schedule. Budget-versus-forecast measures variance from plan. They answer three different questions, and a project can be healthy on one and failing on another.

The practical consequence: a project can be exactly on budget and still run out of cash, and a project can be over budget while burning slowly enough to be in no immediate danger. Budget variance is an accounting judgement about the destination; burn rate is a treasury question about the journey.

If you already track earned value, keep it. Add burn rate beside it: earned value systems usually run on accrual data and monthly cycles, the wrong resolution for a cash question.

Example 3: the same project, three different stories

Take a programme at month 6 of 9. Approved budget $900,000, spent $700,000, forecast at completion $1,010,000. Cash on hand $140,000, net burn $88,000 a month, net new annual savings delivered $260,000. Read three ways:

• Budget view: 78% spent at 67% elapsed, 12% forecast overrun. A cost problem — real, but survivable.
• Cash view: runway = 140,000 ÷ 88,000 = 1.6 months against three months of work remaining. The project needs $264,000 and has $140,000. This is the emergency.
• Value view: burn multiple = 700,000 ÷ 260,000 = 2.7x. The spending is producing something, expensively.

Each view implies a different action: cost control, a funding decision this month, or a scope review. A report that shows only the first gets the response wrong.

What actually controls burn rate?

Scope, sequencing, and commitment timing — in that order. Cost-cutting that targets visible line items produces a small, temporary dip and a larger cost later.

1. Scope is the only lever with a large, permanent effect. Removing a workstream removes its labour, its tooling, and its dependencies. Trimming 5% from every line item reduces quality and morale and typically saves less than expected, because the expensive parts remain.

2. Sequencing changes the shape of the curve, not the total. Moving a build phase after a buy phase can halve peak burn without changing the final cost. If the constraint is cash rather than budget, sequencing is often the cheapest available fix.

3. Commitment timing is the most underused lever. A hire approved in March but starting in June does not burn in April. An annual licence bought in January instead of October shifts twelve months of cost into a different financial year. Neither changes total cost; both change runway.

4. Payment terms are a financing decision. Net-60 instead of net-30 buys a month of runway on every invoice at no interest cost. Stretching terms beyond what suppliers can absorb damages delivery, so treat it as borrowing, not as saving.

> Common mistake: Cutting burn by delaying payments and deferring maintenance, then reporting the improvement. Both move cost into the future at a markup. Runway bought this way is borrowed, not earned.

Why does committed burn deserve its own number?

The burn rate you can stop is smaller than the rate you have. Committed burn is spend locked in by contract, licence, or approved headcount; it sets the floor beneath your runway.

Consider a project with $70,000 a month of current net burn, of which $18,000 comes from three annual contracts that cannot be cancelled and $22,000 from staff on notice periods. If the project is paused tomorrow, burn does not fall to zero — it falls to roughly $18,000 until the contracts expire.

• The minimum runway is longer than decision-makers assume. A “stop everything” instruction still leaves months of committed cost.
• New commitments should be dated, not just approved. A signed contract is a burn-rate decision whether or not anyone framed it that way.

A practical rule: any commitment above 2% of remaining budget should state its start date and its exit cost in the approval note. Those two fields turn a procurement decision into a runway decision.

What are the trade-offs?

• Cutting burn early can cost more than it saves. Delaying a hire that unblocks delivery extends the project, which extends every fixed cost attached to it.
• Net burn flatters cash-strapped projects. A healthy net number built on receipts that might slip is a forecast, not a fact.
• The reporting period is always a compromise. Weekly figures produce false alarms on monthly invoices; quarterly figures are useless for a decision needed in three weeks.

The balanced answer is a monthly headline, a rolling three-month trend, and a forward view of committed step-ups: stable enough to trust, current enough to act on.

Common mistakes to avoid

• Using the P&L instead of the bank. Accrual smoothing hides the timing that determines whether you can pay.
• Ignoring committed spend. A burn rate that only counts paid invoices understates the floor.
• Averaging lumpy months and calling it a trend. Report the individual months next to the rolling average.
• Treating burn as a performance score. Low burn is not efficiency; it may be a project that has stopped moving.
• Reporting burn without runway. A rate without a date helps nobody.
• Forecasting linearly. Mobilisation, licence renewals, and completion bonuses all create steps.

Where project tooling fits

Burn-rate problems are usually visibility problems. The budget lives in finance, the commitments in procurement, the work in a task board, and the cash position in a bank account nobody on the delivery team can see.

Doitify brings the delivery side into the same workspace as the money: project budgets and finance management alongside tasks, sub-tasks, owners and milestones, with work and performance reports that show planned versus actual over time. Because milestones and payment dates sit next to the work that triggers them, the gap between “work complete” and “cash received” becomes visible early.

Two honest limitations, and Doitify is our product so weigh them here. It is not an accounting system and does not replace your ledger or treasury function — the cash figure still comes from finance. And no dashboard fixes a project whose scope exceeds its funding.

Conclusion

Burn rate is a simple division with an unusually direct consequence: it converts spending into a date. Gross burn tells you what it costs to keep going, net burn tells you how fast the balance is falling, and runway tells you when the conversation becomes urgent.

Track it in cash rather than accrual, report it with runway rather than alone, and include the commitments you cannot switch off. Then pair it with a value measure — burn multiple for revenue work, delivered milestones for everything else. A project that burns slowly while delivering nothing is not efficient; it is idle, and idle never appears on the burn chart.

If this post on project burn rate was helpful, you might also enjoy Project Budget Management: Complete Guide and Project Management Software for Consulting Firms.