Copilot Match Changes: How Profile Refreshes Affect Candidate Matches

This article explains why Findem's Copilot candidate matches can appear inconsistent, how resume-based and enriched profile data are used, what happens during verification and refresh, and what to do if you see persistent mismatches.

How Copilot Uses Resume and Enriched Profile Data

Findem Copilot aggregates candidate information from multiple sources, including ATS resume data and public profiles. When these sources have conflicting information, the system typically prioritizes the most recent data. If a resume dated recently does not include a current job title, it may override the public profile information and affect search and exclusion filters.

For general background on Copilot, check out the article, What is Findem’s Copilot.

Why a Candidate’s Match Status Can Change

Copilot uses a multi-stage candidate matching process. Initially, candidates may be selected based on resume information. When the system performs more comprehensive profile enrichment and matching, some candidates might no longer meet the exact job title or industry requirements.

Search results and preview rows are driven by a search index that can lag behind the real-time profile view. The Enriched Profile always displays the most current data in real time, while the search index may temporarily show an older version of a profile. That indexing delay can cause a candidate to appear as a high-priority match in search results but show as “Not Match” when you open the Enriched Profile.

Common causes of mismatches include:

• The profile data had not refreshed yet.
• Backend load or queue prioritization delaying enrichment.
• Source data not being available at the time of refresh.
• The profile failing experience or quality criteria used by the enrichment process, so its data is not surfaced.
• Certain fields, such as contact details, being unavailable and subject to periodic retry attempts.

For more details on how refresh timing can affect profile data, see Profile Refresh Timing: Why Findem Profiles May Differ from LinkedIn.

What Happens During Verification and Refresh?

When Copilot is processing candidate profiles, there is a temporary verification stage where profiles are tagged with a “Verifying and Enriching Data” indicator. During this phase, profiles that may not match the search criteria are briefly visible. These profiles are automatically removed after the verification process is complete, ensuring that only the most relevant candidates are displayed in the final search results.

During a Copilot search, profiles may temporarily appear as high-priority matches due to the search refresh process. When search parameters are changed, the system takes 20–30 seconds to update and recommend new matches. During this refresh period, some profiles might briefly show up before being removed from the search results if they do not fully meet the search criteria.

The platform refreshes its pool of profiles at a cadence comparable to leading search engines, typically every 1–2 months across the dataset. In addition, Copilot preprocessing updates candidates matched from a job description before a project begins and keeps those candidates from being more than 14 days out of date. Copilot also refreshes and verifies contact information as part of that process.

How to Review and Validate Suspected Mismatches

If you encounter inconsistencies in candidate profile matching, you can validate what you are seeing by checking multiple data sources and views. Recommended steps include:

• Check both the ATS resume and public profile for the candidate.
• Verify the experience details in different profile views.
• Look at the specific channel, such as ATS or public, when reviewing matches.

Because Findem Copilot prioritizes the most recent data when aggregating candidate information from ATS resume data and public profiles, these checks help clarify which source is currently driving the match behavior.

When to Contact Findem Support

If you continue to see persistent discrepancies in profile matching after reviewing both resume and public profile data, verifying experience details across views, and checking the channel used for the match, you should contact Findem Support.

Support can investigate inconsistencies where candidates appear as high-priority matches in search results but show as “Not Match” in the Enriched Profile, where index delays are suspected, or where the multi-stage matching process appears to produce unstable results for the same type of search. Support can also review cases where mismatches appear to be related to refresh cadence, enrichment quality criteria, or fields such as contact details that are subject to periodic retry attempts.