Vettara
Menu

Recruitment guide

Recruitment intake meeting checklist: a brief your team can use

Leave a recruitment intake meeting with a usable brief, not just a page of opinions. This checklist helps the hiring manager and recruiter agree what the person needs to accomplish, what research should investigate and which decisions are still open. Copy the questions into your own document. The format is our suggested working template, 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 job-analysis guidance connects job tasks with the competencies needed to perform them. Use that principle to turn a broad request into questions your team can investigate.

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 fieldIllustrative entryStill to resolve
OutcomeBuild a repeatable enterprise sales process in the UAE.Hiring manager to agree the baseline and review period.
Essential capabilityExperience owning a complex business-to-business sales cycle.Assess personal responsibility, not only employer reputation.
Preference or learnableFamiliarity with the team's CRM is useful, not automatically essential.Confirm the available training.
Work patternDubai-based role with customer travel under discussion.Confirm attendance expectations and travel scope.
Research marketEnterprise software and adjacent B2B businesses with relevant sales complexity.Approve the title and company boundaries.
EvidenceRole history may indicate relevant account responsibility.Confirm deal ownership and outcomes during assessment.
OwnersHiring 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, non-confidential 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 legal-compliance guarantee. Your team remains responsible for evaluating evidence and deciding the next step.

Sources and further reading

See how Vettara supports executive search →

Keep exploring

Recruitment guide

Hiring breaks before the first interview: fix the brief

A stronger candidate shortlist starts with an agreed role brief. Separate essential criteria from preferences and turn a vague hiring request into a research plan.

Read the guide →
Recruitment guide

AI sourcing software vs ATS: find the gap before you buy

Compare candidate sourcing software and applicant tracking systems by the work you need done. Check evidence, overlap and handoffs before adding another tool.

Read the guide →
Recruitment guide

AI should support your hiring decision, not make it

Candidate scores are not hiring decisions. Use AI recruitment research with checkable evidence, explicit uncertainty and meaningful human review.

Read the guide →

Your next search starts here

Put the guide into context.

Bring a role brief to a Vettara demo and discuss how your team can structure research and review candidate evidence.

Prefer to send a note? Contact us