Headcount Planning: Attrition, Backfills, Fully Loaded Cost, and Payroll Reconciliation

"You use law of big numbers. Consolidate to a higher level and you'll get to a point where you'll always have some level of turnover. Replace role in Department A, and then someone in Department B will resign by then. So yes, use average salary. Usually it becomes a constant negative payroll for the full year."

— Source: r/FPandA (24 upvotes)

For most FP&A teams, headcount is one of the biggest budget line items: 60-80% of total operating expenses at many companies.

Yet, getting headcount right is hard. You need to account for attrition (people leaving), backfills (time to replace them), merit increases (raises), promotions, and new hires. And all of this feeds into payroll, which finance must reconcile to the actual payroll system.

This guide walks through how to build a headcount plan that is realistic, ties to payroll, and accounts for the messiness of hiring, firing, and turnover.

Why headcount planning matters

• Largest expense: Payroll and benefits are often the largest line in OpEx. Get headcount wrong, and your entire budget is off.
• Cash impact: Hiring timing, ramp time, and severance costs affect cash forecasts.
• Capacity constraint: The number of engineers, salespeople, or support reps determines what the business can deliver. Headcount plans should align to revenue/growth targets.
• Complication: Unlike most expenses (rent, software), headcount changes constantly: people quit, get hired, get promoted, move to different departments.

The three questions

A good headcount plan answers:

• How many people will we have each month? (accounting for attrition, new hires, transfers)
• What will we pay them? (base + bonus + benefits + payroll taxes)
• Does this align to our strategy and budget targets? (if we hire 10 engineers, does that deliver the product roadmap?)

Most FP&A teams struggle with the first two. The third is usually owned by operations/CEO, but finance must validate it.

The challenge: predicting who will leave

You don't know which individual will quit. But you can estimate the attrition rate: the percentage of your workforce expected to leave in a given period.

Example: You started 2025 with 100 employees. By end of June, 5 employees had left. Average HC for H1: 98. Attrition rate: (5/98) × 100 = 5.1% for the first half of the year.

How to forecast attrition

• Use historical data: Look at the past 12-24 months. What was your attrition rate? Is it stable or trending?
• Break it down by department: Some departments have high turnover (sales, customer support), others low (engineering, finance). Different departments have different rates.
• Adjust for current environment: If the market is hot (tech booming), attrition may increase. If layoffs are happening across the industry, attrition may drop.
• Factor in known departures: If you know someone is leaving in Q2, don't estimate it; include it as a known fact.

Illustrative example: 200-person company, average attrition rate 15% annually (typical for most industries).

• Expected departures per year: 200 × 15% = 30 people
• Monthly attrition assumption: 30 / 12 = 2.5 people per month
• If Sales has 20% attrition and Engineering has 10%, Sales will lose 1.5 people/month and Engineering 1 person/month.

A note on conservatism

Most FP&A teams are conservative: they don't explicitly forecast attrition. Instead, they treat attrition as a savings opportunity. They budget headcount at full staffing, but know that attrition will reduce spend during the year.

One Reddit practitioner explains: "You don't forecast attrition unless you 100% know it is happening. Attrition sits as a savings opportunity in the model. If you forecast attrition, you're saying 'we expect someone to quit and we won't replace them immediately.' Usually you bump up forecasted quota over real quota to account for attrition anyway."

This approach is pragmatic: it avoids the awkward conversation of "we're expecting some of you to quit," while acknowledging that some amount of headcount savings will occur.

What is time-to-fill?

For example: Sarah in Sales quits on June 30. You post the job on July 1. You interview candidates in July. You make an offer on July 30 (30 days). The new person starts on August 15 (46 days total). Time-to-fill: 46 days.

Typical time-to-fill by role

• Sales: 45-90 days (competitive, needs ramp time)
• Engineering: 60-120 days (long lead, sourcing is hard)
• Support/Operations: 30-45 days (easier to fill)
• Finance/Accounting: 45-75 days
• Leadership/executive: 90-180 days (very long, external search often needed)

These are illustrative. Your company may be faster or slower based on recruiting capabilities and market demand.

Modeling backfills

When an employee leaves, the backfill approach depends on your situation:

• Replace immediately: Post the job same day. Budget for a vacancy period (30-60 days) where the role is empty, then the new hire starts.
• Don't replace: If budget is tight or the role is no longer needed, don't backfill. The person's salary stays in the budget as a savings.
• Consolidate: Combine the departing role with another role or redistribute the work. No backfill needed.

In a headcount model, backfills look like this:

• Month 1: Employee A departs. HC drops by 1. Budget salary reduced by 1/12 × annual salary (prorated for partial month).
• Months 2-3: Vacancy period (60 days). HC remains down by 1. Budget remains reduced.
• Month 4: New hire B starts. HC goes back up by 1. Budget salary returns to normal.

If the new hire has a different salary (e.g., because they're a different level), adjust accordingly.

What is fully loaded cost?

Salary alone is only part of the story. When budgeting headcount, you must include the full cost.

What goes into fully loaded cost

Calculating fully loaded cost

Illustrative example: Software engineer with $120,000 base salary

This engineer's base salary is $120K, but the fully loaded cost is $197.8K. This is what should go in your headcount budget.

The multiplier (165% in this example) varies by company:

• Service/consulting firms: 1.5-1.8x (higher benefits, bonus, overhead)
• Tech startups: 1.4-1.6x (lower overhead allocation)
• Manufacturing: 1.3-1.5x (lower benefits, lower bonus)
• Non-profits: 1.3-1.5x (lower bonus)

Calculate your company's multiplier by dividing total payroll (salary + bonus + benefits + taxes + overhead) by total salary. Use this to convert headcount to payroll dollars.

Simple approach: Person-level for small companies (under 150 HC)

For small companies, list every person:

• Column A: Employee ID or name
• Column B: Department
• Column C: Job title
• Column D: Start date
• Column E: Departure date (if applicable)
• Column F: Annual salary
• Column G: Fully loaded cost
• Columns H-S: Monthly HC count (is this person employed in this month?), 1 or 0

Then, total each month column to get monthly HC, and sum fully loaded cost × HC count to get monthly payroll.

This approach is transparent but becomes unwieldy at 200+ people.

Scalable approach: Department and role level

For larger companies, group by department and role:

• Row: [Department] [Job Title]
• Column A: Current HC
• Column B: Average salary
• Column C: Fully loaded cost
• Column D: New hires (planned)
• Column E: Departures (estimated)
• Column F: Time-to-fill (months)
• Columns G-R: Projected HC by month

Example:

From this, you can calculate: "January payroll = (8×$247.5K) + (5×$165K) + (10×$228K) + (2×$115.5K) = $4.3M"

One Reddit practitioner notes: "At 80 headcount you should be using actual people plus actual salary, then roll forward for leavers and joiners. Role title at avg salary banding is if you have too many people to forecast person by person."

The challenge

Your headcount model says: "We have 150 people, fully loaded cost is $25M/year, so monthly payroll should be ~$2.08M."

But actual payroll comes from the payroll system, and it often doesn't match your forecast. Why?

• Ramp time: New hires don't start on day 1. There's lag between the hire date and the start date.
• Severance: When someone is laid off, they may get severance, which shows up in payroll but isn't ongoing salary.
• Bonuses: Annual bonuses may be paid in January or December, not evenly throughout the year.
• Benefits changes: Mid-year benefits elections or changes affect the fully loaded cost.
• Raises and merit increases: Raises may happen mid-year, but you budgeted for the old salary.

How to reconcile

• Validate HC count: Pull the headcount roster from HR each month. Compare actual HC to your model. Are they the same?
• Validate pay rates: Spot-check a few employees' pay rates against your model. Are they correct?
• Reconcile totals: Sum your model payroll for the month. Compare to actual payroll from the payroll system. What's the difference?
• Investigate gaps: If model says $2.08M and actual is $2.12M, you're over by $40K. Why? New hires you didn't capture? Bonus paid? Severance?
• Update assumptions: Once you understand the gap, update your model: "New hires ramp over 2 months, not 1." or "We always pay Q2 bonuses in April."

The goal: your model headcount and payroll forecast should tie to actual payroll every month, with every difference explained (timing of hires, leavers, bonuses, benefits true-ups). Agree a tolerance with your CFO and investigate anything outside it.

Common reconciliation issues

• HR and Finance have different HC counts: HR counts "people on the payroll." Finance may count FTEs (full-time equivalents), including part-timers as 0.5. Agree on a definition.
• Contractor spend vs HC: Contractors and freelancers show up in OpEx, not payroll. Make sure you're comparing like-to-like.
• Payroll timing: Payroll may be processed on different dates than the month end. Account for this lag.
• GL vs payroll system: The general ledger payroll account and the payroll system may record differently. Finance reconciles both.

Consumer brands must tie headcount to operational capacity: revenue, orders, customers, SKUs. Unlike SaaS (where headcount is often fixed by role), consumer brand headcount scales with physical output.

Headcount planning template for consumer brands (example assumptions)

Example staffing ratios and assumptions: The following are illustrative assumptions only. Your actual ratios depend on automation, outsourcing, geography, and growth rate. Build a model with your own data and update as you scale.

Illustrative example: Headcount and payroll growth from $8M to $12M revenue

Example assumptions: A beauty brand currently at $8M revenue is forecasting growth to $12M by end of year. Using example staffing ratios from above, here's a headcount and payroll build:

Payroll impact analysis: Growing from $8M to $12M ($4M growth = 50%) requires +12.5 FTE (36% headcount growth). Incremental payroll is $730K, or 18% of the $4M of new revenue. Compare that with the contribution margin on the new revenue: if new revenue earns less than 18% contribution after variable costs, the growth plan loses money before any other fixed cost.

Timing matters: Hire support reps by August to meet Q4 demand (account for 30-day ramp). Hire warehouse staff by July (60-day ramp for training). Add buyer in August for SKU complexity. Wait until Q3 to add account manager (60-day fill, start in October for Q4).

Important: These are illustrative example ratios. Your company's staffing ratios depend on automation level, outsourcing, headcount specialization, and growth rate. Build your model with your own data. If your reps handle 400 tickets a month rather than 600, the same growth needs 30 reps instead of 20. If you outsource fulfillment to 3PL, headcount doesn't scale with orders.

Headcount is often the largest line in an operating budget, yet many finance teams forecast it loosely: "add 10% headcount growth, assume average salary, done."

The problem: one wrong assumption (time-to-fill is 60 days, not 30) and your entire payroll forecast is off. By mid-year, you're 5% above budget with no way to explain it.

Best-in-class FP&A teams build detailed headcount models that account for attrition, backfills, ramp time, and fully loaded cost. They reconcile monthly to actual payroll. When headcount needs change (new hire, departure, promotion), the model updates, and they see the payroll impact.

For consumer brands, this is critical: headcount directly impacts capacity (how many orders can fulfillment handle?) and margin (payroll is a large % of COGS/OpEx). Forecasting it accurately is the difference between running out of capacity mid-quarter and being prepared.