What is resource forecasting in project management?

Introduction

Resource forecasting gives project teams an early view of a question that can derail even a well-planned project: will the right people, skills, time, and capacity actually be available when the work reaches them? In project management, that visibility shapes everything from timelines and staffing decisions to workload balance and delivery confidence.

This guide explains what resource forecasting is, how it differs from resource planning, the methods teams use, the data behind a useful forecast, and how to build one step by step.

What is resource forecasting in project management?

Resource forecasting in project management is the process of estimating the people, skills, time, budget, equipment, and other resources a project will need over a future period. It gives project managers an early view of expected demand and whether the required capacity is likely to be available when the work begins.

A useful resource forecast should answer four questions:

• What resources will be required?
• How many resources will be needed?
• When will they be needed?
• Will they be available at that time?

What resources can be forecast?

Depending on the project, teams may forecast:

• People and roles: Engineers, designers, project managers, analysts, or other contributors.
• Skills and expertise: Specialized capabilities needed for particular phases or deliverables.
• Time and team capacity: The amount of effort teams can realistically commit.
• Budget: Expected spending required to support delivery.
• Equipment and materials: Physical resources needed to complete the work.
• Software and infrastructure: Tools, licenses, environments, or technical capacity.
• Contractors, vendors, and external services: Outside support required when internal capacity is limited.

What does a resource forecast include?

A practical project resource forecasting model typically captures:

• Project or workstream: Where the demand is coming from.
• Required role or resource type: The kind of resource needed.
• Skills or experience required: The capability level expected.
• Estimated effort: Hours, days, FTEs, or percentage capacity.
• Expected start and end dates: When the resource will be required.
• Available capacity: How much relevant capacity is expected to be free.
• Demand confidence: How certain the upcoming work is.
• Forecasted resource gap: The difference between expected demand and available capacity.

Resource forecasting vs. resource planning

Resource forecasting and resource planning are closely connected, but they answer different questions. Forecasting looks ahead to estimate future demand and likely availability. Planning uses that information to decide how resources should support upcoming work.

The surrounding practices, including capacity planning, allocation, and scheduling, turn that forecast into concrete staffing and delivery decisions.

In practice, these activities usually follow a simple sequence: teams forecast demand, assess capacity, plan resources, allocate them to work, and schedule those assignments against project timelines.

How resource forecasting fits into resource management

Resource forecasting sits at the beginning of a broader resource management process. The forecast provides visibility into future needs, while the stages that follow turn those estimates into practical staffing and scheduling decisions.

Forecast demand → assess capacity → plan resources → allocate resources → monitor actual usage

• Forecast demand: Estimate the people, skills, time, and other resources upcoming projects are expected to require.
• Assess capacity: Compare forecasted demand with the capacity and capabilities likely to be available during the same period.
• Plan resources: Decide how available resources should be distributed across projects, teams, or priorities.
• Allocate resources: Assign specific people or resources to approved work based on the plan.
• Monitor actual usage: Track how resources are being used during delivery and feed those insights back into future forecasts.

This creates a continuous resource planning and forecasting cycle, where actual project performance helps teams refine future estimates.

Why is resource forecasting important?

Resource forecasting helps teams make better delivery decisions before constraints become visible in the middle of execution. It gives project managers and team leads a clearer picture of whether planned work is realistic given the people, skills, and capacity available.

1. Creates more realistic timelines and commitments

When teams understand how much capacity is available, they can set delivery dates that reflect actual staffing conditions. This reduces the risk of building project plans around people who are already committed elsewhere.

2. Surfaces capacity and skill gaps early

Forecasting shows where expected demand exceeds available capacity and where specific expertise may be missing. Teams can then adjust scope, sequence work differently, arrange training, hire, or bring in external support before the gap affects delivery.

3. Reduces workload conflicts and improves utilization

Project resource forecasting helps identify overlapping assignments across projects and makes it easier to distribute work more evenly. It also highlights periods where capacity may be underused, giving teams more room to rebalance upcoming work.

4. Supports better hiring and contractor decisions

Longer-term forecasts help leaders distinguish between a short-term capacity spike and a sustained resource gap. That context makes hiring, contractor, and staffing decisions more deliberate.

5. Improves project and portfolio prioritization

Resource forecasting gives leaders a practical way to compare planned demand with available capacity before approving new initiatives. When several projects compete for the same teams or skills, this visibility helps determine what can realistically move forward and when.

What factors influence resource forecasting?

A resource forecast is only as useful as the assumptions behind it. Several factors can change either the amount of work expected or the capacity available to deliver it.

• Project scope and complexity: Larger or more complex projects usually require more time, specialist skills, coordination, and review effort.
• Project pipeline and future demand: The volume and likelihood of upcoming work directly affect how much capacity teams may need in the weeks or months ahead.
• Historical project performance: Previous estimates, actual effort, delays, and staffing patterns can provide a more realistic baseline for future forecasts.
• Current workload and resource availability: Existing assignments determine how much capacity is genuinely available for new work.
• Required roles and skills: A team may have enough people overall while still lacking the specific expertise a project requires.
• Project timelines and dependencies: Tight deadlines, overlapping phases, and dependent work can increase demand during particular periods.
• Leave, attrition, and operational responsibilities: Planned leave, team changes, support work, maintenance, and recurring responsibilities reduce the capacity available for project delivery.
• Budget and hiring constraints: Financial limits, hiring lead times, or contractor availability can restrict how quickly resource gaps can be addressed.
• Changing priorities and market conditions: New customer needs, shifting business priorities, or changes in demand can move projects forward, delay them, or alter their resource requirements.

Good resource management forecasting accounts for these variables rather than treating capacity as fixed throughout the project lifecycle.

What data is needed for resource forecasting?

Reliable resource forecasting depends on current, consistent project and capacity data. If the inputs are outdated, even a well-designed forecasting process can produce misleading results.

• Active and upcoming projects: Include approved, probable, and tentative work so teams can distinguish committed demand from work that may still change.
• Project scope, deliverables, and milestones: These show the amount and type of work the team is expected to complete.
• Project phases and expected timelines: Knowing when each phase begins and ends helps identify when particular resources will be needed.
• Effort and duration estimates: Estimates provide the basis for calculating how much capacity each project is likely to consume.
• Required roles and skills: Capture the specific expertise needed across different stages of the project.
• Current assignments and available capacity: Review existing commitments to understand how much time people or teams can realistically take on.
• Historical estimates and actual results: Past planned-versus-actual data can improve future assumptions about effort, duration, and staffing.
• Leave, holidays, meetings, and recurring work: These reduce usable capacity and should be reflected in the forecast.
• Project priorities, dependencies, and delivery risks: Priority changes and dependent work can affect sequencing, timing, and resource demand.

The more frequently this information is updated, the more useful the resource forecast becomes for planning future work and identifying capacity gaps early.

How to forecast resources for a project

A useful resource forecasting process starts with demand, then works backward into the people, skills, and capacity needed to deliver it. The goal is to make future resource requirements visible early enough for teams to adjust plans before shortages affect execution.

Step 1: Define the forecasting period

Start by deciding how far ahead the forecast needs to look. The right horizon depends on the type of work and the decisions the forecast is meant to support.

For example:

• A sprint-level forecast can help teams plan immediate capacity.
• A monthly forecast can support near-term staffing decisions.
• A quarterly forecast can help with hiring, contractor needs, and portfolio planning.
• A full-project forecast can show how resource demand changes across major phases.

The further out the forecast goes, the more uncertainty it should allow for. Near-term work can usually be estimated in greater detail than work several months away.

Step 2: Review current and upcoming project demand

Next, map the work that may require resources during the forecasting period. This should include active projects, approved initiatives, likely future projects, and any major deadlines already on the calendar.

At this stage, the aim is to understand where demand is coming from and when it is expected to arrive. Teams should also include recurring work that competes for the same capacity, such as maintenance, support, internal initiatives, or customer commitments.

Step 3: Categorize demand by confidence level

Future work does not always carry the same level of certainty. Treating every possible project as fully committed can inflate resource requirements and make the forecast harder to use.

A simple approach is to group demand into:

• Confirmed: Approved work with a clear start date or committed delivery window.
• Probable: Work that is likely to proceed but still depends on an approval, customer decision, or planning milestone.
• Tentative: Early-stage opportunities or initiatives that may change substantially or may never begin.

These categories help teams understand both expected demand and the uncertainty around it. A forecast can then show what capacity is definitely needed and what additional capacity may be required if probable or tentative work moves forward.

Step 4: Break each project into phases or work areas

Resource demand usually changes throughout a project. A project may require heavy design support early on, more engineering capacity during implementation, and additional QA or documentation closer to release.

Break each project into meaningful phases or work areas, such as:

• Research and discovery
• Planning
• Design
• Development
• Testing
• Review
• Launch
• Post-launch support

This creates a clearer picture of when different roles and skills will be needed instead of treating the project as one uniform block of work.

Step 5: Estimate effort by role and skill

Once the phases are clear, estimate how much effort each one is likely to require and which roles or skills will provide that effort.

Teams can express requirements in several ways:

• Hours: Useful for detailed project resource forecasting.
• Days: Easier for medium-term planning where hourly precision adds little value.
• Percentage capacity: Useful when someone is expected to spend part of their time on a project, such as 25% or 50%.
• Full-time equivalents (FTEs): Helpful for longer-term capacity planning, especially when forecasting across several teams or projects.

For example, a six-week development phase might require one backend engineer at full capacity, one frontend engineer at 75%, and a designer at 20%.

The unit matters less than consistency. Teams should use a format that everyone involved in resource planning and forecasting understands.

Step 6: Assess current resource capacity

Now compare those requirements with the capacity already available.

Review:

• Existing project assignments
• Team size
• Planned leave and holidays
• Support and operational responsibilities
• Meetings and recurring commitments
• Required skills and experience
• Known staffing changes

A common mistake is to treat every working hour as available project capacity. In reality, people spend time on support, coordination, reviews, internal work, and other responsibilities. The forecast should reflect usable capacity rather than theoretical availability.

Step 7: Compare resource demand with available capacity

This is where the forecast starts producing actionable insight. Compare what each project requires with the capacity expected to be available during the same period.

Look for:

• Resource shortages: Demand exceeds the number of people or hours available.
• Skill gaps: Capacity exists, but the required expertise is missing.
• Scheduling conflicts: The same person or team is needed by several projects at once.
• Underused capacity: Available resources have limited planned work during a period.
• Project bottlenecks: A shortage in one role could delay work for several other teams.

For example, a project may have enough engineering capacity overall but still face a bottleneck because two initiatives need the same database specialist during the same week.

This demand-versus-capacity comparison is one of the most important parts of how to forecast resources for a project because it turns estimates into specific planning decisions.

Step 8: Test alternative scenarios

A forecast becomes more useful when teams can explore what happens under different assumptions.

Test scenarios such as:

• A project starts two weeks later.
• Scope increases or decreases.
• A high-priority initiative moves ahead of another project.
• A team member becomes unavailable.
• A contractor or new hire joins the team.
• A probable project is approved.
• A tentative project is canceled.

Scenario planning helps teams see which constraints are temporary and which require a larger change in staffing, sequencing, scope, or timelines.

For instance, if moving one project by two weeks resolves a capacity conflict, hiring may be unnecessary. If the same shortage appears across several scenarios and several months, the team may be looking at a longer-term capacity gap.

Step 9: Create the resource forecast

Bring the information together into a forecast that is easy to review and update.

At minimum, it should show:

• Project or workstream
• Forecast period
• Required role or resource type
• Required skills
• Estimated effort
• Available capacity
• Demand confidence
• Forecasted gap
• Planned action

The forecast can be maintained in a spreadsheet, resource-management tool, or project-management system, depending on the size and complexity of the organization. The important part is that the underlying assumptions remain visible and can be updated as circumstances change.

Step 10: Review and update the forecast regularly

Resource forecasts lose value quickly when they are left untouched. Project scope changes, schedules move, new work enters the pipeline, and team availability changes over time.

Review the forecast at a cadence that matches the pace of the work. Teams operating in short delivery cycles may revisit it weekly, while longer-range portfolio forecasts may be reviewed monthly or quarterly.

Each update should replace assumptions with actual information where possible. Compare estimated effort with actual effort, update project confidence levels, account for staffing changes, and revise future demand. Over time, this feedback loop improves forecast accuracy and gives teams a stronger basis for future resource planning.

Resource forecasting methods and techniques

Different projects call for different forecasting methods. Some teams rely on expert input, while others have enough historical and capacity data to use more structured approaches. In practice, resource forecasting methods are often combined rather than used in isolation.

1. Expert judgment

Expert judgment relies on people who understand the work well enough to estimate what it will require. Project managers, engineering leads, functional managers, and subject-matter experts can provide input on effort, staffing levels, skill requirements, and likely constraints.

This method is especially useful for new or unusual work where historical data offers little guidance. Its accuracy improves when estimates come from several informed contributors rather than a single person.

2. Historical or analogous forecasting

Historical forecasting uses data from similar completed projects to estimate future resource requirements. Teams might compare effort by role, project duration, staffing levels, or planned versus actual resource usage.

For example, if three previous integrations of similar complexity required roughly six engineer-weeks and two weeks of QA support, that history can provide a useful starting point for the next one.

The comparison works best when the projects are genuinely similar in scope, complexity, technology, and team structure.

3. Bottom-up forecasting

Bottom-up forecasting starts at the most detailed level. Teams estimate the effort required for individual tasks, deliverables, or project phases, then combine those estimates into an overall resource forecast.

A product launch, for example, might be broken into research, design, development, testing, documentation, and release work. Each phase is estimated separately by role before the totals are combined.

This approach can produce detailed forecasts when the scope is mature, although it requires more planning effort than higher-level methods.

4. Top-down forecasting

Top-down forecasting begins with an overall estimate for the project and distributes that requirement across teams, roles, or phases.

A team might estimate that an initiative will require 12 person-months of effort, then allocate that total across engineering, design, product, and QA based on experience or expected workload.

This method is useful during early planning when detailed task information is unavailable. Teams can refine the forecast later as the project becomes clearer.

5. Trend-based forecasting

Trend-based forecasting looks for patterns in historical workload, resource utilization, or project demand and extends them into future periods.

A platform team that consistently spends around 30% of its capacity on support and maintenance, for example, can include that pattern when estimating how much capacity will remain for upcoming projects.

This method works best when past patterns are relatively stable, and the underlying operating conditions have not changed significantly.

6. Capacity-versus-demand forecasting

Capacity-versus-demand forecasting compares projected resource requirements with the capacity expected to be available during the same period.

This approach is particularly useful when several projects share the same people or skills. Teams can see where demand exceeds supply, where unused capacity exists, and which periods are likely to create bottlenecks.

The result often becomes the basis for resource allocation, project sequencing, hiring, or contractor decisions.

7. Skills-based forecasting

Skills-based forecasting focuses on the capabilities future work will require. Instead of asking whether ten people are available, the forecast asks whether the team has enough people with the right expertise.

For example, a project may need sufficient engineering capacity overall but still face a shortage of security, data, infrastructure, or mobile expertise.

This approach is especially valuable for technical teams where specialist knowledge can determine whether work can move forward.

8. Scenario-based forecasting

Scenario-based forecasting creates several versions of the future based on different assumptions.

A team might model:

• Expected scenario: Current plans and staffing remain broadly unchanged.
• High-demand scenario: More projects are approved or scope increases.
• Constrained scenario: Capacity falls because of hiring delays, leave, or competing priorities.

Comparing these scenarios helps leaders understand which resource decisions remain viable under changing conditions.

9. Rolling-wave forecasting

Rolling-wave forecasting uses different levels of detail depending on how far into the future the team is looking. Near-term work is forecast in detail because there is more certainty, while longer-term demand stays at a higher level until more information becomes available.

For example, a team may forecast the next four weeks by named role and estimated hours, the following quarter by team capacity, and later periods by broad demand ranges.

This method works well in environments where priorities and project requirements change frequently because the forecast becomes progressively more detailed as work approaches.

Resource forecasting example

Consider a product team planning an eight-week feature release. The work requires input from product management, design, frontend and backend engineering, QA, and technical documentation.

Example scenario

The team expects the release to move through planning, design, development, testing, and launch preparation over eight weeks.

Estimate resource demand

For each role, the team estimates how much effort will be needed during the release window.

• Product manager: 60 hours
• Product designer: 80 hours
• Frontend engineer: 140 hours
• Backend engineer: 160 hours
• QA engineer: 100 hours
• Technical writer: 40 hours

Compare demand with availability

The next step is to compare required effort with the capacity actually available.

Make a resource decision

The forecast shows two clear gaps: design and QA.

The team could respond by reducing design scope, moving part of the release timeline, shifting work to another available contributor, or bringing in temporary QA support. The forecast gives the team enough visibility to make that decision before the shortage affects delivery.

Common resource forecasting challenges

Resource forecasts become less reliable when the underlying project or capacity data changes faster than teams can update it. Four challenges tend to have the biggest impact.

1. Limited visibility into future work

If upcoming projects, probable initiatives, or pipeline demand are missing from the forecast, teams can underestimate future resource needs and commit capacity too early.

2. Changing scope and priorities

Scope changes, shifting deadlines, and reprioritized projects can quickly alter resource demand. Forecasts need regular updates to stay aligned with the work that is actually moving forward.

3. Inaccurate capacity and effort data

Outdated availability, unrealistic effort estimates, and untracked operational work can make teams appear to have more capacity than they really do.

4. Shared resources across multiple projects

Specialists and high-demand contributors are often assigned across several initiatives. Without visibility across those commitments, resource conflicts can remain hidden until schedules begin to overlap.

How to measure resource forecast accuracy

Forecast accuracy shows whether the assumptions behind resource planning are holding up once projects move into execution. Teams can compare forecasted figures with actual outcomes and use the differences to improve future estimates.

Useful measures include:

• Forecasted effort vs. actual effort: Compare estimated hours, days, or FTE requirements with the effort actually used.
• Forecasted demand vs. actual demand: Track whether expected project and portfolio demand materialized at the level anticipated.
• Forecasted availability vs. actual availability: Compare expected team capacity with the capacity that was actually available after leave, operational work, and changing assignments.
• Capacity variance: Measure the difference between the capacity predicted for a period and the capacity ultimately required.
• Resource conflict frequency: Track how often overlapping assignments or shortages require projects to be rescheduled or resources to be reassigned.
• Unplanned staffing needs: Monitor unexpected hiring or contractor requests that arise because the forecast underestimated demand or specialist requirements.
• Resource-related project delays: Review how often delivery dates move because required people or skills were unavailable.

Teams do not need to track every metric. The most useful measures are the ones tied to the decisions the resource forecast is meant to support, whether that is project scheduling, capacity planning, hiring, or portfolio prioritization.

How project management software supports resource forecasting

Project management software can make resource forecasting more reliable by keeping project demand, assignments, timelines, and delivery data in one place. The goal is to reduce manual guesswork and give teams a clearer view of upcoming work and available capacity.

Useful capabilities include:

• Visibility across active and upcoming projects: Helps teams understand where future demand is coming from.
• Project intake and prioritization: Makes it easier to capture proposed work and distinguish high-priority initiatives from lower-confidence demand.
• Project phases, tasks, and estimates: Provides the detail needed to estimate when different roles and skills will be required.
• Ownership and assignment tracking: Shows who is already committed and where workload conflicts may emerge.
• Timelines and dependencies: Helps teams identify overlapping work, sequencing constraints, and periods of concentrated demand.
• Custom fields for roles, skills, and confidence levels: Allows teams to structure forecasting data around the way they plan resources.
• Workload and capacity visibility: Supports comparisons between planned demand and available team capacity.
• Historical project data: Gives teams a reference point for improving future effort and resource estimates.
• Dashboards and reporting: Makes capacity gaps, workload patterns, and project demand easier to review across teams.
• Scenario planning: Helps teams compare the impact of changes in scope, timing, priorities, or staffing.
• Integrations with HR, time-tracking, CRM, or financial systems: Bring relevant staffing, demand, effort, and budget data into the forecasting process.

The most useful setup is one where project information stays current enough to support resource planning and forecasting without creating a separate manual reporting process.

Final thoughts

Resource forecasting gives teams a clearer view of whether upcoming work matches the people, skills, and capacity available to deliver it. That visibility helps project managers make better decisions about timelines, staffing, priorities, and sequencing before resource constraints affect execution.

The strongest forecasts stay practical. They use current project data, account for uncertainty, compare demand with real capacity, and improve over time as teams learn from actual delivery. When resource forecasting becomes part of regular project planning, teams can respond to changes earlier and plan future work with greater confidence.

Frequently asked questions

Q1. What are the 7 steps of forecasting?

A practical forecasting process typically includes:

1. Define the forecasting period.
2. Review current and expected demand.
3. Gather historical and current data.
4. Estimate future requirements.
5. Compare demand with available capacity.
6. Test different scenarios and assumptions.
7. Review actual outcomes and update the forecast.

The exact process can vary depending on whether the forecast is focused on resources, budgets, demand, or project delivery.

Q2. What are the 7 basic resources in management?

Seven commonly managed resource categories are:

1. People
2. Time
3. Budget
4. Skills and expertise
5. Equipment
6. Materials
7. Technology and infrastructure

The mix varies by project. Software teams may focus more heavily on people, skills, time, and technical infrastructure, while construction or manufacturing projects may place greater emphasis on equipment and materials.

Q3. What are the types of resource planning?

Common types of resource planning include workforce planning, capacity planning, project resource planning, resource allocation, resource scheduling, skills planning, and financial resource planning. Teams often use several of these together depending on the scale and complexity of their projects.

Q4. What are resource management tools?

Resource management tools are software platforms that help teams plan, allocate, schedule, and monitor resources across projects. Typical capabilities include workload visibility, capacity planning, assignment tracking, project scheduling, time tracking, skills management, dashboards, and reporting.

Q5. What are the five forecasting methods?

Five widely used forecasting methods are expert judgment, historical or analogous forecasting, bottom-up forecasting, top-down forecasting, and trend-based forecasting. Teams may also use scenario-based, skills-based, capacity-versus-demand, or rolling-wave forecasting when planning across multiple projects or longer time horizons.