Blog
Blog Details

Capacity Planning Example for Operations

Jeremy Block
November 20, 2026
Use this capacity planning example for operations to balance workload, forecast delivery dates, protect team capacity, and make credible commitments daily.

A delivery date is only credible when the people required to deliver it are actually available. That is the purpose of a capacity planning example for operations: turn a list of projects into a clear view of what the team can complete, where the constraints are, and what must change before commitments are made.

For growing teams, the failure point is rarely a lack of effort. It is planning work against headcount instead of usable capacity. A six-person engineering team may look fully available on an org chart, while meetings, PTO, support work, and existing project commitments leave only a fraction of the week open for new delivery.

A capacity planning example for operations

Consider a B2B software company planning the next four weeks. Its product delivery group includes six engineers, two designers, and two QA specialists. Leadership wants to deliver a customer migration, a new self-service portal, and a set of maintenance improvements within the same month.

At first glance, the team has 1,600 hours available: 10 people multiplied by 40 hours per week, over four weeks. That number is not useful for decision-making. It assumes every hour is interchangeable, every person is available, and no operational work happens alongside project delivery.

The operations lead starts with role-based gross capacity, then removes known constraints. One engineer has a week of PTO. The team also reserves 15% of time for recurring meetings, reviews, coordination, and administrative work. Finally, leadership protects 10% of remaining delivery time for production issues, customer escalations, and small work that cannot be predicted at the start of the month.

| Role | Gross hours | PTO impact | After recurring work | Protected buffer | Planned project capacity | | --- | ---: | ---: | ---: | ---: | ---: | | Engineering | 960 | 40 | 782 | 78 | 704 | | Design | 320 | 0 | 272 | 27 | 245 | | QA | 320 | 0 | 272 | 27 | 245 |

This is the real planning baseline. The organization is not deciding whether it has 10 people. It is deciding how to allocate 704 engineering hours, 245 design hours, and 245 QA hours without creating a schedule that fails the first time an urgent request arrives.

Add demand by role, not just by project

Next, the project leads estimate the work required during the four-week period. Estimates do not need false precision, but they must identify the role needed to complete the work.

The customer migration requires 420 engineering hours, 80 design hours, and 100 QA hours. The self-service portal requires 250 engineering hours, 64 design hours, and 72 QA hours. Maintenance improvements require 160 engineering hours, 32 design hours, and 48 QA hours.

The total demand is 830 engineering hours, 176 design hours, and 220 QA hours. Design and QA have capacity remaining. Engineering does not. The team is short by 126 engineering hours before the month begins.

That finding changes the discussion. Without it, leaders may announce all three initiatives and ask the team to prioritize as they go. With it, they can make an intentional choice while dates, scope, and staffing are still adjustable.

What operations should do with the gap

A capacity gap is not automatically a reason to hire or reject work. It is a prompt to make the trade-off visible. In this example, the operations lead has several credible options.

The company could move part of the portal into the next planning period. It could reduce the portal's first-release scope, such as delaying a lower-value workflow. It could bring in short-term engineering support if onboarding time and coordination overhead do not outweigh the benefit. Or it could deprioritize maintenance improvements, recognizing that this may increase customer or technical risk.

Each option carries a different cost. A contractor may close the numeric gap but still slow the team if the work depends on deep product context. Reducing scope can protect the date, but only if the removed work is genuinely nonessential. Deferring maintenance may appear inexpensive until support volume rises. Capacity planning does not remove these decisions. It gives leaders the information to make them with confidence.

In this case, the company delays 80 engineering hours of portal work and moves 50 hours of maintenance work to the following month. That reduces engineering demand to 700 hours, leaving a small four-hour margin against planned capacity. The margin is narrow, but it is intentional and protected by the separate 10% operational buffer.

Schedule the work across the weeks

A monthly total can still hide a problem. If the migration requires most engineering work in the first two weeks, the team may be overbooked early even though the four-week plan appears balanced.

The operations lead therefore allocates capacity by week. Engineering has roughly 176 planned project hours per week. The migration receives 105 hours each week for the first two weeks, then 95 hours in week three and 115 hours in week four for final remediation. The portal receives a smaller, steady allocation. Maintenance is scheduled around fixed support windows instead of being treated as work the team will somehow fit in later.

This weekly view also exposes dependency risk. Design work for the portal must be ready before engineers can start certain flows. QA capacity may be available overall, but testing cannot be compressed into the last three days without creating defects or delaying release. A workable plan sequences roles around dependencies, not simply around total hours.

Use capacity as a live operating signal

The plan should not stay in a spreadsheet untouched for four weeks. Capacity changes when someone is pulled into a sales escalation, an estimate proves wrong, a customer issue becomes urgent, or a project milestone moves.

Operations leaders should review planned versus actual allocation at least weekly. If engineering has already used 55% of its migration allocation halfway through week two but delivered only 35% of the expected work, the forecast needs to change. The right response may be to adjust scope, reassign work, or move a date. Pretending the original date still holds only moves the surprise to customers and executives.

A centralized scheduling system makes this easier because the team can see availability, assignments, and conflicts in one place. With TeamBuilt, operations leaders can compare capacity by person, role, department, and project while maintaining a real-time view of the work already committed. That reduces the manual reconciliation that often makes planning data stale before a decision is made.

Avoid the common planning shortcuts

The most damaging shortcut is treating utilization as the goal. A team planned at 100% utilization has no room for urgent work, estimation error, collaboration, or normal variation in delivery. It may look efficient on a report while becoming unreliable in practice.

Another mistake is averaging capacity across roles. Spare design hours cannot complete backend development, and available QA hours cannot compensate for a missing product decision. Capacity is only useful when it reflects the skills, timing, and dependencies required by the work.

Finally, do not confuse a tentative assignment with a commitment. If a person is listed on three projects at 30% each, that allocation needs to be tested against meetings, support obligations, PTO, and the calendar. The total may fit mathematically while the daily schedule remains impossible.

Make delivery promises from capacity, not optimism

A useful capacity plan does more than identify overload. It gives operations a disciplined way to explain what the team can deliver, what it cannot, and which decision would change the outcome. That clarity builds trust with leadership, customers, and the people doing the work.

When the next request arrives, do not ask whether the team can squeeze it in. Ask which planned allocation it will replace, what role capacity it consumes, and how it changes the delivery forecast. That is how a plan becomes an operational system rather than a hopeful calendar.

Jeremy Block

More From This Author

Ready to take control of your bench?
Join 1,000+ startups using Teambuilt to simplify their people management.