Capacity planning is the process of checking whether you have enough capacity (people's hours, equipment, or bookable appointment time) to meet forecast demand over a set period, then adjusting capacity or demand to close any gap. The term covers four different disciplines: project resourcing, workforce shift planning, production planning and scheduling capacity. Each has its own tools, metrics, and buyer.
Most published guides cover only the first one: resource management software for agencies and professional services firms. That is a real discipline with a mature tool market, and this guide covers it. But it is not what a sales leader means when they ask whether the team has capacity for next quarter's demos, or what a clinic manager means when patients can't get an appointment for two weeks.
This guide defines the term, explains the three classic strategies, sets out the process all four types share, then takes each type in turn with the tools and use cases that belong to it.
Capacity planning answers two questions: how much work is coming, and how much can we absorb? The gap between those numbers is the planning problem, and you can close it from either side: add capacity, or shape demand.
What makes the term confusing is that "capacity" means something different depending on what you produce.
|
Type |
What is being matched |
Who owns it |
Typical tools |
Planning horizon |
|
Project and resource |
People's available hours against project demand |
Resource managers, PMOs, agency ops |
Float, Resource Guru, Runn, Productive, Kantata |
Weeks |
|
Workforce and shift |
Staff on shift against forecast arrival volume |
Contact center and operations managers |
Workforce management systems |
Days |
|
Production |
Machine and plant hours against production orders |
Manufacturing planners |
ERP and MRP systems |
Months |
|
Scheduling (appointment) |
Bookable appointment slots against booking demand |
Sales, clinical, advisory and customer success leaders |
Scheduling platforms with capacity reporting (e.g., OnceHub Capacity Planning report) |
Days to hours |
Two things follow from that table. The tools do not substitute for one another, and most "best capacity planning software" lists cover row one only.
Every type of capacity planning uses one of three strategies, which differ in when you add capacity.
Lead strategy: add capacity before demand arrives. Simpplr describes lead as increasing capacity before the demand arises, with the risk of overcapacity if demand doesn't materialize. In scheduling, that means opening extra demo slots or adding hosts before a campaign launches.
Lag strategy: add capacity after demand is confirmed. It avoids paying for capacity you don't need, but it can delay meeting demand. In scheduling, that means adding a host only after the Capacity Planning report shows the same hours under capacity for several weeks.
Match strategy: add capacity in small steps that track demand. It sits between lead and lag, and it needs frequent monitoring. In scheduling, that means reviewing availability weekly against the report and adjusting in small steps.
Capacity planning also happens at three levels, as Apptio frames them: strategic (years), tactical (months to a year) and operational (day to day).
All four types run the same four steps. The inputs differ; the sequence does not.
1. Forecast demand. What volume of work, tickets, orders or bookings is coming, over what horizon? The most reliable input is your own history for the equivalent period, such as last quarter, the same month last year or the same day last week, adjusted for anything you know has changed.
2. Measure real capacity, not theoretical capacity. A 40-hour week is not 40 billable hours, and eight open calendar hours are not eight bookable appointment slots once buffers, existing meetings and admin are subtracted. This step is where many plans go wrong, because the theoretical number is the easy one to get.
For appointment capacity, use this formula:
Bookable slots = (open hours − existing meetings − admin) ÷ (meeting length + buffer)
Example: 8 open hours with 1.5 hours already booked leaves 390 minutes. At 30-minute meetings plus a 15-minute buffer, that is 8 bookable slots, not 16.
3. Find the gap, in both directions. Under-capacity is the obvious failure: more demand than you can serve, so work is turned away, queued or delivered late. Over-capacity is the quieter one: capacity sitting idle that you pay for in salary or in opportunity cost. Both are worth catching.
4. Adjust, then re-measure. Add or reduce capacity, or shape demand to fit. The levers differ by type:
Then measure again, because a plan that is never checked against what actually happened is a forecast, not a planning process.
The horizon matters as much as the method. Production planning works in months, project resourcing in weeks, shift planning in days, and scheduling capacity in days or hours. Match your review cadence to your horizon: a quarterly review of a weekly constraint tells you about problems you have already lived through.
The question: can we staff the work we have committed to, and can we take on what is in the pipeline?
This is the meaning most published guides cover, and it has a mature tool market. The unit is a person's available hours; the demand is project work; and the job is matching people with the right skills to the right work without overloading anyone.
Tools. Resource Guru puts people, meeting rooms and equipment on one shared schedule, with clash management that prevents double-bookings and a waiting list for work that doesn't fit yet.
Float leans toward visual scheduling for larger teams across offices and skill sets, with a strong link between capacity and project financials. Runn focuses on forecasting, plotting scheduled work against available hours weeks ahead so you can check whether the next project is staffable before agreeing to it.
Larger services firms tend toward Kantata, Productive or Saviom, where capacity sits alongside budgets and margin.
Price. Resource Guru starts at $4.16 per person per month (billed annually), Float at $7, and Runn at $7 per resource seat with a 20-seat minimum (vendor pricing pages, October 2026). Enterprise portfolio platforms are quoted on request.
Use cases. Deciding whether to accept a new client engagement. Spotting that three of four team members are maxed out before committing to a deadline. Planning hiring against a pipeline rather than against last month's rush. Identifying underutilized staff whose time is billable but unsold.
|
Tool |
Capacity type |
Best for |
Starting price |
Free trial |
|
Resource Guru |
Project and resource |
Small teams scheduling people, rooms and equipment |
4.16/person/monthbilledannually(5 monthly) |
30 days, no credit card |
|
Float |
Project and resource |
Visual scheduling across teams and offices |
7/person/monthbilledannually(8 monthly) |
30 days |
|
Runn |
Project and resource |
Forecasting whether upcoming work is staffable |
$7/resource seat/month (Lite), 20-seat minimum |
See runn.io/pricing |
|
OnceHub |
Scheduling (appointment) |
Teams booking meetings through shared Booking Calendars |
10/seat/monthbilledannually(12 monthly), Schedule plan |
14-day Engage trial, no credit card |
Prices from each vendor's pricing page, October 2026. Prices change often; check before you buy.
The question: how many people do we need on shift, at what times, to meet arriving demand?
The unit here is a staffed hour, and demand arrives rather than being committed in advance: calls, tickets, patients, customers. It is the most statistically driven of the four, because arrival patterns are forecastable from history and the cost of getting it wrong shows up immediately as queue time or idle staff.
Tools. Workforce management platforms, which combine demand forecasting, shift scheduling, intraday adjustment and adherence tracking. Contact centers and healthcare operations are the heaviest users; retail and hospitality run lighter versions of the same thing.
Use cases. Rostering a support team against predicted ticket volume. Re-forecasting during the day when call volume spikes. Holiday and seasonal coverage planning. Calculating how many agents a service level target actually requires.
The question: can the plant produce the order book in the time available?
The oldest version of the discipline, and the most formalized. The unit is machine or line hours, constrained by equipment, materials and labor. Rough-cut capacity planning checks feasibility at a high level; capacity requirements planning works it out in detail against the production schedule.
Tools. ERP and MRP systems, where capacity planning is a module rather than a standalone product, because it has to sit on the same data as inventory, purchasing and the production schedule.
Use cases. Committing to a delivery date. Deciding whether to add a shift or outsource an order. Planning maintenance downtime without breaking the schedule. Sizing a capital investment against forecast demand.
The most direct way to plan appointment capacity is to measure utilization per bookable time slot, compare it with past booking demand for the same hours, and adjust availability or host limits where the two diverge.
OnceHub's Capacity Planning report does this for any Booking Calendar. It shows hourly utilization for the coming week and daily utilization for the coming month, and flags each block red (under capacity) or blue (over capacity) when past demand was at least 20% above or below current capacity.
It's the type most capacity planning guides skip, and the one sales, healthcare, advisory and customer success teams run into every week. The unit is a bookable appointment slot, demand is inbound booking requests, and the failure modes are specific:
Signs you need more appointment capacity:
Signs you're offering too much:
Both are correctable, but only if you can see slot-level utilization rather than a monthly booking total.
OnceHub includes a Capacity Planning report built for appointment capacity. Find it under Analytics → Capacity Planning. It's included on OnceHub's paid plans from Schedule upward, not on the free Basic plan.
Example: in the comparison period, with five reps on the demo calendar, the Tuesday 10 to 11am block took 13 meetings. Two reps have since moved teams, so that block now offers 10 slots. Past demand is 30% above current capacity, so the block shows red. Meanwhile, Friday 4 to 5pm offers 8 slots but took only 3 meetings. It shows blue, so that time can go back to focus work.
The adjustment happens on the Booking Calendar itself. Once the report shows a gap, change the Booking Calendar's availability, buffers and start times, and its workload limits: the maximum meetings each host can take per day, week and month, where the strictest limit applies. For group or concurrent sessions, set the maximum bookings per time slot. Workload limits apply to hosts, not co-hosts.
One caveat, because OnceHub states it in its own documentation: the figure is an estimate of available capacity, and it can shift depending on actual booking times and calendar settings such as workload rules, start times and buffers. Treat it as a strong signal about where to look rather than an exact slot count.
See your own slot-level utilization: run OnceHub's Capacity Planning report on your Booking Calendar with a 14-day free trial.
If you want the wider measurement picture around this, our guide to the scheduling KPIs that reveal team workload covers what to track alongside utilization.
Four numbers cover most of it, across all four types.
Utilization rate. Utilization rate = capacity used ÷ capacity available × 100. For example, 8 of 10 slots booked is 80%. It's useful and routinely misread: 100% utilization is not a target, it is a system with no slack, which fails on the first disruption.
The gap, signed. Not just how far off you are, but in which direction. Under and over require opposite responses, and a single "variance" figure hides which one you have.
Forecast accuracy. How close last period's forecast was to what happened. Without this you cannot tell whether your plan is improving or you are just getting luckier.
Time to correct. How long between a gap appearing and the adjustment landing. A weekly review on a constraint that moves daily means you are always reacting to last week.
Capacity planning is one idea applied to four different units of work, which is why the term causes so much confusion. The discipline is consistent: forecast demand, measure real capacity, find the gap in both directions, adjust, re-measure.
What changes is the unit and therefore the tool. If your constraint is billable project hours, the resource management market is mature and well served. If it is staffed hours against arriving volume, that is workforce management. If it is machine time, it lives in your ERP.
And if your constraint is bookable time, whether a prospect can find a demo slot this week or a patient can get an appointment before they give up, that is appointment capacity planning, and it needs slot-level visibility rather than a monthly total. OnceHub's Capacity Planning report is built for that specific job.
It's included on paid plans from Schedule upward, and new accounts start with a 14-day trial of the Engage plan, no credit card required. That's enough time to run the report against your own Booking Calendar.
Capacity planning is the process of checking whether you have enough capacity, such as people's hours, equipment or bookable appointment time, to meet forecast demand over a set period, then adjusting capacity or demand to close any gap. It covers four disciplines: project resourcing, workforce shift planning, production planning and scheduling (appointment) capacity.
Capacity planning is classified three ways. By strategy: lead, lag and match. By time horizon: strategic, tactical and operational. By what's being planned: project and resource, workforce and shift, production, and scheduling (appointment) capacity planning. Most software sold as "capacity planning" covers project and resource planning only.
Lead, lag and match are the three classic capacity planning strategies. A lead strategy adds capacity before demand arrives, a lag strategy adds it after demand is confirmed, and a match strategy adds it in small steps that track demand. Lead risks paying for idle capacity, lag risks missing demand, and match needs frequent monitoring.
The capacity planning process has four steps, the same across every type. Forecast demand using your own history for the equivalent period. Measure real capacity rather than theoretical capacity. Identify the gap in both directions, since over-capacity costs money as well as under-capacity. Then adjust and re-measure, matching your review cadence to the horizon of what you are planning.
Capacity utilization = capacity used ÷ capacity available × 100. For appointments, that is booked slots divided by available slots: 8 of 10 slots booked is 80% utilization. Calculate available slots from real capacity: open hours minus existing meetings and admin, divided by meeting length plus buffer.
The best capacity planning tool depends on which type you mean. For project and resource planning, Resource Guru (from $4.16 per person per month billed annually), Float (from $7) and Runn (from $7 per resource seat, 20-seat minimum) are common starting points, with Kantata, Productive and Saviom for larger services firms. For scheduling capacity, OnceHub's Capacity Planning report shows slot-level utilization and compares upcoming capacity against past demand, available on paid plans from $10 per seat per month, with a 14-day free trial.
Compare slot-level utilization with past demand for the same hours. In OnceHub, red blocks in the Capacity Planning report mark hours where past demand exceeded current capacity by 20% or more. Other signs are an earliest available slot that keeps moving later and the same hours filling every week.
Look for hours that rarely fill. In OnceHub's Capacity Planning report, blue blocks mark hours where past demand was at least 20% below current capacity. Cut published availability there and give that time back to focus work.
OnceHub is built for appointment capacity planning. Its Capacity Planning report shows Booking Calendar utilization in Day and Week views, compares upcoming capacity against past demand, and flags under- and over-capacity blocks, and its workload limits let you cap meetings per host per day, week or month.
Many scheduling tools report booking volume and popular times. Capacity planning also needs utilization against available slots and a comparison with past demand, and OnceHub's Capacity Planning report provides both.
No. A system running at full utilization has no slack, so any disruption, such as an overrun, a sick day or a demand spike, immediately becomes a failure that spreads. Planners typically target a band below full utilization that leaves room to absorb disruption, and treat sustained 100% as a signal to add capacity rather than as success.
Capacity planning asks whether you have enough overall capacity for forecast demand, usually over weeks or months. Resource planning allocates specific people or assets to specific work. Capacity planning is the question; resource planning is part of the answer. Many tools do both, which is why the terms get used interchangeably in product marketing.
OnceHub (vendor-published, ours)
Capacity planning strategies and levels
Tool pricing (vendor pricing pages, October 2026)
Tool descriptions and category listings (vendor-published)
Disclosure: OnceHub publishes this guide, and its Capacity Planning report appears in it as an example tool for one of the four types described. OnceHub is a customer engagement platform that engages, screens and schedules across phone and web, with Phone Agents, chatbots, Routing Forms and a native scheduling engine. It doesn't perform project resource planning, workforce shift planning or production planning, and the guide scopes it to scheduling capacity only. Other platforms named are described from published documentation and vendor pricing pages, grouped by the type of capacity planning they address rather than ranked.