An industrial company in the south of France had accumulated more than 8,000 CVs in its old ATS, collected over years of speculative applications and past hiring campaigns. Nobody ever reopened them: the old tool's keyword search made the database practically unusable beyond a few months.
Two technical roles to fill, with no external sourcing budget
Two maintenance technician roles had to be filled quickly, with no extra budget to post new ads or brief an agency. The HR team first imported its existing CV database, then ran a plain-language search describing both roles — experience, certifications, geographic proximity.
What the search surfaced
Out of the 8,000 profiles, several dozen still matched the need: some had applied for a different role a few years earlier, others had applied speculatively with no follow-up. Each profile was requalified and scored against the two current openings, without consuming a single credit — searching your internal pool is included, unlike external search.
- Both roles were filled from applications already in the database.
- No new ad was posted on job boards for this hire.
- The CV database, until then considered dead weight, became a candidate source in its own right.
The lesson
A large CV database is only a problem when it is unreadable. Once requalified through a plain-language search, it becomes a talent pool again — sometimes enough on its own to avoid a full sourcing campaign.