Why you need an annual hiring plan
Most companies recruit reactively. A manager submits a requisition when someone quits or when the workload becomes unbearable. HR scrambles to source candidates, negotiate with finance for budget approval, and fill the role under time pressure. The result is longer time-to-fill, higher cost-per-hire, and worse candidate quality.
An annual hiring plan reverses this sequence. Instead of reacting to departures and growth pressure, you anticipate them. You enter the year with approved headcount, allocated budgets, and a quarterly timeline that tells recruiters exactly when to start sourcing for each role.
The benefits are measurable. Companies with formalized hiring plans report 20 to 30 percent shorter time-to-fill because sourcing starts before the need is urgent. Budget surprises disappear because every hire is pre-approved with a salary range. Hiring manager satisfaction improves because they see their requests reflected in a concrete plan with dates attached.
The plan also protects you during downturns. When the CEO asks "can we pause hiring for Q3?" you can show exactly which roles would be affected, what the business impact would be, and which roles are non-negotiable. Without a plan, these conversations devolve into politics rather than data.
An annual hiring plan is also a recruiting team capacity tool. If your plan calls for 40 hires across the year with a typical 45-day time-to-fill, your two recruiters will each manage roughly 5 active requisitions at any given time. That is sustainable. If the plan calls for 60 hires, you need a third recruiter or agency support. The plan makes this visible before capacity becomes a bottleneck.
The template structure: what goes where
An effective annual hiring plan has five sections. Each one answers a specific question that stakeholders care about.
| Section | Answers | Primary audience |
|---|---|---|
| Executive summary | How many hires, total cost, strategic rationale | C-suite, board |
| Department breakdown | Which roles, what level, what department | Hiring managers, HR |
| Budget allocation | Salary ranges, benefits load, recruiting costs | Finance, HR |
| Quarterly timeline | When each role opens, target start dates | Recruiters, hiring managers |
| Review cadence | When to compare actual vs. plan, who leads | HR leadership |
The executive summary should fit on one page. It states the total planned hires for the year, the total budget required, and the business rationale (e.g., "35 hires to support 40% revenue growth target, including 12 backfills for projected attrition"). This page is what gets approved or rejected. Everything else is supporting detail.
Keep each section self-contained so stakeholders can review only their relevant portion. Finance does not need to read individual role justifications. Hiring managers do not need the company-wide budget rollup. Structure the template so each audience finds their answers without wading through irrelevant detail.
Department-by-department planning
The department breakdown is the core of your hiring plan. For each department, document every planned hire with enough detail that a recruiter could start sourcing immediately.
For each role, capture: department, role title, seniority level (junior/mid/senior/lead), hire type (new headcount or backfill), justification (one sentence explaining why this role is needed), target start date, estimated salary range, hiring manager name, and sourcing strategy (internal promotion, external hire, agency, referral).
Engineering example: You have 18 engineers today. Historical attrition is 20%, so expect to lose 3 to 4 people. The product roadmap requires two new feature teams, adding 6 engineers. Total engineering hires for the year: 9 to 10. Break this down by quarter based on product milestones: 3 in Q1 (backfills for recent departures), 3 in Q2 (first new feature team), 3 in Q3 (second feature team), 1 in Q4 (buffer for unexpected attrition).
Sales example: Current team is 12 account executives. Revenue target requires 40% more pipeline capacity. That means 5 net-new AEs plus 2 backfills for expected turnover. Ramp time is 3 months, so Q1 hires generate revenue in Q2. Front-load sales hiring to maximize revenue impact: 4 hires in Q1, 2 in Q2, 1 in Q4.
Support functions: Finance, legal, HR, and operations typically grow at a slower rate. Plan these roles based on employee-to-support-staff ratios. A common benchmark is one HR generalist per 75 to 100 employees. If you are growing from 100 to 150 employees, you need one additional HR hire. These roles are often the first to be deferred during budget pressure, so document the consequences of deferral: increased workload on existing staff, compliance risk, or delayed employee support.
This level of detail prevents the most common hiring plan failure: vague entries like "2 to 4 engineers, sometime in H2." Vague entries do not get budget approval, do not trigger recruiter action, and do not produce hires. Every row in your plan should have a specific role title, a specific quarter, and a specific salary range.
Budget allocation and cost modeling
Finance will reject any hiring plan that does not include a clear budget model. Here is how to build one that survives scrutiny.
Total cost per hire formula: Base salary + benefits load (25-35% of base) + recruiting cost (agency fees, job board spend, ATS cost allocation) + onboarding cost (equipment, training, ramp-period productivity loss). For a mid-level engineer with a $90,000 base salary, the fully loaded cost is approximately $125,000 to $135,000.
| Cost component | Typical range | How to estimate |
|---|---|---|
| Base salary | Market benchmarks | Use salary surveys, internal pay bands |
| Benefits load | 25-35% of base | Ask finance for your company's actual rate |
| Recruiting cost | $3,000-$8,000 per hire | Job boards + ATS + agency (if used) |
| Onboarding cost | $1,000-$5,000 | Equipment, training, ramp time |
| Contingency | 10% of total | Market-rate adjustments, unplanned hires |
Partial-year cost calculation. A hire starting in July costs only half the annual salary in year one. Your budget model should calculate costs from the target start date through December, not assume full-year costs for every hire. This distinction can reduce your budget request by 20 to 30 percent and makes finance more likely to approve the plan.
For ATS costs specifically, Treegarden's flat-rate pricing simplifies this calculation. At $299/month for the Startup plan with unlimited users, the per-hire cost decreases as hiring volume increases. There is no per-seat surcharge when you add hiring managers or interviewers to the platform. Compare this to per-user ATS platforms where adding 10 interview panelists at $50/user/month adds $6,000 to your annual recruiting technology budget.
Budget approval tip
Present your budget in two views: total annual investment and cost-per-hire. The total number is what finance approves. The cost-per-hire number is what justifies the investment. If your total hiring budget is $1.2 million for 30 hires, the cost-per-hire is $40,000. Compare this against the cost of leaving positions vacant (lost revenue, overtime, contractor spend) to make the ROI case clear.
Building a quarterly timeline
The quarterly timeline translates your hiring plan from a static list into an operational schedule. It answers two questions for each role: when does the recruiter start sourcing, and when does the new hire start?
Work backwards from the target start date. If you need a senior product manager starting July 1, and your average time-to-fill for PM roles is 60 days, the requisition must be approved and published by May 1. Add 2 weeks for approval workflow. That means the hiring manager should submit the request by mid-April. Your Q2 plan should flag this role as "sourcing begins April 15."
Q1 priorities: Backfills for Q4 departures, critical roles that block revenue, and any roles with historically long time-to-fill (engineering, executive). Front-loading hard-to-fill roles prevents a Q3 bottleneck when multiple roles compete for recruiter bandwidth.
Q2 priorities: Growth roles aligned with mid-year business milestones. This is typically the highest-volume quarter for hiring because it balances urgency with ramp time before year-end. If your plan is top-heavy in Q2, consider whether your recruiting team has the capacity to manage the volume or whether some roles should shift to Q1.
Q3 priorities: Second wave of growth hires and any roles deferred from Q1/Q2. Watch for summer slowdowns in candidate availability, particularly in Europe where August hiring nearly stops. Plan for extended timelines in Q3 and compensate by starting sourcing 2 to 3 weeks earlier than normal.
Q4 priorities: Strategic hires for next year, succession-planning moves, and interns or graduate hires with January start dates. Q4 hiring volume is typically lowest, which makes it a good time for process improvements and refining your approval workflow for the next annual cycle.
Map each role to its quarter on a single-page view. This becomes the document your recruiting team references weekly. Any role that slips from its planned quarter gets flagged in the next quarterly review with a root-cause analysis: was it budget hold, slow approvals, insufficient pipeline, or hiring manager availability?
Headcount approval workflow
The fastest way to derail a hiring plan is a slow or unclear approval process. When a hiring manager submits a requisition and waits three weeks for a signature chain to complete, you lose candidates and credibility.
Define approval tiers based on role level and budget impact:
Tier 1 (pre-approved): Roles already in the annual hiring plan with approved budget. The hiring manager submits the requisition and it goes directly to recruiting. No additional approval needed. This should cover 70 to 80 percent of your hires.
Tier 2 (manager + VP): Roles in the plan but with modified scope (different level, different salary range, or different timeline). Requires VP approval within 3 business days. If no response within 3 days, auto-escalate to the next level.
Tier 3 (VP + CFO): Unplanned roles not in the annual plan. These require business justification, budget identification (which planned role gets deferred to fund this one?), and CFO sign-off. Target: 5 business days maximum.
Document these tiers in your hiring plan so every stakeholder knows the rules before they submit a request. The number one source of approval delays is ambiguity about who needs to sign off. Remove that ambiguity and you remove the delay.
An ATS with a built-in headcount approval workflow automates this process. The hiring manager fills out a requisition form, the system routes it to the right approver based on the tier rules, sends reminders on deadline, and auto-escalates if needed. No email chains, no lost requests, no ambiguity about who needs to approve what.
Treegarden streamlines headcount approvals
Treegarden's approval workflow routes requisitions to the right stakeholder automatically based on role level and budget tier. Pre-approved roles in your annual plan skip the queue entirely. Hiring managers get notified the moment their request is approved, and recruiters see the new requisition in their pipeline within minutes. No email chains. No spreadsheet tracking. Startup plan: $299/month, unlimited users.
Connecting the plan to your ATS
A hiring plan that lives in a spreadsheet and an ATS that lives in a browser tab will diverge within the first month. Connecting the two eliminates manual reconciliation and gives leadership real-time visibility into plan execution.
Plan-to-pipeline sync. Each approved role in your hiring plan should automatically create a requisition in your ATS. The requisition inherits the role title, department, salary range, and target start date from the plan. Recruiters see exactly what they need to fill and when, without consulting a separate document.
Progress tracking. Your quarterly review should compare planned hires against actual hires, planned budget against actual spend, and planned timelines against actual time-to-fill. If your plan calls for 8 Q2 hires and you have 3 offers accepted with 2 in final round and 3 not yet started, that is a data point that drives action. An ATS dashboard surfaces this comparison automatically.
Variance reporting. When actual results deviate from the plan, you need to understand why. Did sourcing start late? Was the salary range below market? Did the hiring manager reject qualified candidates? ATS data answers these questions with pipeline analytics, rejection reason tracking, and time-in-stage metrics. Each deviation becomes a learning that improves next year's plan accuracy.
Recruiter workload balancing. An integrated system shows which recruiter owns which requisitions and how many active roles each person manages. If one recruiter has 8 active requisitions and another has 3, redistribute before the overloaded recruiter starts dropping balls. This visibility is impossible when the plan and ATS are separate systems.
Treegarden connects your workforce plan directly to hiring execution. Every planned role appears alongside active requisitions and pipeline data. The quarterly review becomes a 30-minute dashboard walkthrough instead of a day-long spreadsheet exercise. Learn more about how headcount planning integrates with active hiring.
Frequently asked questions
What should an annual hiring plan include?
An annual hiring plan should include a department-by-department headcount breakdown, role specifications with seniority levels, a quarterly timeline mapping when each requisition opens and when the target start date falls, a budget allocation per role covering salary, benefits, and recruiting costs, an approval workflow specifying who signs off on each requisition, and contingency buffers for unplanned departures. The plan should also identify sourcing channels for each role type and set measurable targets like time-to-fill and cost-per-hire.
How far in advance should I build a hiring plan?
Start building your annual hiring plan 8 to 12 weeks before the fiscal year begins. This gives you time to collect headcount requests from department leaders, validate budget allocations with finance, run the numbers through an approval workflow, and have approved requisitions ready to publish on day one of Q1. Companies that start planning in January for a January fiscal year are already behind. Sourcing for critical roles should begin before the plan is formally approved.
How do I allocate hiring budget across departments?
Start with revenue-generating departments. Sales and engineering typically receive 50 to 60 percent of the hiring budget because their headcount directly impacts revenue capacity. Allocate the remainder based on operational necessity and strategic priorities. Each department's allocation should include base salary, benefits load (typically 25 to 35 percent of base), recruiting costs (agency fees, job board spend, ATS subscription share), and onboarding expenses. Build a 10 percent contingency reserve for unplanned hires or market-rate adjustments.
Should I review the hiring plan quarterly or stick to the annual version?
Quarterly reviews are essential. Business conditions change: a product launch moves up, a key client churns, or attrition spikes in one department. Each quarterly review should compare actual hires against plan, recalculate remaining budget, adjust timelines for unfilled roles, and reprioritize based on current business needs. Without quarterly reviews, your plan drifts from reality and hiring managers lose trust in the process. An ATS with dashboard reporting makes these reviews a 30-minute exercise instead of a full-day spreadsheet reconciliation.