A new vacancy comes in and the first reflex is to post an advert, open a job board or start a fresh search. Yet your Applicant Tracking System usually already holds hundreds or thousands of candidates who applied earlier, were runners-up, were placed before or registered for future roles. Many of them already have a recorded history, known skills and a record of how they prefer to be contacted. Searching your own database first is often the fastest and cheapest route to a shortlist, but only if the data is reliable enough to find the right people. This article explains how to search your own Applicant Tracking System before sourcing externally: which data has to be in place, how to search in a structured way, what to check before you contact anyone and how to record the outcome so the next search is better.
The approach works in every segment. Recruitment agencies build up a candidate base over years that is worth more than any single advert. Staffing desks need available people quickly and often find them among workers who finished an earlier assignment. Secondment firms look first at their own professionals whose assignment is ending. Executive search firms reuse earlier longlists and market maps for a new search. In-house recruitment teams have earlier applicants and internal candidates who already know the organisation. In every case the question is the same: who do we already know who could fit this role?
Why your own database comes first
Candidates in your own system have already been in contact with you. You know how earlier conversations went, which feedback they received and what they were looking for. Contacting them is usually quicker than finding and qualifying unknown people, and a candidate who had a good experience before is more likely to respond. A runner-up from an earlier vacancy is the most obvious example, but the same applies to good applicants who were rejected only because of timing, to former placements and to people who sent an open application without a vacancy. External sourcing remains necessary for many roles; searching your own database first simply makes sure you do not overlook people you already know.
Data that has to be in place
- A shared list of skills and tags, so recruiters describe the same skill in the same way
- Recorded work location and travel radius, languages and proficiency levels and, where relevant, certificates with expiry dates
- Recorded preferences such as contract type and working hours and the salary expectation, with the date they were last confirmed
- A recorded reason or rejection reason for every earlier process that stopped
- One record per person: duplicates merged rather than kept side by side
Without these fields a search returns either too little or too much. Free-text notes help, but structured fields are what let you filter reliably.
Searching in a structured way
Start from the structured vacancy brief. Translate the must-have requirements into filters: skills from the shared list, location within the travel radius, language level, required certificates and contract type. Search first on the must-haves only, then narrow down with the nice-to-haves. Save the search with the vacancy so a colleague can repeat it and so you can run it again later in the process. Look not only at candidates who applied for similar roles, but also at earlier placements and at people in talent pools for related functions. For staffing work, combine the search with confirmed availability; for secondment, include professionals whose assignment end date is approaching.
Checks before you contact anyone
- Is the record still within its retention period, and may you still contact this person about new roles?
- Does the candidate fall under an off-limits agreement with a client?
- Is the candidate already active in another vacancy, so you manage both processes rather than surprise them twice?
- Was this candidate already presented to the same client, so you avoid a double submission?
- Through which preferred contact channel should you approach them?
These checks take minutes and prevent the awkward situations that make candidates and clients lose trust.
Recording the outcome
Record every approach on the candidate record: when you contacted them, for which vacancy and with what result. Update preferences that changed, such as salary, availability or location, and confirm the date. When a candidate from your own database moves into the pipeline, keep the original source and add how they were found again, so you can later see how many shortlisted candidates came from your own database rather than from new adverts. That makes it possible to see over time how much your database contributes, instead of guessing.
When to move on to external sourcing
Agree in advance how long the internal search may take and how many suitable candidates you need before external sourcing is unnecessary. For an urgent staffing request that may be a single morning; for an executive search assignment it may be part of the first week of research. If the internal search does not deliver enough suitable candidates, start the advert or external search straight away and record that decision on the vacancy. Searching your own database first should speed up the process, not delay it.
A practical start
- Check that skills, location, languages and preferences are recorded in structured fields with a shared list
- Merge duplicate records and remove records whose retention period has passed
- For every new vacancy, run and save a search based on the must-have requirements before posting an advert
- Check retention, off-limits agreements, active processes and earlier submissions before contacting anyone
- Record every approach and its result, and track how many shortlisted candidates came from your own database
Use what you already know
Your candidate database is one of the most valuable assets of your recruitment work, but only when it can be searched reliably. Keep the data structured and current, search it before every new vacancy and record what each search delivers. Explore the product or book a demo — we will show how candidate records, saved searches and pipelines work together in BoldATS for your segment.