The Intake Brief Nobody Writes: How Hiring Managers Are Setting Their Own Searches Up to Fail

If you had to name the single biggest predictor of a tech search that fails, takes twice as long as it should, or produces a hire who exits within a year, the answer is not the sourcing strategy, the compensation band, or the interview process. It is the absence of a well-constructed intake brief before the search begins.

This is not a new observation, but it is one that the industry has mostly refused to act on. Survey data from the Society for Human Resource Management consistently finds that fewer than 35 percent of hiring managers report having a formal intake process for new requisitions. Most searches begin with a JD, which is often a recycled document from the last time the role was open, and end when someone accepts an offer for a role that may or may not be accurately described by that document. The gap between what was written and what was needed is where most hiring failures live.

What Most TA Teams Actually Receive

The typical intake process at an enterprise or GCC runs as follows. A headcount requisition is approved. HR receives a ticket. TA is assigned the req. The job description attached is the one that was posted last time this role was filled, with the date updated and possibly a couple of technology stack updates added by whoever had five minutes to look at it. The hiring manager is sent an email confirming the req has been picked up. Sourcing begins.

Nobody sat down and asked: what does this role need to accomplish in the next 90 days? What has made previous hires in this function succeed or struggle? What is the team dynamic this person is walking into? What is the real technology environment, as opposed to the aspirational one described in the JD? What are the unstated requirements, the leadership style compatibility, the growth expectations, the things you would only know if you have been in that team?

What a Good Intake Brief Actually Covers

A proper intake brief for a senior technology role should cover six areas. These are not bureaucratic checkboxes. They are the questions that, when answered, allow a sourcing function to do its job properly.

Technical requirements, specifically ranked. Not a list of every tool in the stack, but the three to four things without which this person cannot succeed in this role. Ranked in priority order so that tradeoffs can be made intelligently when a candidate is strong in some areas and developing in others.

Team context. Who they will be working with, at what level of seniority, in what functional model. Whether they will be leading, contributing, or both. What the team's current dynamic is: high-performing and established, or being built, or in transition from one state to another.

Culture fit markers. Not vague values statements but observable behaviours. What does someone who fits well here actually do? What does someone who does not fit do? What communication style works in this environment? These questions are hard to answer but the answers are consistently the most useful information a recruiter can have when assessing a candidate.

90-day success criteria. What does good look like at 30 days, 60 days, 90 days? Not a job description, but a success picture. If the hiring manager cannot answer this question, the search should not start yet because the role is not fully defined.

Historical failure modes. What has made previous people in this role, or equivalent roles, fail or exit? This is the question most hiring managers do not want to answer because it requires honesty about the team, the manager, or the organisation. It is also the question whose answer is most predictive of future attrition.

The unstated requirements. Every hiring manager has a picture in their head of the person they want that is not fully captured in the JD. Drawing that out explicitly is the difference between sourcing for the job description and sourcing for the actual need.

Why This Does Not Happen

The reason most searches start without a proper intake is not ignorance. TA leaders know this information matters. The reason is structural: the intake conversation requires 45 to 60 minutes of a hiring manager's time before any visible hiring activity begins, and in most organisations there is no mechanism to require it and no consequence for not doing it. Hiring managers are busy. TA is measured on time-to-fill. Everyone defaults to starting sourcing because starting sourcing feels like progress.

The organisations that have solved this problem have made the intake conversation a gate, not a recommendation. The req does not go live until the intake brief is complete and signed off. That creates a small amount of friction at the start of the process in exchange for a significant reduction in wasted cycles downstream. The net effect on time-to-hire is positive, not negative, because the searches that start with a proper brief close faster and produce fewer re-opens.

The Quality-to-Shortlist Difference

The most direct measure of what a good intake brief produces is the quality-to-shortlist ratio: the percentage of submitted profiles that the hiring manager considers worth interviewing. For searches that begin with a full intake session, this ratio runs at 55 to 70 percent based on our own engagement data at Qfyre. For searches that begin with a recycled JD and no intake conversation, the ratio runs at 20 to 30 percent.

That difference means hiring managers spend less time in interviews with candidates who were never right for the role. It means the people who go through your process are more likely to receive an offer. It means the candidates you do not hire are treated more respectfully because the reasons are real rather than the result of a mismatch that should have been surfaced before sourcing began.

The Fit Discovery session is the first step in the FYRE methodology for the same reason the intake brief is the first requirement in any properly run search: because every subsequent decision in the process depends on the quality of the brief that started it. Get that right, and the rest of the funnel works. Skip it, and you are optimising a system that is already pointed in the wrong direction.

If you are running searches right now from JDs that were last substantively updated two years ago, the intake session is the change with the highest return on investment available to you. It costs 45 minutes. It pays back in every search that does not need to be reopened.