Team capacity is the working time actually available for planned tasks in a given period. It is not the same as total working hours, because you have to subtract meetings, day to day operations, leave and any work that is not project work. Workload, on the other hand, is how much work is waiting to be done. Comparing the two shows whether the plan is realistic. If workload consistently exceeds capacity, something will slip, however hard the team works.
What is the difference between capacity and workload
Capacity is the supply side. It describes how much work the team can do. Workload is the demand side. It shows how much work is being asked of the team. Our article on what workload is explains in detail how to measure it.
The two only make sense together. The same amount of work can be easy in a week when everyone is in and impossible in a week when two people are on leave. That is why workload should always be measured against capacity, never on its own.
How to calculate your team’s capacity
The calculation is simple. The hard part is filling it in honestly.
- Start with team members’ working hours for the period.
- Subtract leave, public holidays and planned absences.
- Subtract recurring meetings.
- Subtract time spent on day to day operations, such as customer requests, support and admin.
- What remains is the capacity available for project work.
Here is an illustration. A team of four works 160 hours in total in a week. If each person spends five hours a week in meetings and ten hours on daily operations, 100 hours remain for project tasks, not 160. If you ignore that gap, the plan is overcommitted from day one.
The exact numbers differ from team to team. What matters is that you work it out once for your own team, so you have a realistic starting point.
Why you should not plan for one hundred percent
It is tempting to fill all available capacity, because it seems to get the most work done. In practice the opposite happens.
The first reason is that some estimates always come in low. Without buffer, every slipped estimate drags another task with it.
The second is that something always comes up. An urgent customer request, a bug that needs fixing right away, a colleague out sick. If the plan covers every hour, there is no room for these, and they eat into planned work.
The third is that in a fully loaded system, waiting grows. When everyone works at one hundred percent, every new request or handoff ends up in a queue. Tasks wait longer and longer for each other, even though everyone is working all the time.
So leave buffer on purpose. How much depends on your own experience. If planned work regularly spills over the end of the week, the buffer is too small.
How to handle changing capacity
Capacity is not constant. It shifts with leave, people moving between projects, a new colleague ramping up, or a seasonal peak. A plan built on an average week falls apart in a harder one.
Two simple habits help.
- Plan for the period, not the average. Every time you plan, check who will actually be available in that period.
- Treat a change in capacity as a decision. When someone drops out, do not just redistribute their tasks. Decide what slips and tell the people who are waiting for it.
Capacity planning in small teams
In a small team capacity is especially fragile. If one of five people is missing, that is a fifth of the capacity. Small teams also often have areas tied to a single person, whose absence cannot easily be covered.
So in a small team, alongside capacity, watch where all the knowledge sits with one person. If someone’s workload is consistently high, that is not only their problem. Our article on recognizing overload covers this in more depth.
How capacity shows up in a task management tool
In MyPro Sync every task can carry an effort estimate in hours, an expected completion date and a deadline. That shows how much work falls into a given period and on a given person. The manager overview shows the team’s tasks filtered by assignee, so you can compare workload with the time someone can actually spend on project work. Capacity itself, meaning how much time each person has, is something the team has to define. No tool can do that for you.
The first step
Work out your team’s real capacity for next week using the five steps above, and compare it with the estimated hours of the planned tasks. If the gap is bigger than you expected, the team is not slow. The plan was too optimistic.