Hiring Manager Intake Meeting Template
Four documents and three sheets, built so the meeting ends in a signed choice between level, budget and the start date.
Free download · No account needed
The intake conversation nobody has in week one
Level, budget, date. Pick two
Where your own history says the search takes longer than the date allows, one of these three is happening whether or not anybody decided it.
A. Hold The Level And The Budget
Give up the date. Costs whatever a week of slippage costs, which is a figure the hiring manager has to supply. If nothing happens when the date moves, this option is free and there was never a trilemma.
B. Hold The Level And The Date
Pay above the band. Frequently the cheapest option in the first year, and almost always the first one rejected, because the delay it avoids is not in anybody's budget line while the salary is.
C. Hold The Date And The Budget
Lower the level. Cheapest over a long horizon and the most expensive in year one, because the extra weeks to independent delivery and the supervision they need are real and land on somebody already covering the empty seat.
There Is No Fourth
Widening the search, adding a sourcer, running two recruiters. All real things to try, all attempts to move the median, and none of them a way out: until the median actually moves, the plan still rests on the old one. So they belong in the capacity commitment, not in the choice.
The questions on an intake template are usually fine. What none of them does is make anybody choose. A manager wants a senior person, at the salary they budgeted, starting soon, and where your own history says that search runs longer than the date allows, those three cannot all be held. Something gives. The only question is whether it gives in week one with the arithmetic on the table, or in month four with a quarter gone and nobody having decided anything.
So the days come from your own closed requisitions, grouped on two variables rather than one: the level, and where in the band the accepted offer actually landed. That second cut is the one nobody runs. At Larkspur Analytics, nineteen closed engineering requisitions say a senior search at or below midpoint took a median 118 days and one above the 75th percentile took 67. Which turns paying above band from a concession into a schedule instrument with a number on it.
REQ-2091 needed somebody in 74 days. Holding level and budget costs 44 days late and 52,800 of contractor cover. Paying 148,000 lands seven days early and is cheapest in year one by 21,337. Hiring at mid level lands fourteen days early and is cheapest over 3.1 years by 33,090. The order inverts, so the answer turns on a horizon that is on no template. This feeds the interview loop and the requirement register.
What is in the pack
Time to Fill by Level and Band Position
Your own closed requisitions grouped on two variables at once, with every individual day count listed rather than summarised, medians rather than means, and a group size warning on anything under five observations. The second variable is the one no applicant tracking system reports.
The three priced options
Each one carried to a first-year total on a fixed twelve-month window, a year-two annual salary, and a total across the stated horizon. Plus the crossover month where the cheapest-in-year-one option stops being cheapest, computed from its advantage over its annual penalty.
Requirement Priority
Every requirement with what the person does in week two that needs it, whether it is teachable in a quarter, how it would be tested, and what would be accepted instead. A must-have needs a week-two answer and a test, or it is recorded as a preference. Content validity under the federal selection guidelines rests on a job analysis of the important work behaviours and their relative importance, and relative importance is exactly what this column is.
Intake Questions
Twenty-five questions, and the last nine are the ones that make the meeting produce something. What a week of slippage costs. How long you expect this person in this seat. Then the three options with their numbers, and which one we are doing.
Role Agreement
One page, signed by both people, keeping all three priced options visible including the two nobody chose. Section six names the option, quotes the manager's own reasoning, and states what is being given up with a figure and an approver.
Trade-off Note
Half a page sent to the people the choice affects rather than filed with the requisition. Each rejected option carries the number that made it attractive, and the note flags where the delay cost lands in the accounts.
Timeline and Capacity Commitment
Both sides' promises with named owners and consequences. Days to first submission, submissions a week, interview slots held, feedback turnaround, and the recruiter's concurrent requisition count, because a date missed by a slow debrief is not a sourcing failure.
How it works
- 1
Send two years of closed requisitions
With the level, the band, the accepted offer and days from open to accept. The 75th percentile gets computed from the band rather than guessed from the offers.
- 2
The gap comes back first
Your median for this level and band position, the date it implies, the date the manager asked for, and which of the three options are even available.
- 3
The meeting produces two answers
What a week of slippage costs, and how long you expect this person in this seat. Neither is in any role request, and the options cannot be priced without both.
- 4
One option gets signed, and what it gave up
All three stay visible in the agreement. The choice, its cost, its approver and the reopen date go in with names against them.
Frequently asked questions
Why not just use a list of intake questions?
Because a list produces answers that were never tested against each other. The manager says senior, says 132,000 and says ten weeks in three separate replies, and nothing in the form notices that the company's own record makes those three mutually exclusive. The choice is the artifact; the questions only exist to make it possible.
Where do the days actually come from?
Your closed requisitions, grouped by level and by where in the band the accepted offer landed. Not an industry benchmark. The second cut is the one that matters and almost nobody runs it, because it is the only segmentation that converts money into weeks in your own numbers rather than in somebody else's.
Is paying above the band really faster, or is that just correlation?
It is a correlation in your own data, and the pack says so rather than claiming a mechanism. Above-band offers may go to stronger candidates, or to searches that had already stalled. What makes it usable is that it is your record, with the group size printed next to it, which is more than a benchmark can offer.
What if the manager will not put a number on the delay?
Then ask what happens if the date slips a month and write the answer down. If the honest answer is that nothing much happens, the date is a preference, option A is free, and there is no trilemma on this role. That is a real and common outcome. An urgent date with no consequence behind it will be traded away silently in month three.
Why does the horizon change the answer?
Because the trade-off costs are one-off and the salary difference is permanent. Here the above-band option is cheapest in year one by 21,337, then costs 16,000 a year more forever, so it stops being cheapest at month 28. Against the lower-level option it stops at month 22. Different horizons, different answers, same numbers.
Where does this sit against the rest of hiring?
First, on one requisition. It settles the level and the band that the requirement register turns into a job description, before the interview loop assigns competencies and the offer prices the number. All of them together against the recruiters you have is the capacity plan. Four documents, three sheets, free.
End the intake with a signature, not a summary
Send a role request, your band structure, and two years of closed requisitions. The first thing back is the gap between your own median and the date somebody has asked for, in days.
Edit with AI