Recruitment intake meeting: agenda, questions and checklist
Run a focused hiring-manager intake meeting with a 30-minute agenda, practical questions and a six-step checklist. Includes a fictional UAE sales brief.
Vettara editorial team · · Updated
A recruitment intake meeting is a discussion between a recruiter and hiring manager before sourcing begins. Its output is an agreed role brief: outcomes, essential criteria, practical conditions, search scope, evidence standards and decision owners. Use the agenda, questions and six-step checklist below to record decisions and unresolved questions. The timing and fictional example are our suggested working approach, not a required standard or a promise about hiring outcomes.
Before the meeting: bring decisions, not adjectives
Ask the hiring manager to bring the business reason for the hire, the reporting line and any approved practical constraints. Bring the existing job description if there is one, but treat it as an input rather than an agreed search specification.
OPM's guidance on job analysis connects job tasks with the competencies needed to perform them. Use that principle to turn a broad request into questions your team can investigate.
How to conduct a recruitment intake meeting: a 30-minute agenda
For a role the team already understands, use this suggested 30-minute agenda to keep the discussion focused. Allow more time for a new or contested mandate. Share the draft brief in advance and finish by reading back the decisions; do not shorten a disagreement just to meet the timebox.
| Time | Question to ask the hiring manager | Decision to record |
|---|---|---|
| 0–5 minutes | Why are we hiring, and what work must change? | Business need, responsibilities and expected outcomes |
| 5–10 minutes | Which capabilities are essential, and why? | Must-haves, preferences and acceptable alternative evidence |
| 10–15 minutes | What location, budget and work pattern are approved? | Confirmed conditions and owners for missing answers |
| 15–20 minutes | Which markets and company types make sense to research? | Search scope and the reason for each boundary |
| 20–25 minutes | What would justify progressing a person for assessment? | Evidence standard, gaps and human checks |
| 25–30 minutes | Who approves the brief and reviews the first research? | Decision owner, next review and versioned brief |
Who should attend the intake meeting?
Include the recruiter running the search and the hiring manager who owns the role. Bring a specialist reviewer or another decision-maker when they own a requirement that the hiring manager cannot resolve alone. Name one person who can approve changes to the brief.
The recruiter translates the need into a research plan; the hiring manager explains the work and tradeoffs. Neither should assume the other has confirmed the budget, work arrangement or assessment process. Record who will resolve each open item.
1. Agree the work and expected outcomes
What will this person own? What should change after they join? Write outcomes that the hiring manager can explain, including the context and an agreed review period.
Replace “commercially strong leader” with the work behind the phrase. Do not invent targets the business has not approved.
2. Separate essentials, preferences and learnable skills
For each requirement, ask why it matters to the work. Which capability must be present at the start, which experience is helpful, and what could be learned with support?
Record alternative ways someone could demonstrate the capability. A particular employer or identical job title should not become an automatic exclusion rule without a job related reason.
3. Confirm location, work pattern and practical conditions
Write down the location, onsite or remote expectations, travel, compensation range and intended start window. Label each item confirmed, provisional or unresolved, with an owner for unanswered questions.
Do not infer a person's willingness to relocate, availability or acceptance of these conditions from a profile. Those require confirmation through the recruitment process.
4. Define the target market and explain why
List the role titles, company types and markets that research should cover. Explain their connection to the mandate. Distinguish an approved research boundary from a convenient starting point.
If the scope produces few plausible research leads, revisit the brief with its owner. Do not silently broaden the assignment or declare the market exhausted.
5. Decide what evidence and uncertainty look like
For every essential criterion, name the information that could support it and the questions a profile cannot answer. Record source dates and contradictions. Keep missing evidence separate from evidence that a requirement is not met.
Agree what must be clarified in assessment. A description of an employer's success does not establish an individual candidate's contribution.
6. Name the owners and the next review
Record who approves the brief, who reviews the research and who resolves changed requirements. Give the brief a version and set the next review point.
The meeting is complete when those owners accept the decisions and open questions, not when every box contains an answer.
Example: a fictional UAE enterprise sales lead
This is an illustrative brief, not a real vacancy, candidate record or screenshot of product output. The details demonstrate how to separate a requirement from an assumption.
| Brief field | Illustrative entry | Still to resolve |
|---|---|---|
| Outcome | Build a repeatable enterprise sales process in the UAE. | Hiring manager to agree the baseline and review period. |
| Essential capability | Experience owning a complex business to business sales cycle. | Assess personal responsibility, not only employer reputation. |
| Preference or learnable | Familiarity with the team's CRM is useful, not automatically essential. | Confirm the available training. |
| Work pattern | Role based in Dubai with customer travel under discussion. | Confirm attendance expectations and travel scope. |
| Research market | Enterprise software and adjacent B2B businesses with relevant sales complexity. | Approve the title and company boundaries. |
| Evidence | Role history may indicate relevant account responsibility. | Confirm deal ownership and outcomes during assessment. |
| Owners | Hiring manager approves; recruiter researches and records gaps. | Agree the date and purpose of the next review. |
Take the agreed brief into Vettara
Vettara supports brief led candidate research and evidence backed shortlist review. Bring the agreed, nonconfidential version to a demo and check that the research preserves its boundaries and unanswered questions.
Do not treat the checklist as an automatic assessment or a guarantee of legal compliance. Your team remains responsible for evaluating evidence and deciding the next step.
What should happen after the intake meeting?
Send the agreed brief to its owners, resolve open requirements, and schedule a review of the first research against the same criteria. When the role changes, record the change and reassess the search scope instead of quietly applying new criteria.
In a Vettara demo, bring a nonconfidential version of that brief. Ask to follow the candidate research and inspect the supporting information and unanswered questions. Research supports human assessment; it does not confirm a person's interest, availability or suitability.
Review AI recruitment software against your team's process Bring your brief to a Vettara demoSources & further reading
Bring your brief and book a Vettara demo