Here is a practical framework for managing project budgets in a way that gives you early warning on overruns, clear accountability for spend, and reliable data for financial reporting.
Step 1: Set Budgets at the Right Level of Granularity
Project-level budgets are necessary but not sufficient. A $500K project budget doesn’t tell you whether the engineering work is on track — it just tells you the total envelope. You need budgets broken down by cost category (people, software, external services, infrastructure) and ideally by team or workstream.
The right level of granularity is the level at which you can take action. If you can’t do anything with a budget number, it’s too aggregated.
Step 2: Track Commitments, Not Just Actuals
Most budget tracking focuses on actuals — what has been spent. This is a lagging indicator. By the time a budget overrun appears in the actuals, the damage is done.
Track commitments — approved expenditures that haven’t been invoiced yet. A contractor engagement signed but not yet billed is a commitment. Future salary costs for the team are commitments. The gap between your total budget and your total commitments is your true remaining capacity to spend.
Step 3: Allocate People Costs to Projects
For most tech companies, people costs are 60–75% of total project budget. But people costs are rarely tracked at the project level — they’re tracked by department in the P&L. This disconnect creates a systematic blind spot: projects appear under-budget because people costs aren’t attributed to them.
Fix this by running a simple internal transfer pricing model — assign a cost rate to each team (based on fully-loaded salary + overhead) and allocate to projects based on capacity allocation percentages. It doesn’t need to be accounting-perfect; it needs to be directionally accurate.
Step 4: Establish a Monthly Budget Review Cadence
Every project should have a monthly budget review: budget vs actuals vs forecast. The forecast — what you expect to spend by the project end date — is the critical number. It’s the one that tells you whether you need to intervene now or whether you’re on track.
Any project where the forecast exceeds the budget by more than 10% should trigger an exception conversation: what’s driving the variance, and what’s the decision?
Step 5: Create a Culture of Budget Accountability
Budget accountability requires that project leads see their budget data regularly and feel ownership over it. A budget managed exclusively by finance, reviewed only by the COO, creates no behavioural change at the project level.
Give project leads access to their budget dashboards. Include budget status in project reviews. Treat budget management as a core project management competency, not a finance function.
