Workforce planning connects a business objective to the people, time, capabilities, and cost required to deliver it. A useful plan states its horizon and assumptions, compares demand with available supply, tests several scenarios, chooses accountable actions, and reviews forecast errors. It remains a decision process, not an annual headcount document.
Start with one decision and two horizons
Write the decision before opening a workforce spreadsheet. For example:
By the October operating review, decide how the UK service group will cover a new weekend commitment from January while maintaining weekday service and required specialist approval.
The sentence names the geography, work, deadline, service constraint, and decision date. It prevents a broad "future workforce" exercise from collecting every available HR field without resolving a business choice.
Separate the horizons that need different evidence:
| Horizon | Typical decision | Useful unit | Review trigger |
|---|---|---|---|
| Near term | Cover next quarter's demand | Hours, shifts, qualified coverage | Demand, absence, vacancy, or schedule change |
| Operating plan | Fund roles and development for the next year | Positions, capacity, capability, and cost | Budget or service-plan change |
| Strategic | Prepare for a different operating model | Capability, location, work design, and scenarios | Strategy, technology, market, or regulatory change |
Do not force all three into one level of detail. A strategic scenario should show capability choices and uncertainty. A near-term plan needs named coverage, timing, and actions.
The U.S. Office of Personnel Management's Workforce Planning Guide describes a continuing model that links strategic direction, workforce analysis, action planning, implementation, and review. The framework is designed for U.S. federal agencies, but its core discipline transfers: each step should refine the next rather than produce a plan that is frozen after approval.
Step 1: Translate strategy into work demand
Begin with the work, not job titles. Record the product, service, project, or operating outcome and what drives its demand.
| Demand field | Question |
|---|---|
| Outcome | What must the organization deliver? |
| Demand unit | Cases, orders, projects, service hours, locations, or another observable unit |
| Volume range | What are the low, base, and high assumptions? |
| Timing | When does demand arrive, and what deadlines apply? |
| Location | Where must work happen, and what can move? |
| Capability | What knowledge, skill, authority, or certification is required? |
| Service constraint | What quality, safety, legal, or customer condition must hold? |
| Evidence | Who owns the assumption, and when was it approved? |
Translate volume into work only as far as evidence allows. If handling time ranges from 20 to 35 minutes, keep that range in the scenarios. If a new process could change demand, model it separately instead of embedding the hoped-for improvement in the baseline.
Step 2: Describe workforce supply as it will be available
Headcount is one supply measure. The plan may also need scheduled hours, productive capacity, skill coverage, location, contract constraints, planned leave, known departures, vacancies, and development lead time.
Use source labels so planners can challenge the evidence:
- system record: position, contract, pay, location, or schedule from an authoritative system;
- demonstrated evidence: work sample, completed assignment, certification, or approved assessment;
- self-report: experience or interest stated by the employee;
- manager observation: contextual evidence that requires a named reviewer;
- planning assumption: a future availability, learning, hiring, or retention estimate;
- unknown: a gap that must stay visible.
O*NET, sponsored by the U.S. Department of Labor, provides a current occupational database with tasks, skills, work activities, and work context. It can help create a shared external vocabulary. It does not prove what a particular employee can do or replace the organization's evidence about its own work.
For a detailed capacity calculation using demand hours, scheduled hours, timing, and skill constraints, use the headcount and capacity worksheet.
Step 3: Calculate gaps under more than one scenario
Compare supply and demand in the same unit. A gap can be:
- total capacity;
- coverage during a specific time window;
- required capability or authorization;
- location or language coverage;
- leadership or manager capacity;
- hiring, development, or transition lead time;
- cost against the approved envelope;
- confidence in the evidence itself.
Build at least three plausible scenarios. "Base" should not quietly mean "approved target." Give each scenario an owner, assumptions, and evidence date.
| Scenario | Demand | Supply | Main gap | Decision that changes |
|---|---|---|---|---|
| Lower demand | Delayed or reduced volume | Current plan | Capability may remain constrained | Postpone some sourcing |
| Working assumption | Approved operating range | Expected supply | Timing and specialist coverage | Combine development and hiring |
| Higher demand | Earlier or larger volume | Same near-term supply | Capacity and location | Prepare contingent capacity |
External data can inform an assumption without becoming the internal forecast. The U.S. Bureau of Labor Statistics JOLTS program publishes job openings, hires, and separations estimates. Compare the relevant industry, geography, definitions, and revision schedule before using them. Local time-to-hire and acceptance data remain necessary.
Step 4: Diagnose the gap before choosing hiring
Ask why the gap exists:
- Did demand volume or timing change?
- Is scheduled capacity in the wrong place or period?
- Is a required capability scarce, stale, or poorly evidenced?
- Does the process create avoidable work or rework?
- Is development possible within the decision window?
- Is internal movement feasible and wanted?
- Are vacancies or departures already reducing supply?
- Is the gap an artifact of missing or mismatched data?
One headcount gap can produce different actions. A short peak may need temporary coverage. A recurring skill constraint may justify development or hiring. Work that no longer supports the service may be redesigned or stopped. A schedule mismatch can remain after total hours increase.
The Skills England 2026 reports combine quantitative and qualitative evidence to assess demand and supply by sector. They illustrate why national or sector evidence should be iterated and combined with employer and place-based knowledge rather than treated as one permanent shortage list.
Step 5: Compare a portfolio of responses
Evaluate more than one response for every material gap:
| Option | Earliest useful effect | Cost | Evidence needed | Main constraint |
|---|---|---|---|---|
| Develop current employees | After learning and demonstrated practice | Learning, supervision, reduced short-term capacity | Readiness, opportunity to practise, assessment | Time and available supervision |
| Move or redeploy | After agreement and transition | Transition and backfill | Capability, interest, receiving-team need | Creates a gap elsewhere |
| Change schedule or location | When agreements and coverage allow | Premiums, travel, coordination | Demand by time and place | Employee and operating constraints |
| Hire | After approval, search, notice, and ramp-up | Recruitment, vacancy, pay, onboarding | External supply and local lead time | May arrive after the gap |
| Use contingent supply | Contract and onboarding lead time | Rate, procurement, management | Availability and required authorization | Continuity and knowledge retention |
| Redesign work or process | After design, consultation, and testing | Change work and transition | Demand cause, quality, risk | Benefit uncertain before test |
| Manage demand | According to customer or portfolio decision | Revenue or service trade-off | Priority and service consequence | Business acceptance |
Do not count the same benefit twice. A process change that reduces demand also changes the hiring requirement. A development plan initially consumes expert capacity before it adds supply.
Step 6: Turn the selected option into an action plan
Each action needs:
- the gap and scenario it addresses;
- accountable owner;
- approved scope and population;
- start, milestone, and decision dates;
- financial and capacity effect;
- dependencies and approvals;
- employee impact and communication;
- success, review, and stop measures;
- fallback if the assumption fails.
Keep the forecast separate from the commitment. "Hire six" is an action. "Six hires start by January with the required approval" contains assumptions about approval, search, acceptance, notice, and onboarding. Track those stages separately.
Step 7: Review assumptions against actuals
At each review, compare:
- forecast demand with actual demand;
- expected supply with available supply;
- planned actions with delivered actions;
- expected timing and cost with actual timing and cost;
- gap measures before and after action;
- unintended employee, service, or risk effects;
- what should change in the next forecast.
Record why the plan moved. The purpose is not to defend the original estimate. It is to improve the next decision.
OPM's human capital analytics planning page includes both quantitative and qualitative sources and emphasizes turning analysis into action. A mature review makes the evidence, decision, owner, and result traceable.
Work through a fictional plan
This example demonstrates the method and is not a benchmark.
A UK service group plans to add weekend coverage in January. Operations produces three demand ranges and identifies one activity that requires specialist approval. HR confirms current positions and known vacancies. Managers provide schedules and demonstrated approval records. Finance supplies loaded cost ranges.
The working scenario shows enough total monthly hours but a weekend gap and too few approved specialists. The team compares four actions:
- voluntary schedule changes within applicable agreements;
- supervised development for two current employees;
- one external specialist hire;
- central specialist support during the transition.
Development is less expensive than hiring but may not finish before January. The external hire could arrive later than planned. Central support covers the transition but reduces capacity elsewhere. Leaders select a combined plan: begin development, open a specialist search, and reserve central support for a defined period.
The plan records the assumptions that could change the decision: weekend demand, employee agreement, assessment completion, candidate availability, and central capacity. The next review asks whether those assumptions held. It does not claim that the plan predicted a particular person's behavior.
Choose software after the operating method
Software can help maintain assumptions, permissions, scenarios, approvals, and actuals. It cannot decide which evidence is credible or which trade-off the organization accepts. Use the existing workforce planning tools comparison to commission the appropriate planning layer. Use the anticipating hiring needs guide when the decision is whether and when a recruitment action should start.
Where Lontra may fit
Lontra can be evaluated when a planning assumption depends on current employee or manager context. Review the current platform capabilities, then use one focused campaign, up to 30 invitations over 60 days with no credit card, to examine one question such as a process constraint, development barrier, or local practice.
Treat conversations as context for human review, not as verified capacity, a complete skills inventory, or a prediction of individual behavior. Managers receive a brief rather than raw employee responses, and aggregate HR views use a minimum of five respondents. Verify every required connection, export, and forecasting function separately.
Sources
- U.S. Office of Personnel Management: Workforce Planning Guide
- U.S. Office of Personnel Management: Workforce planning with human capital analytics
- Skills England: Annual skills report and sector assessments 2026
- U.S. Bureau of Labor Statistics: Job Openings and Labor Turnover Survey
- U.S. Department of Labor sponsored O*NET Database
