What Is an Intake Meeting? Questions, Checklist, and Template

Six weeks into a search, the hiring manager rejects a fourth candidate for a skill that never appeared on the scorecard. The panel has changed twice. One interviewer has been double booked three times because nobody asked what her Tuesdays look like.

The recruiter did everything right after the kickoff call. The kickoff call lasted twenty minutes and covered the job title, the salary band, and a vague sense that the last person in the role was not quite senior enough.

That call was the cheapest place to prevent all of it.

Intake is the least expensive stage in hiring and the most consequential. Everything downstream inherits it: the search strategy, the screening bar, the interview loop, the calendar. Vague inputs do not stay vague. They harden into rework.

What is an intake meeting?

The terminology moves around. Intake meeting, intake call, job intake, recruiting kickoff: same function. A recruiting intake form is the artifact that comes out of it, the written record of what was agreed.

The distinction that matters is between intake and the paperwork before it. A job requisition is the approved request to open a role: budget, headcount, sign-off. The intake meeting is what happens after that approval, when the role stops being a line item and becomes a search. The requisition authorizes hiring. The intake defines it.

One more distinction. Intake is not a briefing where the hiring manager talks and the recruiter takes notes. It is a negotiation. The recruiter's job is to leave with decisions, not a wish list.

Why does a twenty minute intake meeting decide six weeks of coordination?

Recruiting teams are absorbing more volume with less staff. Workday reports application volumes up 32% globally while open roles fell 13%, and Gartner finds 78% of recruiting leaders working with flat or shrinking budgets. There is no slack in the system for avoidable rework.

Undefined intake creates exactly that kind of rework, and it lands on the recruiting coordinator first. Based on candidate.fyi data across 257,946 coordination signals, availability-based scheduling consumes 243 minutes of coordination per loop against 27 minutes when a candidate self-schedules. Time-to-interview runs 5.9 days manually versus 3.9 days automated. A manual reschedule sits unresolved for about 68 hours, against roughly 21 hours when it is handled autonomously.

Now put an undefined panel into that math. Every panel change restarts the availability hunt. Every restart is another 243 minute cycle and another 68 hour gap the candidate experiences as silence. Greenhouse found 50% of candidates have ghosted an employer, and 24% blame slow communication. The intake meeting sits upstream of all of it. See the real price of no-shows and last-minute reschedules for the downstream arithmetic.

What questions should you ask in an intake meeting?

Use this as a running checklist. It is ordered so the conversation moves from why the role exists to how you will actually run it.

Business context

* Why does this role exist now, and what happens if it stays open another quarter?

* Is this a backfill or new headcount? If a backfill, what did the last person do well, and what was missing?

* Who does this person work with most outside the team?

Success at 90 days

* What are the two or three things this person must deliver in the first 90 days?

* How will you know at the six month mark that this hire worked?

Requirements, split honestly

* Which three requirements are genuinely disqualifying?

* Which are preferences you would trade away for a stronger candidate elsewhere?

* Which of these did you list only because the last job description had it?

The honest pitch

* Why would a strong candidate take this job over a competing offer?

* What is genuinely hard about the role that we should say out loud?

Compensation and process

* What is the approved range, and where in it can we move?

* How many interview stages, and what does each one actually assess?

* Who makes the final decision, and who only advises?

Panel and availability

* Who exactly sits on the loop, by name, for each stage?

* What recurring windows can each interviewer protect each week?

* Who is the named backup for each interviewer?

* What is our committed turnaround for feedback after each stage?

The last block is the one to protect when the meeting runs short. Requirements can be refined over the first few candidates. A panel that was never named cannot be scheduled.

Not sure which stage is actually costing you days? The two minute coordination maturity assessment pinpoints where your loop breaks down.

What does a recruiting intake form need that most templates miss?

Search for a recruiting intake form template and you will find a dozen good ones. Almost all are strong on the role and silent on the calendar. That gap is the whole problem.

The named panel, per stage. Not someone from platform. A name, a title, and a stage. Named panels can be load balanced and given backups. Unnamed panels get assembled in a hurry by whoever is free, which is how interviewers end up assessing things they were never calibrated on.

Protected availability windows. Ask each interviewer for recurring blocks they will hold. This single field converts scheduling from a negotiation into a lookup. It is also the field hiring managers resist most, which tells you roughly what it is worth.

Committed feedback turnaround. Agree the number at intake, in hours. Feedback delay is invisible in most reporting, and it is where candidates go cold.

Write these in as required fields. Optional fields on an intake form are decorative. If the panel and availability rows can be left blank, they will be, and the cost surfaces four weeks later when nobody can explain why a strong candidate has been waiting nine days for a second round.

Is a formal intake meeting just overhead if you talk to hiring managers constantly?

This is the fair objection, and it deserves a direct answer rather than a process lecture.

The objection has real merit. Recruiters embedded with a business unit often do know the roles better than any form would capture. Adding a mandatory thirty minute ceremony to every requisition is a good way to teach people to rush through it. Ceremony is not alignment.

But the test is not how often you talk. It is whether the conversation produced decisions someone else could act on. Ask one question about any open role: could a coordinator who has never spoken to the hiring manager build the loop from what is written down? If the answer is no, the alignment lives in one person's head, and it will not survive that person taking a week off.

So scale the format to the risk:

* Straightforward backfill, same panel, unchanged scorecard: a form is enough. Confirm the panel and availability are still accurate and move on.

* New role, new manager, senior scope, or a role that failed a previous search: a full meeting. These are the roles where unstated assumptions cost the most.

* Any role whose requirements list runs past eight items: a full meeting, specifically to cut the list down.

The goal is not more meetings. It is that no search starts on assumptions nobody wrote down.

How does candidate.fyi turn intake decisions into coordination?

candidate.fyi is an AI coordination layer for interviews, powered by fyi, an agent that runs scheduling, confirmations, reminders, and reschedules end to end. Intake decisions are what it operates on: define the panel, the stages, and the availability rules once, and the loop builds itself from there.

That division of labor shows up in the numbers. fyi handles 46% of scheduling tasks autonomously, candidates self-serve 26%, and coordinators keep the 28% that genuinely needs judgment. Automated touchpoints also rate higher with candidates, at 4.63 out of 5 for automated recruiter screens against 4.22 for manually coordinated interviews. Relativity Space moved scheduling from 2.8 days to 16.2 hours in six weeks. Intercom gets candidates to a first interview in under 24 hours.

When candidate.fyi connects to Workday, scheduling starts the moment a candidate advances, and every invite, update, and reschedule flows back so Workday stays the source of truth. The confirmation email fires from the same source, which is why it never drifts out of sync with the schedule.

None of this rescues a bad intake. An agent can schedule a panel instantly. It cannot tell you the panel was wrong. Define it properly once, and coordination stops being a job. For the mechanics downstream, see our interview scheduling best practices, and the coordination maturity model for which stage to fix first.

Frequently asked questions

What is an intake meeting in recruiting?

An intake meeting in recruiting is the structured kickoff between a recruiter and a hiring manager at the start of a search. It defines the role, the must-have requirements, the compensation range, the interview stages, and the panel. Its purpose is to replace assumptions with written decisions before sourcing begins.

What is the difference between an intake meeting and an intake call?

There is no functional difference. Intake call, intake meeting, job intake, and recruiting kickoff all describe the same conversation. Some teams use intake call for a shorter check-in on a straightforward backfill and intake meeting for a full session on a new or senior role, but the agenda is the same.

What should a recruiting intake form include?

A recruiting intake form should capture business context, first 90 day deliverables, must-have versus nice-to-have requirements, the compensation range, the interview stages, the named panel per stage, each interviewer's protected availability windows, and the committed feedback turnaround. Make the panel and availability rows required rather than optional.

How does the intake meeting connect to Workday or your ATS?

In most ATS setups the intake output lives outside the system, in a doc or a recruiter's notes, so the panel and availability get re-entered at scheduling time. With candidate.fyi connected to Workday, the panel and stage structure become the scheduling configuration, so coordination begins when a candidate advances and every update flows back to Workday.

How long should an intake meeting be?

Thirty minutes is enough for a straightforward backfill. A new or senior role usually needs forty-five to sixty. Length matters less than output: if the meeting ends without a named panel per stage and availability windows for each interviewer, it was too short regardless of how long it ran.

The bottom line

The intake meeting is thirty minutes that either removes six weeks of friction or creates it. Most teams treat it as a briefing about the role. Treat it instead as the moment you lock the operating decisions: the disqualifying requirements, the named panel, the availability each interviewer will protect, and the feedback clock.

Write those down where a coordinator can act on them. Then the search runs on decisions instead of assumptions, and the calendar stops being the thing that slows your hiring down.

Want to see what happens after a clean intake? We will map your loop against your current coordination load. Book a demo.