Marcus T. on ASR III, Kestrel Federal Systems
- Previously submittedSubmitted to Kestrel Federal Systems on Mar 14ASR II requisition, by Jordan P. Marcus T. starts in Previously submitted instead of Sourced.
Duplicate Guard
Available now
Never send the same candidate to a client twice.
Flags a candidate who was submitted to the same client in the last 12 months the moment you add them to a requisition, and shows the earlier submission.
Two recruiters, one candidate, one client
The same person goes to the same client from two desks, and the fee dispute starts before the first interview.
How it works
- 1
Add a candidate to a req
The way you do today.
- 2
Checked against the last 12 months
If they were submitted to the same client in that time, they start as previously submitted, with the earlier submission as the reason.
- 3
See it wherever they are
The requisition shows a previously submitted warning on that candidate, whatever their stage.
- 4
Duplicate records wait for you
Likely duplicate profiles are proposed for a person to merge, and a merge can be undone.
Request: Add Marcus T. to the ASR III req for Kestrel Federal Systems.
Request: Review likely duplicates.
Likely duplicates
- Proposed mergeDana R., résumé upload, Oct 2Same email and phone as the record below.
- Proposed mergeDana R., CSV import, Aug 18
Nothing merges until you approve it, and every merge can be undone.
Fictional example. Duplicate Guard works this way in ANDY today.
What you control
What you approve
Every merge of two records.
- Merge records
- Always needs a person. No setting changes this.
What’s recorded
The earlier submission behind every warning, and every merge with the record needed to undo it.
Autonomy setting
Every requisition shows its mode: Co-Pilot, Hybrid or Custom. Co-Pilot, the default, sends nothing without your approval.
How approval works