In short
A useful hiring plan is a table, not a narrative. One row per role, with why it is needed now, the outcome it must deliver, the capability that cannot be learned on the job, a hire-by date, who decides, and what happens if it slips. Sequencing comes from two constraints working against each other: the cash you have and the interview capacity you can actually supply. A plan can look affordable and still ask for more senior interview time than the team has.
Key facts
- Format
- One row per role, eleven columns
- Sequenced by
- Cash and interview capacity, together
- Easiest column to skip
- Who makes the final decision
- Review it
- When something slips, not monthly by ritual
The hiring plan template
Start here. Copy these columns into a spreadsheet — the example row is filled in so the intent of each one is obvious, then delete it and put your own roles in. The sections after it explain how to sequence the rows and who should own each decision.
| Column | What goes in it | Example |
|---|---|---|
| Role | The role as you will advertise it | Senior backend engineer |
| Why now | The thing that is blocked or at risk without this person | Platform work is queued behind one person |
| Outcome required | What must be true six months after they join | Ingest pipeline rebuilt and owned by someone other than the CTO |
| Must-have capability | What cannot be learned on the job here | Production experience of high-throughput data pipelines |
| Hire-by date | When the outcome needs to be in progress | End of Q1 |
| Salary or range | What you will actually pay, not an aspiration | Your own figure for your market |
| Interview owner | Who runs the process and keeps it moving | Head of Engineering |
| Decision owner | Who says yes or no, finally | CTO |
| Dependencies | What must happen first, including other hires | After the platform lead starts |
| Risk if delayed | The consequence, in business terms | Enterprise onboarding slips a quarter |
| Status | Where it is now | Brief written, not open |
Salary is left for you to fill in. We publish no salary benchmarks, because we have no sourced UK figures and an invented range is exactly the number somebody would plan against.
Why a plan and not a list of roles
A list of job titles with target months is not a plan; it is a wish. What makes it a plan is that each row states the decision behind it — why this role, why now, what it has to produce, and what you will do if it is late. It is also what makes it defensible to a board, because the questions they ask are answered in columns rather than in prose.
It does not need to be a document. A spreadsheet with the columns above beats a well-written page, because a page cannot be sorted, re-sequenced or costed.
Sequencing: two constraints, not one
Cash is the constraint everyone sequences against. The second one is interview capacity, and it is easier to miss because it does not appear in the budget. Every open role consumes senior time — briefing, screening, interviewing, debriefing, closing — and that time comes from the same people who are supposed to be building.
So sequence against both. Work out how many searches your senior people can genuinely support at once, then check the plan against that number rather than the other way round. Order the roles so each one either unblocks the next or can run without the people the previous search is occupying.
The other sequencing rule worth holding: hire the person who makes the next hire easier. A platform lead who can then assess platform engineers changes the cost of every subsequent search in that area.
Must-have versus nice-to-have, decided in advance
Write the must-haves before you see any candidates, because the list moves the moment you meet someone impressive who does not match it.
- A must-have is something the person cannot learn here in time to deliver the outcome.
- If every line is a must-have, none of them is, and the list has stopped doing its job.
- Keep the list short enough that you could defend every item on it to the person you are about to reject for missing one.
- Write the transfer test for each adjacency you would accept, so it is agreed rather than argued at shortlist.
- Revisit the list if the search stalls — but revisit it deliberately, in writing, not candidate by candidate.
Who owns each decision
Decision owner is the easiest column to leave blank and an expensive one to skip. An offer that needs three people to agree, none of whom is accountable, is an offer that moves slowly — and a slow offer is one a candidate with other options may not wait for.
Name one decision owner per role. The interview owner keeps the process moving; the decision owner says yes or no. They can be the same person for a junior role and should not be for a leadership one.
What the plan costs, and when
A hiring plan has three cost layers and they do not arrive together: salary and employer costs from the start date, recruitment cost on whatever terms you agreed, and the internal time the searches consume. The first two can be modelled; the third is the one that is easiest to leave out of the model entirely.
Model the recruitment cost per month rather than per role, because that is how it hits the bank account. A plan with four hires in one quarter and traditional placement fees concentrates the recruitment cost into the same weeks as four new salaries, four laptops and four onboardings — which is a cash shape worth seeing before you commit to the sequence rather than after.
What changes by stage
Earlier, the plan is short and the roles are broad: you are hiring people who can cover more than one thing, and the sequencing question is mostly which constraint hurts most. At that size the decision owner is a founder, because there is nobody else it could be.
Later, the plan gets longer, the roles get narrower and the dependencies multiply, because hires start depending on managers who do not exist yet. The failure mode shifts from picking the wrong role to running more searches than the organisation can interview for.
These are tendencies, not rules. A deep-tech company at seed can have a narrower first hire than a consumer company at Series A, and the plan should follow the work rather than the funding label.
When to revisit the plan
Review on events, not on a calendar ritual that nobody prepares for.
- A search passes its hire-by date without a shortlist.
- A dependency moves, which re-sequences everything behind it.
- Runway changes, in either direction.
- An outcome is delivered another way, which should remove a row rather than leave it open.
- Two searches are competing for the same interviewers, which means the sequence was too optimistic.
Common questions
- What should a startup hiring plan actually contain?
- One row per role with why it is needed now, the outcome it must deliver, the must-have capability, a hire-by date, the salary you will pay, the interview owner, the decision owner, dependencies, the risk if it slips, and current status. An empty column is usually a decision nobody has made yet rather than a detail that does not matter.
- Should a hiring plan be a document or a spreadsheet?
- A spreadsheet, or anything else you can sort and re-sequence. The value of a plan is that you can reorder it when a dependency moves and re-cost it when runway changes; a well-written page cannot do either. Write the narrative for the board from the table, not instead of it.
- When should a hiring plan be reviewed?
- On events, not on a monthly ritual nobody prepares for. A missed hire-by date, a moved dependency, a change in runway, an outcome delivered another way, or two searches competing for the same interviewers — each of those changes the sequence and is worth a deliberate re-plan.
- Should the hiring plan include contractors and part-time help?
- Yes, if they are delivering an outcome on the plan. Leaving them out makes the sequence look more achievable than it is, and hides the case where a contractor is the better answer for a defined piece of work.
- What is the easiest mistake to make in a hiring plan?
- Sequencing against cash alone. A quarter that the budget can carry can still ask for more senior interview time than the team has, and the result is several half-run processes rather than one finished hire.
Plan several hires together
Add the roles you expect to hire, phase them across the year and see the combined monthly cost of the whole plan.
Open the team hiring plannerAny percentages or figures shown in this article are illustrative examples used to explain the model. They are not quoted rates, market benchmarks or salary data.