Getting a candidate long-list into your ATS
Agree how candidate research will enter your ATS or CRM before the search, including the fields and context your team needs. Cruvo publishes the reviewed list in an invited workspace and can discuss another handoff format. A clear plan helps preserve the research when your team starts managing candidates elsewhere.
In short
- Agree the destination, delivery format and required fields before the research handoff so expectations are clear.
- Preserve candidate identity, research source and fit reasoning when mapping information into the system your team uses.
- Test a small sample for duplicates, field placement and access before transferring the full agreed list.
An applicant tracking system, or ATS, holds the hiring process. A candidate relationship management system, or CRM, holds relationships across opportunities. Your team may use one system for both jobs. When candidate research enters that system, it needs enough context for colleagues to understand who the person is and why they were included.
Plan the transfer around those needs. Keep the candidate’s identity connected to the role, evidence and next action. Cruvo delivers the reviewed list in an invited workspace and can discuss another format before the search. Explain the destination and required fields so the delivery route can be agreed for your team.
What belongs in the destination system?
Choose the information the recruiter will use to manage this candidate. That includes identity, a professional profile, the relevant role and research source. Keep the selection reasoning available too, so a colleague taking over the record can understand why the person is being considered.
Put the fit reasoning where a reviewer will look for it, either in a note or through a link to the research. Set the initial stage accurately. A person who has been researched but not contacted should enter as a sourced prospect. Record replies and interviews as they happen, so the system reflects the actual conversation.
How should you map the candidate fields?
List the fields in the agreed delivery format and match them to fields in your system. Include name, employer, title, professional profile URL, source, role and notes. Check which destination fields are required and decide what to do when the research has no value for one.
Consult the instructions for the system receiving the data. Greenhouse’s import guide explains its template and permissions. LinkedIn Recruiter’s file guidance specifies its own columns. Use the relevant requirements to check your file before import. A field that looks useful in a spreadsheet still needs an appropriate home in the candidate record.
How do you avoid duplicate candidate records?
Check whether your team already has a record for the person. An earlier application, referral or search may have created one. Compare the name with a professional profile URL or a known email address before deciding that the new research belongs to a new candidate.
When the person already exists, add the new role and evidence in the appropriate place. Keep earlier contact history available. Check the system’s matching rules before importing a batch. Otherwise, separate records can leave one colleague looking at the research while another sees a conversation that has already begun.
What should you test before a full import?
Try a small sample before transferring the full list. Include a new candidate, an existing contact and a record missing optional information. Open the results in your system to see whether each case has been handled as intended.
Inspect the identity fields, role, source, notes and stage. Ask the colleague who will use the research to check the links and access. Resolve errors before moving the remaining records. Keep track of successful rows so a retry does not import them again. Apply the same checks when records are entered manually.
How does Cruvo support the handoff?
Cruvo delivers the reviewed long-list in an invited workspace. If your team needs another format, discuss it before research starts. Name the system, the information required and the colleague handling the transfer so we can establish the delivery route.
For BambooHR or another named ATS, explain the specific action required. Adding a candidate, attaching evidence and updating status are separate needs. Agree which actions the handoff covers. Your team can also review the research in Cruvo while managing interviews elsewhere. The guide to working the long-list explains how to keep those decisions and notes organised.
FAQ
Can we receive the long-list as a spreadsheet?
Discuss a spreadsheet handoff before the search begins. Cruvo’s standard delivery is an invited workspace with the reviewed list and evidence. Identify the fields you need and where they will go so the format can be considered for your engagement.
Can Cruvo push candidates straight into our CRM?
Agree the route for your CRM with Cruvo. Specify the task, such as creating a candidate or attaching the research to an existing person. That lets the discussion establish the format, actions and responsibilities involved.
Does Cruvo connect directly to BambooHR today?
Discuss the BambooHR handoff before commissioning research. Explain whether your team needs candidate records, supporting evidence or later status updates. Agree which actions the delivery covers and who will perform them for the engagement.
Should we transfer everyone on the long-list?
Transfer the records that support your hiring workflow. Your team can review the list first and move selected people, or keep a broader role record where appropriate. Preserve the evidence explaining why each transferred person was included.
What happens to the candidate scores during transfer?
Keep the score connected to its brief and evidence. Decide where the destination system will hold that context or link to it. A reviewer needs the criteria behind the number to interpret it and choose the next action.
How should we record a candidate we already know?
Locate the existing record and decide where the new role and research belong. Preserve earlier conversations and source details. Check matching behaviour before the full import so the new information reaches the right person record.
Will imported outreach status stay synchronised with Cruvo?
Agree where activity will be maintained and how updates will reach the other system. An initial transfer and ongoing updates need separate consideration. Discuss both if your workflow depends on having current status in two places.
How do data corrections affect an imported record?
Correct each copy your team uses. A record of the systems that received the research helps locate them. The candidate-data guide explains the correction process and how candidates can request access, removal or other action.
Sources
Talk with Cruvo
Tell us where you are with the hire. We can discuss the role, show you how the research works and talk through how your team would use it. You can start with questions or an unfinished brief.
Or email hello@cruvo.app directly.