Most bad searches do not fail on the sourcing. They fail on the call before it. A recruiter takes a rough job description, nods through a 20 minute brief, and starts sending profiles. Two weeks later the hiring manager rejects the whole shortlist, changes a must-have, and the search resets. That reset was decided at the intake meeting, not on LinkedIn.
Quick disambiguation, because the phrase is overloaded. This guide is about the recruiter intake meeting: the alignment call between a recruiter and a hiring manager before sourcing begins. It is not an HR onboarding intake, a legal client intake, or a school intake. If you searched hoping to prep for a call a recruiter booked with you as a candidate, this is the other side of that conversation.
Getting it right matters because hiring is expensive and mostly unmeasured. SHRM's 2025 benchmarking puts the average cost per hire at $5,475 for non-executive roles and $35,879 for executives, and found that only 20% of organizations track quality of hire at all. So the teams most likely to make a costly hire are often the ones with no way to tell whether it worked. The intake meeting is the cheapest point in the entire process to prevent that.
What a recruiter intake meeting is
An intake meeting is a focused conversation, usually 30 to 45 minutes, between the recruiter and the person who owns the hire, before any outreach happens. The output is not notes. It is a shared, written definition of the role, an honest read on whether it can be filled as described, and agreement on how the first candidates will be judged.
It helps to separate three things people call "intake."
| Meeting | Who is in the room | Purpose |
|---|---|---|
| Recruiter intake meeting (this guide) | Recruiter and hiring manager | Define the role and test whether it is fillable, before sourcing. |
| Panel kickoff or calibration | Recruiter and the full interview panel | Align on how candidates will be evaluated, after intake. |
| HR intake | HR and an employee or new hire | Onboarding or case intake. Unrelated to sourcing. |
Why the order-taker loses
There are two ways to run this call. You can take the order, or you can diagnose the problem. The order-taker writes down the requirements and leaves. The diagnostician leaves with a role the hiring manager may not have fully articulated when the call started.
The shift is old advice that still separates the top of the field from the rest. Lou Adler has argued for years that the most valuable thing you do at intake is define the work, not the skills: what this person has to accomplish in the first few months, not the checklist of tools they should have used before. A requirement of "five years of Python" tells you nothing about whether the person can do the actual job. A performance definition, "in the first 90 days, take over the payments service and cut its error rate," tells you exactly who to look for and how to pitch them.
The other durable idea comes from the hiring book Who, by Geoff Smart and Randy Street: leave the meeting with a scorecard, a short written definition of the outcomes and competencies that make someone right for the role. Every intake template on the internet borrows this. Almost none of them use it to push back when the outcomes and the offered comp do not match.
The questions that surface the real role
Generic checklists ask for the job title, the salary range, and the timeline. Those get you a job description you could have read yourself. The questions below are built to surface the requirements the hiring manager has not written down.
Ask what this person will ship in their first 90 days. The answer exposes the real seniority bar, which is often a level above or below the title. Ask who has done this role well on the team and who struggled, because the failure story usually contains the unwritten must-have that no JD ever states. Ask which two requirements the manager would trade away to hire a month sooner, which forces the honest split between must-have and nice-to-have. Ask for the honest pitch including the hard parts, because you will need it in outreach and you will lose candidates late if you discover the hard parts at the offer stage. And ask what happened the last time they rejected someone who looked strong on paper, which reveals the criteria they judge by but never say.
Write the answers as observable evidence, not adjectives. "Has run enterprise discovery calls solo" is something you can source and verify. "Customer-obsessed" is not.
The market-reality layer no checklist has
Here is where a recruiter stops being a note-taker and becomes worth the fee. Every template above helps you understand what the manager wants. None of them tells you whether the market will give it to them.
Three questions turn the intake into a reality check. What does this role actually cost in today's market, against real compensation benchmarks rather than last year's budget? Is it fillable on this timeline given how many people with these skills are available in this location? And which of these must-haves could be met by strong passive candidates who are not actively looking, rather than only by the small pool applying right now? A hiring manager who wants a rare skill set at a below-market band on a three-week timeline is not giving you a search. They are giving you a reset in a month, and the intake meeting is your one chance to say so while it is still cheap to fix.
This is the conversation Glozo's market intelligence is built for, and yes, I help build Glozo, so weigh that. Supply and demand by role and geography, compensation benchmarks, and an "Open to Offers" read on who is actually receptive all sit in one view, so you can walk into the intake with the market numbers instead of guessing at them. The tactic works with any data source you trust. The point is that the strongest intake meeting is a negotiation with reality, and reality is knowable now.
What AI changes about intake, and what it doesn't
In 2026 the mechanics of the intake meeting are largely automated, and the judgment is not. Both halves are real.
AI notetakers now record the call, transcribe it, generate a structured intake brief, and write it back into the ATS. Tools like Metaview and BrightHire do this natively, with general notetakers like Fireflies adding ATS sync, and a large language model will draft a first question list from the job description before you dial in. That is genuine time back, and if you are still typing up intake notes by hand you are spending your scarcest attention on the cheapest part of the task.
What no tool does is the part that decides the search. Reading whether the urgency behind the req is real or performative. Pushing back when the must-have list is unhireable at the budget. Judging whether the role can be filled at all on this timeline. Those are trust-and-judgment calls a human has to own, which is exactly why the intake meeting sits in the "about half automatable" band on the Recruiting Automation Map: capture is handled, diagnosis is yours. The wider argument for why that judgment layer stays human is in where automation stops.
| Part of the intake | 2026 reality |
|---|---|
| Recording and transcribing the call | Automated |
| Drafting the intake brief and writing it to the ATS | Automated |
| Generating a first question list from the JD | Automated |
| Reading real urgency and commitment | Human |
| Pushing back on unrealistic requirements or comp | Human |
| Judging whether the role is fillable | Human |
Leave with three artifacts, not a page of notes
A good intake meeting ends with things you can act on, not a transcript you will never reopen.
The first is a drafted scorecard: four to six outcomes and competencies, each tagged must-have or nice-to-have, each written as observable evidence. Draft it out loud in the last five minutes so the manager corrects it while you are still on the call. The second is a pre-read for the next round: send the manager two or three real profiles at different levels before you go wide, so they react to actual people instead of an abstract spec, which is the fastest way to catch a misaligned level. The third is a booked calibration review of your first batch, on the calendar before you leave, so feedback has a deadline instead of drifting for a week.
Intake meeting red flags
A few signals that the search is about to go sideways, and what to do about each. If the manager cannot name a single outcome for the first 90 days, the role is underdefined and you should not source yet. If everything is a must-have, nothing is, and you push for the two they would trade. If the person on the call is not the real decision-maker, book a short follow-up with whoever is before you spend a credit. If the comp does not match the market for the skills named, say so on the call with the numbers, not in an apology three weeks later. And if no calibration review gets booked, expect vague feedback and a slow search.