Team capacity planning starts with the load, not the hours

What is team capacity planning, and why do hours alone not measure it?

Team capacity planning is the practice of deciding how much work a team takes on by looking at what the team can carry, not only at who is available and for how many hours. Most plans start from headcount and working time because those are easy to count. They are a starting point, not the whole answer.

The INSPQ makes the point in its workload sheet for the Grille d'identification de risques psychosociaux du travail. Workload, it says, is hard to define and goes beyond the quantity of work the employer prescribes. It has a subjective side: the workload people feel is as important as the workload requested. The sheet asks for a view of the whole job: the complexity of the real work, formal and informal demands, the resources and tools available, the time available and the unforeseen events nobody scheduled.

OHA reads that whole job through the Five Loads: decisional, cognitive, emotional, relational and administrative. It is OHA's framework for naming what the work asks of people. It gives a manager a better planning question than how many hours are free: which load is this plan about to add to?

What does a full calendar hide?

A full calendar hides the interruptions, the contradictory requests and the work that arrives unplanned. These are the things the INSPQ sheet asks workers about: whether the workload is excessively high, whether the work is very hectic, whether it demands intense concentration for long periods, whether contradictory demands arrive often, whether tasks are often interrupted and whether there is enough time to finish.

OHA calls the strain that interruption and context-switching put on attention and working memory cognitive load. Two people with the same hours booked can carry very different cognitive load: one has long uninterrupted blocks, the other switches between requests all day. A plan that counts only hours cannot tell them apart.

Managers are often the ones holding the plan together. In the Canadian Survey on Working Conditions for 2024-2025, Statistics Canada found that half (50.2%) of workers in management frequently worked to tight deadlines, meaning half of the time or more during the previous 12 months. It also found that 34.6% of managers reported unpaid work in their free time several times a month or more to meet work demands.

When a plan works only because someone's evenings absorb the overflow, the capacity is borrowed, not available. The signs a manager can see this week show where that is already happening. The check below takes about a minute. It uses five of the ten statements in OHA's capacity self-portrait, one for each load, so you see all five side by side.

How do you plan work against a team's capacity?

Start from what people report, plan around the load that reads highest, and leave room for what nobody can schedule. The INSPQ says the quantity of work, the intellectual demands and the time constraints can be assessed by asking workers how they perceive their real workload. Put questions of that kind to the team before the next planning round: is the workload excessively high, is the work very hectic, are tasks often interrupted, is there enough time to finish?

Then name the load. Run the check above with the team, or with the person closest to the work, and treat the highest reading as the constraint the plan has to respect. For cognitive load, that means protecting uninterrupted time and dropping recurring meetings that end without a decision. For decisional load, it means writing down who decides what. For administrative load, it means removing or reassigning one report or approval before adding another.

Then plan with margin. The INSPQ lists practices that include making sure the tasks set can be done within regular hours, adding resources or temporary help in a period of overload, setting priorities again and leaving some tasks aside after consulting the workers concerned, and phasing changes with periods of stabilization so people can recover. Each is a planning decision, and each works best before the overload, not after. If you need the reading for a whole function rather than one team, see what a capacity diagnostic measures.

Why does control over the work matter as much as its amount?

Because strain depends on demand and control together, not on demand alone. In a 1979 paper in Administrative Science Quarterly, Robert Karasek tested a model on national survey data from Sweden and the United States. The consistent finding, he reported, was that the combination of low decision latitude and heavy job demands is associated with mental strain.

The CCOHS describes the other side of it: even when demands are high, employees who also have high decision-making ability are able to thrive. The INSPQ adds that several studies have linked a high workload combined with low decision-making autonomy to mental, musculoskeletal and cardiovascular illness.

For a plan, that means the team should have a say in how the work is sequenced and who does what within the deadline. A plan handed down in full leaves demand high and control low, the combination those sources describe. A plan the team helps shape keeps the demand but gives people room to manage it.

How often should a team's capacity plan be revisited?

Often, and in short loops, because the real workload moves with new requests, people's capacities and unforeseen events. The INSPQ recommends a regular way of knowing the real workload and readjusting it, and gives weekly team meetings, exchanges between colleagues about difficulties and regular one-to-ones between manager and employee as examples.

Add a longer loop on top. OHA's Capacity Circle™ runs over 90 days: measure the loads, act on the one that dominates, then answer the same statements again so the comparison is like for like. A reading that has not moved is also information: the change you made was not the one using up the capacity.

Plan your own load in the same pass. The INSPQ notes that a high workload among managers is thought to get in the way of the support and availability their teams need.