River
Y CombinatorBacked by Y Combinator
Log InStart Free
FREE TEMPLATE

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.

Edit with AIDownload Word and CSV

Free download  ·  No account needed

What you get

Pack of 7 files: 4 documents, 3 spreadsheets

Hiring Manager Intake Meeting Template
  • How the Trade-off Is PricedDocument
  • Intake QuestionsDocument
  • Role AgreementDocument
  • Trade-off NoteDocument
  • Requirement PrioritySpreadsheet
  • Time to Fill by Level and Band PositionSpreadsheet
  • Timeline and Capacity CommitmentSpreadsheet
RiverHiring Manager Intake Meeting Template

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.

Cheapest in year one, most expensive over three

One requisition, three priced options, and the segmentation that makes the middle column possible.

Hiring Manager Intake Meeting Template
RiverYour Own History

Time to Fill by Level and Band Position

Illustrative for a fictional analytics firm, Larkspur Analytics. Nineteen requisitions closed in the engineering family over two years. Medians, not means, and every day count listed rather than summarised.

LevelBand position of the accepted offernDays to fill, eachMedianGroup size
seniorat or below midpoint596 / 108 / 118 / 141 / 187118ok
seniorabove the 75th percentile452 / 63 / 71 / 8867four only
midat or below midpoint641 / 52 / 58 / 63 / 74 / 8960.5ok
midabove the 75th percentile429 / 36 / 44 / 5140four only
Paying above the 75th percentile cut the senior median from 118 days to 67. Senior band 118,000 / 138,000 / 158,000, so the 75th percentile is 148,000. Mid band 96,000 / 110,000 / 124,000.

The second column is the whole mechanism. Every applicant tracking system reports time to fill by role or by department; almost none of them segments by where in the band the accepted offer landed, which is the one cut that turns money into weeks. Group sizes are printed beside the medians rather than hidden: a median of four observations is worth reporting and worth flagging in the same breath, and a page that showed 67 days without the n would be selling something.

RiverThe Three Options

The three options, priced

REQ-2091 Senior Data Engineer. Intake 2 March 2026, needed in seat by 15 May, which is 74 days. Budgeted offer 132,000. A week of slippage costs 8,400, being one contractor engineer-week on a migration with a contractual go-live. Onboarding data: seven weeks to independent delivery at senior, nineteen at mid.

OptionLevelOfferMedian
days		In seatvs the
date		Trade-off
cost		First
year		Year 2+
salary		Over
3.1 yrs
A. Hold level and budgetsenior132,00011828 Jun44 late52,800141,764132,000418,964
B. Hold level and datesenior148,000678 May7 early0120,427148,000431,227
C. Hold date and budgetmid112,00060.51 May14 early57,392150,674112,000385,874
Option A detail. 44 days late is 6.3 weeks x 8,400 = 52,800; salary 132,000 for 246 of 365 days = 88,964.
Option C detail. 12 extra ramp weeks at half output is 6 engineer-weeks x 8,400 = 50,400; plus 19 weeks x 4 hours of senior supervision at a loaded 92 = 6,992; salary 112,000 for 304 days = 93,282.
Crossovers. B beats A for 28 months (21,337 of advantage against 16,000 a year). B beats C for 22 months (30,247 against 36,000 a year).

Read the last two columns against each other. The order fully inverts: the option that breaks the budget is cheapest in year one, the option that lowers the level is cheapest across Larkspur's own median tenure of 3.1 years, and the two views disagree completely. Which is why the pack refuses to recommend an option and instead refuses to close an intake until somebody states the horizon. It is the question the whole conversation turns on and it appears on no intake template. Larkspur chose A, for a reason no arithmetic reaches: the migration cannot be led by somebody twelve weeks short of independent delivery, and the supervision would land on the one senior engineer already covering the empty seat.

RiverRequirement Priority

Requirement Priority

The trilemma assumes the level is real. Often it is not, and then option C stops being a concession. Ten rows as stated by the hiring manager, with what survived.

RequirementStatedRecordedWhat they do in week two that needs itTestReason
recorded
Production streaming pipelines at scalemustmustruns the migration cut-over unattendedbroken-pipeline take-homeyes
SQL and warehouse modellingmustmustwrites the schema mapping for tenant onelive modelling exerciseyes
Multi-tenant data isolationmustmustdesigns the tenant boundary, week threescenario walkthroughyes
Leading a technical workstreammuststrong prefcoordination starts week six, not twostructured behaviouralyes
Our specific orchestration toolmustpreferencenot used until week five, learnablenoneyes
Eight years of experiencemustpreferencenothing specific identifiednoneno
Analytics or SaaS industry backgroundmustpreferencenothing specific identifiednoneno
Seven stated must-haves, three survived. Three more rows at strong preference and preference are not shown. A must-have needs a specific week-two answer and something that could test it. Both, or it is recorded as a preference.

Content validity [requires a job analysis of the important work behaviours and their relative importance](https://www.ecfr.gov/current/title-29/part-1607/section-1607.14), and relative importance is what this column is. Where two procedures serve the same legitimate interest and are substantially equally valid, [the one with the lesser adverse impact should be used](https://www.ecfr.gov/current/title-29/section-1607.3), which is a reason to prefer a requirement that predicts over one that filters. Nothing here says a requirement is lawful or job related in the sense any regulation means. The two rows with nothing in the reason column are recorded as having none, and routed.

Edit with AI

What is in the pack

01

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.

02

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.

03

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.

04

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.

05

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.

06

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.

07

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. 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. 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. 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. 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.

Sources

  1. eCFR29 CFR 1607.14 (opens in a new tab)

Written by

Chandler Supple

Co-founder & CEO, River

Chandler has spent the last six years working in AI, building tools for millions of users and Fortune 100 companies. In 2025, he co-founded River to build a new kind of operating system for AI agents.

LinkedInGitHubX

Reviewed by

Brian Joseff, Co-founder, River

LinkedInX

Related

Job description and requirement register

Turns the surviving must-have column into a job description with an objective test written next to every requirement.

Interview process and scorecard

Assigns one interviewer per competency and weights them, using the priorities this intake settled.

Job offer letter and pay equity check

Prices the number at the other end, including what an above-band offer does to the people already in the job.

More free templates

Behavioral Interview Question Bank

Free behavioral interview question bank by competency, with a sheet that scores every question on rating spread and on separation against post-hire outcomes.

Candidate Rejection Email Templates

Free candidate rejection email templates by stage, plus the stale candidate queue that finds everybody already closed in your ATS with nothing ever sent.

FCRA Adverse Action Process Template

Free FCRA adverse action template: both letters, the assessment note, and the waiting period computed from your own written standard rather than remembered.

Interview Process and Scorecard Template

Free interview process template with a weighted competency sheet: one owner per competency, anchored ratings, and an audit of the loop you run today.

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