Team capacity planning: available hours, booked hours and who is really free
Team capacity planning for managers: work out each person's real available hours, book work against them, spot overload early and run short sprints.
Last checked 5 min read
Ask a manager whether the team can take on one more project and the answer is usually a guess. Someone looks busy, someone else looks free, and the work lands on whoever said yes last. Team capacity planning replaces the guess with two numbers per person per week: the hours they actually have, and the hours already booked. Once you can see both, most allocation arguments settle themselves.
Team capacity planning starts with available hours
Available hours per person are not "40 a week". Work them out properly:
- Shift hours. A 9:30 to 6:30 shift with an hour's lunch is 8 hours a day. A plant engineer on six days a week has 48.
- Minus leave. Approved leave, half days and short leave.
- Minus holidays. Use the person's own location's holiday list. Mumbai and Bengaluru do not share every holiday.
- Minus fixed commitments. Recurring meetings, the weekly review, a training session.
Then apply a focus factor. Nobody turns every available hour into planned work: there are emails, questions from colleagues and small fires. Planning against about 80% of what is left is realistic for most office teams; for support-heavy roles, 60% may be closer.
Working-hour limits also apply. The OSH Code sets a limit of 8 hours a day for workers, with overtime rules on top, and state shops and establishments laws cover many office staff. A plan that only works if people stay late every evening is not a plan.
A worked example: a design team in Pune
A six-person design team plans the week of 14 September 2026. Monday the 14th is a festival holiday at the Pune office.
| Person | Shift hours | Leave and holiday | Meetings | Available | At 80% |
|---|---|---|---|---|---|
| Anjali (lead) | 40 | 8 (holiday) | 8 | 24 | 19 |
| Rahul | 40 | 8 (holiday) | 3 | 29 | 23 |
| Sneha | 40 | 16 (holiday + 1 day leave) | 3 | 21 | 17 |
| Imran | 40 | 8 (holiday) | 3 | 29 | 23 |
| Kavya | 40 | 8 (holiday) | 3 | 29 | 23 |
| Vikram (Bengaluru office) | 40 | 0 | 3 | 37 | 30 |
The team has about 135 plannable hours, not 240. Vikram, based in Bengaluru where the holiday list differs, is the only one with a full week. If the client brief needs 160 hours of work this week, the gap is visible on Friday the week before, not on Thursday at 9 pm.
Booked hours: where they come from
Booked hours are everything already promised:
- Task estimates. Every task gets an estimate in hours. It does not need to be precise; "about 4 hours" is enough.
- Project allocations. "Rahul is 50% on the Nashik plant signage project this month" books 20 hours a week.
- Meetings. Calendar meetings booked in Google or Outlook.
When booked hours are higher than available hours, the person is over-allocated. That is the moment to act: move a due date, give the task to someone with spare hours, or say no.
Reading a workload heatmap
A workload heatmap shows people down the side, days or weeks across the top, and colours each cell by how full it is: green under 80%, amber 80 to 100%, red above 100%. Three patterns are worth looking for:
- One person always red. Usually the senior person everyone goes to. Spread the work, or protect their time.
- A red week coming. A release, a month-end close or an audit. Move non-urgent work out of that week now.
- Someone always green. Either they are under-used, or their work is not being recorded. Ask before assuming.
Keep the heatmap private to the manager line. People outside the team need to know when a colleague is free for a meeting, not what they are working on.
Over-allocated team members: what to do
When the numbers show someone at 130%, there are only four honest options:
- Move the date. Tell the requester now, with the reason.
- Move the work to someone with spare hours and the skills.
- Cut scope. Deliver the essential part first.
- Add capacity for a defined period: a contractor, overtime with approval and pay, or borrowing from another team.
"Ask them to manage" is not on the list. Repeated overload shows up later as mistakes, sick leave and resignations.
Sprints for non-software teams
Sprints come from software, but the idea works anywhere: plan a fixed amount of work for two weeks, then look back.
- Marketing: campaign assets for the fortnight, sized against the team's hours.
- HR operations: a joining batch, an appraisal cycle step, a policy update.
- Finance: month-end close tasks split across two short cycles.
- Facilities: a floor refurbishment broken into two-week chunks.
At the start, pick work that fits the team's plannable hours. At the end, review what was done and why the rest was not, and carry it over. After three cycles you know your team's real pace, which makes the next promise to a client or a department head much safer.
Leave and holidays change the plan
Capacity changes every time someone applies for leave, takes a comp off or adjusts their shift. Plans should update when leave is approved, not when someone notices an empty chair. Clear rules help here too: our guides on short leave for employees and comp off validity rules cover two of the most common sources of surprise absences.
A weekly routine for managers
- Thursday or Friday: check next week's available hours and the heatmap.
- Move or reassign anything that pushes a person above 100%.
- Confirm estimates on the larger tasks with the people doing them.
- Monday: a 15-minute stand-up to confirm the plan and flag blockers.
- Once a month: compare estimates with actual hours and adjust.
The workload view in the Vatsin Task Manager works this way: available hours from each person's shift, working days, leave and holidays; booked hours from task estimates, project allocations and connected calendar meetings; red when someone is over-allocated. A spreadsheet can do it for a small team. What matters is that the numbers are updated every week and that the manager acts on them.