A good zero-based budget is not an exercise in justifying every paper clip. It's a structured way of answering one question repeatedly:
"If we were starting this department today, what spending is actually required to achieve our objectives?"
The key is to budget at the level of meaningful business decisions, not individual transactions.
Here's a practical framework that many finance teams use.
Step 1: Start with the department's mission and goals
Before listing expenses, define what the department is expected to deliver during the coming year.
For each major objective, identify:
- Required outcomes
- Key performance indicators (KPIs)
- Expected workload or demand
- Strategic priorities from leadership
Example:
| Objective | Success Measure |
|---|
| Reduce customer response time | <24 hours |
| Launch two new products | On-time releases |
| Maintain regulatory compliance | Zero audit findings |
This prevents budgeting around historical habits.
Step 2: Break the department into decision packages
Instead of budgeting by accounting category first, budget by activities or services.
Examples:
- Customer support
- Employee training
- Software development
- Compliance
- Equipment maintenance
- Marketing campaigns
Each becomes a "decision package."
For each package answer:
- What does it accomplish?
- Why is it needed?
- What happens if it isn't funded?
- Who benefits?
- What resources does it require?
This is the heart of zero-based budgeting.
Step 3: Define service levels
Avoid treating every activity as all-or-nothing.
For each package define multiple funding levels.
Example:
| Level | Description |
|---|
| Minimum | Keeps operations running |
| Standard | Meets expected performance |
| Enhanced | Improves growth or efficiency |
Now management can make informed tradeoffs instead of blanket cuts.
Step 4: Estimate resource requirements
Only now calculate costs.
Typical categories include:
- Personnel
- Benefits
- Contractors
- Software licenses
- Equipment
- Office expenses
- Travel
- Training
- Professional services
- Contingency (where appropriate)
Every estimate should have a clear basis, such as:
- Headcount × salary
- License cost × users
- Vendor quote
- Expected transaction volume
- Historical utilization (used only as evidence—not as the budget itself)
Step 5: Separate fixed from discretionary spending
This helps identify where decisions can actually be made.
Fixed or unavoidable
- Salaries for essential staff
- Contractual obligations
- Compliance costs
- Required software
Discretionary
- Conferences
- Additional training
- New initiatives
- Consulting
- Equipment upgrades
This immediately focuses discussion on the areas where choices exist.
Step 6: Prioritize decision packages
Rank every package by business value.
A simple scoring model works well.
| Factor | Weight |
|---|
| Supports company strategy | High |
| Revenue impact | High |
| Customer impact | High |
| Regulatory requirement | Very High |
| Efficiency improvement | Medium |
| Nice-to-have | Low |
If funding becomes limited, the ranking already identifies what should be protected.
Step 7: Challenge every assumption
For every significant expense ask:
- Is this activity still necessary?
- Is there a cheaper way?
- Can technology replace part of it?
- Can another department share the cost?
- Can spending be delayed?
- Can service levels be reduced with acceptable impact?
Zero-based budgeting is about questioning assumptions—not automatically eliminating costs.
Step 8: Prepare the business case
Every major spending area should fit on roughly one page containing:
- Purpose
- Business value
- Annual cost
- Key assumptions
- Risks if not funded
- Expected outcomes
- Performance metrics
If someone asks, "Why are we spending $150,000 here?" the answer should already exist.
Step 9: Build the consolidated budget
Now combine all approved packages into categories like:
| Category | Annual Cost |
|---|
| Personnel | |
| Technology | |
| Facilities | |
| Operations | |
| Professional Services | |
| Training | |
| Capital Equipment | |
| Total | |
This becomes the formal departmental budget.
Step 10: Create an assumptions register
This is often overlooked but makes the budget much easier to defend.
Document assumptions such as:
- Hiring two additional employees in Q2
- Software vendor increases prices by 4%
- Travel returns to 75% of pre-pandemic levels
- Production volume grows 12%
- Inflation assumed at 3%
When assumptions change, everyone understands why the budget may need to change.
Avoid getting bogged down
A common mistake is trying to justify thousands of tiny expenses individually. Instead, focus your effort where it matters.
A practical guideline is:
- Spend 80–90% of your analysis on the largest 20% of cost categories.
- Group small recurring items into reasonable buckets (e.g., "Office supplies," "Miscellaneous subscriptions") unless they are unusually large or strategically important.
- Require detailed justification only for material costs, new spending, or areas where management has genuine choices.
This keeps the process rigorous without becoming inefficient.
A simple workflow
- Define departmental objectives.
- List major activities (decision packages).
- Determine minimum, standard, and enhanced service levels.
- Estimate resources for each package.
- Justify every major cost with evidence.
- Rank packages by business value.
- Challenge assumptions and look for efficiencies.
- Consolidate into the annual budget.
- Document assumptions and risks.
- Track actual spending against the same decision packages throughout the year.
This approach produces a budget that is both defensible—because every significant expense is tied to a business objective—and manageable, because it concentrates attention on the decisions that materially affect departmental performance rather than on low-value administrative detail.
