Ask a Chief People Officer what their workforce plan looks like, and they will likely show you a slide deck presented at the last board meeting, or a spreadsheet updated during the annual planning cycle. Ask a recruiter what their ATS pipeline looks like, and they will show you a live view of active requisitions, candidate stages, and interview schedules.
These two documents describe the same organisation's talent needs - one from 30,000 feet, one from ground level. Yet in most companies, the people maintaining them never look at each other's work. The strategic workforce plan says the company needs 25 more engineers in H2. The ATS shows the company has 8 engineering reqs open and one recruiter assigned. The gap between those two data points is where hiring plans fail.
Connecting workforce planning to your ATS is not primarily a technology problem. It is a process problem - one that technology enables but does not automatically solve. This guide walks through the four workforce planning models in practical use, why the ATS disconnection happens, and how to build the bridge that makes strategic plans actually execute.
What Strategic Workforce Planning Actually Means
The term "workforce planning" is used to describe at least three different activities, which creates significant confusion about what tools and processes are needed:
Strategic workforce planning is a 12-36 month view of the capabilities the organisation needs to execute its strategy. It answers questions like: "If we are moving from a product-led to a sales-led growth model, what sales capability do we need to build, and can we build it through hiring or do we need to restructure?" or "As AI automates portions of our current workflows, which roles will be redefined and which will be eliminated?" This is fundamentally a leadership conversation that informs the structure of the headcount plan.
Operational headcount planning is a 1-4 quarter view of specific roles, budgets, and timelines. It translates the strategic direction into concrete hire targets: Q3 we hire 4 account executives, 2 solutions engineers, and 1 sales operations manager. This is the planning layer that connects directly to the approval workflow and, from there, to the ATS.
Recruiting execution is the daily workflow of sourcing, screening, interviewing, and closing candidates against approved open requisitions. This is what the ATS is designed to manage.
The failure mode most companies experience is treating all three as separate processes with separate owners and separate tools. The fix is not to collapse them into one activity - they operate at genuinely different time horizons and require different kinds of thinking - but to build the connective tissue between them: the data flows that let strategic decisions inform operational plans, and operational approvals trigger recruiting execution automatically.
The 4 Workforce Planning Models
There is no single correct approach to workforce planning. The right model depends on the business's growth stage, the predictability of its demand, and the sophistication of its HR function. The four models in widest practical use are:
1. Demand-Driven Planning
Demand-driven planning derives headcount targets from business demand metrics. Revenue per FTE targets determine total headcount. Customer-to-support-staff ratios determine support headcount. Engineering capacity requirements tied to product roadmaps determine engineering headcount. This model is most effective when business demand is predictable and when there are clear, validated relationships between headcount inputs and business outputs.
The ATS connection for demand-driven planning is the cleanest: when demand projections update, headcount targets update, and the delta between current headcount and target headcount generates headcount requests that flow through the approval workflow and into the ATS automatically.
2. Scenario-Based Planning
Scenario-based planning acknowledges uncertainty by building multiple headcount scenarios - typically conservative, base, and aggressive - and defining the business triggers that would activate each. If Q2 revenue is within 5% of plan, execute the base headcount scenario. If Q2 revenue exceeds plan by 15%, activate the aggressive scenario. If Q2 revenue misses plan by 10%, activate the conservative scenario.
This model requires the ATS to support holding approved headcount in a "staged" state that can be activated rapidly when a trigger condition is met, rather than requiring a new approval cycle for each scenario flip. Not all ATS platforms support this - it is a meaningful differentiator for high-velocity growth companies.
3. Skills-Based Planning
Skills-based planning starts from a capability gap analysis rather than from headcount numbers. The organisation identifies the skills it needs in 12-24 months based on strategic direction, audits current employee capabilities, and determines whether the gap should be closed through external hiring, internal development, or structural changes like partnering or contracting.
The ATS connection for skills-based planning is through job description and screening criteria: the skills identified in the capability gap analysis should directly inform the competencies assessed in interviews and the knockout questions used in ATS screening workflows.
4. Zero-Based Planning
Zero-based planning requires every headcount request to be justified from the current business need rather than from the prior year's approved headcount as a baseline. Every role - including roles that have been in the headcount plan for years - must make an affirmative case for its existence each planning cycle.
This model is most disruptive to implement but most effective at eliminating bloat in mature organisations. From an ATS perspective, it requires a more robust headcount request form that captures business justification, because every role is genuinely evaluated on its merits rather than assumed on the basis of prior approval.
Most Companies Blend Models
In practice, most organisations use a blend: demand-driven planning for volume roles (sales, support, operations) where the headcount-to-output relationship is well understood, and skills-based planning for specialist roles (engineering, product, data science) where the capability is harder to acquire and the strategic decision is about which skills to build versus buy. Zero-based review is typically applied as an annual audit of the headcount plan rather than as the primary planning methodology.
Why Most ATS Platforms Don't Support Workforce Planning Natively
The architecture of most ATS platforms reflects their origin: they were built to solve a recruiter's workflow problem, not a strategic planning problem. The core data model is built around candidates - their applications, their stage in the pipeline, their interview feedback, their offers. The job requisition is treated as a container for candidates, not as an output of a planning and approval process.
This means the requisition typically appears in the ATS at the moment a recruiter creates it - not at the moment it was approved in the workforce plan, and not with any of the approval history or business justification that led to its creation. The context that Finance cares about (why this role was approved, at what cost, by whom) is absent from the ATS record entirely.
The operational consequences are predictable:
- Recruiters open roles in the ATS that Finance did not approve - creating budget surprises
- Approved roles sit unexecuted in the planning spreadsheet because no one notified the recruiter that approval was granted
- Role details drift between the approved version (title, level, compensation) and the posted version (what the recruiter actually puts in the ATS)
- Finance cannot see which approved roles are in active search and which are not - making headcount forecasting unreliable
These problems are not caused by bad people - they are caused by a missing connection between the planning and execution layers of the hiring process.
Building the Bridge: Headcount Plan → Job Requisition → ATS Pipeline
The architectural solution is to make the headcount approval workflow part of the ATS, rather than a separate process that the ATS receives outputs from. When these two layers are unified, the gap disappears: an approved headcount request automatically becomes an active ATS requisition, with all approved fields pre-populated and the recruiter notified immediately.
Building this bridge requires four components:
1. A structured headcount request form inside the ATS. The request captures all the fields that approvers need - role title and level, department, backfill vs. net-new, business justification, compensation range, target start date - and this data travels with the role through every stage of the approval process and into the active requisition without re-entry.
2. A configurable approval routing engine. Different role types trigger different approval chains: a backfill in an approved headcount plan routes to HR business partner and department head; a net-new role outside the plan routes to department head, finance, and executive sign-off. The routing engine enforces these rules without requiring manual workflow management.
3. Automatic requisition activation on final approval. When the final approver marks the headcount request as approved, the system creates the active requisition automatically and assigns it to the correct recruiter. No email chain, no manual creation step, no data re-entry.
4. Hiring velocity reporting back to the planning layer. Actual time-to-fill, offer acceptance rates, and candidate pipeline conversion rates feed back into the workforce planning view so HR leadership and Finance can see whether the approved headcount plan is being executed on the projected timeline.
How Treegarden Handles Workforce Planning Integration
Treegarden's headcount approval workflow is built natively into the ATS - not integrated via API from a separate tool. When a headcount request is submitted, it routes through a configurable approval chain with SLA tracking and automatic escalation. On final approval, the active requisition is created automatically, pre-populated with all approved role data, and the assigned recruiter receives an immediate notification. Leadership sees a live dashboard showing which approved roles are in active search, which are pending approval, and how actual hiring velocity compares to the workforce plan timeline.
Skills Gap Analysis Using Your ATS Data
Your ATS is one of the richest sources of skills gap data in the organisation - but most companies never analyse it at this level. The data exists in three places:
Job descriptions and screening criteria. Every job description your organisation has posted contains an implicit statement of the skills you considered important enough to hire for. Aggregating job descriptions across departments and time periods reveals skill clusters - the capabilities that appear repeatedly across multiple roles. These are your organisation's core skill requirements. Comparing them against your HRIS employee records identifies where the organisation is currently thin and where it is well-covered.
Offer decline data. When candidates decline offers, the reason (compensation, role scope, competing offer, location) is often captured in the ATS. Systematic offer decline analysis by role type and skill set reveals where the organisation is not competitive for specific capabilities. An engineering team with a 40% offer acceptance rate for data engineers and a 75% acceptance rate for backend engineers has a compensation or employer brand problem specifically in data engineering - intelligence that should directly inform the workforce plan.
Pipeline conversion rates by skill cluster. Comparing the number of candidates screened to the number advanced to offer, segmented by the primary skill being assessed, reveals where the organisation has abundant supply and where it struggles to find qualified candidates. Low conversion rates at the phone screen stage for a specific skill set indicate a supply constraint - the workforce plan should account for longer time-to-fill and may need to consider alternative acquisition strategies (upskilling, contracting, or geographic expansion).
Annual Workforce Planning Calendar
Workforce planning is most effective when it runs as a structured annual process rather than an ad hoc activity. The calendar below shows the recommended timing for a company with a January fiscal year start:
| Month | Activity | Owners |
|---|---|---|
| September | ATS data review - analyse prior year hiring velocity, offer acceptance, and skills gap signals | HR Analytics / TA Leadership |
| October | Department heads submit headcount requests for the coming year; HR reviews for completeness | Department Heads, HR BPs |
| November | Finance reviews headcount requests against budget scenarios; scenario modelling completed | Finance, HR Leadership |
| December | Annual headcount plan approved; Q1 roles activated in ATS; recruiters assigned | Executive team, HR, TA |
| February / May / August | Quarterly plan review - compare actuals to plan; activate next quarter's roles; process mid-year changes | Finance, HR Leadership, TA |
Frequently Asked Questions
What is strategic workforce planning?
Strategic workforce planning is the process of analysing current workforce capabilities and forecasting future talent needs based on business strategy, then building a plan to close the gap between where you are and where you need to be. It differs from operational headcount planning in scope and time horizon: operational planning typically looks one to two quarters ahead and focuses on specific roles and budgets, while strategic workforce planning looks 12-36 months ahead and focuses on capability clusters, skills gaps, and the organisational design decisions that determine what kinds of talent the business needs to execute its strategy. In practice, the two are interdependent - strategic workforce planning sets the direction, and operational headcount planning translates that direction into specific hire decisions with budgets and timelines.
Why don't most ATS platforms support workforce planning natively?
Most ATS platforms were built to solve an operational problem: manage the flow of candidates through a hiring pipeline. They are optimised for the recruiter's daily workflow - posting jobs, reviewing applications, scheduling interviews, collecting feedback - and they do this well. Workforce planning is a different problem at a different altitude: it is about deciding which roles to open in the first place, when, and at what cost. This requires financial modelling, scenario analysis, and multi-stakeholder approval workflows that are fundamentally different from candidate pipeline management. The result is a gap: strategic decisions are made in spreadsheets or finance tools, and execution happens in the ATS, but the two systems are not connected. Platforms like Treegarden close this gap by building the approval workflow directly into the ATS, so the planning and execution layers are the same system.
What are the four workforce planning models?
The four main workforce planning models are: (1) Demand-driven planning, where hiring targets are derived from business demand projections - revenue per headcount ratios, customer-to-support-ratio targets, or engineering capacity requirements tied to product roadmaps. (2) Scenario-based planning, where HR and Finance build multiple headcount scenarios and define the business triggers that activate each. (3) Skills-based planning, which starts from a skills gap analysis rather than headcount numbers - identifying the capabilities the organisation needs 12-24 months from now. (4) Zero-based planning, where every headcount request is justified from scratch against current business needs rather than from the prior year's approved headcount as a baseline. In practice most organisations blend demand-driven and skills-based approaches, with scenario planning for high-uncertainty periods and zero-based review as an annual audit.
How do you use ATS data for skills gap analysis?
ATS data is an underutilised source for skills gap analysis. Patterns in job descriptions reveal which skills the organisation values. Screening knockout questions show which skills are considered non-negotiable. Offer acceptance data reveals where compensation is below market for specific skill sets. Candidate pipeline conversion rates by skill cluster show whether the organisation can attract the capabilities it needs at the compensation it is offering. To use this data systematically: export all job descriptions from the past 12-24 months and extract skill requirements; compare these against current employee skills in your HRIS; identify skills that appear frequently in job descriptions but have long time-to-fill or low offer acceptance rates. These are your critical skills gaps - the capabilities most important to the business and hardest to acquire.