Zero-based forecasting reviews staffing needs from the ground up, using current employment as a starting point rather than relying on past trends. By weighing each role against workload and organizational goals, managers can make clearer decisions about hiring, retaining, or reducing staff.

Multiple Choice

Which forecasting method starts with the organization's current level of employment?

The correct approach for forecasting that begins with the organization's current level of employment is Zero Based Forecasting. This method requires that each new period’s forecasts be made from a "zero base," meaning it does not assume any levels of employment based on historical data or trends. Instead, it starts fresh, evaluating all positions and workloads for the business from the ground up, considering what is truly necessary to meet current organizational goals. This approach is particularly useful for organizations looking to align their staffing needs directly with their strategic objectives and resource allocations. By examining what the organization currently has and critically assessing future needs, it ensures that any growth or downsizing is based on rational needs rather than assumptions derived from past employment levels. In contrast, other methods like Bottom-Up and Top-Down Forecasting rely on existing projections and often extend from historical data. Trend Analysis also emphasizes patterns and past data to predict future employment needs, which differs fundamentally from the fresh assessment required in Zero Based Forecasting.

Zero-Based Forecasting: Building Workforce Plans From the Ground Up

A workforce plan can look solid on paper and still rest on a shaky assumption: that the jobs an organization has today are the jobs it will need tomorrow. Zero-based forecasting challenges that idea. It asks leaders to review staffing needs afresh for each planning period, rather than simply extending past employment patterns into the future.

The name can sound a little puzzling. If forecasting starts with a “zero base,” does that mean the organization pretends it has no employees? Not quite. Managers can use the current workforce as a starting point for discussion, but they don’t automatically carry every existing position into the next plan. Each role and staffing need must be justified against the organization’s goals, workload, and resources.

That distinction matters. A business may have a team of ten people today, but changes in technology, demand, or strategy could mean it needs eight people next year—or twelve, or a different mix of skills altogether. Zero-based forecasting makes room for that reassessment.

What zero-based forecasting really means

Zero-based forecasting estimates future staffing needs by reviewing work and roles from the ground up. Instead of treating last year’s headcount as the default, leaders ask what the organization needs to accomplish in the coming period and what people or skills are required to do it.

The “zero” refers to the forecast’s starting assumptions, not necessarily to the number of employees on the payroll. Past staffing levels may provide useful context, but they aren’t treated as proof that the same roles should continue unchanged. A position is included because it supports a real need—not simply because it appeared in last year’s budget.

For instance, a university department might be reviewing its staffing plan after a large shift toward online services. It could look at the work now being done, identify tasks that have grown or faded, and decide which skills are needed next. Some existing roles may remain essential; others may need to change, combine, or be replaced by new capabilities.

This makes the approach strategic as well as financial. Staffing decisions connect to what the organization is trying to achieve, rather than following old patterns by default.

Why start fresh when history is useful?

Historical data can be helpful. If a retail company sees a predictable increase in customer demand each holiday season, previous years may offer a sensible guide to future staffing. Yet history can also keep an organization tied to arrangements that no longer fit.

Imagine a customer service team that once needed many employees to answer routine questions by phone. The company adds a self-service portal, and customers begin resolving common issues online. If managers simply carry forward the old headcount, they may overlook the change. A fresh review can reveal that the team now needs fewer people for routine calls but more staff with technical or specialist knowledge.

Zero-based forecasting is useful when the organization’s direction, workload, or operating model is changing. It can also help leaders spot roles that have grown through habit rather than clear demand. That doesn’t mean every planning cycle has to become a full-scale organizational overhaul. The point is to question assumptions, not to create disruption for its own sake.

There is a trade-off, though: a thorough review takes time. Managers need reliable information about workloads, skills, costs, and future plans. Without that, “starting from zero” can become a slogan rather than a useful way to make decisions.

How it differs from other forecasting methods

Workforce forecasting methods all help estimate future staffing needs, but they don’t begin in the same place.

Trend analysis uses patterns from past data to estimate what may happen next. If a company’s workforce has grown by a similar amount each year, trend analysis might project continued growth. This can be efficient when conditions are stable. It can be less reliable when the organization is changing fast or when earlier patterns no longer apply.

Top-down forecasting starts with broad organizational goals or senior-level estimates. Leaders might set a target for labor costs or total staffing, then pass that direction to departments. The method can give an organization a clear overall frame, though it may miss local details if managers closest to the work have little input.

Bottom-up forecasting begins with information from departments or teams. Managers estimate the people and skills they’ll need, and those estimates move upward for review. This can capture day-to-day realities, but separate teams may make inconsistent assumptions unless someone coordinates the process.

Zero-based forecasting differs because it asks leaders to justify staffing needs anew rather than assuming existing positions will continue. In practice, organizations can combine methods. A senior leader may set financial limits, departments may submit workload estimates, and a zero-based review may examine whether each proposed role supports current priorities.

The methods aren’t rivals in every situation. They’re different lenses. A trend line shows where staffing has been heading; a bottom-up estimate reveals what teams say they need; a zero-based review asks whether those needs still make sense.

A closer look at the process

A zero-based workforce forecast usually starts with the organization’s goals for the period ahead. Those goals might include opening a new service, reducing wait times, meeting new regulations, or moving more work online.

Next, leaders examine the work itself. What tasks must get done? How much work is expected? Which skills are essential, and where are current employees already equipped to meet the need? This step can reveal that the issue isn’t simply the number of people. The organization may need different skills, clearer job design, or better coordination between teams.

Then managers estimate the roles and staffing levels required. They compare those needs with the existing workforce and identify gaps, overlaps, or areas where responsibilities could shift. Finally, they consider costs and constraints. A plan might identify a need for more expertise but also recognize that hiring is not the only way to fill it; training, redeployment, or redesigned work may also be relevant.

Communication matters throughout. Employees can feel uneasy when a staffing review begins, especially if they hear only that every role is being questioned. A clear explanation helps: the purpose is to understand future work and match resources to real needs, not to assume that every position should disappear.

The benefits—and the limits

The main benefit is a closer link between staffing and organizational priorities. When leaders examine work rather than copying the old headcount, they can make more informed decisions about hiring, role changes, and resource allocation. The method can also highlight obsolete tasks and neglected skill gaps.

Still, zero-based forecasting doesn’t guarantee a perfect prediction. Business conditions can shift, and even careful estimates involve uncertainty. Nor should a fresh review dismiss institutional knowledge. Long-serving employees may hold important insight into how work gets done, including the small details that don’t show up in a spreadsheet.

A balanced forecast treats past information as evidence, not as a command. It also values input from the people who understand the work firsthand. That combination helps prevent two common mistakes: blindly repeating old staffing patterns and making abrupt cuts based on incomplete information.

A workforce plan that can change with the work

Organizations don’t stand still, so their staffing plans shouldn’t be set in stone. Zero-based forecasting offers a way to look beyond habit and ask what the organization needs now. It begins with the work and goals ahead, then weighs current roles against those needs.

That fresh start doesn’t erase the past. It puts the past in its proper place—as useful context, but not an automatic blueprint. When leaders keep that distinction clear, they can build workforce plans that are more thoughtful, more flexible, and better connected to the work people are actually being asked to do.