What Happens to Your Shortlist When the Client Changes the Job Requirement Halfway Through Screening

Recruit Bud is an AI voice screening system that calls and interviews job candidates on a hiring team's behalf. When a client revises the job requirement partway through a search, Recruit Bud can re-screen the existing candidate pool against the new brief in hours instead of restarting the calling process from zero.

An agency gets a brief, builds a candidate list, and screens 150 to 200 people against it over one or two weeks. Then the client comes back and says the requirement has shifted. Maybe the years of experience bar moved. Maybe a "nice to have" skill became mandatory. Maybe the budget band changed and candidates who were fine at the old number are no longer in range.

Every one of those 150 to 200 conversations was measured against a role that, as of that email, no longer exists.

In short

• A shifted job requirement does not usually mean the whole candidate list is wrong, and it does not always mean contacting candidates again at all.

• The requirement change is almost always client-side, not something the agency's intake process could have caught earlier.

• The real cost of a mid-search requirement change is not the client relationship. It is the recruiter hours spent re-establishing facts that were already gathered once.

• A budget or compensation change usually just means recalculating scores against numbers already on file, not a new conversation.

• A specific new requirement, like a certification or a shift preference, usually just means one targeted question, not a full re-screen.

• When most changes turn into a setting update or a single question instead of a redo, a requirement change stops being a fight worth having with the client.

Why does the requirement change after the search has already started?

This is rarely the agency's fault, and it is worth saying plainly, because it is easy for a recruiter to internalize a shifted brief as a sign they scoped the search wrong.

The person who writes the job description is often not the person the new hire will report to. A generic brief goes out, the agency starts calling against it, and only once the hiring manager sees a handful of real candidates does anyone say what they wanted in the first place. "I need someone who has actually run a night shift, not just supervised one" is the kind of clarification that only surfaces once real people are on the table.

Budget approvals shift too. A role gets sanctioned at one compensation band, then finance revisits headcount mid-quarter and the band moves. None of that has anything to do with how the agency ran the search.

The pattern shows up again and again across agencies that fill roles for external clients rather than for themselves: the brief you are handed on day one is a best guess, and the real requirement only gets sharp once candidates start showing up against it.

What does this cost an agency today?

When the requirement shifts, most agencies handle it the same way: someone goes back through the candidate list and re-runs the qualifying questions relevant to the new bar, one call at a time.

If 180 candidates were screened against the old brief and the change touches even one qualifying question, all 180 conversations are now technically incomplete for the new requirement. In practice, a recruiter has to decide which candidates are worth calling back, then reach them again.

That second call runs into the same connect-rate problem as the first one. What screening calls actually cost an agency does not change just because this is round two. If anything, a candidate who has already been called once and is now being called again about the same role is more likely to be short with the recruiter, not less.

The agency usually absorbs this cost without billing for it. Raising the requirement change as a separate, billable event is a fight most agencies do not think is worth having over what looks, from the client's side, like a small tweak. So the rework gets done, unbilled, on top of whatever else the recruiter's week already looked like.

The slower this rework takes, the more it also puts the agency at risk on the other side of the relationship: the client who is waiting on a revised shortlist notices the delay, and speed on the shortlist is what gets an agency called first for the next role, not just this one.

What needs to be re-checked when the requirement changes?

A requirement change almost never invalidates an entire candidate conversation, and it does not always mean contacting the candidate again at all. What happens next depends on what kind of thing changed.

Some changes do not need a new conversation with the candidate, only a change to how the existing answers get scored. A compensation band is the clearest example.

Most agencies already ask for expected CTC in the first screening call, so if a client raises a warehouse supervisor role's ceiling from ₹28,000 to ₹32,000 a month, nothing needs to be asked again. Every candidate already gave a number. Only the budget setting on that job needs to change, and every candidate's fit against the new band gets recalculated on its own.

Other changes need one new fact, not a new interview. If a client decides a forklift operator role now requires a valid license, and that was not part of the original questions, the fix is a single targeted question, not a full re-screen. That can go out as one WhatsApp message, or a short call that asks only that one thing, without repeating the availability, location, and experience questions the candidate already answered.

A smaller set of changes genuinely calls for re-engaging the candidate in something closer to a full conversation, usually when what moved is a skill or experience requirement central to whether the person qualifies at all, not a side detail.

How Recruit Bud handles this

1. The job description in the system gets updated to reflect the client's revised requirement.

2. Recruit Bud checks what kind of change this is: a number that was already captured, a new question that was never asked, or a shift in the core requirement.

3. If it is a number already on file, like expected CTC, nothing gets sent to the candidate. The existing answer gets rescored against the new figure automatically.

4. If it is a new one-off fact, only that question goes out, over WhatsApp first and a short call if needed, without re-running the rest of the interview.

5. If the core requirement moved enough to affect who qualifies at all, the recruiter talks to the system to adjust the generated interview flow, usually in under ten minutes, and the pool gets re-run through the updated flow.

6. The recruiter sees this activity live as it happens.

7. A report generates automatically at the end, showing which candidates still qualify under the revised requirement, exportable as a CSV to send straight to the client.

Because most requirement changes turn out to be a number to recalculate or a single question to confirm, not a reason to redo the interview, a change that used to mean days of re-calling usually turns into minutes of updating a setting, or an afternoon of re-screening the pool on the rare occasion the whole flow does need to change.

[IMAGE: Split view showing a job description being edited on one side and an updated interview question flow regenerating on the other]

What changes for the agency once this happens?

A requirement change stops being something the agency has to absorb unbilled, because re-checking a candidate pool no longer costs what a full re-screen used to cost.

[IMAGE: A recruiter dashboard showing a candidate list re-screened against an updated job requirement, with the changed fields highlighted]

Candidates who get this kind of follow-up over WhatsApp first tend to finish it, for the same reasons WhatsApp works better than a cold call for the first screening round. A candidate who has already spoken to the agency once is even less likely to pick up an unfamiliar number a second time, so starting the re-screen over a channel they already recognize matters more here, not less.

None of this requires the agency to negotiate a change order with the client before doing the work. It just means the work itself got cheap enough that the argument was never necessary.

Frequently Asked Questions

Why does a client change the job requirement after the search has already started?

Usually because the person who wrote the brief was not the person who has to work with the hire, or because the hiring manager only clarifies what they actually want once real candidates start showing up. Neither of these is something the agency can prevent by writing a tighter brief upfront.

Should an agency charge extra when a client revises the requirement mid-search?

Some agencies try, but it is a hard conversation to win, because from the client's side it feels like a small tweak, not a new assignment. It is easier to make the rework itself cheap enough that it stops being worth arguing about.

Does re-screening against a revised JD mean re-calling every candidate from scratch?

Usually not. If a compensation band moved and expected CTC was already captured, nothing needs to be asked again, only the scoring against the new number. If a new one-off requirement appears, like a certification or a shift preference, that is usually one targeted question over WhatsApp or a short call, not a full interview. A full re-screen is only needed when the core experience or seniority requirement itself has moved.

How do you know if a requirement change is small enough to just re-screen versus a completely new search?

If the core function of the role is the same and only a specific skill, experience band, or location constraint moved, it is a revision. If the seniority level or the function itself changed, that is closer to a new search and should probably be scoped and priced as one.