Monday morning, the week plan is open, an urgent project is in the queue, and it feels like “it will fit.” On Thursday the shock arrives: a regional holiday half the team followed, someone in training, another person off in the middle of the sprint. The plan looked good on paper. The capacity was theoretical.
That scene repeats in consultancies, agencies, and service companies. Not for lack of goodwill. For lack of a number that already discounts what real life takes out of the calendar.
Spreadsheet capacity is not team capacity
The classic math is simple: 8 hours × 5 days × N people. It gives a pretty ceiling. Nobody lives that ceiling.
There is a local holiday, vacation, a day off, onboarding, someone who works 6 hours, someone who on Thursday was already on another client. When you promise a deadline with a full ceiling, you are promising with people who will not be there.
The result is familiar:
- a schedule with no real slack;
- overload on some people and idle time on others;
- rework to redo the plan in the middle of the week;
- a conversation with the client based on an estimate, not on availability.
Planning capacity for real is not “how many weekly hours this person has on their badge.” It is crossing what was expected that day with what was already logged — and with the day the person should not even be logging.
Why instinct scales badly
While the team is small, the manager holds the calendar in their head. It works until the first holiday crosses two late projects.
Then the shortcuts start: one spreadsheet for vacation, another for holidays, allocation on the meeting slide. Each source is late in its own way. At close, nobody can say whether the hole was a lack of people or a lack of time entries.
Treating this as discipline (“write down the days off”) does not solve it. A day off noted in the group does not enter the math of the next project.
Four steps to plan with a number, not with instinct
1) Set each person’s capacity
Hours in the day, days of the week, exceptions. Without that, any dashboard lies. In RabbitWork this lives on the user record — the steps are in set user capacity.
You do not need a sophisticated rule in the first month. You need an honest ceiling: someone who works 6 hours cannot show up as 8.
2) Put holidays and absences in the same place as the hours
If the holiday lives on a separate spreadsheet, it does not enter planning. Holidays and absences on the account calendar (and on the person) are what turns “theoretical capacity” into “who is available on Tuesday.”
Before you promise a deadline, the question becomes: who can actually work on those days?
3) Look at the person × period grid every week
Once a week, compare what was expected with what was logged. Did someone stay under the ceiling (they did not log)? Did someone go over (ghost hours or overload)? Did someone log on a day with no capacity (Saturday, a day off, vacation)?
The people capacity dashboard is that grid: a bar of what was logged against the day’s ceiling. A registered absence shows up in the cell. It does not replace the report by client — it answers another question: did the person log on the day they were supposed to.
People capacity dashboard
4) Use the number to negotiate, not only to chase
Capacity serves to protect the team. “We cannot pull one more project this fortnight” is a better sentence when it comes from a visible ceiling, not from an impression.
If a total looks odd, open the entries behind that number and decide whether the problem is the time entry or the real load.
What changes when capacity is real
You stop discovering the holiday on Thursday. You distribute load before exhaustion. You negotiate the deadline with the client without inventing slack afterward.
Capacity management and the holiday calendar arrived in RabbitWork in 2026 — the history is in the Changelog. The ritual is weekly: an honest ceiling, absence on the calendar, the grid open, the decision on the number.
If your planning still fits in 8 × 5 × N, it is worth seeing how this looks in RabbitWork at rabbitwork.io.
