Why Headcount Plans Fall Apart by Q2

Every January, I sit in the same meeting to review our staffing and workforce planning. The headcount plan looks clean. Every role maps to a business reason. Every start date lines up with a project kickoff. The total comp number ties perfectly to the budget the board approved. Everyone nods. Everyone signs off. Then Q2 closes, and that plan looks nothing like reality.

I have led FP&A and strategic finance teams long enough to stop being surprised by this. I have never stopped being annoyed by it, though. Staffing and workforce planning sits in a strange spot in the budget. The assumptions almost always break within ninety days. Yet most companies still treat the annual headcount plan like a fixed contract. It is not a contract. It is a forecast, built from a snapshot of the business in November or December. Business conditions rarely hold still that long.

A pattern you have probably lived through

Maybe you already know this pattern. A hiring manager tells you in Q4 that a role is locked in and funded. Then May arrives, and the search sits on hold, “pending a broader look at the org.” Or maybe you work in finance instead. You have to explain why a team is still short two people in June. That gap persists even though you approved the funding back in January. Both of you are living downstream of the same root problem. Everyone treated the plan as finished the day the board approved it. Nobody treated staffing and workforce planning as the start of a conversation that needed to run all year.

Let me walk through why this happens. I have watched it happen more times than I care to count, and I want to share what actually helps a plan survive past the first quarter.

Your January plan is a guess wearing a budget’s clothes

Here is the uncomfortable truth about annual staffing and workforce planning. You finalize a number in December. That number rests on assumptions about revenue growth, attrition, hiring speed, and shifting priorities. Those assumptions hold true for a moment. Then they start to decay the instant the fiscal year begins.

Sales tells you their pipeline supports twelve new account executives. Product says it needs six engineers to hit the roadmap. Customer success asks for four more specialists to protect response times. You gather these requests and run them through a model. You layer in an attrition assumption from last year’s data, and you land on a number. That number becomes gospel for the next twelve months.

None of the inputs hold still

None of those inputs stay static, though. Revenue comes in above or below plan. A key product bet gets reprioritized halfway through the year. A competitor changes the market overnight. Two senior people you were counting on resign in February. Q1 actuals close, and you pull up a variance report in April. The plan you built with such confidence in December already needs a rewrite.

This does not mean your planning discipline failed. It simply reflects how forecasting works when you model people and markets more than a quarter out. Most organizations do not fail by building an imperfect plan. They fail by treating that imperfect plan like a fixed commitment. A good plan behaves more like a living hypothesis, one that needs regular checks and honest updates as new information arrives.

Three cracks that show up almost every time

After enough cycles of this, you start to notice the same fault lines in staffing and workforce planning. They show up in nearly every headcount plan that unravels by Q2. I want to walk through the three I see most often. Name the crack early, and you can usually catch it before it splits the whole plan open.

The attrition assumption is one number pretending to be a model

Most annual plans bake in a single flat attrition rate, often somewhere between twelve and eighteen percent. They apply that rate evenly across every team and every month. That number looks tidy in a spreadsheet. It rarely reflects how people actually leave organizations.

Attrition does not spread evenly across the calendar. It clusters around bonus payouts and performance review cycles. It also clusters in the first few months of a new year, when people who have felt unhappy for a while finally act on it. CandorIQ’s 2026 workforce planning research cites Bureau of Labor Statistics data on this pattern. Roughly 3.3 percent of the workforce separates from its employer every month. That compounds to something close to one third of the workforce turning over across a full year, counting both voluntary and involuntary departures. Picture a plan that assumes attrition trickles out smoothly across twelve months. Now picture forty percent of that annual attrition actually landing in the first four months. Your headcount and your backfill budget fall out of sync before spring even arrives.

Hiring speed rarely matches recruiting capacity

The second crack runs quieter. Finance approves a headcount number. The plan rarely accounts for how long it actually takes to source, interview, and close a candidate. It also rarely accounts for how many searches your recruiting team can realistically run at once.

Picture this scenario. Your plan calls for forty new hires in the first half of the year. The average time to fill a role runs seventy five days at your company. Meanwhile, your recruiting team can only handle twelve open searches at a time. You have already built a bottleneck that no budget approval can fix. The org chart says the roles carry funding. The calendar says they will not fill anywhere near on schedule. By Q2, finance sees a headcount plan with far fewer people on payroll than budgeted. On paper, that looks like savings. In practice, delivery is usually just falling behind, wearing a favorable variance as a disguise.

The business plan moves and the headcount plan stays put

The third crack matters most. It is also the one I spend the most time discussing with my CFO. A headcount plan supports one specific version of the business plan: certain revenue targets, certain launch dates, certain market expansion timelines. Those underlying assumptions shift to some degree by Q2, almost every time. The headcount plan needs to shift right along with them.

Here is what usually happens instead. Leadership revises the business plan in a strategy meeting. Everyone agrees the new direction makes sense. The headcount plan keeps running quietly on the old assumptions, because nobody explicitly reopened it. Six months later, you notice the problem. A team of people is still supporting a product line that leadership deprioritized in March. Right next to them sits a team that is understaffed for the initiative that actually became the priority.

Approval steps quietly eat the calendar

A fourth crack does not get discussed as often. It has nothing to do with attrition, recruiting capacity, or shifting priorities. It comes down to the sheer amount of time that disappears between including a role in the annual plan and actually opening a requisition.

In a lot of organizations, an approved headcount number in the annual budget does not equal an approved requisition. Someone still has to submit the request. A department head has to sign off. Finance has to confirm the funding again. Someone else has to give final approval before recruiting can act. Each step can eat days or weeks. These steps often do not start until a manager gets around to them, sometimes in February or March, even for a role the company funded back in December. By the time the requisition finally goes live, a meaningful chunk of the year is already gone, and recruiting has not even opened the search yet. Nobody did anything wrong here. The process itself simply runs slower than the calendar the plan assumed.

Why the reckoning lands in Q2

A few forces converge around the second quarter. That convergence explains why staffing and workforce planning tends to unravel there, rather than trickling out evenly across the year.

Real numbers finally exist

Q1 actuals close, and for the first time you have real data instead of assumptions. Revenue either tracks to plan or it does not. You can see January and February attrition numbers in the system. You can finally measure time to fill on the roles you tried to open, instead of estimating it. This marks the first real moment in the year when finance can compare the plan to reality with any confidence. That comparison rarely flatters anyone.

Bonus season and the reforecast deadline collide

Most companies run merit increases and bonus payouts in Q1 or early Q2. That timing predictably triggers a spike in voluntary attrition, as people collect what they were waiting for and leave. Budget owners who quietly disagreed with headcount decisions made back in December start pushing back too. They feel the real impact on their team’s capacity now, not just in theory. Boards and leadership teams typically request a formal reforecast around this point in the year. That request forces every function, workforce planning included, into an honest reckoning between what actually happened and what the plan assumed.

Put those forces together, and Q2 becomes the moment when the gap between plan and business turns impossible to ignore. The plan did not actually break in Q2. It broke gradually, starting back in January. Q2 simply forces everyone to look at it directly.

What I actually do differently now

I used to treat the annual headcount plan the way most finance teams do. Build a number once a year, then defend it for twelve months. That is not how I work anymore. The shift has meaningfully improved how credible our staffing and workforce planning process feels to the rest of the business.

I rebuilt how we model attrition and capacity

I stopped relying on a single attrition number. Instead, we model attrition by function and by quarter, using historical patterns specific to each team rather than one company wide average. Sales attrition does not behave like engineering attrition. Attrition in Q1 does not behave like attrition in Q4. A plan that respects those differences holds up far better under scrutiny.

I also connect every headcount request to a capacity constraint, not just a budget line. Before we approve a requisition, we ask how long it will realistically take to fill. We factor in current recruiting bandwidth and the difficulty of the role. If the honest answer says a role will not fill until September, we plan the year around that reality. We do not pretend the person starts in March just because the org chart says so.

I built a monthly review cadence

Instead of an annual review, we revisit the headcount plan every month, not just at the formal quarterly reforecast. That does not mean it changes every month. Most months the review simply confirms the plan still holds. But when something does shift, whether that is an attrition spike, a reprioritized product line, or a revenue miss, we catch it within weeks. We no longer discover it buried in a Q2 variance report months after the drift began.

I also treat reforecasting as normal now, not as failure. This might be the biggest mindset shift of all. Early in my career, I saw a midyear headcount revision as proof the original plan was badly built. Now I see something else as the real red flag: an annual plan that never gets revised at all. Markets move. People leave. Priorities change. A workforce plan that cannot flex with that reality is not disciplined. It is simply outdated.

I closed the gap between HR, finance, and recruiting

Finally, I bring HR and finance into the same room from the start, instead of after something breaks. So much of the disconnect between staffing plans and financial plans comes from one thing. HR and finance work off separate models, and those models only get reconciled once a problem forces the conversation. Recruiting, HR business partners, and finance now build the workforce plan together from day one. We share assumptions about attrition, time to fill, and business priorities. The plan simply starts out more honest, and far fewer surprises wait for us in Q2.

The distance between an approved budget line and a live requisition also got shorter. We cut the approval chain down to what we truly needed. A set of roles now gets pre approved at the start of the year, so managers are not waiting on a fresh signature for every hire the plan already funded. That single change bought us weeks, sometimes months, on roles that used to sit idle simply because nobody had gotten around to the paperwork.

A simple way to think about it going forward

Here is the one reframe I want every finance leader and every people leader to take from this. Staffing and workforce planning is not a single decision you make once a year. It is an ongoing exercise in matching people capacity to business need. Business need does not sit still for twelve months just because the budget calendar says it should.

Build the January plan with the best information you have. Then treat every following month as a chance to check that plan against what is actually happening. Do not treat a revision as a threat to the plan’s integrity. Model attrition with more nuance than a single flat rate. Be honest about how long hiring actually takes, given your real recruiting capacity. Keep the workforce plan tethered to the current version of the business plan, not the version that was true when the budget was first approved.

None of this makes headcount planning easy. Staffing and workforce planning will always involve forecasting something inherently unpredictable: human behavior, inside a moving business. But it does make the Q2 reckoning a lot less painful. By the time you get there, you have already been adjusting all along, instead of discovering everything at once.

Frequently Asked Questions

Why do headcount plans typically break down by the second quarter?

In staffing and workforce planning, Q2 marks the first point in the year with real data to compare against the plan. Q1 actuals have closed. You can see attrition patterns from the first few months, and most companies run a formal reforecast around this time. The plan does not actually break in Q2; it has usually been drifting since January. Q2 simply makes the gap too large to ignore. Research from SHRM on strategic workforce planning points to a similar pattern. Ninety two percent of organizations consider workforce planning important, yet only forty two percent consider themselves effective at it. That gap tends to surface once real quarterly data shows up.

What is the biggest mistake finance teams make when building an annual headcount plan?

They apply a single, flat attrition rate across every team and every month of the year. Attrition clusters around bonus cycles and the start of the year far more than a smooth annual average suggests. Model attrition by function and by quarter instead of using one company wide number. You get a far more resilient plan.

How often should a workforce plan get reviewed?

Review it monthly, at minimum, even if the formal reforecast only happens quarterly. A monthly review does not force constant change. Most months will simply confirm the plan still holds. But it catches drift within weeks rather than months, whether that drift comes from attrition, hiring delays, or shifting business priorities. That timing makes the fix far easier.

Does reforecasting headcount midyear mean the original plan failed?

No, and this belief causes real damage in traditional budgeting culture. A workforce plan that never needs adjustment usually just means nobody checked it against reality. It rarely means the original plan was perfect. Business conditions shift constantly. A staffing and workforce planning process that cannot adapt to that shift creates more risk than one that reforecasts on a regular basis. Analysis from American Recruiting and Consulting Group on midyear workforce reforecasting makes a similar case. It describes structured reforecasting as a way to protect revenue and delivery, not as an admission of failure.

How should HR and finance work together to make headcount plans more accurate?

Build the plan jointly from the start, rather than reconciling separate models after a problem surfaces. Recruiting, HR business partners, and finance should share assumptions about attrition, time to fill, and business priorities from day one. That alone removes most of the surprises that typically show up midyear. CandorIQ’s workforce planning research makes the same point. Workforce plans built with cross functional input from the outset hold up meaningfully better than plans one department builds alone.

What role does hiring speed play in why headcount plans slip?

It plays a large role in staffing and workforce planning, and teams often overlook it. A budget approval does not account for how long it actually takes to source, interview, and close a candidate. It also does not account for how many searches a recruiting team can realistically run at once. A plan that assumes instant hiring the moment you approve a role will almost always show a gap by Q2. That gap shows up between budgeted and actual headcount, even when nothing about the underlying business changed.

References

1. SHRM Labs, “Strategic Workforce Planning: Navigating the Future of HR”
2. American Recruiting and Consulting Group, “H2 Workforce Planning Under Tight Headcount: A 90 Day Playbook to Protect Revenue and Delivery”
3. Sybrid, “90% of HR Leaders Struggle With Workforce Planning in 2026”
4. CandorIQ, “Strategic Workforce Planning Guide for Professionals in 2026”
5. HR Executive, “HR Leaders on 5 Workforce Planning Strategies That Turn Talent Into Competitive Advantage”