Change the brief, and the old scores know

Briefs move, and that is normal

Three weeks into a search the hiring manager mentions that the Kubernetes line was never really a dealbreaker, and someone strong who can pick it up is fine. Or the role opens to Pune as well as Bengaluru. Or the team decides they will take a level below and grow the person into it.

None of that is a failure of briefing. A brief is a hypothesis about a market, and running the search is how you test it. The briefs that change once or twice are the ones being tested; the ones that never move are usually the ones nobody has looked at since the kickoff call.

The difficulty is not the change. It is what the change does to the work already done.

A score belongs to a version of the brief

A score is not a fact about a person. It is a judgement of that person against a particular set of requirements, with particular ones marked as dealbreakers. Relax a must-have and the judgement becomes an answer to a question that is no longer being asked.

What makes this quietly expensive is that nothing about the score looks any different afterwards. It sits in the list at the same size, in the same column, beside scores produced an hour ago. There is no visible seam between the two.

So a shortlist assembled after a brief change is usually a mix of two standards. The people judged last week were marked down for missing a requirement that has since become a preference. The people judged today were not. Ranking the two groups against each other produces an order that means nothing, and the candidates it penalises are not the weakest ones. They are the ones who happened to be scored early.

A stale score is not wrong. It is the answer to a question you have stopped asking.

The follow-up comes from the change, not from somebody’s memory

After an edit to the brief, we re-score automatically the people the change can affect: candidates not yet contacted who are at or above the bar, or whose failed must-have was the thing changed. Everyone else is held, not contacted, until you re-run scoring, rather than left sitting there looking current.

That follow-up is driven by the edit itself. It is not a flag a person has to remember to set, which matters more than it sounds, because the moment a brief changes is precisely the moment nobody is thinking about bookkeeping. A recruiter who relaxes a requirement at six on a Friday does not also have to work out what that implies for the candidates already scored, and the colleague who picks the role up on Monday does not have to know the conversation happened at all.

It also covers the case nobody plans for: a change made by someone else, on a role you are not watching, days after the scoring ran. A manual flag is only ever as reliable as the person with the most on that day.

Why holding beats the two alternatives

There are only three things a system can do with scores produced under an old brief, and the other two are worse.

It can leave them looking current. That is the common default, it costs nothing to build, and it is the reason shortlists quietly carry two bars at once. Or it can discard them, which throws away work that was paid for and may well still be correct, since relaxing one requirement does not change the verdict on most people in the pool.

Holding states the position accurately instead. This judgement was made against an earlier version of the brief, it may still hold, and nobody should be contacted on it until scoring has been re-run. That is a smaller claim than either alternative makes, and it is the only one of the three that is true.

What this changes for your week

• Changing your mind stops being expensive. You can relax a requirement in week three without it turning into an exercise in remembering who was scored when.
• One shortlist, one bar. When five names go to a hiring manager, they were judged against the same brief as each other.
• Relaxing a requirement stops burying the people it used to exclude. The candidates a change is meant to rescue are exactly the ones an old score keeps at the bottom of the list, which is why an uncontacted candidate whose failed must-have changed is re-scored automatically.

How to use it

1. Make the change on the brief rather than in your head. A requirement you have privately decided to ignore is still doing its work on every candidate the system judges.
2. Look first at who the change should affect. Relaxing a must-have usually matters most for the people it rejected, not for the ones who cleared it anyway.
3. Re-run scoring for the held candidates before you compare across them. Until you do, the order between the two groups is not a ranking.
4. Tell the hiring manager the brief moved, and when. It is a much easier conversation before they have seen a shortlist than after they have questioned one.