Anticipating hiring needs means deciding when a verified workforce gap requires recruitment preparation or an approved search. Model demand, available capacity, capability, expected movement, and hiring lead time as ranges. Set triggers before the gap becomes urgent, while comparing development, movement, process, contingent, and demand options against hiring.
Separate preparation from permission to hire
A team can prepare before it has evidence to open a position. Use four distinct states:
- Watch: an assumption or early signal needs evidence.
- Prepare: validate the role, work, budget range, market, and selection process.
- Open: an authorized owner confirms the gap and starts recruitment.
- Pause or stop: demand, supply, budget, or another response changes the need.
This distinction reduces two common costs. Waiting for a vacancy can leave no time to source and onboard. Opening every possible role can waste recruiter capacity and create a poor candidate experience when approval never arrives.
Define the hiring need as work
Avoid copying last year's organization chart into the forecast. Start with:
| Field | Question |
|---|---|
| Outcome | What must the team deliver? |
| Work unit | Which volume, service, project, or coverage measure drives demand? |
| Time window | When must capacity be available? |
| Location | Where must work happen, and what can move? |
| Capability | Which skill, knowledge, authority, or certification is essential? |
| Quality or risk | Which service, safety, legal, or customer condition must hold? |
| Duration | Is the gap temporary, seasonal, transitional, or continuing? |
| Evidence | Who owns each assumption, and when will it be reviewed? |
Only then describe a role. One requirement may combine several jobs, or several apparent vacancies may disappear after work is redesigned. A job title is a packaging choice, not the original demand.
The U.S. Office of Personnel Management's Workforce Planning Guide connects strategic direction, supply and demand, gap analysis, action planning, implementation, and review. Its federal procedures do not set a private employer's process, but they illustrate the sequence: validate the workforce need before turning it into a recruitment action.
Build demand and supply ranges
Create lower, working, and higher scenarios for the period when the new capacity would be useful.
Demand inputs
- approved sales, service, production, project, or location plan;
- demand volume and time-window range;
- expected handling or delivery time;
- quality, authorization, or coverage requirements;
- planned technology or process change;
- work that can be stopped, delayed, or moved;
- confidence, owner, and evidence date.
Supply inputs
- scheduled and usable current capacity;
- filled positions and approved vacancies;
- confirmed starts and realistic readiness dates;
- internal movement already agreed;
- development plans with practice and assessment time;
- temporary or partner capacity under an available contract;
- aggregate departure and absence ranges;
- capacity consumed by onboarding, supervision, or change work.
Do not add separate gaps until you understand their overlap. A specialist shortage may occur inside the same weekend capacity gap. Hiring one person may not solve either if the role starts after the peak or lacks the required approval.
For the underlying capacity arithmetic, use the headcount and capacity worksheet. For the wider demand-to-action process, use the workforce planning guide.
Calculate the date by which a decision is needed
Work backward from the ready-to-contribute date, not the contract signature or start date.
Decision date = ready date - duration of the critical path - contingency
Map approval, sourcing, selection, notice, onboarding, and supervised practice on that path. Some stages can overlap, so do not add every duration when the evidence shows parallel work. Use the longest dependent sequence and record which overlap the plan assumes.
Use local distributions by role, location, and hiring route. A single average can hide a long tail and does not show which stage causes delay.
| Stage | Local evidence | Lower | Working | Higher | Owner |
|---|---|---|---|---|---|
| Need validation and budget | Recent approved requests | Finance and hiring owner | |||
| Role and selection design | Comparable roles | HR and work owner | |||
| Sourcing | Applicant and outreach records | Talent acquisition | |||
| Assessment and decision | Stage timestamps | Hiring owner | |||
| Candidate notice and checks | Accepted offers | HR | |||
| Onboarding | Start-to-access records | Manager and operations | |||
| Demonstrated readiness | Work evidence | Work owner |
OPM's workforce planning elements explicitly connect supply-and-demand scenarios, competency gaps, hiring needs by number and occupation, approvals, and tracking. Use your own measured process times rather than importing its federal timetable.
Set triggers before reviewing the forecast
A trigger should name the evidence, threshold, action, owner, and expiry date.
| Trigger | Required evidence | Action | Stop or review condition |
|---|---|---|---|
| Persistent capacity gap | Demand and matching available hours across agreed scenarios | Prepare or open a role | Gap closes through verified supply or demand change |
| Critical capability gap | Required work plus demonstrated internal coverage | Prepare development and external sourcing in parallel | Internal readiness meets the date and risk condition |
| Approved expansion | Signed scope, timing, and budget range | Build pipeline before final opening date | Scope or timing moves beyond the review window |
| Known departure | Confirmed date and role requirement | Decide replace, redesign, move, or stop work | Work is redistributed with accepted risk |
| Aggregate movement range | Suitable history and population forecast | Reserve a capacity range, not named replacements | New actuals move the range |
| Hiring-process delay | Local stage time exceeds plan | Start preparation earlier or fix the stage | Stage performance returns within tolerance |
Avoid triggers such as "engagement fell" or "the model flags a person." They do not establish a hiring requirement. Employee accounts may help identify a process constraint or test whether work is changing. They should not become a hidden departure probability.
Work a fictional example
The figures below demonstrate the worksheet and are not a market benchmark or customer result.
A support team must provide an additional 1,200 service hours during a 12-week launch. The current schedule can supply 900 matching hours after planned leave, training, and administration. The initial gap is 300 hours.
The team tests four responses:
- move 80 hours of lower-priority work outside the launch period;
- provide 60 hours through an existing temporary contract;
- develop one current employee for specialist work, consuming 40 supervised hours during the 12-week period before adding an estimated 100 hours in that same period;
- hire for the remaining recurring requirement.
The first three actions do not simply add 80 + 60 + 100. Moving work reduces demand. The temporary contract adds matching supply. Development has a net contribution of 60 hours in the period because it consumes 40 supervised hours before adding 100. If development is delayed after the 40 hours have been committed, it contributes no hours before the launch. The higher case begins with 1,380 demand hours, then applies the same 80-hour deferral to show 1,300 hours of net demand.
| Scenario | Demand | Matching supply | Remaining gap | Hiring action |
|---|---|---|---|---|
| Development finishes on time | 1,120 hours | 1,020 hours | 100 hours | Prepare pipeline; validate whether the continuing gap justifies a role |
| Development is delayed after supervision starts | 1,120 hours | 920 hours | 200 hours | Open approved search and reserve transition cover |
| Launch reaches higher case and development finishes | 1,300 hours | 1,020 hours | 280 hours | Review role count, contingent capacity, and service priorities |
The team wants productive capacity by the launch, so it works backward through approval, sourcing, selection, notice, onboarding, and supervised practice. It opens recruitment only when the delayed-development or higher-demand trigger is confirmed. The decision log records why.
Use external labor data as context
The U.S. Bureau of Labor Statistics JOLTS program publishes monthly and annual estimates of job openings, hires, and separations. It can help frame national, regional, or industry conditions. It cannot replace the employer's vacancy, acceptance, notice, and readiness data, and releases may be revised.
The U.S. Department of Labor sponsored O*NET Database provides tasks, skills, work activities, and work context for occupations. Use it to challenge role design and sourcing language, then verify the actual work and essential requirements locally.
The Skills England 2026 reports assess sector skill demand and supply using quantitative and qualitative evidence. Sector evidence can inform a sourcing or development assumption. It does not prove that a particular vacancy will be hard to fill.
Review the pipeline as part of the forecast
Track stages with compatible denominators:
- roles approved, prepared, open, paused, and closed;
- suitable applicants by source and role;
- assessment starts and completions;
- offers, acceptances, withdrawals, and starts;
- time in each stage, including long-tail cases;
- new-hire access, onboarding, and demonstrated readiness;
- forecast need compared with actual available capacity.
A large applicant count does not prove sufficient qualified supply. A signed offer does not equal productive capacity. If a stage changes, update the ready-date range and the workforce scenario.
Assign decisions and stop conditions
For each possible role, record:
- work and capability need;
- scenarios in which it is required;
- alternatives considered;
- budget and approval owner;
- preparation and opening triggers;
- ready-date range;
- employee, service, and operating risks;
- pause or stop condition;
- next review date;
- actual outcome and lesson.
This turns proactive hiring into governed preparation. It does not mean opening requisitions months early without evidence.
Where Lontra may fit
Lontra can be evaluated when a hiring assumption depends on current employee or manager context, such as a changing process, hidden workload, development barrier, or local practice. Review the current platform capabilities, then use one focused campaign, up to 30 invitations over 60 days with no credit card, to examine that question.
The conversation output supports human review. It does not predict a named departure, calculate the hiring forecast, validate a skill, or open a requisition. Managers receive a brief rather than raw employee responses, and aggregate HR views use a minimum of five respondents. Verify every required connection and export separately.
Sources
- U.S. Office of Personnel Management: Workforce Planning Guide
- U.S. Office of Personnel Management: Workforce planning elements
- U.S. Bureau of Labor Statistics: Job Openings and Labor Turnover Survey
- U.S. Department of Labor sponsored O*NET Database
- Skills England: Annual skills report and sector assessments 2026
