What is IT capacity planning, and what should a CIO measure?
IT capacity planning is the discipline of matching the people-hours your IT organization can actually deliver (supply) with the work the business is asking for (demand), so you can decide what to staff, defer, contract out, or automate before delivery slips. A CIO should track four numbers: net capacity after leave and run work, committed and requested demand, the run-versus-change split, and the gap between planned and actual effort.
IT capacity planning for CIOs
A practical guide to matching headcount and budget with what the business is asking for.
Last updated :
Why capacity is a CIO problem, not a project-manager problem
Demand on IT grows faster than headcount. Digital initiatives, security and compliance work, and AI projects all compete for the same engineers, while a large share of the team's time is already spoken for by keeping the lights on. When nobody can say how much real capacity exists, every request looks feasible until delivery dates start to slip.
Capacity planning turns that argument into numbers. It gives the CIO a defensible answer to “can we take this on?” and a clear trade-off to put in front of the executive team.
The four numbers every CIO should know
- Net capacity: available person-days after PTO, holidays, training, and run work, then adjusted by a realistic focus factor.
- Demand: work already committed plus work requested, expressed in the same unit as capacity.
- Run versus change: the share of capacity absorbed by operations versus projects and transformation.
- Planned versus actual: how far real effort diverges from the plan, which tells you how much to trust the forecast.
The four levers when demand exceeds supply
- Hire: add permanent headcount, accepting the lead time to recruit and ramp up.
- Contract: bring in vendors or contractors for bounded work, at a higher day rate but faster.
- Defer or descope: move work to a later quarter or cut scope, which needs a clear priority call.
- Automate and re-skill: reduce run effort or widen the pool of people who can do scarce work.
How to present capacity to the board or executive team
Keep it to one view: capacity, committed demand, and the gap by domain for the next two quarters, with the decision you need. Executives respond to a clear trade-off (“to deliver X by Q3 we either add four contractors or defer Y”) far better than to a utilization chart.
When to move beyond spreadsheets
Spreadsheets work for one team. They break when people are shared across projects, when more than one person maintains the plan, or when you need to show what changes if a project moves. At that point you need a single source of truth for assignments and a way to compare scenarios. Heavy enterprise PPM suites cover far more than capacity; a lighter capacity layer is often enough for an IT organization of 20 to 500 people.
KPIs for the CIO dashboard
| Indicator | Definition |
|---|---|
| Allocation rate by team | Planned workload divided by net capacity; above 100% signals overload. |
| Run / change split | Share of capacity spent on operations versus new work. |
| Forecast accuracy | Actual effort divided by planned effort across completed projects. |
| Contractor share | Portion of delivery capacity supplied by external resources. |
| Single points of failure | Critical skills held by only one person. |
A quarterly capacity planning cycle
- Refresh net capacity for the next two quarters by team and skill.
- Consolidate committed and requested demand in the same unit.
- Identify gaps and conflicts, and model options with what-if scenarios.
- Take the trade-off to the executive team and record the decision.
- Track planned versus actual and feed the lessons into the next cycle.
FAQ
What is the difference between capacity planning and resource planning?
Capacity planning looks at the aggregate: do we have enough people-hours for the portfolio? Resource planning is the operational view of who is assigned to what, and when. You need both.
How often should a CIO review capacity?
Quarterly for the planning cycle, with a monthly check on the allocation rate and planned versus actual, and an ad hoc review when a major project or departure changes the picture.
Do I need a PPM tool for capacity planning?
Not necessarily. A PPM suite adds demand, financial, and benefits governance. If your core need is capacity, conflicts, and planned versus actual, a lighter tool can be enough or can sit alongside a PPM.
What headcount ratio should I plan for run versus change?
There is no universal ratio; it depends on your estate and maturity. Measure your own split over several quarters, then decide deliberately how much run work you want to reduce.
Go further
See your team's real capacity
Import your teams and projects as CSV and see capacity and overload in half an hour.
14-day free trial