# Hiring Manager Intake Meeting Questions & a Worked Recruitment Brief

Hiring manager intake meeting questions and a worked brief: connect tasks, requirements, sources, and agreements before opening the role.

- Canonical URL: https://www.harmate.com/en/blog/hiring-manager-intake-meeting-questions-brief
- Author: Harmate Team
- Published: 2026-10-25
- Updated: 2026-10-25T22:45:58.889360+00:00
- Language: en

## Content

# Hiring Manager Intake Meeting Questions & a Worked Recruitment Brief

A hiring manager intake meeting prepares a role before recruitment opens. It helps the manager and recruiter clarify the work, conditions, and unresolved decisions before writing the advertisement or reviewing applications. A list such as “independent, dynamic, strong communicator” is not enough: different people can imagine different work behind those words.

This template links each requirement to a task and source, then separates agreements from questions still needing checks. It is not a candidate scorecard. It clarifies the need upstream without deciding whom to hire.

## Start with the work to be done

The [US Office of Personnel Management describes job analysis](https://www.opm.gov/policy-data-oversight/assessment-and-selection/job-analysis/) in terms of tasks, necessary competencies, and the relationship between them. We use that principle of describing work. It does not make this template a validated assessment or legal guidance.

The manager can bring examples of activities, outputs, and recent difficulties. The recruiter can ask what must be known on arrival, what can be learned, and why a condition is considered essential. If a source is missing, record a check instead of turning a preference into a requirement.

This stage comes before [reviewing applications](/en/blog/predictive-recruitment-why-matching-beats-simple-selection) and preparing [structured interview questions](/en/blog/structured-hiring-interview-guide-criteria-questions-and-notes). Those methods do not replace a clearly described need: a precise interview question can still examine a poorly justified requirement.

## Prepare the discussion with the right material

Include people who can describe the role and resolve questions about its scope. Bring the current role description, work to be transferred, known objectives, and confirmed constraints. Distinguish current documents from habits and assumptions.

Clarify the request’s status: a proposed role, confirmed replacement, changed scope, or authorized opening. The meeting does not automatically approve recruitment. Each unresolved point needs an owner and an observable condition for resolution.

[Workable’s intake meeting questions](https://resources.workable.com/hiring-manager-intake-meeting-questions) already cover the need, criteria, timeline, and coordination. The worked record below makes task-to-requirement links and available evidence explicit, including disagreements that remain unresolved.

## Questions to ask before opening the role

| Topic | Suggested question | Follow-up |
|---|---|---|
| Need | What work needs doing, and what is currently missing to do it? | Is it a new task, different volume, or responsibility to transfer? |
| Activity | Can you describe a recent situation representative of this role? | What was the output, for whom, and under which conditions? |
| Priority | Which tasks should the person take on first? | Which can wait or be supported? |
| Requirement | Why is this skill necessary? | Which concrete task could not be performed without it? |
| Learning | What can be learned after joining? | With what support, time, and limitations? |
| Collaboration | Which roles will the person work with? | What information and decisions pass between them? |
| Conditions | Which job conditions are confirmed and need explaining? | Who can confirm anything uncertain? |
| Participation | Who takes part in recruitment, and with which responsibility? | Who can answer a question about the need or approve a change? |
| Closing | What have we agreed, and what still needs checking? | What is missing before the role can open? |

These questions concern the role, not private information about individuals. Do not use the brief to invent an ideal personality profile or seek someone who resembles the existing team.

## Separate essential, learnable, and unsupported requirements

These are discussion conclusions to document, not labels assigned automatically by a tool. Ask for the reason behind each requirement and check the actual conditions for learning. “We can train someone” remains an assumption if nobody has the time or resources to do so.

Conversely, “five years of experience” may indirectly express a more specific need. Ask which work situation the person must handle and what supports the proposed threshold. Do not arbitrarily substitute another number. Have the people responsible for the need explain and review the requirement.

An unsupported preference should not be presented as an established fact about the job. If it remains disputed, preserve that disagreement in the record and identify what would help resolve it.

## Worked brief: coordinating learning content

**Entirely fictional example.** A team wants to open a content coordination role. The manager initially requests experience with a particular software package. The recruiter asks which task that requirement supports.

| Expected task | Proposed requirement | Available source or evidence | Disagreement or unknown | Agreement or check |
|---|---|---|---|---|
| Prepare an edition from approved text. | Know the team’s software. | An example edition and current workflow are available. | Is knowledge required on arrival, or would experience with a comparable tool be sufficient? | The manager checks whether onboarding support is available before settling the requirement. |
| Consolidate feedback from several authors. | “Be very diplomatic.” | Two examples of conflicting comments are described. | The adjective does not specify what the person must do. | Describe the task: summarize differences, ask the editorial owner to decide, and track the agreed version. |
| Track missing material against the publishing schedule. | Flag a dependency before publication. | The schedule and a missing-image case are examined. | Who can move publication? | The editorial owner keeps that decision; this role flags the dependency and proposes an update. |
| Help launch a new content format. | Immediate experience with that format. | The format is not yet defined. | The task is insufficiently described to justify a firm requirement. | Keep it as a need to clarify rather than an application filter. |

The table does not determine which candidate would be suitable. It helps avoid publishing inconsistent expectations or letting a vague term carry conflicting interpretations.

## Close the intake with traceable decisions

The final record includes agreed scope, priority tasks, justified requirements, confirmed learning support, and open questions. It also states who can authorize opening the role and how changes will be shared. Do not turn “needs checking” into “approved” in the advertisement.

Ask the manager and relevant contributors to review the record. If two stakeholders expect incompatible activities, the brief should expose the disagreement before candidates are asked to resolve it. A later change may be legitimate; document what changed and revisit the affected materials.

For an unresolved point, specify what evidence is needed rather than record a vague reminder. In the example, the question is not simply “check training.” It is whether someone can provide the software introduction within the proposed start conditions, and which tasks can be supported meanwhile. Until confirmed, that support should not be promised.

[Harmate Open Questions](/en/product/open-questions) can help review several written scoping responses alongside their source excerpts. The team checks meaning and decides scope. Harmate does not determine legitimate job requirements, authorize a role, or select candidates.

The useful result is a need clear enough to prepare the next stage and visible uncertainties with a way to resolve them. The brief remains a revisable working document, not a promise of a successful hire.