Most advice about intake meetings assumes the hiring manager shows up with a settled role and the recruiter’s job is to extract it. Often the role isn’t settled at all. The manager knows roughly what the team is missing, and they’ll work out what they actually want by looking at candidates.

The 2026 AI & Hiring Alignment Report asked how many of a team’s searches start with the recruiter and their counterpart aligned on requirements. Where AI was core to hiring, 68% of searches started that way. Where teams didn’t use AI, 49% did. Each figure is a share of searches. Teams aren’t the denominator here. The study is a survey Metaview ran with 505 recruiting leaders and hiring managers at companies with 200 or more employees in North America and EMEA, and it didn’t test what produced the gap. The stronger group is the one to look at. Even there, close to a third of searches begin without agreement on what they’re looking for.

So this article treats the intake as the first of two conversations. It isn’t the one that settles the role. Thirty minutes to write down what’s been decided, name what hasn’t, and book the review where the rest gets decided. Below: how to prepare, the agenda, the eight questions, a template you can copy, and what to do with the call once it ends.

What an intake meeting can and cannot settle

An intake meeting can settle the facts of the job. What the team is trying to get done. What the work looks like week to week. Who the new person sits with, what the process is, what the range is. None of that is hidden. The hiring manager already knows it, and half an hour of good questions will get it out of them.

It can’t settle the trade-offs, because those are the parts the hiring manager usually hasn’t had to decide yet. Deep domain experience against speed. A specialist against someone who can cover two jobs. The candidate who’s obviously strong and obviously expensive. Nobody resolves any of that in the abstract. It gets resolved when a real person is in front of you and somebody has to say yes or no.

That changes what you write down, in two ways. First, the useful output of an intake is two lists where most templates have one: what was agreed, and what was left open. A requirement nobody could rank against another requirement belongs in the record, marked as unresolved. That’s information the search needs, and it disappears if the notes only capture conclusions.

Second, the meeting should end with the next conversation already on the calendar. If the trade-offs get resolved when the manager sees candidates, then the first profile review is where the role actually gets defined. Left as “we’ll find time,” that review lands after the first rejection. It needed to come before it.

Before the call: give the hiring manager something to react to

Send two things a day or two ahead: the current job description with your questions marked on it, and three or four real profiles at different levels.

The profiles are the important part, and they don’t need to be good. They exist so the hiring manager has something specific to say yes or no about. A manager who asks for someone “senior enough to run discovery alone” and then rejects a profile with eight years of experience has told you something the word senior never would. Ask what was missing and you’ll leave with an answer you can write down.

That’s craft advice, and the data below doesn’t measure it. Nothing there shows that profile reactions produce clearer requirements. The defensible claim is a narrower one: a rejection you can ask about is more specific than an adjective, and specific requirements are easier to source against.

Set the invite so the purpose is obvious. “Quick sync on the PM req” invites a hiring manager to forward the job description and leave.

The 30-minute agenda

Thirty minutes is a budget, and the data doesn’t say it’s the right length. Across 3,511 intake calls classified in Metaview’s corpus, the mean length was 35.3 minutes, so this agenda fits in thirty and tends to run a little past. Unfamiliar or senior roles need more. The structure holds either way, because each segment has an output you can point at when it’s done.

Protect that last segment when the call runs long and something has to give. Nothing here measures how often it gets dropped, but a review nobody has scheduled is a review nobody owns, and by the argument above it’s the one meeting where the role gets its real definition.

The eight questions, and what a missing answer tells you

The job description tells you what somebody wrote down. These eight tell you how the job will actually work and, just as usefully, which parts the hiring manager hasn’t settled. Ask each one and note whether you got an answer or a maybe. The maybes go on the open list.

• First 90 days. “What should this person deliver in their first 90 days?” This moves the conversation from a list of traits to work somebody will own. If the answer is a list of meetings to attend, the role may not have a defined job inside it yet.
• The success pattern. “Who has done similar work well here, and what made them effective?” You want the conditions around that person rather than a request to clone their résumé.
• The failure mode. “What would make someone struggle in this role?” Answers often point at missing support or unclear ownership rather than a missing skill.
• The tradeable requirements. “Which of these are genuinely non-negotiable, and which would you trade for strength elsewhere?” This is the question that most often produces a maybe, and a maybe here is the most useful thing you can leave with. It tells you which decision the profile review has to force.
• The week-six calendar. “What does this person’s week look like once they are settled in?” Meetings, decision rights, and daily partners describe a job more precisely than a title does.
• The internal-candidate test. “What would rule out a strong internal candidate?” Useful for separating a need for new expertise from a need for more capacity.
• The honest pitch. “Why would a good candidate want this job, and what will they find hard about it?” You need both halves before you can describe the role to anyone.
• The last rejection. “What made you turn down the last candidate who looked strong on paper?” This surfaces preferences that never reached the job description. It is also the question most likely to contradict something said earlier in the same meeting, which is worth catching in the room.

When you hear a vague word, ask what it looks like in practice. “Strategic” can mean owning the roadmap, influencing executives, or working without close supervision. Those need different evidence and different interviewers, so you have to pin the word down before anyone writes a scorecard.

Then write down the non-answers. A hiring manager who can’t rank two must-haves against each other has shown you where the search is going to get stuck, and that’s worth more in the record than a confident answer to a question they’d already thought about.

These questions also give your sourcing strategy and your interview panel the same starting point, which is a modest claim: everyone reads the same document. They won’t all read it the same way, and that’s what the calibration review is for.

The intake template you can copy

Six sections, and a third column that most intake templates leave out.

A template holding only agreed requirements reads as though the role were settled, and three weeks later nobody can tell which lines were decisions and which were guesses. The third column is what stops that.

Fill the third column honestly. If it comes out empty after half an hour on a role nobody has hired for before, the questions probably weren’t pushed hard enough.

Then turn the agreed lines of the middle column into a draft scorecard before anyone leaves. Keep each criterion job-related, mark it must-have or nice-to-have, and name the stage that will assess it. That same split carries over to the scorecard template the panel fills in. Write criteria as evidence somebody can look for: “has led enterprise discovery calls without a sales engineer” gives an interview rubric something to test, and “customer-obsessed” doesn’t.

Leave the third column out of the scorecard. An unresolved trade-off handed to four interviewers comes back as four different scorecards.

What to do with the call after it ends

The intake produces a record, and the record is only worth having if it exists before the next thing happens. That’s two jobs: get the conversation into notes people will read, and get profiles moving while the conversation is still fresh.

When everyone on the call knows and agrees, Metaview’s Notetaker records and transcribes the conversation and turns it into structured notes. That takes care of the transcription. Metaview doesn’t decide which of the manager’s sentences was a requirement, which was a preference, and which was a trade-off nobody resolved. That reading belongs to the recruiter, and it’s the part of the job worth doing slowly. Check the draft against your own memory of the call, fix what it flattened, and add the open column, which no set of notes can infer, because it’s a record of what wasn’t said.

When the requirements move in week three, and they will, you can go back and read what was agreed. That’s the one reason the transcript is worth keeping.

How those notes reach your ATS depends on the integration, and it varies by tool. The integrations page lists what each one supports today. Check it before you promise a hiring manager that the brief will appear next to the candidate record.

A captured intake also gives AI Sourcing somewhere to start: with Metaview on the call, the agent can use the transcript to draft the initial search and candidate profile. The recruiter reviews and approves that profile before the search runs, and that step isn’t a formality. The draft is built from what the manager said, including the parts they hadn’t decided, so the recruiter’s edit is where an open question stays open and doesn’t get quietly guessed at.

Across 26,356 intake-linked searches in Metaview’s corpus, a first shortlist arrived a median of 17.6 minutes after the call ended, with the middle half between 14.2 and 23.2 minutes. A quarter of those searches took longer than 23.2 minutes, and the quartiles won’t tell you how much longer the slowest ones ran. Speed is also separate from accuracy. The figure measures how long a first list took to appear, and it says nothing about whether the people on it suited the role.

The caveat doesn’t cost you much here. A shortlist that exists the same afternoon means the profile review can happen while the intake conversation is still in everyone’s head, which is the second conversation this whole article has been pointing at.

Here’s the one thing this article can’t do for you. Everything above helps a recruiter and a hiring manager agree, in writing, on what they’re looking for. None of it tells you whether what they agreed was right. Two people can be perfectly aligned on a bad specification, and an interview record holds nothing about what happened once somebody started the job. Judging whether the criteria were the right ones takes outcome data gathered on the job, and that’s a separate exercise from anything described here.