Manufacturing runs on simple math. One person, one machine, one fixed output per hour. Multiply people by hours, and capacity is a known number.
Knowledge work doesn't work that way. Developers, project managers, consultants, analysts, and other knowledge workers rely on focus, judgment, and collaboration, not a fixed output per hour. The work changes shape depending on what a person is doing at that moment, so one available hour does not always equal one usable hour.
Interruptions, meetings, context switching, deep work, and flexible schedules all change how much capacity a person can actually use.
So resource planning for knowledge workers should ask more than "How many hours are free?" It should ask "How much of that time can realistically support delivery?"
Why the Traditional Capacity Formula Breaks Down
Traditional resource planning often starts with a straightforward calculation:
Capacity = Number of People × Available Working Hours
The formula is useful as a baseline. It tells managers how much time a team theoretically has. The problem is that it treats every available hour as equal and assumes that time can be converted into output in a relatively predictable way.
Knowledge work doesn't behave like that. Someone might have 10 hours free on their calendar, but those hours can get split across meetings, broken up by unplanned requests, spread thin across multiple projects, or too short and scattered for work that needs real focus.
So a plan can look fine on paper and still fall apart in practice. For example:
40 working hours → 30 hours allocated → 10 hours available
Those 10 hours look like 10 hours of capacity. But they don't tell you:
- Are those hours together, or spread out in small pieces?
- How many other projects are pulling at this person's time?
- How much extra work is likely to come up anyway?
- Does the time available match the kind of work that needs doing?
- Is any of it actually free for collaboration with the rest of the team?
Adjusting the formula, like subtracting meeting time or applying a utilization rate, can make the number more realistic. But it's still just one number trying to describe something more complicated.
For knowledge work, capacity isn't only about how many hours are free. It's about whether those hours can actually be used.
Five Forces That Separate Real Capacity From Planned Capacity
The gap between planned capacity and usable capacity doesn't come from one problem. It comes from several forces that show up in most knowledge work, often at the same time.
1. Interruptions
An interruption can break the flow of a task before it is finished. The cost is not limited to the minutes spent responding. The person also needs time to recover context and resume the original task.
That means an hour that looks available on a resource plan can produce far less progress when it is repeatedly interrupted.
2. Meetings
Meetings occupy real time on a calendar, but they rarely get subtracted cleanly from capacity plans. A person can look fully available for a project and still have half their day already committed to meetings that never show up in a resourcing spreadsheet.
3. Context Switching
Context switching, the act of moving between projects, tools, or types of work, creates a cost that rarely appears in a resource plan.
Each switch requires the person to reload context, priorities, and information before meaningful work can resume. Someone may therefore have a reasonable allocation on paper while spending a large part of their capacity moving between workstreams rather than progressing them.
4. Deep Work
Some tasks need long, uninterrupted blocks of focus to move forward at all. A calendar with plenty of open time can still fail to offer a single block long enough for this kind of work, which means the hours exist but the capacity they were meant to represent doesn't.
Read also: How to Do Deep Work The Right Way To Boost Your Concentration
5. Flexible Schedules
Flexible hours help people manage their own workload, but they make it harder for a manager to see who's actually working when, and how much overlap exists for collaboration. Capacity that looks solid on paper can be scattered across times that don't line up with the rest of the team.
None of these forces are visible in a formula built on people multiplied by hours. They only show up when someone looks at how a day actually unfolds, which is exactly what a static capacity number can't capture.
What "Available" Actually Means
In a resource plan, "available" usually means hours left after existing work is accounted for. For knowledge work, that's not enough.
Someone can have 10 hours open and still have very little real capacity. Those hours might be split across meetings, spread over several projects, or interrupted so often that none of them add up to real progress.
A more useful way to think about availability is to separate how much time exists from how usable that time is.
1. Theoretical Capacity
The total working time a person or team could provide during a given period, before accounting for leave, existing assignments, or other commitments.
Theoretical Capacity = Number of People × Working Hours in the Period
Example: 5 people × 40 hours/week = 200 person-hours/week
So the team's theoretical capacity is 200 hours a week.
This is a baseline for planning, not a forecast of how much work the team will deliver.
2. Available Capacity
The working time that remains after known commitments are accounted for, such as existing project assignments, planned leave, recurring meetings, and other scheduled responsibilities.
Available Capacity = Theoretical Capacity − (Leave + Meetings + Admin Overhead)
Example: 200 theoretical hours − (15 hours of planned leave + 25 hours of internal admin/meetings) = 160 available person-hours/week.
The Reality: This tells managers how much time is on the table to be assigned to projects. However, it still does not guarantee that this time can be spent productively.
This gives managers a useful view of remaining time. It doesn't tell them whether those hours fall in useful blocks, or whether they suit the kind of work that needs doing.
3. Usable Capacity
Usable capacity is the part of available time you can reasonably plan to use for productive work. Since people also spend time on meetings, admin work, collaboration, and unexpected requests, not every available hour can be used for planned work.
One way to estimate it is:
Estimated Usable Capacity = Available Capacity × Utilization Rate
Example: 160 available hours × 75% target utilization = 120 planned productive hours/week
The 75% is a planning assumption, not a universal standard. The right rate depends on the role, type of work, and how much time is normally spent on non-project work.
This gives managers a more realistic planning number than assuming 100% of available hours can go to planned work.
Available capacity tells you how much time is left. Estimated usable capacity tells you how much you can reasonably plan to use.
How to Plan Resources When Capacity Isn't Fixed
Knowledge-work capacity changes as project commitments, priorities, schedules, and unexpected work change. Instead of setting capacity once and leaving the plan unchanged, managers should review the resource picture as the work evolves.
Step 1. Start With Available Capacity
Begin with working hours and remove time that is not available for planned project work, such as leave, meetings, and recurring administrative work. Then account for existing project commitments.
Available Capacity = Working Hours − Non-Project Time − Committed Project Hours
This gives managers a baseline for how much time remains, but it should not be treated as a guaranteed amount of delivery capacity.
Step 2. Check How Capacity Is Distributed
The total number of open hours doesn't tell the full story. What matters is when those hours happen, and whether they're long enough to be useful.
A person with 10 hours scattered across a week doesn't have the same capacity for deep work as someone with two clear five-hour blocks, even if the total is the same.
Step 3. Look Across Projects
Resource planning should account for a person's commitments across all projects. A person may appear to have capacity within one project while already carrying significant work elsewhere.
Step 4. Match Work to the Capacity Available
Consider what the work actually requires. Routine tasks can fit into shorter gaps. Complex or collaboration-heavy work usually needs longer focus blocks or overlapping schedules.
Step 5. Leave Room for Unplanned Work
Keep some capacity flexible for urgent requests, rework, unexpected issues, and shifting priorities. A plan with no slack breaks the moment something unplanned shows up, which in knowledge work, is often.
Step 6. Review and Replan
Capacity keeps shifting as work changes. Reviewing it regularly, rather than once at the start, is what keeps a resource plan realistic instead of outdated.
Read also: How to Create a Resource Plan for Any Project (Even with Limited Resources)
How TaskFord Helps Managers Plan Real Capacity
The challenge is not calculating a capacity number once. It is keeping that number useful as projects, assignments, and priorities change.
TaskFord connects project planning, resource workload, schedules, and progress in one workspace, so managers can see the work behind the capacity numbers and make decisions based on the current plan.
With TaskFord, managers can:
- See workload across projects: Identify where people are already committed and where the same resources are being shared across projects.
- Spot capacity conflicts early: See overlapping assignments and workload pressure before adding more work.
- Connect resources to project plans: Understand how changes to timelines, assignments, or priorities affect the wider delivery plan.
- Track progress against the plan: Compare planned work with actual progress to identify when the resource picture needs to be reassessed.
- Replan as conditions change: Adjust assignments and schedules when priorities shift, projects change, or new work appears.
TaskFord does not turn knowledge-work capacity into a fixed or perfectly predictable number. Instead, it gives managers a connected view of projects, resources, workload, and progress, helping them make more realistic decisions about what the team can deliver.
Read also: How Operation Teams Leverage TaskFord for Resource Planning in Project Management
Conclusion
Knowledge-work capacity cannot be understood by counting hours alone. Meetings, interruptions, context switching, focus requirements, and changing schedules all affect how much available time can realistically support delivery.
The goal of resource planning is not to predict every hour perfectly. It is to maintain a clear view of commitments, workload, and changing capacity, then adjust the plan as conditions change.
Counting hours tells you how much time remains. Understanding how that time will actually be used is what tells you whether the work gets delivered.
