Small teams rarely miss deadlines because people are lazy. They miss them because the work promised is larger than the hours available, and nobody noticed until it was too late. Capacity planning is the habit of comparing the two before you say yes. This guide answers the most common questions: what capacity planning is, how to do it without special software, and how to keep it useful.
What is capacity planning?
Capacity planning means estimating how much work your team can realistically complete in a given period, then matching it against the work that is coming in. Capacity is the supply of productive hours. Demand is the work that has been requested or promised. The plan shows where the two meet and where they do not.
Why does it matter more for small teams?
In a team of five, one sick day, one resignation or one urgent client request changes the picture noticeably. There is no spare pool of people to absorb the shock. A short, regular plan turns unpleasant surprises into trade-offs you make on purpose.
How do you plan capacity step by step?
1. Calculate real available hours
Start with contracted hours, then subtract public holidays, planned leave, training and recurring meetings. A person paid for 40 hours a week rarely has more than 25 to 30 hours left for project work. Planning with 40 is the most common reason capacity plans fail.
2. Reserve a buffer for the unplanned
Support requests, rework and small favours always appear. Hold back 15 to 20% of capacity for them, and more if your team is mostly reactive. Look at last quarter to see what the real figure was instead of guessing.
3. List the demand
Write down every project, recurring task and commitment, each with a rough estimate in hours or days. Rough is fine: a range such as 20 to 30 hours is more honest than a falsely precise 24. Do not forget the invisible work, such as onboarding, reviews and administration.
4. Compare supply and demand
Put both on one page, per person or per skill, for the next four to eight weeks. Where demand exceeds capacity you have an overload. Where capacity exceeds demand you have room to take on something new or to invest in improvements.
5. Decide what gives
When the numbers do not fit, you have four honest options:
- Reprioritise. Drop or pause the work that matters least.
- Reschedule. Move a deadline that has some flexibility.
- Add capacity. Borrow a colleague, use a contractor or start hiring.
- Reduce scope. Deliver a smaller first version.
Working harder is not on the list. Overtime hides the problem for a week or two and then makes it worse.
A simple example
A team of four has 160 contracted hours a week. After holidays, meetings and administration, about 110 hours are available for real work. Holding back 20% for unplanned requests leaves 88 hours. The planned work for next week adds up to 105 hours. That gap of 17 hours is visible on Monday morning, so the team lead can postpone a low-priority report or ask for help, instead of discovering the problem on Friday afternoon.
Common capacity planning mistakes
- Planning at 100% utilisation. A team booked solid has no room for anything unexpected. Aim for 75 to 85% of available hours.
- Treating people as interchangeable. Ten free hours of a designer do not help when the bottleneck is the one person who can do the accounts.
- Ignoring multitasking. Juggling many projects at once costs time in switching, so real output drops.
- Planning once and forgetting it. Priorities, absences and demand change every week.
- Keeping the plan private. If only the manager sees it, nobody else can warn you when it is wrong.
Keeping the plan useful
Spend fifteen minutes a week updating it, ideally at the same time as your team meeting. Compare what you planned with what actually happened, and adjust your estimates and your buffer. After a few cycles, your numbers will be far more reliable than any template. A spreadsheet is enough to start. If you already track projects and KPIs in FulcrumGrid Command Center, you can keep workload figures next to them, so an overloaded week is visible alongside the project it threatens rather than in a separate file.
Count the hours you really have, be honest about the work coming in, and decide early what gives. A modest plan that you update every week beats a perfect one you never look at.
Frequently asked questions
What utilisation rate should a small team plan for?
Most teams do best at 75 to 85% of available hours. The remaining time absorbs unplanned requests, sick days and estimates that turn out too low. Planning at 100% almost guarantees missed deadlines.
How far ahead should a small team plan capacity?
Plan the next four to eight weeks in detail and the next quarter roughly. Detail further out goes stale quickly, but a rough view helps you spot big peaks, holidays and hiring needs in time.
Do I need special software for capacity planning?
No. A spreadsheet with people in rows, weeks in columns and hours in the cells is enough for most small teams. Move to a dedicated tool only when the spreadsheet becomes hard to keep current.
What if demand is always higher than capacity?
Then the issue is not planning but priorities. Show the gap in hours to whoever sets the priorities and ask them to choose what to drop, delay or fund. A permanent overload needs a decision, not more effort.
FulcrumGrid Command Center
See workload next to your projects
FulcrumGrid Command Center helps you track KPIs and projects in one place, so overloaded weeks show up before deadlines slip.