Skip to main content
Calcimator

Project Burn Rate Calculator

Track budget consumption and forecast project spending.

About this calculator

This calculator measures how fast a project is actually spending money and projects that pace forward. Weekly Burn Rate is Spent to Date divided by Elapsed Weeks -- a plain average of the pace run so far. Because Elapsed Weeks sits in the denominator, the same Spent to Date reported after 6 weeks instead of 16 roughly triples the computed rate, and every other figure on this page is derived from that single Weekly Burn Rate number. Projected Total Spend multiplies that historical rate by Total Project Weeks, on the assumption spend continues at the same pace for the rest of the schedule -- a real limitation, since most projects do not spend at a constant weekly rate. Staffing often ramps up mid-project, late-stage testing and fixes can cost more per week than early planning, and one-time purchases spike a single week's number without changing the underlying trend.

Budget Variance compares that straight-line projection against Total Budget, flagging an overrun before it happens rather than after. Allowable Burn Rate answers a different question -- given what remains in the budget and the weeks still remaining, what weekly rate keeps the project on budget from this point forward, independent of the pace run so far. Cost Per Person divides the current Weekly Burn Rate evenly across Team Size; it is an average share of spend, not a tracked figure for any individual team member, contractor, or line item. Weeks Until Budget Depleted divides Remaining Budget by Weekly Burn Rate; it shows -1 rather than 0 when nothing has been spent yet, since a literal 0 would misleadingly read as "already out of money" for a project that hasn't started spending -- 0 is reserved for the genuine case where Spent to Date has caught up to or passed Total Budget. Schedule Health is Elapsed Weeks as a percentage of Total Project Weeks -- a pacing figure, not a judgment on budget performance, which Budget Health tracks separately.

Inputs

$
$

Results

Weekly Burn Rate

$14,166.67

Remaining Budget$215,000.00
Projected Total Spend$283,333.33
Budget Variance$16,666.67
Budget Used %28.3%
Allowable Burn Rate$15,357.14
Weeks Until Budget Depleted15.2
Weekly Cost Per Person$2,833.33
Schedule Health30%
How to Use This Calculator
  1. Enter the Total Budget and Total Project Weeks planned for the project.
  2. Input Spent to Date and Elapsed Weeks — how much has actually been spent, and how many weeks in.
  3. Enter Team Size to see Weekly Cost Per Person.
  4. Review Weekly Burn Rate and Allowable Burn Rate together, and check Budget Variance for an early overrun warning.
  5. If Weekly Burn Rate exceeds Allowable Burn Rate, investigate scope creep or resource overruns immediately.

How the result changes with Elapsed Weeks

Elapsed WeeksWeekly Burn Rate
3$28,333.33
4.5$18,888.89
9$9,444.44
15$5,666.67

What each input means

Total Budget
Total project budget.
Spent to Date
Total amount spent so far.
Elapsed Weeks
Number of weeks since project started.
Total Project Weeks
Total planned project duration in weeks.
Team Size
Number of team members.

What each result means

Weeks Until Budget Depleted
-1 means the project isn't currently spending, so the budget won't deplete at this pace. 0 means the budget is already fully spent.

How this is calculated

Worked example, using the default values

  1. Identify Input Parameters
    5 parameters
    Total Budget = 300000, Spent to Date = 85000, Elapsed Weeks = 6, Total Project Weeks = 20, Team Size = 5 = 5 input(s) provided
  2. Calculate Weekly Burn Rate
    Weekly Burn Rate
    14166.67 = $14,166.67
  3. Calculate Remaining Budget
    Remaining Budget
    215000 = $215,000
  4. Calculate Projected Total Spend
    Projected Total Spend
    283333.33 = $283,333.33

Engine last updated . Checked against 1 independently-derived test — how we verify calculators. Built by Paul Gunder, a software engineer, not a licensed financial, medical, or legal professional.

Frequently Asked Questions

Why does raising Total Project Weeks not change Weekly Burn Rate?

Weekly Burn Rate is Spent to Date divided by Elapsed Weeks -- a measure of the pace already run, not the plan going forward. Total Project Weeks only feeds figures that project or compare against the full schedule, like Projected Total Spend and Allowable Burn Rate; the observed pace itself does not change when the overall timeline is extended or shortened.

Why is Team Size inert with respect to Weekly Burn Rate?

Weekly Burn Rate only reflects money spent, derived from Spent to Date and Elapsed Weeks -- it has no headcount term. Team Size only enters the calculation through Cost Per Person, which divides the already-computed Weekly Burn Rate evenly across the team; adding or removing people changes that average share, not the underlying weekly spend figure.

What does a negative Budget Variance mean?

Budget Variance is Total Budget minus Projected Total Spend, so a negative result means the current Weekly Burn Rate, extrapolated unchanged for the rest of the schedule, would exceed the total budget. It is an early warning based on straight-line extrapolation of the pace observed so far, not a certainty -- actual spend does not have to continue at exactly that rate.

Is Cost Per Person the actual amount spent on each team member?

No -- it is Weekly Burn Rate divided evenly by Team Size, an average across the whole team rather than a tracked per-person expense. If spend concentrates in a few roles, such as contractors or specialized tooling, the real cost attributable to any one person can differ substantially from this evenly-split figure.

The questions that sit next to this one — chosen by subject, including calculators filed under a different category.

More in Business & Entrepreneurship.