More Candidates Does Not Mean a Better Search

A recruitment team I worked with was regularly getting more than 1,000 results from an ATS candidate search. The search technically worked, but the list was so broad that recruiters left the system and went straight to SEEK.

I understood why. Nobody wants to work through 1,000 loosely matched candidates with a live job to fill. The useful measure is not how many people the ATS can find. It is how quickly the recruiter can reach a credible shortlist.

What is ATS candidate search?

ATS candidate search is the process of finding people already stored in a recruitment database by using job titles, skills, locations, availability, history and other criteria. Some systems also use AI matching or relevancy scoring to rank candidates against a job.

A good search turns existing candidate data into a manageable group of people worth reviewing. A poor search creates noise, even when the right candidate is somewhere in the database.

Your database may already contain the right candidate

Recruitment businesses invest a lot of time and money building their candidate databases. Then a new job comes in and the recruiter begins the search somewhere else.

Sometimes the database genuinely does not contain the right person. But sometimes the candidate is already there and the ATS or CRM search makes them difficult to find.

That is frustrating for recruiters and expensive for the business.

Your recruitment system should make it easier to use the people and relationships you already have. If searching an external job board feels faster, it is worth understanding why.

Boolean search logic can turn 1,000 results into a useful shortlist

Search logic sounds technical, but the basic problem is usually quite simple.

You might want to search for a Project Manager OR Project Lead OR Programme Manager. Those titles belong together because any of them may be relevant.

But the candidate should also have the right location AND the required skills.

If the ATS treats every job title, skill and location as an OR, it brings back anybody who matches any one of them. That is how a fairly specific request turns into a pool of 1,000 people.

A recruiter should not need to be a Boolean expert to get a useful shortlist. The default search logic, the interface and the training all need to support the way recruiters naturally think about a role.

Candidate matching is only as useful as the data behind it

Even the best candidate matching technology has to work with the information in the system.

Job titles written five different ways, overlapping categories, missing skills and old candidate profiles all affect what comes back. AI can help make sense of some of it, but it does not remove the need for a database structure that fits the business.

I like broad categories with more specific talent pools underneath them. It keeps the ATS manageable while still giving recruiters enough detail to narrow a search properly.

The exact structure will be different for every business. The important thing is that it reflects how the team actually recruits, not how somebody thought they might recruit when the system was first configured.

Watch where recruiters abandon the ATS candidate search

If you want to know whether candidate search is working, sit with the recruiters and watch them use it.

Where do they get stuck? Which results do they immediately rule out? When do they give up? Where do they go next?

That behaviour will tell you whether the issue is the data, the search configuration, the platform or the training. Often, it is a bit of all four.

Whether the team is using Bullhorn Search and Match, JobAdder, Atlas, Tracker or another system, the outcome should be the same: a relevant group of candidates that feels possible to work through.

The aim is not to prove that the ATS can find the most people.

It is to help the recruiter know who to call next.

Achieve helps recruitment businesses improve their system data, candidate search, talent pools and workflows so recruiters can get more value from the database they already have.

Frequently asked questions about ATS candidate search

Why does my ATS candidate search return too many people?

The search may be treating too many criteria as optional, using broad categories or working with inconsistent data. Review the AND and OR logic, the fields being searched and the quality of job titles, locations and skills.

Is AI candidate matching better than Boolean search?

They solve different problems. Boolean logic gives recruiters precise control, while AI matching can surface relevant candidates whose records use different language. The best setup often lets recruiters use both and understand why a person appeared in the results.

How can we improve candidate data in our recruitment CRM or ATS?

Start with the information that affects current searches. Standardise important fields, remove overlapping categories, update availability and make it easy for recruiters to record useful information during normal work.

Can Achieve improve Bullhorn Search and Match?

Achieve can help review search behaviour, data structure, talent pools, workflows and recruiter training in Bullhorn and other recruitment platforms. The aim is a search process recruiters will actually use.