Meet Monica, who runs operations at a services firm. Arjun leads an analyst team and Sara leads support. They're fictional, but their problems will feel familiar. We'll follow Monica as she builds her first plan, and we'll see what Arjun and Sara do with it.
What is workforce capacity planning?
Workforce capacity planning is the practice of working out how much work your people can do, then comparing that with the work you expect. The aim is to find shortages and spare time early, before deadlines slip or people burn out. It is a numbers exercise, not a hiring plan.
Three terms get mixed up, so here is how they differ.
Workforce planninglooks at the long view.
- Which roles you'll need over years
- Hiring and pay
Capacity planninglooks at hours against demand.
- Hours people can deliver
- Work expected in coming weeks or months
Resource planningassigns names to work.
- Which person takes which task
Capacity planning comes first and sets the limit. Resource planning then fills that limit with names. For the long view, read our post on workforce planning. At a services firm, hours are the product, so a gap in capacity shows up as late work.
Monica's firm wins several projects in one week. She's pleased, then her director asks whether the team can take them all. She has a feeling and nothing to show for it.
In short: capacity planning replaces a gut feeling with a comparison you can show.
What are the seven steps of a capacity plan?
Monica's first attempt covers every team at once, and the sheet collapses under missing data. She starts again with a single team and a single quarter. That small scope is the first step, and it turns the plan into something she can finish.
A capacity plan is a loop, not a one-off report. Do the seven steps in order the first time, from scope to review. After that, most of the work is refreshing two of them, current capacity and expected demand, so each round goes faster.
Swipe sideways for full table
Step | The question | What you produce |
|---|---|---|
1. Set the scope | Which teams, and which period? | A clear boundary |
2. Measure capacity | How many hours can they deliver? | Available hours per team |
3. Forecast demand | How much work is coming? | Demand in hours |
4. Find the gap | Is capacity above or below demand? | A gap in hours |
5. Check skills | Do we have the right skills? | A skills view |
6. Choose actions | How do we close the gap? | A short plan |
7. Review | What changed since last time? | An updated plan |
In short: start with one team, then repeat the loop with the same layout.
What is the formula for workforce capacity?
Usable capacity is the hours your people can really give to planned work, and it is usually lower than the hours on the contract. Compare it with demand to get the gap. A negative gap is a shortage, and a positive gap is spare time you can use.
Swipe sideways for full table
Measure | How to work it out | Made-up example |
|---|---|---|
Available hours | People × contracted hours, minus time off | 10 × 160 = 1,600, minus 120 = 1,480 |
Usable capacity | Available hours × planned load share | 1,480 × 0.8 = 1,184 |
Capacity gap | Usable capacity minus demand | 1,184 minus 1,300 = 116 hours short |
Capacity used | Demand ÷ usable capacity | 1,300 ÷ 1,184, about 110% |
These numbers are made up to show the arithmetic. They are not a benchmark. The planned load share of 0.8 is your own choice, and you should set it from your team's history.
Vacation is only one kind of time off. Holidays, sick days and training also come out of contracted hours, so counting every contracted hour overstates what a team can give.
Arjun's team looks fully staffed on paper, so he plans work to every contracted hour. Then leave, a training week and a long block of meetings come out. His team is a person short, and he finds out in the last week.
In short: your first number is usable hours, not headcount, and you should be able to defend the load share you pick.
How do you forecast the work that is coming?
Forecast demand in hours of work, not in numbers of projects, because one project can be large and another small. Your own history is the best starting point, and each estimate should carry a note on what it assumes. Refresh it every month so the plan keeps pace with the work.
Past hours
Hours spent on similar work in earlier periods.
Signed work
Work already agreed, counted in full.
Likely work
Pipeline work, counted at a lower weight.
Seasons
Busy and quiet months you already know about.
Events
Launches, audits, year end and policy changes.
Margin
A little room for work nobody has asked for yet.
Sara's team always gets a rush in March. Last year's hours show it clearly, but nobody put it in the plan, so the rush arrives as a surprise again.
In short: your own history is the cheapest forecast you have, so use it before you guess.
Where are the skill gaps hiding?
Free hours can hide a shortage, because a free person isn't always the right person. Build a simple skills grid, with people down the side and skills across the top, and rate each person. Then list what the demand needs. The empty cells show where hours exist but the skill doesn't.
Arjun has analysts with free time, but the new work needs data engineering, and none of them has it. On paper his team can take the project. In practice it can't.
The same report says workers can expect 39% of their existing skill sets to be transformed or become outdated over 2025 to 2030. Its 63% figure comes from a survey of employers, not a count of unfilled roles.
In short: count skills as well as hours, or the plan will say yes to work nobody can do.
How do you close a capacity gap?
Match the fix to how long the gap lasts and how fast you need it. Training and hiring take months, borrowing is quick, and automation pays off when work repeats. Moving a deadline is also a real choice, if the customer agrees.
Swipe sideways for full table
Option | It fits when | Watch for |
|---|---|---|
Buy (hire) | The gap is long term | Slow to start |
Build (train) | The skill is close to what people have | Time off the work while learning |
Borrow (contractors) | The gap is short or urgent | Cost and handover time |
Bot (automate) | The same work repeats | Setup time |
Move the work | A deadline can slide | Customer trust |
Buy, build, borrow and bot are common labels for the first four rows. AIHR's capacity planning guide also names three timing styles. A lead strategy builds capacity before demand arrives. A lag strategy waits until demand is clear. A match strategy adjusts in near-real time.
Monica has a gap that lasts a few months. She picks a contractor for the short stretch and opens a hire for the longer gap. Arjun's team grumbles, because the contractor needs weeks of handover before being useful.
In short: a gap that ends within a quarter calls for a borrowed hand, and a gap that stays calls for a hire.
How does capacity planning work for a call center?
A call center plans in contacts and handle time rather than projects. Workload is expected contacts times average handle time (AHT), the minutes spent on each contact. Then add agents to cover shrinkage, the share of paid time agents can't take contacts.
Sara's plan counted the agents on the payroll. Every Monday morning the queue grew, because some of those agents were in training, on leave or in a team meeting.
Swipe sideways for full table
Step | Made-up example |
|---|---|
Expected contacts in a week | 6,000 |
Average handle time | 8 minutes |
Workload hours | 6,000 × 8 ÷ 60 = 800 |
Hours per agent per week on the phones | 40 |
Agents needed on the phones | 800 ÷ 40 = 20 |
Shrinkage rate | 0.25 |
Agents to schedule | 20 ÷ (1 minus 0.25), about 27 |
This is a simple estimate. Real schedules also need demand by time of day and a service level target, so treat it as a starting point.
In short: plan for the people on the phones, not the people on the payroll.
Which capacity planning tools do you need?
You need three kinds of data: actual hours, planned absence and a comparison of plan with actual. A spreadsheet covers all three for one team, so start with a capacity planning template, then choose software for the question the sheet can't answer.
Swipe sideways for full table
Column | What to enter | Why it matters |
|---|---|---|
Team | Team name | Who the row is about |
People | Headcount | The starting point |
Contracted hours | Hours per person in the period | Gross capacity |
Time off | Leave, holidays, training | Reduces capacity |
Available hours | Contracted hours minus time off | What you can plan with |
Planned load share | Your chosen share, such as 0.8 | Room for surprises |
Demand | Forecast hours | What is needed |
Gap | Spare or missing hours | The decision number |
A matching Excel workbook goes with this guide. It has a capacity sheet with these columns, a call center sheet and a skills grid, all with made-up numbers for you to replace.
Capacity planning template
The Excel workbook that goes with this guide: a capacity sheet, a call center sheet and a skills grid, with formulas and made-up numbers. In this preview the file isn't attached. It sits next to the draft as capacity-planning-template.xlsx.
We360.ai is our product, and its capacity planning module belongs in the software group. Plans differ, so check with your account manager which one includes it.
What it showsin the capacity planning module.
- How work is spread across people and teams
- How busy teams are across time periods
- Planned versus actual workload
Where it fitsin your setup.
- Part of the Advanced Analytics plan
- Leaves keep an auditable trail of planned absences
- Attendance shows presence, hours and breaks
What the docs don't describeso plan it elsewhere.
- Demand forecasting
- Skills grids
- Call center interval schedules
The We360.ai docs describe the module, and the leaves page covers time off. Our capacity planning software page gives the overview. The privacy page says individual typed characters are never recorded and webcam feeds are never accessed.
We360.ai helps us track team activity, working hours, and productivity without interrupting daily work.
Monica builds the sheet with her own team's numbers and shares it with her leads. One lead copies last quarter's demand by mistake, and the gap looks fine until Sara spots it.
In short: build the layout first, then pick the tool that answers the question the sheet can't.
How do you tell if the plan is working?
A working plan predicts well and leaves people room to breathe. Monitor a few numbers you can explain in a sentence, review them on a set cadence, and read each one against the team's own history. We couldn't verify a standard target for any of them, so treat published percentages with care.
Swipe sideways for full table
Measure | What it tells you | Read it with care |
|---|---|---|
Forecast accuracy | How close expected hours came to actual hours | One odd month isn't a trend |
Capacity used | The share of usable capacity that demand takes up | Near the top leaves no slack |
Overtime | Hours worked beyond the contract | Steady overtime means the plan is short and burnout is closer |
Backlog | Work waiting to start | It can reflect priorities, not capacity |
Five mistakes make a plan look better than it is.
- Planning to every contracted hour, as if nobody takes leave
- Forecasting once a year, when demand moves monthly
- Counting hours without counting skills
- Using one load share for every team
- Keeping the plan private, so nobody can correct it
Arjun updated his plan in January and never touched it again. In the busiest month, several people are on leave at once, and the sheet still shows a full team. Monica finds the update date is months old.
In short: a plan with no update date is a guess, however good the formula looks.
FAQ
What is capacity planning? +−
Capacity planning compares how much work a team can do with how much work is coming, then closes any gap. For people, it counts usable hours and skills. Servers and software have their own version, which compares supply with expected load. This guide covers people.
How is resource capacity planning different from resource planning? +−
Resource capacity planning checks whether your people and tools can supply the hours the work needs. Resource planning assigns named people to named tasks. Capacity comes first and sets the limit. Publishers often use the terms interchangeably, so check which one a template means.
What is IT capacity planning? +−
IT capacity planning usually means sizing servers, storage and networks so systems can handle expected load. People capacity uses hours and skills instead. The method is the same: compare what you can supply with what you expect to need, then act on the gap before users feel it.
What is capacity planning in project management or agile? +−
It estimates how much work a team can take on in a period, such as a sprint. Count team members and working days, subtract leave and meetings, and compare the result with the planned work. If the work doesn't fit, move some of it or add help.
What is the best capacity planning software? +−
The best one answers your next question. Check that it shows actual hours, planned leave and a plan-versus-actual view, and ask for a trial with one team. We360.ai's module sits on the Advanced Analytics plan, so confirm what your plan includes.
How often should you update a capacity plan? +−
Monthly for most teams, and weekly when demand changes fast. That is our recommendation, not a verified standard. Review the whole plan each quarter, and update sooner when you win large work or lose a team member. Write down what changed each time.
Is there a free workforce capacity planning Excel template? +−
Yes. The workbook that goes with this guide has formulas ready for capacity, call center staffing and skill gaps. The eight columns in the tools section also work in any spreadsheet. Replace the made-up numbers with your own.
Related Guides

Bench time is the paid period between client projects when an employee has no billable assignment. It costs staffing and IT services firms revenue, and it worries the people waiting for work. This guide covers the formula, a sourced benchmark, US pay rules and fair ways to cut it.
