ChatGPT for recruitment agencies

How Can a Recruitment Agency Review Suspected Duplicate Candidate Records w AI Before an ATS Merge?

A recruitment agency can use AI to prepare an evidence checklist for suspected duplicate candidate records, not to decide that two records are the same person or merge them. Preserve both IDs, conflicting contact details, work history and downstream references. The authorised ATS steward checks identity and the exact product's merge behaviour before any separately approved action. A shared name or email is a lead for review, not proof. Keep suitability screening, placement and payroll decisions outside this task.

Review Identity & Field Preservation Separately

Two records can look similar while representing different people. Even a genuine duplicate may contain fields that a merge will not preserve. The ATS steward therefore needs two answers: is the identity match supported by authorised original evidence, and what would happen to each record's data in this specific system? A tidy combined profile is not enough.

Bullhorn ATS merge documentation, checked 21 November 2026, explains primary/secondary selection, warns that not all fields transfer and says the secondary candidate record is deleted. Its examples of non-transferring data include addresses, custom text fields and rate information. Bullhorn One's candidate-specific guidance warns against candidate merges because of Pay & Bill impacts and directs customers to discuss a potential merge with Support first. Neither original displays a dated revision or numbered product version. These are product-specific warnings, not a procedure for your ATS or permission to merge.

A Synthetic Record-Pair Review

Synthetic DR8 export v2, not candidate material or a real merge. Tokens below stand for invented fields, with no personal contact details. Product edition, Pay & Bill use and identity confirmation are not supplied.

Swipe to read every column, or focus the table and use the arrow keys.

FieldCA041CA092
Label & inboxSample label; E7Same sample label; E7
Phone & historyP1; WH1P2; WH2
AddressAddress token AAddress token B
Downstream referenceNo placement in supplied extractPlacement PL2
Expected review draft, not an executed product test:

HOLD. Shared label and E7 do not establish one person. Preserve CA041 and CA092, P1/P2, WH1/WH2 and address A/B. Ask the steward to check authorised identity evidence, the product/edition and PL2's downstream dependencies. Pay & Bill status is unknown. Do not select a primary record, combine fields or perform a merge.

A reviewer passes this fixture only if both IDs and every conflict remain visible and no missing value becomes zero or absent history becomes proof of no placement. Negative control: two confirmed different people sharing an office inbox must remain separate. A matching contact field does not override contradictory identity evidence.

Prepare the Steward's Decision, Not a Merge Command

Request a source-referenced question list: identity evidence to inspect, conflicting fields, attachments and work-history references, placements or other dependencies, exact vendor guidance and the owner of each unresolved question. Keep private originals in their authorised record system. Do not ask AI to verify a passport, infer consent or decide which person's history is more credible.

This is distinct from formatting one CV or comparing employment terms. It does not assess a candidate's suitability or change recruitment status. Any later native-system action needs its own authority, current product checks and preservation decision. Never assume a merge is reversible.

Guardrails

AI may omit a conflicting field, invent a match or combine histories. A named ATS data steward checks every statement against approved originals; instructions do not guarantee identity, accuracy, completeness or alerts. Start with synthetic or minimised examples. Actual candidate material requires an approved product, configuration, access, retention and applicable duties. A workspace alone is not a privacy guarantee.

Exports are manually supplied by default. ATS reads, writes, merges, deletion, recruitment-stage changes, messages and payroll actions need separately authorised, configured and tested integrations. No action is performed by this review. When vendor guidance requires support involvement, follow that exact product boundary rather than applying a generic AI checklist.

iMPLEMENTAi can build one review Skill around your field map and human handoff. Pilot known non-matches, ambiguous pairs and missing downstream information. See current implementation offers and company data governance.

Common Questions

Does the Same Email Prove Two Records Are One Person?

No. Shared inboxes and conflicting evidence require review. The authorised steward checks original identity evidence rather than treating a similarity score as proof.

Will Every Field Survive an ATS Merge?

Do not assume so. Check the exact product and edition. Bullhorn's documentation warns that some fields do not transfer; another ATS may behave differently.

Can AI Choose the Primary Candidate Record?

Not in this workflow. It preserves source IDs and conflicts for the authorised steward. Primary selection and any mutation are separate decisions.

Does This Change Payroll or Recruitment Status?

No. The review does not merge, delete, message, change a stage or touch payroll. Downstream dependencies must be checked before any separately authorised native action.