What file formats can I import into Edvenity?
Edvenity supports CSV candidate import with custom field mapping to match your spreadsheet columns to candidate profile fields.
Recruiting Workflow / Talent Pool Use Case
CSV Candidate Import for Recruiters
Import candidates from CSV files and spreadsheets into Edvenity, with field mapping, duplicate detection, and batch tracking for your recruiter-owned talent pool.
Primary keyword
CSV candidate import
Best fit
Recruiters and staffing teams migrating candidate data from spreadsheets, legacy systems, or exported databases into a searchable talent pool.
How This Workflow Runs in Edvenity
CSV Candidate Import for Recruiters is a specific recruiting workflow, not just a generic AI feature. The value comes from connecting the work before and after the task: job setup, candidate intake, screening evidence, recruiter review, and the next hiring action.
A useful recruiting workflow should make the next decision clearer. Edvenity keeps the candidate record, interview evidence, assessment results, and recruiter actions close together so teams can move from intake to shortlist without rebuilding context in spreadsheets or separate tools.
Workflow Steps to Cover
1. Upload a CSV of candidates with custom field mapping
This step should produce evidence a recruiter can review later: status, score, candidate context, or the next recommended action. That is what separates workflow software from a static checklist.
2. Detect and skip duplicate candidate records
This step should produce evidence a recruiter can review later: status, score, candidate context, or the next recommended action. That is what separates workflow software from a static checklist.
3. Track import batches with a full audit trail
This step should produce evidence a recruiter can review later: status, score, candidate context, or the next recommended action. That is what separates workflow software from a static checklist.
4. Move imported candidates into the searchable talent pool immediately
This step should produce evidence a recruiter can review later: status, score, candidate context, or the next recommended action. That is what separates workflow software from a static checklist.
5. Invite imported candidates to open job roles
This step should produce evidence a recruiter can review later: status, score, candidate context, or the next recommended action. That is what separates workflow software from a static checklist.
Related Edvenity Features and Next Pages
Frequently Asked Questions
Does Edvenity detect duplicate candidates during import?
Yes. Edvenity runs automatic duplicate detection during CSV import so the same candidate isn't added to your talent pool twice.
Can I see what was imported in each batch?
Yes. Every CSV import is tracked as a batch with a full audit trail, so you can review or troubleshoot specific imports.
Who is this CSV candidate import workflow for?
Recruiters and staffing teams migrating candidate data from spreadsheets, legacy systems, or exported databases into a searchable talent pool.
What should recruiters prepare before using this workflow?
Recruiters should define the job criteria, screening questions, candidate stages, evidence they want to collect, and the next action after a candidate is reviewed.
How does this workflow avoid manual duplicate work?
The workflow keeps candidate activity attached to the same record, so recruiters do not have to copy scores, interview notes, assessment outcomes, or stage updates between spreadsheets and separate tools.
Which Edvenity features support this use case?
This use case connects most directly with Talent Pool, Recruiting.