Why Headcount Plans Fall Apart in the Second Quarter

Headcount plans fall apart in the second quarter because they were built on two assumptions that are never true: that hiring happens evenly across the year, and that nobody leaves. By month five you are usually behind on hiring, down a person or two you did not plan to lose, and the plan on the wall no longer describes anything.

The short answer is that a plan which lists twelve roles across twelve months is not a plan. It is a wish. A plan that survives is one that says which roles are load bearing, which are optional, and what happens when two people resign.

The three assumptions that break

Hiring is not evenly spaced

Annual plans divide roles neatly across quarters because a spreadsheet makes that easy. Real hiring clumps. You get three good candidates in one month and none for the next two. Notice periods stack up. Someone accepts and then does not join. By the end of the first quarter you are not slightly behind, you are behind on the specific roles that were meant to unblock everything else.

Attrition is not in the plan at all

Most annual plans have a line for new roles and no line for replacement. Yet somebody will leave. Not as a pessimistic forecast, just as arithmetic across a team of any size. When it happens, the replacement hire competes with the growth hire for the same recruiter, the same interview slots and the same manager's attention. Growth loses, because a gap hurts today and a new role hurts later.

Ramp time is treated as zero

A role filled in month four does not produce in month four. It produces somewhere later, and in the meantime it consumes reviewer time and manager time from people who were already busy, which is most of what a first month actually costs. Plans that count a start date as a capacity date are always optimistic by a quarter.

What actually happens by month five

The pattern is consistent enough to be worth naming.

• Two or three roles are open longer than planned
• At least one person has resigned, usually one you would rather keep
• The manager who was going to do the interviewing is now covering the gap
• A hire made in month two is still ramping and needs more support than expected
• Somebody senior is quietly doing three jobs and has not said so

Nothing in that list is a failure. It is the normal shape of a year. The problem is only that the plan did not describe it.

How to write a plan that survives

Rank the roles, do not just list them. For each role, answer one question: what stops if this is not filled? If the honest answer is "nothing stops, we just go slower", label it that way. When the year gets tight, you want to know in advance which roles you were always willing to defer, rather than making that decision under pressure in month six.

Put a replacement line in the plan. Not a name, just a placeholder acknowledging that some hiring capacity in the year will go to backfill. This changes the conversation with finance from "we missed the plan" to "we used the buffer we said we would need".

Write down the two person exit scenario. Pick the two people whose leaving would hurt most and write half a page on what happens. Who covers, what pauses, what gets outsourced, which deadline moves, and whether a contractor would cover the gap better than a permanent hire. Doing this in a calm month takes an hour. Doing it in a bad week takes a fortnight and produces worse answers.

Stagger the start dates you control. Two people starting the same week costs more than two people starting three weeks apart, because the onboarding load lands on the same person twice. If someone is arriving from abroad, have the salary account conversation ready before their first week.

Review at the quarter, not at the year. A plan reviewed once a year is a document. A plan reviewed at the quarter, where roles get moved, dropped or promoted in priority, is a tool.

The visibility problem underneath

Most of this is harder than it should be because the information sits in three places. Open roles are in one system, the people already on the team are in another, and what those people are actually working on is in a third. So the question "if this person leaves, what stops" takes someone a day of digging.

That is the case a workspace like SicherOne argues for: projects, HR records and AI agents on one set of records, so who is on leave, who owns what, and who is covering are answerable in one place rather than three. A person still makes every judgement call about who to hire and when. The plan just gets easier to check against reality.

The one habit worth keeping

Once a quarter, write two sentences next to each open role: why it is still open, and what has not happened because of it. If you cannot write the second sentence, the role may not be needed. If you can write it easily and it is serious, that role should have moved up the list a month ago.