Blog Capacity
The resourcing meeting costs more than you think
Nobody budgets for this meeting. It is the most expensive one you run and the one that produces the fewest decisions per minute spent.
The meeting nobody decided to have
The pattern shows up in almost every professional services firm past twenty people. Each team meets for an hour a week to review who is on what. Then the project leads meet for another ninety minutes to consolidate, reading allocation percentages out loud while somebody types them into the planning tool.
Nobody chose this. It accreted. First it was three people talking for five minutes, then the team leads had to be in the room, then a tool arrived and someone had to spend time filling it in. At some point it became a fixed calendar block that goes unchallenged because it simply has to happen.
What is interesting is that most of the time is not spent deciding anything. It goes on reading out information that already exists somewhere so the rest of the room has it. That is the part you can remove.
The arithmetic, with the assumptions on the table
The numbers below describe a mid-sized firm. Swap in your own — the method is the point, not the specific figure.
- Team meetings. Six teams, six people each, one hour a week. That is 36 person-hours weekly.
- Consolidation meeting. Six project leads, ninety minutes. Another 9 hours, at rates well above the average.
- Cost per hour. Not salary — fully loaded cost. At a loaded cost of £66,000 a year over roughly 1,700 working hours, that is about £39 an hour. Call it £55 for the leads.
- Weekly total. 36 × £39 + 9 × £55 = £1,900 a week.
- Annual total. Across 46 effective weeks, roughly £87,000 a year. That is one senior hire spent entirely on shuffling people.
What you can cut, and what you cannot
It is worth being straight here, because the easy promise — eliminate your resourcing meetings — does not hold up. Three separate things happen in that room and only two of them are waste.
The first is informing: who is on what, how much capacity is free, which project ends in three weeks. This should not be delivered in a meeting. It is a state, and a state gets looked up.
The second is transcribing: reading percentages aloud so someone can enter them. This is manual data movement and it is indefensible. The person who knows the number should enter it directly, at the moment they know it, not on Thursday.
The third is deciding: who goes on the new engagement, what to do with the person free in October, whether to take the work that came in yesterday. That is a genuine conversation and it is not going away. But it takes twenty minutes rather than two and a half hours once everyone arrives already informed.
What has to be in place before you can shrink it
The meeting exists because the data lives nowhere you can look it up. To reduce it, the order matters and you cannot skip steps:
- Projects carry declared start and end dates. Without them there is no way to know who comes free and when, and the meeting stays the only place that knowledge exists.
- Allocations carry a percentage, not a yes or no. Half the people in a consultancy are split across engagements, and without percentages you cannot add anything up.
- Planned absence is loaded and deducted automatically. If August holiday does not appear in the capacity plan, the capacity plan is wrong in August.
- Each lead edits their own slice directly. If it still has to go through one person who types, you have relocated the meeting rather than removed it.
How you know it is working
The meeting does not vanish from the calendar. It changes content.
When it works, nobody arrives to find out what is happening. Everyone has looked at the plan beforehand, and the room gets used for the three or four calls that genuinely need shared judgement: the engagement that has gone sideways, the person who could go to either of two places, the opportunity that needs a yes or a no.
There is a second symptom, harder to measure and worth more: you stop saying «let me come back to you Thursday» when someone asks whether you can take the work.
Frequently asked questions
Is a spreadsheet not faster?
For eight people and two projects, yes, and you should not change anything. The spreadsheet breaks when several people need to edit it at once, when it has to be cross-checked against absence, and when someone needs six-week-out availability without opening the file. That is the point where it turns into the meeting.
What if my team does not track time?
Capacity planning does not require time tracking to work. It requires allocations with percentages and project dates. Time tracking is what comes next, when you want to compare what you planned against what actually happened. Starting with planning alone is perfectly reasonable.
How long does it take to set up?
Loading people and projects is an afternoon with a template. The slow part is getting leads into the habit of updating their slice when something changes, instead of saving it for the meeting. That takes a few weeks and depends more on habit than on tooling.
All of this is built into Fichaloto. See how it works.
Keep reading
Capacity
Planned, clocked, charged: three numbers that should match and usually do not
Most companies can tell you what they planned and what they invoiced. Very few can tell you, for a given week, whether those two things are related.
Capacity
Being allocated at a hundred per cent is not billing at a hundred per cent
Most arguments about utilization are really arguments about what is being measured, and nobody has said so out loud.
Capacity
Before accepting a project: how to check whether the team can deliver
You need three numbers: the hours the project will need each month, the free hours your team has in those months, and a buffer. Almost nobody has the second one.