Quick answer: "Budget template" means something different depending on what you're managing. A project budget template tracks planned versus actual cost for one initiative — labor, vendors, software, contingency. A program budget template rolls several related project budgets into one view with a shared contingency reserve. A portfolio budget template allocates a fixed funding ceiling across everything competing for it, by strategic value rather than by project. All three work fine in Excel individually. The strain shows up at the seam between them — the point where someone has to manually copy numbers from one level up into the next.
Below are all three, built the way each one actually needs to work, with free downloadable templates for each — plus an honest account of where Excel stops being enough as you move from managing one project to managing all of them.
Three altitudes, three different templates
A project manager, a program manager, and a portfolio director are all technically "doing a budget," but they're answering different questions:
— Project budget — "Are we spending what we planned to spend on this initiative, and where's the variance coming from?"
— Program budget — "Across the five projects that make up this program, who's over, who's under, and does our shared contingency cover it?"
— Portfolio budget — "We have a fixed amount of money this year. What's it allocated to, and does that allocation still match what actually matters strategically?"
Using a project-level template to answer a portfolio-level question (or vice versa) is the single most common reason budget spreadsheets feel like they're fighting you. Pick the template that matches the question you're actually being asked.
1. Project budget template
This is the workhorse: one project, one budget, tracked against actuals as the work happens.
What it needs, at minimum:
— Cost categories that match how the organization actually spends — typically labor/internal resources, contractors or professional services, software and licenses, hardware or equipment, travel, training, and a contingency reserve. Generic "misc" categories are where budget accountability quietly goes to die.
— A CAPEX/OPEX column next to each category, if your finance team requires that split for reporting (most mid-size and enterprise PMOs do). Getting this right at the line-item level saves a painful reclassification exercise at quarter close.
— Planned, committed, and actual columns — not just planned versus actual. "Committed" (a signed PO, a contractor engagement letter) sits in between: money that isn't spent yet but is no longer available either. Templates that skip this column consistently overstate how much budget is actually still free.
— Variance in both dollars and percentage. A $2,000 overage on a $10,000 line and a $2,000 overage on a $400,000 line are not the same problem, and a percentage-only or dollar-only view hides that.
— Monthly phasing, not just a project-total row. Spend rarely lands evenly across a project's timeline, and a phased view is what lets you catch "we're 40% through the timeline and 70% through the budget" before it becomes a steering committee surprise.
The free template (project-budget-template.xlsx) includes all of the above, plus an optional earned-value mini-section — percent complete, planned value, earned value, cost performance index — for teams that report against schedule and cost together rather than cost alone.
This level is genuinely Excel's home turf. One owner, one file, one source of truth. The formulas are simple SUM and SUMIFS, and there's no coordination problem because nobody else is editing it at the same time.
2. Program budget template
A program budget isn't a bigger project budget — it's a rollup of several project budgets that also has its own money to manage: a shared contingency reserve that individual projects draw against instead of each holding their own.
What it needs, at minimum:
— A per-project summary row — budget, actual, variance, percent complete, and RAG status for each constituent project, so a program manager can scan the whole program in one screen instead of opening five files.
— A pooled contingency section, separate from any project-level contingency. Program-level contingency exists precisely because pooling risk across several projects is more efficient than every project holding its own untouched buffer "just in case." The template needs to show the reserve, what's been drawn down, by which project, and what's left.
— A change request log. The contingency reserve is meaningless without a record of who asked for a draw-down, how much, and who approved it — otherwise the "remaining reserve" number in the summary tab is just a guess.
— Totals that actually foot — program total planned should equal the sum of every constituent project's planned budget, and the template should make that easy to verify at a glance rather than something you have to reconcile by hand every reporting cycle.
The free template (program-budget-template.xlsx) includes a program summary tab with per-project rollup rows, a contingency reserve tracker, and a change request log, pre-linked with the formulas that keep the totals honest.
This is where Excel starts to show its first real seam. The rollup itself — five projects' numbers landing in one summary — is easy in principle (a SUM across rows) and painful in practice, because those numbers usually have to be typed in by hand from five separate project trackers. The template can't fix that; it can only make the manual step as fast and error-resistant as a spreadsheet is capable of being.
3. Portfolio budget template
A portfolio budget is a different exercise again: instead of rolling numbers up, you're allocating a fixed ceiling down, across everything competing for it.
What it needs, at minimum:
— A funding ceiling, stated explicitly — the total portfolio budget for the period, with allocated and remaining-unallocated totals that update as rows get added, so it's immediately visible whether the portfolio is over-committed before it's over-spent.
— A strategic theme or category column, so allocation can be summarized by what the money is actually going toward — growth, run-the-business, compliance, innovation — not just by project name. Leadership rarely asks "how much did Project 14 cost"; they ask "how much of our budget is going to growth initiatives versus keeping the lights on."
— Priority rank alongside budget, so it's possible to see at a glance whether dollar allocation actually tracks strategic priority, or whether a lower-priority initiative is quietly consuming a disproportionate share.
— CAPEX/OPEX summarized at the portfolio level, not just per line item — most finance teams need this split reported as a portfolio-wide total, and a template that only tracks it per project makes someone rebuild that summary by hand every time it's requested.
The free template (portfolio-budget-template.xlsx) includes a portfolio summary tab with budget-ceiling tracking, a by-theme allocation summary, and a CAPEX/OPEX split — all formula-driven from the same row-level data.
This is the level where Excel's limits stop being an inconvenience and start being a real risk. A portfolio budget answers "does our spending still match our strategy," and that answer is only trustworthy if the underlying actuals are current. In a spreadsheet, actuals get to the portfolio tab through a chain of manual updates — project tracker to program summary to portfolio summary — and each hop in that chain is a place for a number to go stale, get fat-fingered, or simply not get updated the week it mattered. A portfolio decision made on a rollup that's two weeks old isn't really a portfolio decision; it's a guess with a spreadsheet attached.
This is the specific gap a platform like PPM Express is built to close: instead of three separate files with a human copying numbers between them, budget and actuals roll up automatically from project to program to portfolio, because the data has one source instead of three manually synced copies. If you're still doing that rollup by hand, it's not a sign you're doing it wrong — it's a sign you've reached the point where the tool, not the process, needs to change.
Where each level actually breaks
Being specific about when Excel stops being enough is more useful than a blanket "spreadsheets don't scale" warning:
— Project budget in Excel: rarely breaks. One owner, one file, low coordination overhead. Stays workable indefinitely.
— Program budget in Excel: starts to strain around five to eight constituent projects, or as soon as more than one program manager needs to update the rollup. Version drift ("whose copy is current?") shows up here first.
— Portfolio budget in Excel: breaks in a different way — not usually version drift, but staleness. The math still works; the numbers feeding it are the problem, because nothing forces the chain of manual updates beneath it to stay current.
None of this is an argument against starting in Excel. It's an argument for knowing, before you build a process around a workbook, which of these three jobs you're actually solving — and for noticing the moment a spreadsheet's limitation becomes the thing costing you time and trust, rather than discovering it during a steering committee meeting.
Frequently asked questions
What's the difference between a project budget and a program budget? A project budget tracks planned versus actual cost for one initiative. A program budget rolls several related project budgets into a single view and typically manages its own pooled contingency reserve that constituent projects can draw against — something a single project budget doesn't need.
What's the difference between a program budget and a portfolio budget? A program budget rolls existing project budgets up into a summary. A portfolio budget works the other direction — it allocates a fixed funding ceiling down across everything competing for it, organized by strategic priority rather than by project grouping, and doesn't assume the items in it are related the way a program's projects are.
Do I need CAPEX/OPEX tracking in a project budget template if my company doesn't require it? No — it's only necessary if your finance function reports that way. If it doesn't apply, drop the column; a template with fields nobody fills in accurately is worse than a leaner one that stays current.
How many projects can a program budget rollup realistically handle in Excel? Most teams stay comfortable up to five to eight constituent projects with a single owner maintaining the rollup. Past that, or once more than one person needs to update the summary, version-control problems tend to show up faster than the math does.
Can Excel handle portfolio-level budget allocation? For a static, point-in-time allocation exercise (like an annual planning cycle), yes. For ongoing tracking — where actuals need to stay current as project spend happens continuously — Excel's limitation isn't the formulas, it's that actuals only update when someone manually re-enters them, which makes portfolio-level decisions only as current as the last manual refresh.
Key takeaways
Match the template to the altitude you're actually managing at: project templates track one initiative's spend, program templates roll several of those up with a shared contingency, and portfolio templates allocate a fixed ceiling across everything by strategic priority. All three work well in Excel on their own. What doesn't scale in a spreadsheet is the connective tissue between them — the manual rollup from project to program to portfolio — and that's worth recognizing as a process problem, not a personal failing, the day it starts costing more time than the budgeting itself.
.svg){kind=small}
