Hiring Plan: Build a Recruiter-Ready Operating System

A hiring plan should turn expected roles into work a recruiting team can actually prepare, sequence, and review. A list of titles and target dates is not enough. Recruiters also need to know why each opening exists, which roles are ready, who owns the next action, what evidence will define a qualified candidate, and whether the team can support the planned work.

This is a portfolio-level record. It sits above the job requisition workflow, which gives one recruiting request a stable identity and state, and above the candidate pipeline, which tracks people after recruiting begins. Keeping those levels separate prevents one planning sheet from becoming a second requisition system or candidate tracker.

The U.S. Office of Personnel Management's current Workforce Planning Guide describes a cycle that sets direction, analyzes workforce needs, develops an action plan, implements and monitors it, then evaluates and revises it. GitLab's current handbook provides a concrete operating example: it names a single source of truth for its hiring plan, links approved positions with identifiers, shares the plan with Talent Acquisition, and reviews role details and recruiting capacity through a weekly interlock. These sources describe different organizations, but both show that a hiring plan is a maintained operating record rather than a static wish list.

Define the plan's scope before adding roles

Start by naming the period, included teams, plan owner, participating functions, and review cadence. State which record is authoritative for planned openings and which event moves an item into active recruiting. If another system owns approval or requisition state, link to it rather than copying fields that will drift.

Write a short plan charter:

• Purpose: translate expected hiring demand into prioritized recruiter work.
• Scope: the teams, role types, and planning window included.
• Authority: the record that owns opening approval, assignment, and state.
• Cadence: when owners review changes, readiness, and capacity.
• Exit: the event that creates or activates the linked requisition.

A clear charter stops the plan from absorbing every discussion about workforce strategy, job-description editing, candidate status, and interview feedback. It should coordinate the path into recruiting, not replace each downstream record.

Give every planned opening a durable identity

Use one row per planned role or opening group, with a stable plan ID that survives title edits. GitLab's handbook describes position identifiers as links between approved headcount and its hiring plan. Your identifiers and systems may differ, but the operating principle is durable: recruiters need a reference that does not disappear when a working title changes.

A useful row includes:

• plan ID and current working title;
• team and hiring manager;
• purpose of the opening and expected work;
• number of openings;
• priority class and target recruiting window;
• assigned recruiter or assignment owner;
• readiness state and unresolved dependencies;
• linked requisition and active role brief when available;
• last reviewed date, next review date, and change owner.

Keep candidate information out of this record. The row describes planned work for the recruiting team, not a person being considered for the role.

Separate approval, readiness, and active recruiting

A role can be expected without being approved, approved without being ready for recruiter intake, or ready without being assigned. Treat those as different states. A practical model might distinguish proposed, approved, preparing, ready for intake, assigned, recruiting active, paused, and closed. Use the terms that match your organization, and define an entry event and owner for each one.

Readiness should be observable. Before a role enters active work, verify that its purpose, opening count, target window, hiring manager, recruiter owner, and source role document are current. If the success criteria are still unclear, route the role through a recruiting intake. Do not mark a role ready merely because a date was added.

Prioritize with explicit classes, not hidden arithmetic

Priority is a planning decision, so record its basis in plain language. Teams may distinguish committed work, conditional work, and later work, or use another small set of classes. For every priority, capture the reason, decision owner, decision date, and next review point.

Avoid collapsing unlike considerations into one unexplained score. Timing, role readiness, available recruiting attention, and business sequence can point in different directions. A short priority note makes the tradeoff visible: “ready after role intake,” “depends on an earlier team hire,” or “revisit at the next plan review.” The plan should reveal why work is sequenced, not create false precision.

Make recruiting capacity a visible constraint

Greenhouse's operational guidance recommends defining what a full recruiter workload means for the organization and building a planning model that anticipates hiring needs. The relevant unit is not simply a count of open roles. A repeatable search, a specialized leadership search, and a high-volume opening can demand different preparation, sourcing, review, and coordination.

Classify expected work using a small set of workload types based on your own history. Then compare the plan with the team's observed ability to complete evidence-ready handoffs. The recruiting productivity guide explains how to separate work classes, limit active work, and inspect exceptions. In the hiring plan, the goal is earlier: expose periods where planned demand and available attention do not fit, then change sequence, assignment, or readiness before work becomes an invisible queue.

Convert a planned role into a screening-ready handoff

When a role moves toward active recruiting, create a deliberate handoff from plan to requisition and intake. Carry forward the plan ID, purpose, owners, opening count, priority note, target window, and current dependencies. Link the new requisition back to the plan row so later changes can be traced in both directions.

The handoff is not complete until the hiring team can state what evidence matters. Confirm the core duties, minimum qualifications, preferred signals, acceptable equivalents, and questions that require follow-up. The guide to screening candidates against a job description shows how to connect those criteria to visible resume evidence and qualified human review.

Control plan changes without erasing history

Hiring plans change. Record a material update with the prior value, new value, requester, decision owner, effective date, and effect on recruiter work. A shifted window may change sequence. A new hiring manager may require another intake. A revised opening count may change workload classification. A changed role purpose may require a new role brief rather than a quiet title edit.

Review changes on a defined cadence and route urgent exceptions to a named owner. Preserve the earlier value so recruiters can explain which plan version governed the requisition and screening setup. The plan should make change manageable, not pretend it never happened.

Use AI for plan hygiene, not planning authority

AI can help compare plan versions, normalize role labels, find missing owners, group changed target windows, and draft a handoff summary from approved fields. It may also flag an apparent mismatch, such as an active requisition linked to a plan row still marked as preparing.

Treat every output as provisional. A recruiter, hiring manager, and designated plan owner should verify suggestions against the authoritative records. AI should not approve an opening, assign priority, infer a role's business importance, rewrite selection criteria, or decide which candidates advance.

Hiring plan checklist

• Is the planning period and included scope explicit?
• Does the plan name one authoritative record and owner?
• Does every planned opening have a stable identifier?
• Are approval, readiness, assignment, and active recruiting separate states?
• Does every state have an entry event and next owner?
• Is each priority supported by a visible reason and review point?
• Are workload types based on observed recruiting work?
• Are unresolved dependencies named with owners?
• Does an active item link to its requisition and role brief?
• Are screening criteria confirmed before candidate review begins?
• Do material changes preserve the previous value and operational effect?
• Are candidate records kept outside the hiring plan?
• Does a qualified person retain every planning and hiring decision?

Make the plan the front door to recruiting work

A useful hiring plan is neither a wish list nor a second applicant tracking system. It is the maintained front door to recruiting: stable role identities, distinct readiness states, explicit priorities, visible capacity, controlled changes, and a complete handoff into requisition, intake, and screening. When that layer is trustworthy, recruiters can start the right work with the right context while hiring teams retain clear ownership of every decision.