Resource Forecasting for Professional Services: A Practical Guide

Resource forecasting is the practice of estimating how much work your team will need to deliver over a coming period and how much capacity you will have to deliver it. In a professional-services firm, that means comparing the hours your confirmed projects and likely new deals will require with the hours your people will be available, role by role. Done well, it shows shortfalls and spare capacity weeks before they become missed deadlines or idle consultants. This guide covers the key formulas, a nine-step forecasting process, the main methods, and a worked example with gaps by role.

What Is Resource Forecasting?

Resource forecasting estimates future resource demand and available supply over a defined period. For services firms, the resource is mostly people’s time, broken down by role or skill. The output is a view of where demand will exceed capacity, where capacity will sit unused, and when.

Resource Forecasting vs Planning, Allocation, Utilization, and Capacity Planning

These terms are often used interchangeably, but each answers a different question.

Term	Question it answers	Typical output
Resource forecasting	How much demand and supply will we have over the next period?	Demand and capacity by role and week, with gaps
Resource planning	What resources will we need, and how will we organize them?	Staffing plan, hiring or contracting decisions
Resource allocation	Who works on what, and when?	Assignments of people to projects and tasks
Resource utilization	How was available capacity used?	Utilization rates, usually measured after the fact
Capacity planning	Can our productive capacity meet expected demand?	Go or no-go decisions on work, staffing changes

Forecasting feeds planning, planning shapes allocation, and utilization measures the result. Capacity planning for project teams uses the forecast to decide what to do about the gaps.

Why Professional-Services Firms Need Resource Forecasting

A services firm sells time. When demand outruns capacity, projects slip, people burn out, and the firm turns down or delays work it could have won. If capacity outruns demand instead, billable people sit on the bench and margins fall.

Forecasting matters more as a firm grows. In a 20-person team, the founder can keep everyone’s workload in their head. Past 50 people, with several projects starting and ending each month, that mental model breaks down, a pattern described in what breaks when a services firm crosses 50 employees.

The Two Sides of a Forecast: Supply and Demand

Supply: Available Capacity

Supply starts with scheduled working hours and subtracts the time people will not be available: public holidays, approved leave, and other known absences. From what remains, some time goes to internal work such as training, pre-sales, and management. Only the rest is available for billable delivery.

Forecast supply by role or skill, because a surplus of testers does not cover a shortage of senior developers.

Demand: Confirmed and Pipeline Work

Demand comes from two sources, and they must stay separate:

• Confirmed demand: hours required by signed projects, based on their plans and remaining estimates.
• Pipeline demand: hours that likely new projects would require if they close.

Pipeline demand can be shown in two ways. Probability-weighted demand multiplies each deal’s hours by its estimated chance of closing. Maximum pipeline demand assumes every deal closes. Counting full pipeline hours as if they were confirmed overstates demand and can lead to hiring for work that never arrives.

A Nine-Step Resource Forecasting Process

1. Choose the horizon and intervals: Most services firms forecast one to three months ahead in weekly intervals, with a rougher quarterly view for hiring. The assumption: estimates beyond the horizon are too uncertain to act on.
2. Calculate available capacity by person, role, or skill: Start from scheduled hours for each person and group them by role.
3. Record confirmed project demand: Use each project’s remaining planned hours by role and week. The assumption: project plans and time estimates are current.
4. Estimate pipeline demand with stated assumptions: For each likely deal, record hours by role, expected start date, and probability of closing. Write the probabilities down so others can challenge them.
5. Account for holidays, leave, and internal work: Subtract public holidays and approved leave, then apply a billable share for internal responsibilities.
6. Compare capacity with demand: Calculate the gap for each role and period under each demand scenario.
7. Identify bottlenecks: Look for roles, skills, locations, or weeks where the gap is negative.
8. Model your options: Test responses: reschedule a start date, move people between projects, use contractors, or hire.
9. Review forecast error and update assumptions: Compare last period’s forecast with what happened, and adjust estimates, probabilities, and billable shares.

Resource Forecasting Formulas

These four calculations cover most forecasting needs.

Measure	Formula
Available working hours	Scheduled working hours − holidays − approved leave − other unavailable time
Billable capacity	Available working hours × expected billable share
Capacity gap	Billable capacity − forecast billable demand
Forecast utilization	Forecast billable demand ÷ available working hours × 100

A positive capacity gap means spare billable capacity. Negative gaps mean a shortfall: the work will not get done on time unless you change something. Calculate the gap separately for confirmed, expected, and maximum demand so decision-makers can see the range.

Worked Example: A Four-Week Forecast for an IT Consultancy

The following example is hypothetical. A 60-person IT consultancy forecasts the next four weeks (20 working days at 8 hours a day) for three delivery roles. There is one public holiday in the period, and several people have approved leave.

Step 1: Available capacity by role

Role	People	Scheduled hours	Holiday hours	Approved leave hours	Available hours	Billable share	Billable capacity
Senior developer	4	640	32	48	560	80%	448
Developer	8	1,280	64	96	1,120	85%	952
QA engineer	3	480	24	16	440	85%	374

Senior developers have a lower billable share because they also mentor and support pre-sales.

Step 2: Demand by role (hours)

Source	Senior developer	Developer	QA engineer
Project A: client portal build (confirmed)	220	520	160
Project B: support retainer (confirmed)	60	200	80
Project C: data migration (confirmed)	120	160	60
Confirmed demand	400	880	300
Deal D: mobile app, full hours (70% likely)	80	160	40
Deal E: API integration, full hours (40% likely)	60	120	30
Probability-weighted pipeline	80	160	40
Maximum pipeline	140	280	70

Weighted pipeline for senior developers is 80 × 0.7 + 60 × 0.4 = 80 hours.

Step 3: Capacity gap by scenario

Role	Billable capacity	Gap: confirmed only	Gap: expected (confirmed + weighted)	Gap: maximum (confirmed + all pipeline)
Senior developer	448	+48	−32	−92
Developer	952	+72	−88	−208
QA engineer	374	+74	+34	+4

What the forecast says: On confirmed work alone, every role has spare capacity. Once likely deals are included, developers fall 88 hours short and senior developers 32 hours short, while QA keeps 34 hours to spare. Forecast utilization of available hours for developers rises from 78.6% on confirmed work to 92.9% in the expected case, above their planned billable share of 85%.

Recommended response: Ask the account owner to confirm Deal D’s start date before committing.

If it closes on schedule, bring in a contract developer for roughly 90 hours, a little over two weeks of full-time work. Reduce senior developers’ internal work for the period, and use the QA surplus to start test preparation on Project C early. Leave approved leave untouched; canceling it to close a forecast gap trades a short-term fix for a retention problem.

Resource Forecasting Methods and When to Use Them

Method	How it works	Best for
Bottom-up project estimation	Sum remaining task estimates from each project plan	Confirmed work with detailed plans
Role-based capacity forecasting	Forecast supply and demand by role instead of by person	Firms with interchangeable people within roles
Pipeline-based demand	Add likely deals using probability weights	Firms with a visible sales pipeline
Historical workload analysis	Use past hours by client, project type, or season	Recurring work such as retainers and support
Scenario planning	Compare confirmed, expected, and maximum demand	Decisions about hiring or contracting
Rolling forecasts	Re-forecast on a fixed cadence and extend the horizon each time	Any firm; keeps the forecast current

Most firms combine methods: bottom-up estimates for confirmed work, pipeline weighting for new work, and a rolling cadence to keep both current. Statistical forecasting models rarely add much for a 25 to 150-person firm, since the inputs (project plans and deal probabilities) carry more uncertainty than the method.

Spreadsheets vs Software for Resource Forecasting

A spreadsheet works when a few people own the forecast and projects change slowly. Its limits show as the firm grows: availability, leave, and project hours live in different files, someone has to re-key them each week, and the forecast goes stale between updates.

Software helps most when it keeps the inputs current: planned hours per project, assignments, approved leave, and actual time logged. Whichever you use, the forecasting judgment, especially pipeline probabilities and the response to gaps, still belongs to managers.

Metrics to Monitor

Utilization appears in several forms, and mixing them causes confusion.

Metric	Definition	Use
Historical utilization	Hours worked on billable work ÷ available hours, for a past period	What happened in practice
Planned utilization	Hours assigned ÷ available hours, for a future period	What current assignments imply
Forecast utilization	Forecast demand (including pipeline) ÷ available hours	What the forecast implies
Billable utilization	Billable hours ÷ available hours	How much capacity earns revenue
Capacity gap by role	Billable capacity − forecast demand	Where action is needed
Forecast error	Forecast demand − actual hours, by role	How reliable the forecast is

No published utilization benchmark is a universal target. A healthy level depends on role, seniority, internal responsibilities, and the firm’s model, so compare your own trends over time.

How Often to Review the Forecast

Update the near-term view weekly, when timesheets and leave approvals are fresh. Review the 1 to 3 month view monthly with delivery leads and the account owners who manage the pipeline. Revisit the quarterly view when making hiring decisions. After each period, compare forecast with actual hours and record the main causes of error.

Common Resource Forecasting Mistakes

• Treating pipeline hours as confirmed: Leads to over-hiring or false alarms.
• Forecasting by headcount instead of role: Spare testers do not cover a shortage of architects.
• Ignoring leave and holidays: Overstates capacity, often in the busiest months.
• Assuming 100% billable time: Everyone has internal work; plan for it explicitly.
• Using outdated project estimates: Forecasts inherit the errors in the plans they use.
• Never checking forecast accuracy: Without error tracking, the same mistakes repeat.

How Juntrax Supports Resource Planning Workflows

Juntrax does not generate forecasts automatically. It keeps the operational records a forecast depends on in one place, so managers can run the calculations above on current data.

In Juntrax PSA, projects carry planned hours, and work is broken into tasks that can be grouped into named task sets in a task-planning view, with a counter showing project hours not yet allocated to anyone.

Team members are assigned to projects, and pay rates and bill rates can be managed for each person. Employees log time against projects in timesheets, and leave requests and approvals are recorded in Juntrax HRMS. Project financial dashboards show margin calculated from timesheets, purchase orders, and invoices. Juntrax works alongside your existing accounting system.

Turning the Forecast Into Staffing Decisions

Resource forecasting does not need complex models. Calculate available capacity by role after holidays, leave, and internal work. Separate confirmed demand from pipeline demand, show the gap under each scenario, and decide in advance how you will respond to a shortfall.

Review the forecast on a fixed cadence and learn from its errors. Done consistently, this moves staffing decisions earlier, while there is still time to act on them.

Frequently Asked Questions

What Is Resource Forecasting in Project Management?

It is estimating how many hours, by role or skill, upcoming project work will require, and comparing that with the hours your team will have available.

What Is the Difference Between Resource Forecasting and Resource Allocation?

Forecasting estimates future demand and supply in aggregate. Allocation assigns specific people to specific projects and tasks.

How Do You Calculate Available Capacity?

Subtract holidays, approved leave, and other unavailable time from scheduled working hours. Multiply the result by the expected billable share to get billable capacity.

How Far Ahead Should a Services Firm Forecast Resources?

Most firms forecast one to three months ahead in weekly intervals, with a rougher quarterly view to guide hiring.

How Should Sales Pipeline Be Included in a Resource Forecast?

Weight each likely deal’s hours by its probability of closing, and show confirmed, probability-weighted, and maximum demand separately.

What Is a Good Utilization Rate for Professional Services?

There is no universal figure. It depends on role, seniority, and internal responsibilities, so set targets by role and track your own trend.