How to run a vacancy intake call that actually saves you time

Get the intake right and the search runs itself. Get it wrong and you spend three weeks sourcing against a brief that was never real, before anyone has looked at a single CV. The whole placement is shaped in that first client call.

Here is how to run a vacancy intake meeting that gives you a brief you can actually work from, and the questions that separate it from a search you have to re-open.

Why intake calls go wrong

The usual failure is not skipping the call. It is treating it as a formality. The client lists a job title, a few skills, and a salary, you write it down, and everyone feels productive. Then the first shortlist comes back and the hiring manager says none of these are right, and now you are reverse-engineering what they actually wanted from their rejections.

The brief was thin. You did not know it at the time because thin briefs sound complete in the moment.

Get the context before the checklist

Before requirements, get the why. A role exists for a reason, and the reason shapes everything.

Is this a replacement or a new headcount. If someone left, why did they leave, and what was missing in them that the client wants this time. If it is new, what changed in the business that created the need. The answers tell you what the client is really solving for, which is usually not what the job title says.

Ask what a great hire looks like six months in. Not the skills. The outcome. What will this person have done that makes the client glad they hired them. That answer is your real brief.

The requirements questions that matter

Now the specifics, and the trick is to separate what is genuinely required from what got listed out of habit.

For every must-have, ask why it is a must-have. Half of them will soften under one question, because they were copied from the last job spec. The ones that survive are your real filter.

Get the nice-to-haves separately and named as such, so you are not screening out a strong candidate over something that was never essential.

Pin the things that quietly kill placements late. Salary range, and whether it is real or aspirational. Work model and how flexible it actually is. Notice period they can tolerate. Who else is in the loop on the decision, because a hidden stakeholder is how a done deal falls apart at offer stage.

The process questions nobody asks

The brief is not just the person. It is how the client will hire them.

How many interview stages, and who runs each. How fast can they move, realistically. What does their decision look like, and who has the final say. If the client cannot tell you their own process, that is information too. It usually means a slow, messy search, and you can manage the candidate's expectations from day one instead of losing them to a faster competitor.

Write it down where you will find it

A good intake call is wasted if the brief lives in your memory and a few scribbled lines. Three days later you are working from a softer version of what was said, and the detail that mattered is gone.

The brief needs to be structured and reusable: role context, the real must-haves, the nice-to-haves, salary, work model, process, stakeholders, risks. Same shape every time, so anyone on your team can pick it up and run with it.

This is exactly the gap recording the call closes. You stay present in the conversation instead of typing, and the structured brief comes out of what was actually said, not what survived in your notes.

The short version

Run intake as a real conversation, not a form. Get the why before the what. Challenge every must-have. Pin salary, process, and stakeholders early. Then capture it in a structure you can reuse.

The test for a good intake call is simple. Could someone else run the search from your brief without asking you a single question. If yes, you did it right.

Sonarnote records intake calls locally, without a bot joining the meeting, and turns them into structured job briefs your whole team can work from. See how it works.