Capacity planning and resource management – how to stop chronic overtime and slipping deadlines

Picture a typical conversation at the start of a quarter. The head of operations meets the team leads. Asks how many projects we can take this quarter. Each lead looks at their team, multiplies the number of people by working days and gives a number. We add the projects up, they fit. Off we go. Three months later two projects are a month late, people are tired, the client is unhappy.

What went wrong? Each lead planned capacity assuming each person works 8 hours per day on projects. In reality a person works productively 5–6 hours. The rest is meetings, emails, context switching, short breaks, small office matters. This is not laziness – it is normal human work. Anyone who has worked in an office knows this firsthand.

The second mechanism: planning does not account for holidays, sickness, training. Statistically each person has 25–30 days of leave per year, 5–8 sick days, 3–5 training days. Together 30–40 days a year, i.e. 15% of the year. That 15% rarely lands in the quarterly plan.

The third mechanism: every project has nonlinear overhead. The kickoff meeting, daily stand-ups, retros, integrations, coordination with other projects. That is 10–20% of project time no one plans because everyone assumes it fits inside 8 hours. It does not.

Together these three mechanisms mean the team's real capacity is 65–75% of nominal (people × days × 8h). An organisation planning 100% is planning 130–150% of real capability. Hence the 120% paradox and constant project slippage.

Conscious capacity planning has three levels. Each serves different decisions and needs a different view.

Level 1: weekly current view. Shows how many planned person-hours of work the team has in the coming week and whether it fits in real capacity. This view is for the team manager making daily decisions. It should update automatically from the system where people work (monday.com, Jira, Asana). No manual data entry.

Level 2: quarterly portfolio view. Shows how upcoming projects will load teams in the next three months. This view is for the head of delivery, head of operations, PMO. Lets them make decisions about project prioritisation, deadline shifts, adding resources. Should update weekly, discussed at the monthly business review.

Level 3: annual strategic view. Shows what the organisation will need over the next 12 months, how many people to hire, what competencies are critical. This view is for the leadership team, CFO, head of HR. Should update quarterly, discussed at the strategic review.

Without all three levels capacity planning is fragmented. The manager sees the week but not the quarter. The leadership team sees the year but not the week. Decisions are made without a full picture. As a result projects slip, the team gets frustrated, hiring is delayed.

The three most popular capacity planning tools in 2026 are monday.com Workload, Jira Plans (formerly Advanced Roadmaps) and Float. Each works slightly differently, but all show overload 4–6 weeks earlier than classic methods.

monday.com Workload is an add-on available in higher monday.com plans. Shows each person's load in a timeline or monthly view. Red zones are overload, green is availability. Works automatically from tasks in monday.com, no separate entry required. Most user-friendly for business teams. Price: in the monday.com Pro or Enterprise plan.

Jira Plans (part of Jira Premium) is the deepest capacity planning tool for development teams. Lets you model what-if scenarios (what if we add this developer to project A, how will it affect project B), forecast deliveries, track dependencies between teams. Requires all work to be in Jira. Price: in the Premium Jira plan.

Float is a dedicated capacity planning tool independent of the PM tool. Most often picked by creative agencies, software houses and consulting firms where many people work on different client projects. Very simple interface, strong utilisation reporting. Price: a few to tens of USD/user/month, independent of other tools.

Practical recommendation: business teams on monday.com – Workload. Development teams on Jira – Jira Plans. Agencies and project-driven companies – Float. In mixed organisations we often see two tools side by side, each for its team.

Even the best capacity tool will not replace conscious decisions about rotating people between projects. Two rules that really reduce team burnout.

Rule 1: maximum 3 parallel projects per person. Above that the human brain loses efficiency. Each context switch between projects costs 15–20 minutes of productivity. A person on 5 projects loses 1–2 hours per day just on switching. No laziness involved – neurology.

Rule 2: minimum 2 weeks of continuous work on one project. Shorter means the person constantly switches context and never enters deep work. A conscious PMO plans rotation so each person has 2–4 weeks of focus, then moves to another project.

Conflict forecasting is a skill that can be developed. It is the ability to look at the capacity calendar 6–8 weeks ahead and point at the areas where planned projects need the same people at the same time. A calendar conflict = a decision now, not in a month when it is too late.

The most valuable moment for the weekly capacity review with team leads: the third Saturday of the month. Why? Because you can still see what is coming in the next quarter and have time for decisions before it starts. Not the first Monday of the month, when it is already too late.

The leadership team does not want to look at thousands of tasks assigned to people. They want to see trends. Five numbers that together give them a picture of organisational capacity.

Number 1: utilisation rate – percent of real capacity used on projects. Target: 75–85%. Above 90% means overload and incoming burnout. Below 60% means paying for unused capacity.

Number 2: planned utilisation for the next quarter. Shows whether the upcoming portfolio fits in real capacity. If it shows above 100%, it is too late for planning – a decision is needed on project prioritisation, adding resources or shifting deadlines.

Number 3: forecast capacity gap. How many people will be short in 6 months if the portfolio runs as planned. Shows whether hires are needed now to avoid being stuck in half a year.

Number 4: number of people in burnout state (utilisation >100% for 4+ consecutive weeks). Early signal. Each such person is a risk of leaving, illness, project mistake. The leadership team should be notified immediately, not after the fact.

Number 5: number of projects likely to miss their deadline due to overload. Measured by the capacity tool (Jira Plans, monday.com Workload). Gives the leadership team time for an escalation decision.

Experience from dozens of organisations points to four repeatable capacity planning mistakes. Each can be avoided from quarter one.

Mistake 1: planning 100% of capacity instead of 65–75%. The most common mistake, described at the start of this article. Correction: always plan with a 25–35% buffer.

Mistake 2: capacity only for main projects. The PMO plans team time on portfolio projects, ignoring maintenance, support, current tickets, operational activities. Result: real capacity drifts from planned by 30–50%. Correction: plan everything, including non-project activities.

Mistake 3: no ex-post verification. The organisation plans capacity but never checks how much was actually spent. Without this you cannot calibrate plans. Correction: every project gets a 30-minute review of actual vs planned capacity after closure.

Mistake 4: capacity planning without team manager collaboration. The PMO plans, managers do not know, they argue at the monthly review. Correction: capacity planning is shared – the PMO owns the tool, managers update their teams' data weekly.

Does capacity planning make sense in a small team (5–15 people)? Yes, in a simplified form. In a small team a weekly manager-team conversation about upcoming work is enough. Tool? Sometimes a spreadsheet or simple monday.com board is enough. A full system starts at 30+ people across multiple teams.

How much does deploying a capacity planning system cost? The tool licence alone (monday.com Workload, Jira Plans) is an add-on to existing licences. Consulting deployment (audit of current planning, tool configuration, manager training): EUR 7–18k.

Does AI help in capacity planning? Yes. AI in Jira Plans and monday.com Workload suggests task rotation, predicts overload, automatically balances load. This significantly saves manager work. A fuller picture in our article on AI in project management.

How long does the cultural shift to conscious capacity take? 6–12 months. The first three months are resistance and disbelief. The next three are convincing leaders. The last six are maturing. Without leadership support the change does not stick, because it is a change in how we talk about team work.

What if the leadership team still wants 120% planning? Show data. Pick the last two quarters, count planned capacity vs actual, show how many projects slipped. Data speaks louder than arguments. The leadership team usually reacts when they see the numbers.

Conscious capacity planning is one of the most underrated elements of project management. Organisations that do it well deliver projects on time, have fewer burnt-out people, make faster strategic decisions. Organisations that plan 120% of real capability are constantly in firefighting mode.

The key is three planning levels (weekly, quarterly, annual), a good tool (monday.com Workload, Jira Plans or Float), conscious rotation of people between projects and 5 KPIs for the leadership team (utilisation, planned utilisation, forecast gap, burnt-out count, projects at risk).

Deploying a full system takes 3–6 months and costs EUR 7–18k in consultant work. Real impact after 6 months: project on-time delivery +15–25%, less team burnout, faster leadership decisions.

A fuller picture of PMO's role in capacity planning is in our article on PMO – how to build a Project Management Office. A fuller picture of tool choice is in our article on how to choose a project management system.