Run a hiring forecast meeting that changes the plan

Define the forecast horizon

Choose a period long enough to influence search and onboarding decisions, then identify the roles and teams included. Show approved openings separately from proposed demand and replacements. For each, capture priority, readiness, current stage, likely decision window, candidate-specific joining information where confirmed, and manager onboarding capacity. Do not turn uncertain dates into commitments by removing their assumptions.

Bring changes, not status recitals

Circulate the baseline before the meeting. Ask attendees to flag new approvals, cancellations, scope changes, candidate movement, delayed decisions, and capacity risks. Routine candidate status belongs in recruiting operations. Forecast time is for changes that affect workforce timing, search sequence, delivery plans, or another team's ability to hire.

Use scenarios where certainty is false

For consequential unknowns, show a small number of plausible cases and the decision attached to each. A role might fill in the current window, move later because assessment is incomplete, or reopen. Include what work remains uncovered in each case. Avoid adding numerical precision unsupported by evidence; name confidence and the next event that will improve it.

• Change since the last forecast
• Assumption and evidence behind timing
• Business consequence of movement
• Decision required today
• Owner and next evidence date

Resolve a capacity collision

Illustrative example: product and customer operations both plan three starts in the same fortnight, relying on the same systems trainer. The forecast meeting identifies the conflict before offers are finalised. Leaders protect two critical starts, move one lower-priority search window, and arrange recorded preparation plus live practice for the remaining group. The forecast changes an operating decision rather than merely reporting risk.

Publish the revised baseline

Update sequence, owners, assumptions, and decision dates in the source system or agreed plan. Tell affected recruiters, managers, and candidates only what is appropriate and confirmed. Carry unresolved items into the next review with a named owner. Periodically compare forecasts with actual outcomes to improve assumptions, without treating variance as failure when the underlying business decision consciously changed. Note which forecast assumptions repeatedly prove weak, such as interview availability or approval timing, and assign improvement to the team controlling that input. Keep candidate-specific information restricted. The shared workforce view needs expected capacity and uncertainty, not personal details that do not help a planning decision. Keep a separate line for roles intentionally paused, including the restart condition, so they do not disappear from capacity planning or return as unexplained emergencies.