Capacity planning past the spreadsheet stage
Every service business plans capacity in a spreadsheet at some point. Names down the side, weeks across the top, an allocation in each cell. It is maintained by one person, usually an operations manager or the founder, and it works well for longer than most people expect.
Then it stops working, and the failure is gradual enough that nobody calls it. The sheet is still there. It is still being updated. It has simply stopped being a plan and become a record of what already happened.
How to tell you have passed the point
Four symptoms show up together.
The sheet is updated after decisions rather than before them. Someone allocates a person to a job in conversation, then the sheet is amended to match. At that point it has no forward-looking function.
Only one person can read it. It contains conventions, colour meanings and exceptions that were never written down. When that person takes leave, resourcing decisions either wait or are made without reference to the plan.
It disagrees with reality often enough that people check with a human before relying on it. Once that habit forms, the sheet is decorative and the actual capacity plan lives in a series of conversations.
And it cannot answer the question leadership most wants to ask: if we win this piece of work, can we deliver it, and what would we have to move?
The three inputs most plans are missing
Realistic available hours
Plans built on nominal hours overstate capacity by a wide margin. A full-time employee does not deliver thirty-eight chargeable hours. Leave, training, internal meetings, business development, administration and the general friction of a working week consume a large and reasonably predictable share. Most businesses know this and plan as though they do not, then treat the resulting overruns as individual performance issues.
Work that is committed but not yet sold
Capacity plans typically show confirmed work. The pipeline sits in a different system, owned by a different person, weighted by probability in a way that has no relationship to delivery. The result is that the business commits to timelines during sales conversations without visibility of what delivery is already carrying. Connecting these two is usually the highest-value change available, and it is more an organisational agreement than a technical one.
Skill, not just headcount
Treating people as interchangeable units is what makes a spreadsheet workable and what makes it wrong. In most service businesses a particular job needs a particular capability, and often a particular accreditation or client relationship. A plan showing spare capacity in aggregate while the one person who can do the work is fully committed is worse than no plan, because it supports a confident and incorrect answer.
A capacity plan that only shows availability is a staffing record. A capacity plan that shows what you would have to move is a decision tool.
What replaces the spreadsheet
Not necessarily software. Businesses reach for a resource management platform at this stage and frequently end up with an expensive tool maintained no better than the sheet it replaced, because the underlying problem was never the storage format.
What replaces the spreadsheet is a defined operating rhythm. A regular resourcing meeting with the same participants: someone who owns delivery, someone who owns the pipeline, someone with authority to decide. A standing agenda that covers what is committed, what is likely, where the constraints are, and what decisions are needed this week.
The artefact matters less than the cadence. A well-run weekly resourcing conversation working from an imperfect spreadsheet outperforms an elegant system nobody meets about.
Sequencing the change
Start by correcting available hours. Measure what a full-time person actually delivers over a quarter and use that number. This single adjustment usually explains most of the gap between the plan and reality, and it is uncomfortable because it reveals that the business has less capacity than it has been selling.
Then bring the pipeline into the same conversation, even crudely. Weighted opportunities with expected start dates, reviewed alongside committed work, will tell you more about the next quarter than either view provides alone.
Add skill constraints only for the roles where they genuinely bind, which is usually a handful of people rather than the whole team. Modelling every capability produces a system too detailed to maintain.
Only after that is running should you consider tooling, and by then you will know what you need it to do. The same order applies to reporting infrastructuregenerally: define the decision first, then build the thing that supports it. Businesses that get this right find the resourcing question stops being a source of anxiety and becomes what it should be, which is the input to hiring decisions made on evidence rather than on the feeling that everyone is busy.