Resourcing Q4 Before You Commit to It: A Capacity Check

Every Q4 plan looks reasonable on the slide where it's a list of initiatives. It stops looking reasonable the moment someone lays those initiatives against the actual calendar of the people who have to do the work — and by then the plan has usually already been approved, announced, and staffed against a version of the team's time that doesn't exist. A capacity check is the step that happens between "here's what we want to do in Q4" and "here's what we're committing to," and skipping it is the single most common reason Q4 plans collapse in November rather than October.

Capacity is not headcount

The first mistake is treating capacity as a headcount question — we have twelve people, therefore we have twelve people's worth of Q4. Real capacity is headcount minus everything that already has a claim on that time: planned time off, the holidays that fall inside the quarter, ongoing support and maintenance work that doesn't show up on a project list because it's "just part of the job," onboarding time if anyone new joined recently, and the overhead of whatever meetings and reporting the organization already runs. A twelve-person team rarely has more than nine or ten people's worth of genuinely available project time in a quarter that includes a major holiday stretch, and the gap between twelve and ten is exactly where overcommitment lives.

The fix is mechanical rather than clever: before assigning anything, have each team lead estimate, in days, how much of each person's Q4 is already spoken for by recurring work, approved time off, and known obligations from other initiatives. Subtract that from the total available working days in the quarter. What's left is real capacity, and it is reliably smaller than what the planning slide assumed.

Match initiatives to the calendar, not just the total

A capacity number that adds up on paper can still be wrong in practice, because Q4 is not a smooth block of time — it has a hard stop around the holidays, and most organizations lose real productive days to end-of-year administrative work, performance reviews, and the general slowdown that starts building in mid-December whether anyone plans for it or not. An initiative that assumes eleven working weeks when the actual usable stretch is closer to eight is set up to fail before it starts.

Lay the quarter's initiatives against an actual week-by-week calendar, not a total day count, and check for pileup: does everything important land in the same four-week window because that's when the deadlines were set independently of each other? Pileup is invisible in a list and obvious on a calendar, and it's the difference between a team executing steadily and a team sprinting into a wall in early December.

The honest conversation about trade-offs

A capacity check that produces a shortfall — and it usually does, the first time an organization runs one seriously — forces a conversation that a lot of leadership teams would rather not have: which of the things on the list don't happen this quarter. The instinct is to solve the shortfall by asking people to do more, which works exactly once and costs more than it returns, because the team that sprints through an overcommitted Q4 arrives in Q1 depleted, and the initiatives that got squeezed through under pressure tend to need rework anyway.

The better conversation is explicit trade-offs, made in October rather than discovered in December: if we're doing the new initiative, what gets deprioritized to make room for it, and who is agreeing to that deprioritization out loud. This is uncomfortable in a way that silent overcommitment isn't, which is exactly why silent overcommitment is the more common failure mode — it feels like agreement because nobody objected, when what actually happened is that nobody did the math.

Build in slack on purpose

A capacity plan that allocates one hundred percent of available time to committed work has zero room for the things that always show up mid-quarter and were never on the list: the urgent customer issue, the person who gets sick for a week, the initiative from Q3 that wasn't quite finished. Teams that plan to full capacity aren't more ambitious than teams that don't — they're just one bad week away from every commitment slipping simultaneously, because there's no buffer to absorb the shock.

A reasonable target is planning to somewhere around eighty to eighty-five percent of calculated capacity for committed initiatives, leaving the rest as acknowledged slack rather than pretending it doesn't exist. This isn't padding for its own sake; it's the difference between a plan that bends when reality intrudes and one that breaks.

Revisit it at the midpoint

A capacity check done once in early October and never looked at again is only half useful. Set a short checkpoint around the midpoint of the quarter — not a full replanning exercise, just a look at whether the actual pace of work matches the assumed pace, and whether anything unplanned has already eaten into the slack that was built in. Catching a five-day overrun in mid-November, while there's still runway to adjust scope or timeline, is a manageable conversation. Catching the same overrun in the second week of December, when the holiday shutdown is bearing down and there's no time left to absorb it, is a crisis that a fifteen-minute midpoint check would have prevented.