Every business has to constantly look for new work to survive. The challenge is that capacity doesn’t grow at the same pace. Headcount changes slowly, and the same people carry the critical skills month after month.
This is why capacity and demand need to be viewed together. Capacity shows what the team can deliver in a given period. Demand shows the work the business wants to take on. Once both sit side by side, it becomes clear which months can handle more work and which ones are already tight.
This creates a more disciplined way of planning. With many projects and many roles involved, gut feeling isn’t enough. Capacity vs. demand becomes the baseline—showing what fits, what needs to wait, and what will break the schedule if pushed ahead anyway.
Key Takeaways
- Capacity is the amount of work a team can handle based on their working hours and availability.
- Demand reflects the work the organization wants completed.
- Comparing capacity with demand shows where new work can fit in and where constraints will arise.
- Planning at the capability level matters; surplus hours in one role cannot cover shortages in another.
- Aligning work with actual capacity leads to more reliable delivery, better quality and a team that stays healthy.
What Is Capacity?
Capacity is the amount of work a team can realistically complete within a specific period. It is based on several factors:
- The number of people on the team
- Their weekly availability
- Their skills
The first two points are obvious: The number of people, multiplied by their weekly working hours gives us the overall capacity. But why are skills listed here?
Because people are not interchangeable. A team might have enough total hours, but those hours only help if the right people are available for the right work. Some tasks require specific qualifications, certifications or experience, and only a few people of the team can perform them.
Using our example from manufacturing:
A manufacturing team might have 200 hours of total capacity this week (assuming a 40-hour workweek and 5 people on the team).
Out of that team, only one engineer is certified to recalibrate a CNC machine. If a project requires 20 hours of recalibration work, that work can only be done by that engineer. The rest of the team could be fully available, but their time doesn’t solve the bottleneck.
The overall capacity number looks fine, but the real constraint sits inside one specialized role. To make this visible, break the 200 hours down by capability:
- 40 hours: Process engineering
- 80 hours: Mechanical technicians
- 60 hours: Electrical technicians
- 20 hours: CNC calibration specialist
Seen this way, the issue is clear: The team has hours available, but only 20 of those hours belong to the role required for the CNC work. Capacity is not the 200-hour total—it is the 20 hours of the one person who can do the task.
Therefore it doesn’t make sense to look at capacity at a high level, such as by team. A project often requires a specific skill held by only a few specialists. Their availability—not the total hours across the team—is what determines whether the work can move forward.
So far we’ve used hours to express capacity, and it’s the most common unit. But it’s not the only one. Construction teams often work with output units, developers use story points, and production teams often use machine cycles. As we’ll see later, different units make sense in different environments, depending on the nature of the work.
What Is Demand?
Demand is the total amount of work the organization wants the team to handle.
Demand includes confirmed orders in the order book, upcoming projects, quotes in progress and potential deals currently under discussion.
Demand grows faster than capacity because businesses are always looking for new revenue. Sales activity creates potential work long before anyone checks in detail whether the team can actually support it.
Imagine a mid-sized custom machine manufacturer:
- They may be pursuing new orders through trade shows, advertising and an engaged sales team.
- Each new lead triggers additional work: engineering input for quotes, prototype requests, custom configuration checks, or feasibility reviews.
- These requests add up quickly. The organization creates more demand by chasing growth, while the engineering, production, and maintenance teams operate with the same fixed people and hours.
This is why demand can expand steadily even when capacity does not. The business keeps generating new work, but only part of it can be delivered based on the capabilities available inside the team.
Same as for capacity, the skill requirements behind each piece of work matter just as much as the hours: Many tasks can only be completed by people with specific training, certifications, or experience. The work cannot be reassigned simply because someone else has time available. A large pool of hours across the team doesn’t solve the problem if only a few individuals have the capability required for a particular activity.
Example:
Our machine manufacturing company schedules several activities for the week—equipment calibration, safety inspections, and process tuning. On paper, the total demand is 120 hours for a team with 180 hours of capacity.
It looks manageable until the skill requirements are unpacked:
- Only the controls engineer can update the PLC logic for a new sensor.
- Only the quality engineer can perform and sign off the mandatory compliance inspection.
- Only the technician trained on a specific robotic cell can recalibrate that unit.
Those tasks all land on the same few specialists. Their personal demand exceeds their personal capacity, even though the rest of the team has open hours. This creates a bottleneck invisible in the total demand number.
The conclusion: Demand describes what needs to be done, but it does not guarantee that the right people are available or that they have enough bandwidth to complete it.
How to Determine Capacity
Measuring capacity starts with the people doing the work, the hours they are available, and the period you want to plan for.
Note that capacity is always tied to a time window—for example, capacity per week or per month.
List each person and their actual working schedule. Some are full-time, others work part-time or only on specific days. Each person contributes a different number of available hours, and these differences matter. Capture each individual’s real availability rather than assuming a standard number.
After that, add those hours together to form the capacity for the chosen period. The result is a clear figure—such as “140 engineering hours next week” or “320 technician hours next month”—based on actual schedules rather than guesses.
Example: Capacity by Role (Jan–Mar)
Hours per month
| Role | # of People | Capacity January | Capacity February | Capacity March |
|---|---|---|---|---|
| Process Engineer | 4 | 480 hrs | 440 hrs | 500 hrs |
| Mechanical Technician | 6 | 720 hrs | 680 hrs | 760 hrs |
| Electrical Technician | 3 | 336 hrs | 315 hrs | 345 hrs |
| Automation Specialist | 2 | 240 hrs | 220 hrs | 250 hrs |
| Quality Engineer | 2 | 200 hrs | 190 hrs | 210 hrs |
| CNC Calibration Expert | 2 | 160 hrs | 150 hrs | 170 hrs |
This view shows how capacity changes month to month based on working days, availability, and planned absences. It also makes clear which roles remain constraints, even when the team’s total capacity looks sufficient.
The key point is that capacity comes from real availability within a defined time frame. This makes it a reliable metric to compare against the demand waiting to be delivered.
Putting Capacity and Demand Side by Side
Let’s assume that by August, the machine manufacturing company has a long list of incoming opportunities.
Trade shows generated new leads, the sales team pushed several promising deals forward, and marketing campaigns created additional interest.
All of this activity built momentum, but now the company needs to understand what is actually possible.
Before committing to delivery dates for the following year, they need to compare the demand pipeline with the capacity of their engineering and technical teams.
This is where capacity and demand must sit next to each other. The company already estimated its capacity for January through March, broken down by the key roles involved in production and engineering work.
Now the incoming workload (demand) is mapped to the same roles and the same months. Once both data sets are aligned, the shortfall or surplus becomes clear.
Capacity vs. Demand JANUARY
| Role | Jan Capacity | Jan Demand | Jan Shortfall / Surplus |
|---|---|---|---|
| Process Engineer | 480 hrs | 500 hrs | -20 hrs |
| Mechanical Technician | 720 hrs | 700 hrs | +20 hrs |
| Electrical Technician | 336 hrs | 240 hrs | +96 hrs |
| Automation Specialist | 240 hrs | 250 hrs | -10 hrs |
| Quality Engineer | 200 hrs | 210 hrs | -10 hrs |
| CNC Calibration Expert | 160 hrs | 170 hrs | -10 hrs |
Capacity vs. Demand FEBRUARY
| Role | Capacity February | Demand February | February Shortfall/Surplus |
|---|---|---|---|
| Process Engineer | 440 hrs | 210 hrs | +230 hrs |
| Mechanical Technician | 680 hrs | 665 hrs | +15 hrs |
| Electrical Technician | 315 hrs | 220 hrs | +95 hrs |
| Automation Specialist | 220 hrs | 234 hrs | -14 hrs |
| Quality Engineer | 190 hrs | 110 hrs | +80 hrs |
| CNC Calibration Expert | 150 hrs | 160 hrs | -10 hrs |
Capacity vs. Demand MARCH
| Role | Capacity March | Demand March | March Shortfall/Surplus |
|---|---|---|---|
| Process Engineer | 500 hrs | 510 hrs | -10 hrs |
| Mechanical Technician | 760 hrs | 780 hrs | -20 hrs |
| Electrical Technician | 345 hrs | 250 hrs | +95 hrs |
| Automation Specialist | 250 hrs | 260 hrs | -10 hrs |
| Quality Engineer | 210 hrs | 220 hrs | -10 hrs |
| CNC Calibration Expert | 170 hrs | 180 hrs | -10 hrs |
Interpreting the Data
Looking at capacity alone wouldn’t reveal any of this. The team seems to have hundreds of hours available each month. But once demand is mapped to the required roles, the bottlenecks appear immediately:
- The automation specialist and CNC calibration expert are over capacity every month.
- Process engineering becomes constrained in January and March.
- Mechanical technicians show occasional surplus, but that surplus cannot offset shortages in the specialist roles.
- Quality engineering fluctuates, but the constraints in automation and calibration already prevent key projects from progressing.
This side-by-side view shows what work the company can commit to—and what projects will need rescheduling, re-scoping or additional staffing.
Without placing capacity and demand next to each other at the role level, these constraints would stay hidden until deadlines were missed.
With the shortfall now visible, the company can address the constraint in a targeted way. For the process engineer, several options are now clear:
- Schedule new projects based on the months where capacity exists, rather than forcing them into already constrained periods.
- Shift lower-value work into February, where some surplus exists.
- Reassign a portion of the workload to another engineer with partial overlap in skills.
- Bring in an external process engineer temporarily, if contractor contacts or partner specialists are available.
These actions add capacity, redistribute work or time new commitments in a way that fits the actual capabilities of the team. Once the limitation is explicit, the company can act deliberately instead of hoping the workload will fit into the existing plan.
Capacity Can Be Expressed in Units Other Than Hours
Hours are the most common way to express capacity, but they are not the only relevant unit.
Using Output Units
Some types of work are better represented as output units because the work naturally groups into discrete jobs rather than hours of effort. In these cases, measuring capacity as “jobs per week” or “installations per month” gives a more accurate picture of what the team can deliver.
A good example is a residential construction company. Many of the skilled trades involved—such as excavation, framing, roofing, or electrical rough-ins—operate on a job-by-job basis. Each crew can only complete a certain number of these jobs per month, regardless of the total hours available across the entire company.
| Crew | Monthly Job Capacity |
|---|---|
| Excavation | 5 jobs |
| Concrete & Foundation | 6 jobs |
| Framing | 4 jobs |
| Roofing | 7 jobs |
| Electrical Rough-In | 10 jobs |
| Plumbing Rough-In | 7 jobs |
Measured this way, the constraints become visible immediately. Even if the company has many workers overall, only one excavation crew may be available. This limits the entire pipeline to five new home starts per month. Additional crews downstream cannot start their work until excavation and foundation are completed, which makes the excavation capacity the first bottleneck in the sequence.
Capacity measured in jobs, rather than hours, fits industries where the work is repeatable, discrete, and completed by specialized crews working as a unit. This gives a more realistic view of throughput and highlights where the production flow will slow down.
Using FTE for measuring capacity
Some organizations measure capacity and demand in FTEs – usually tied to specific roles. This works when each FTE value reflects the actual availability of a capability—such as 0.8 FTE of a process engineer or 1.2 FTE of an automation specialist. Used this way, FTEs offer a simple way to compare supply and demand across capabilities.
Summary
The goal is straightforward: deliver projects on time, with solid quality, and without pushing the team past its limit. Understanding capacity and demand is what makes that possible.
Capacity starts with real availability—people’s actual working hours, skills, and constraints. Demand is mapped the same way, over the same period, so the workload is no longer just a list of requests but a measurable amount of work.
Once both are set side by side, the plan becomes clear. Feasible months stand out, bottlenecks are easy to spot, and timelines can be set where they will actually hold. This alignment leads to steadier delivery, fewer surprises, and a team that can do its best work. It also builds trust with customers, because commitments are based on what the organization can really deliver.
FAQs
What is capacity? What is demand?
Capacity is the amount of work a team can complete, taking into account team size, people’s availability and their skills.
Demand is the amount of work an organization wants to be done. These are most commonly planned orders or projects.
Why is it helpful to compare capacity and demand?
Showing capacity and demand side by side reveals the gap between what the team can deliver and what the organization expects. This makes it possible to schedule work in periods where it is actually achievable and avoid overloading people.
Are capacity and demand always measured in hours?
No. Hours are the most common unit to measure capacity and demand. Some industries also use output units — like jobs per month or batches per week, which works well when work is performed in discrete steps. The right unit reflects how the work is actually performed. Capacity and demand must use the same unit so the comparison is meaningful.
Does capacity include vacation, holidays and other time off?
Yes. Capacity needs to reflect the actual time people are available, which means subtracting vacation, holidays and other planned time off. Otherwise capacity would be inflated and lead to unrealistic plans.
