Hiring Plan

What is a Hiring Plan?

A hiring plan translates workforce needs into a schedule that recruiting, finance, and operating leaders can review. A useful plan names the role, department, rationale, owner, approval or planning status, target start date, compensation assumption, and dependencies.

The plan can include roles at different stages. A proposed role may be awaiting approval. An approved opening may be in recruiting. An accepted offer may have a confirmed future start. An active employee belongs in the current-team record. Clear statuses prevent a future intention from appearing as a completed hire.

The financial effect should follow timing and status. A planned hire can inform a planning model or scenario from its target period, while actual payroll should follow the supported active-team workflow. Delays, cancellations, changed compensation, and one-time costs should be recorded explicitly rather than hidden in a single headcount number.

Hiring Plan versus headcount plan

A headcount plan is the broader workforce and capacity view. A hiring plan focuses on the concrete pipeline of roles the organization intends or is approved to fill. The two should reconcile, but they answer different operating questions.

Hiring Plan versus recruiting pipeline

A recruiting pipeline tracks candidates, interviews, offers, and hiring workflow. A hiring plan tracks roles, timing, ownership, status, and financial assumptions. RunwayCal does not claim applicant tracking or candidate management.

Approved hire versus scenario hire

An approved hire is part of governed operating intent, subject to the organization's approval policy. A scenario hire is hypothetical and exists to test an outcome. Neither becomes active payroll until the real team record is updated through the proper workflow.

Plan versus actual

Compare the planned start and entered cost with the actual start and recorded payroll once the hire occurs. The variance can reveal timing or cost differences, but it does not by itself explain why they occurred.

Why it matters

Hiring combines an operating commitment with cost and timing. A governed plan lets teams see which roles are real priorities, when their cost may begin, and which assumptions should change if recruiting moves earlier or later.

The plan also creates a traceable bridge to plan-versus-actual review. That helps leadership update the financial picture without rewriting history or treating every exploratory role as an obligation.

Hiring plan fields

• Role, department, rationale, and accountable owner
• Planned, approved, recruiting, offered, hired, or cancelled status
• Target start date and confirmed start date when known
• Entered compensation and other reviewed people-cost assumptions
• Dependencies, approval evidence, and scenario status where relevant

Illustrative planned-to-active transition

How RunwayCal helps

Common mistakes

• 1Using planned, approved, recruiting, and hired as interchangeable statuses.
• 2Treating a target start date as proof that payroll began.
• 3Mixing a hypothetical scenario hire into the approved hiring plan.
• 4Applying a universal fully loaded cost instead of reviewed assumptions.