← Insights

Operations

Spotting over-allocation before it bites

July 2026 · 6 min read

Nobody plans to book a person at 140 percent. It happens one reasonable decision at a time: a task lands on Priya because she is the right person, then a second, then a favour for another team, each looking fine on its own. By the time the week arrives she is quietly carrying the load of one and a half people, something slips, and the post-mortem calls it "a resourcing issue" as if it arrived by weather.

It did not arrive by weather. It was visible the whole time - just never in one place. Capacity planning is the discipline of putting every person's available hours next to the work you have actually given them, on one grid, so the overload shows up as a number before it shows up as a missed deadline.

Capacity is a number, not a feeling

The starting move is to write down what each person can genuinely do in a week. Not the 37.5 on their contract - the real figure after standing meetings, support duty, holidays and the general friction of a job. Call it their capacity. Then, against each week, record the hours you have committed them to. The gap between the two is the only question that matters, and it has three answers: room to spare, full, or over.

Most teams never get this far because doing it by hand is miserable. You would be summing hours across rows, comparing each total to a different capacity, and re-checking every time the plan moves. So it does not get done, and the overload stays invisible until it bites.

The heatmap does the watching

The fix is to let the sheet colour the answer in for you. Every week-cell turns red the moment allocated hours pass that person's capacity, amber as it nears the limit, and green when there is comfortable headroom. You stop reading numbers and start reading a wall of colour: a band of red across one person's row is a conversation you need to have now; a column of red down one week is a crunch the whole team is walking into.

This is the difference between a planner and a list. A list holds the hours and waits for you to notice the problem. A heatmap surfaces the problem the instant the data creates it - no conditional formatting to build, no formulas to write, no eyeballing.

Utilisation tells you where to move the work

Once every person-week is scored, two summary numbers do the managing. The first is utilisation per person - allocated hours as a percentage of capacity across the horizon. It answers the question a good resource conversation turns on: who is stretched and who is idle? A planner at 130 percent and a colleague at 55 percent is not a staffing shortage, it is a distribution problem, and you can fix a distribution problem in an afternoon.

The second is coverage: the team's total allocated hours against its total capacity, week by week. This is the number that saves you from the optimistic plan. You can have nobody individually in the red and still be short as a team in week seven, because the work simply exceeds the hours you have. Coverage tells you that in advance, while you can still move a deadline, borrow a resource or cut scope - rather than discovering it when week seven arrives.

Working the plan

• Set honest capacity first. Inflate it and every downstream number lies. The whole method rests on this one column being real.
• Pick a unit and hold it. Hours or days, it does not matter - but be consistent down the whole sheet or the totals are nonsense.
• Rebalance until nothing sits in the red. The plan is not finished when the tasks are assigned; it is finished when no person-week is over capacity and the coverage row can carry every week.
• Re-run it when the plan moves. A capacity plan is a live instrument, not a launch-day artefact. The week a new task lands is the week to check who absorbs it.

The plan is ready when every person is inside their capacity, every week is covered, and the crunch weeks are ones you chose to accept rather than ones that ambushed you.

Do that and the "resourcing issue" stops being a thing that happens to you. Over-allocation becomes a red cell you saw on Monday and dealt with, not a burnt-out colleague and a slipped date you explain on Friday.