Zero-Based Budgeting Reform: How It Works

Zero-based budgeting reform means requiring public agencies or other organizations to justify proposed spending from a zero baseline for each budget period, rather than treating last year’s budget as the automatic starting point. It can make priorities and costs more visible, but it is a budgeting method—not a guarantee of lower spending or better services.

What zero-based budgeting means

In conventional incremental budgeting, decision-makers often begin with the previous period’s funding and consider adjustments: a program might receive the same amount, a small increase, or a cut. Zero-based budgeting (ZBB) instead asks managers to build and explain funding requests anew. “Zero-based” refers to the starting point for the review, not to an assumption that every activity should receive no money.

The approach is associated with Peter Pyhrr, who developed and described a formal system for business budgeting in the 1970s. It later attracted interest in government as a way to question established spending patterns and connect resources to priorities. In practice, organizations use different versions: some conduct a comprehensive review each year; others apply the approach to selected departments or spending categories on a rotating schedule.

How the process works

A typical ZBB cycle starts by defining the budget period, goals, and available resources. Managers then identify activities and the staff, equipment, contracts, and other inputs needed to deliver them. They explain what each activity accomplishes, what it costs, and what consequences might follow from funding it at different levels.

Requests are compared and prioritized before leaders decide how to allocate a limited budget. A simplified sequence is:

Set strategic objectives and a realistic spending ceiling.
Identify programs, services, and the work required to deliver them.
Estimate the costs of alternative service or activity levels.
Explain each request with evidence, including expected results and risks.
Rank requests against agreed criteria and allocate available funds.
Track spending and performance, then use the findings in the next review.

For example, a city department proposing to maintain a public facility might show the cost of keeping it open five days a week, extending hours, or reducing service. The decision would consider not just the budget line but also staffing, operating costs, demand, and effects on residents. ZBB does not determine which option is right; it creates a structure for examining the trade-offs.

What reform is intended to change

When people call for “zero-based budgeting reform,” they may mean introducing ZBB, improving an existing system, or requiring more scrutiny of particular areas. The central reform is a change in the questions asked: instead of “How much more or less than last year?” decision-makers ask “What work is needed, what does it cost, and how does it support current goals?”

That shift can challenge the assumption that a long-standing program should continue at its existing level simply because it has done so before. It may also reveal duplicated activities, outdated processes, or costs that have not been clearly linked to outcomes. Conversely, a review may show that a continuing service needs stable or increased resources. A zero starting baseline is a review device, not a verdict against existing programs.

Effective reform usually requires clear definitions of the activities being reviewed, consistent cost data, transparent criteria, and enough time for meaningful analysis. Legislators or executives still set priorities and make final allocation decisions; technical rankings do not replace public or political judgment.

Potential benefits and limitations

ZBB can improve understanding of how resources support activities and make alternatives easier to compare. It can encourage managers to identify the consequences of cuts or expansions rather than presenting a single take-it-or-leave-it request. It may also bring attention to low-visibility costs that incremental reviews overlook.

But a complete annual rebuild can be labor-intensive. Staff may spend substantial time assembling justifications, while decision-makers face a large volume of requests. Cost estimates can be uncertain, and results depend on the quality of data and the criteria used. Activities that produce benefits over many years, prevent rare harms, or are difficult to measure may be undervalued if a review favors simple short-term metrics.

Another limitation is that a nominally zero-based process can become incremental in practice. If there is insufficient time to examine every activity, reviewers may rely on last year’s figures anyway. Alternatively, an organization may devote so much effort to paperwork that it has less capacity for delivering services. ZBB is therefore a management process with costs of its own, not a free administrative fix.

How it compares with other budgeting approaches

Incremental budgeting is relatively straightforward and can provide continuity, but it may preserve outdated assumptions. Performance budgeting connects resources to measures or results, although measuring public value can be difficult. Program budgeting organizes spending around programs or objectives rather than only around departments or inputs. These approaches can overlap: an organization can use performance information within a zero-based review.

Participatory budgeting is different. It gives residents or other community members a role in proposing or selecting certain spending priorities. ZBB describes how requests are built and reviewed; it does not, by itself, specify who participates in decisions. A government could combine the methods, but public input and technical cost analysis remain distinct parts of the process.

When reform is most practical

Starting with a targeted review can be more manageable than requiring every department to reconstruct every budget line at once. An organization might examine a major discretionary category, a set of overlapping services, or a program facing significant changes. A pilot can help reveal the staff time, data, and decision rules the process requires before expansion.

Useful safeguards include:

Use consistent cost definitions and document assumptions.
Assess service quality, access, and long-term effects alongside immediate savings.
Distinguish essential ongoing obligations from genuinely discretionary choices.
Publish understandable criteria and explain how decisions were reached.
Review actual results after funding decisions, rather than treating approval as proof of success.

These steps do not eliminate disagreement. They make it easier to identify whether a decision reflects evidence, stated priorities, or a value judgment that should be discussed openly.

Frequently Asked Questions

Does zero-based budgeting mean every program starts with no funding?
No. It means proposed funding is justified from a zero baseline during the review. Existing programs can receive funding if decision-makers determine that their work and costs merit it.

Is zero-based budgeting the same as cutting budgets?
No. The process can lead to cuts, continued funding, or increases. Its purpose is to review and prioritize requests, not to require a particular total or outcome.

Does zero-based budgeting save money?
It may identify costs or activities that leaders choose to change, but savings are not automatic. Reviews require staff time, and their financial effects depend on the decisions made and the costs of implementation.

How often should an organization use it?
There is no single schedule that fits every organization. Some conduct broad reviews periodically, while others apply ZBB to selected areas or rotate reviews to manage workload.

How is it different from performance budgeting?
ZBB focuses on justifying requests from a zero baseline. Performance budgeting emphasizes the relationship between spending and measured results. An organization can use both, but performance measures alone do not establish the value of every activity.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.