Hiring plan template: a team plan, a one-role plan and the timeline math
On this page
- What goes into a hiring plan
- Template 1: the team or quarterly hiring plan
- Template 2: the single-role hiring plan
- A filled example
- The timeline math, worked backwards
- Budget, pay ranges and posting rules
- Interview stages, owners and capacity
- Why hiring plans slip, and the fix
- A weekly review checklist
- Questions people ask
A hiring plan is a one-page document that says which roles you will fill, by when, with what budget, through which sourcing channels and interview stages, and who owns each step. A good one starts from the date the new person needs to be working and works backwards, so the dates are real. Below are two copy-ready templates (one for a team's quarter, one for a single role), a filled example, and the timeline arithmetic.
The plan sits between two other documents. The job requisition form gets a position approved; the intake meeting gets the role defined. The hiring plan turns both into a schedule people can hold each other to.
What goes into a hiring plan
| Section | The question it answers | Common gap |
|---|---|---|
| Roles and headcount | What are we hiring, how many, and why now? | "Engineers" with no level, location or reason |
| Target dates | When must each person start, and what happens if they do not? | A start date with no working-back to when sourcing must begin |
| Budget | What is the pay range and what will hiring cost? | Range agreed after the offer is drafted |
| Sourcing | Where will candidates come from? | "Post it and see" |
| Interview process | Which stages, who interviews, what each stage assesses? | Five stages that all ask the same questions |
| Capacity | How many interviewer hours does this need per week? | Nobody checked the interviewers' calendars |
| Owners and review | Who is accountable, and when do we check progress? | No weekly review, so slippage is found at quarter end |
Template 1: the team or quarterly hiring plan
Use one of these per team per quarter. Copy it into a document or spreadsheet and replace the brackets.
HIRING PLAN — [Team], [Quarter / period]
Hiring manager(s): [name] Recruiter: [name]
Approver for budget: [name] Last updated: [date]
1. WHY WE ARE HIRING
[Two or three sentences: the business goal, the work that is not getting
done today, and what happens if these roles are not filled by the dates below.]
2. ROLES
# Role / level Location / setup New or backfill Req ID Must start by Priority
1 [title, level] [city, hybrid] [new] [ID] [date] [1-3]
2 [title, level] [remote, states] [backfill: name] [ID] [date] [1-3]
3 ...
3. BUDGET
Role Pay range (posted) Other comp Recruiting cost estimate
1 [$min–$max] [bonus, equity] [job boards, agency fee if used]
2 ...
Total salary cost this period: [sum] Total recruiting cost: [sum]
4. SOURCING PLAN (per role)
Role Channels, in order Owner
1 [referrals → targeted outreach → job board] [name]
2 [internal posting first until date, then external] [name]
5. INTERVIEW PROCESS (per role family)
Stage Length Interviewer(s) Assesses Feedback due
Recruiter screen [30m] [recruiter] [must-haves, logistics] [same day]
Hiring manager [45m] [name] [competencies 1–2] [24h]
[Skills exercise] [60m] [name] [competency 3] [24h]
Final / panel [2h] [names] [competencies 4–5] [24h]
Debrief [30m] [all] [decision] [within 2 days]
6. INTERVIEWER CAPACITY
Expected interviews per week at peak: [n]
Hours needed per week: [n] × [average length] = [hours]
Named backups for each interviewer: [names]
7. TIMELINE (per role, working back from start date)
Start date: [date]
− Notice period: [weeks] → offer accepted by [date]
− Offer and approval: [days] → final decision by [date]
− Interview stages: [weeks] → first screens by [date]
− Sourcing: [weeks] → role open and sourcing by [date]
8. RISKS AND DECISIONS NEEDED
- [e.g. range below market for level; decision needed from approver by date]
- [e.g. hiring manager on leave in week 6; backup decision-maker: name]
9. REVIEW
Weekly check: [day, time, attendees]
Quarter-end review: [date]
Template 2: the single-role hiring plan
For one urgent or senior role, a shorter version works better. It fits on one screen and is easy to send to a hiring manager for a yes.
HIRING PLAN — [Role, level]
Req ID: [ID] Hiring manager: [name] Recruiter: [name]
Why now: [one sentence]
Must be working by: [date] Latest acceptable offer date: [date]
Pay range: [$min–$max] [+ bonus/equity] Approved by: [name, date]
Location / setup: [on-site, hybrid days, remote states]
Must-haves (max 4, from intake):
1. [ ]
2. [ ]
3. [ ]
Sourcing, in order:
Week 1–2: [internal candidates, referrals]
Week 2–4: [outreach to named target companies or profiles]
Week 3+: [job boards / agency, only if pipeline below X screens]
Process:
[Screen] → [HM interview] → [exercise] → [final] → [references] → [offer]
Feedback within [24h] of each stage. Debrief within [2 days] of final.
Interviewers and backups:
[Stage]: [name] / backup [name]
Weekly check: [day]. Plan is off track if: [fewer than N screens by week 3,
no finalist by date].
A filled example
An invented support team, written the way a usable plan reads:
Hiring plan — Customer Support, Q1
Why: Ticket volume from the new self-serve plan lands in February. Without two more agents and a team lead by March 1, first response time on the paid plans misses the contract commitment.
| Role | Setup | Type | Start by | Range |
|---|---|---|---|---|
| Support Agent (x2) | Remote, US Central or Eastern hours | New | Feb 2 | $52,000–$60,000 |
| Support Team Lead | Hybrid, Chicago, 2 days | Backfill | Mar 1 | $78,000–$90,000 |
Sourcing: Agents: referrals and internal posting for one week, then job boards. Lead: internal candidates first (two agents have asked), external search from week 2 in parallel.
Process for agents: 20-minute screen, written ticket exercise (30 minutes, same three tickets for everyone), 45-minute interview with the support manager. Feedback same day.
Capacity: 8 manager interviews a week at peak × 45 minutes = 6 hours. The manager has blocked Tuesday and Thursday afternoons; the lead of the billing team is the backup.
Risk: the lead range is below what two finalists asked for last year. Decision on a higher top of range needed from the VP by January 9.
The timeline math, worked backwards
Most hiring plans fail on dates, because they start from "open the role" rather than from "need the person working". Work backwards with your own numbers from the last few hires of a similar kind; the figures below are an invented example.
| Step | Your past average (example) | Date if start is March 2 |
|---|---|---|
| Start date | — | March 2 |
| Notice period for employed candidates | 3 weeks | Offer accepted by February 9 |
| Offer approval, verbal, written, acceptance | 1 week | Final decision by February 2 |
| From first screen to final decision | 4 weeks | First screens by January 5 |
| Sourcing to reach enough screens | 2 weeks | Role open and sourcing by December 22 |
In this example the plan has to be approved before the winter holidays for a March start, which is exactly the kind of fact a hiring manager needs to see in December rather than discover in February.
How many screens you will need
Use your own pass-through rates from past roles, stage by stage. Suppose, as an invented example, one in two offers is accepted, one in three finalists gets an offer, one in two manager interviews produces a finalist, and one in three screens leads to a manager interview. For one hire you need 2 offers, 6 finalists, 12 manager interviews and 36 screens. If you do not have past rates, track them from this plan on, and do not borrow a number from someone else's funnel.
Budget, pay ranges and posting rules
Settle the pay range in the plan, not at offer. Several states and cities now require a range in job postings. California, for example, requires employers with 15 or more employees to include the pay scale, defined as a good faith estimate of the salary or hourly range the employer reasonably expects to pay, in any job posting, and bars seeking an applicant's salary history (Labor Code § 432.3, as of September 2026). If the role may be filled remotely, check the rules for every place you will accept applicants from.
Recruiting costs worth listing, so nobody is surprised:
- Job board and sponsored posting spend, per role.
- Agency fees, if an agency is a fallback: write down the trigger for using one, such as no finalist by a date.
- Referral bonuses and when they are paid.
- Candidate travel for final rounds and any paid work samples.
- Interviewer time: the hours from the capacity section, which are a real cost even if not a budget line.
Interview stages, owners and capacity
Each stage in the plan should assess something the previous stage did not. Give every stage a named interviewer, a backup, and a feedback deadline. The interview guide template holds the questions for each stage; the plan only needs to say who asks which competency.
Capacity is the part hiring managers skip. Count interviews per week at peak for every open role, multiply by length, add debriefs, and put the hours on calendars before the first screen. When interviewers take notes with a tool, Interview Signal runs on each interviewer's computer without a bot joining the call, and in onsite panels it tracks which questions each interviewer has covered, which helps keep stages from repeating each other.
Why hiring plans slip, and the fix
| What happens | Why | Fix in the plan |
|---|---|---|
| Start dates missed by a month | Dates set from the open date, not worked back from the start date | Use the backward timeline with your own averages |
| Offer declined over pay | Range set before the market was tested | Record the range and a decision date for revisiting it after the first screens |
| Candidates wait a week between stages | No interviewer time reserved | Capacity section with blocked time and named backups |
| Must-haves change in week four | Intake not confirmed in writing | Must-haves copied into the plan and approved |
| Everything is priority one | No ranking across roles | Priority column, 1 to 3, set by the budget approver |
| Nobody notices the pipeline is thin | No review cadence | Weekly 15-minute check with an off-track trigger |
A weekly review checklist
- For each role: screens this week, candidates at each stage, and the date of the next decision.
- Is the role still on track against the backward timeline? If not, change the start date in the plan or change something in the process.
- Any feedback overdue past the deadline in the plan, and who is chasing it.
- Any off-track trigger hit (for example too few screens by week three), and the decision it calls for.
- Range or must-have changes requested, and who approved them.
- Interviewer availability for the next two weeks, including leave.
Questions people ask
What is the difference between a hiring plan and a job requisition?
A requisition asks for approval to open one position and records the budget and reason. A hiring plan says how the position, or a whole quarter of positions, will actually be filled: dates, sourcing, interview stages, owners and the capacity needed from interviewers.
How far ahead should a hiring plan be written?
Work back from the date you need the person productive. Add their notice period, the offer and approval time, your interview process and your sourcing time, using your own past numbers. For most teams that means a plan written a quarter before the start dates, not the week the role opens.
Who owns the hiring plan?
The hiring manager owns the need, the must-haves and the interviewers' time. The recruiter owns the process, the timeline and the reporting. Write both names at the top so a slipping date has an obvious person to call.
How often should a hiring plan be reviewed?
Weekly while roles are open, in a 15-minute check on pipeline, dates and blockers, and at the end of each quarter against what was actually hired. Change the dates in the plan when they slip, so it stays the real schedule rather than a hope.