How to Track Burn Rate Across Multiple Consulting Projects

Run more than a handful of consulting engagements at once and burn rate stops being a nice-to-know metric. It becomes the number that tells you whether a project is quietly eating its budget weeks before the invoice ever goes out. Firms that track burn rate project by project, in a spreadsheet built for one engagement at a time, tend to spot problems only after the margin is already gone. Tracking it across your whole portfolio is a different discipline, and it’s the one that actually protects profitability.

What Is Burn Rate in Consulting?

Burn rate is the pace at which a project consumes its budget, usually measured in dollars or hours spent per week or month. On a single project, it tells you how fast the runway is shrinking. Across multiple projects, it becomes a comparative signal: which engagements are on pace, which are accelerating toward overrun, and which have quietly stalled and are burning less than planned, a sign of understaffing or scope drift in the other direction.

Gross Burn vs. Net Burn

Gross burn rate looks at total cost consumed in a period, regardless of what’s been billed. Net burn rate nets that cost against revenue recognized in the same period. For consulting firms, net burn is the more useful lens because it connects delivery cost directly to what the engagement is actually earning, not just what it’s spending.

The Burn Rate Formula

The core calculation is simple. The complexity shows up when you’re running it across a portfolio.

Burn Rate = (Budget Spent in Period) ÷ (Length of Period)

• Budget spent: labor cost, expenses, and any subcontractor spend logged against the project in the period.
• Length of period: usually weekly or monthly, chosen to match how often your team reviews project health.
• Remaining runway: (Total Budget − Budget Spent) ÷ Burn Rate, which tells you how many periods are left before the budget runs out.

For example, a $200,000 engagement that has spent $60,000 in the first six weeks is burning at $10,000 per week. At that pace, the remaining $140,000 covers roughly 14 more weeks, information that only matters if you’re checking it against the actual weeks left on the statement of work.

Blended Rate Complications

Most consulting teams staff projects with a mix of seniority levels and rate cards. Burn rate calculated on raw hours will understate cost on a project staffed with senior consultants and overstate it on one staffed with junior talent. Calculating burn against blended cost rates, not just hours logged, keeps the comparison honest across a portfolio where staffing mix varies project to project.

How to Track Burn Rate Across Multiple Projects

1. Standardize the time and expense capture. Burn rate is only as accurate as the data feeding it. If some consultants log time daily and others reconstruct it weekly, the numbers won’t be comparable across projects, let alone accurate within one.
2. Set a common reporting cadence. Pick one period, weekly works for most firms, and calculate burn rate for every active project on that same cycle. Comparing a project measured monthly against one measured weekly gives you noise, not insight.
3. Normalize by budget size. A $500,000 engagement and a $50,000 engagement will burn at very different absolute rates. Track burn as a percentage of total budget consumed per period, not just the raw dollar figure, so projects of different sizes sit on the same scale.
4. Layer in planned burn as a baseline. Every project should have an expected burn curve based on its staffing plan and timeline. Actual burn only means something next to that baseline. A project burning at $15,000 a week isn’t a problem if the plan called for $16,000. It’s a problem if the plan called for $8,000.
5. Roll it up into a single view. Once each project has a comparable burn figure, the real value comes from seeing them side by side, sorted by variance from plan. That’s what turns burn rate from a per-project spreadsheet exercise into portfolio-level visibility your operations and finance teams can act on.

Common Pitfalls When Tracking Burn Rate Across a Portfolio

Treating every project on the same rate assumptions. Fixed-fee, time and materials, and retainer engagements all burn differently, and blending them into one calculation without adjusting for contract type produces misleading comparisons.

Reviewing burn rate too infrequently. Monthly reviews catch problems after a full billing cycle has already been affected. Weekly checks give your team room to correct staffing or scope issues before they show up in a client invoice dispute.

Ignoring resource utilization alongside burn. A project can look financially healthy on paper while an individual consultant is overallocated across two or three engagements at once. Burn rate and utilization need to be read together, not separately, to catch that kind of hidden risk.

Summary

Tracking burn rate across a full roster of consulting engagements takes more than a shared spreadsheet template. It takes accurate, real-time time and expense data flowing into one place where every project’s burn is measured the same way and checked against the same plan. That’s exactly the kind of visibility a modern PSA platform is built to deliver.

See how it works for your firm: book a personalized demo.