Candidate Data Retention and Purge Schedule (Retention)
A sequence with 7 steps: Map every data store that holds candidate records before writing a single deletion rule.
By InnovaAI ResearchPublished
What are the steps?
Candidate Data Retention and Purge Schedule (Retention)
- 01
Map every data store that holds candidate records before writing a single deletion rule
Include the ATS itself, any CRM bolted alongside it, email and calendar sync, browser-extension sourcing caches, and exported spreadsheets sitting on agency drives. A purge that misses one store fails the audit.
- 02
Classify each record type by jurisdiction and consent basis
Separate applicants who submitted directly, sourced candidates never contacted, placed contractors, and rejected applicants. Each class carries a different lawful retention window and a different client notification duty.
- 03
Set a default retention clock per class and document the exception path
A common baseline is 12 months for rejected applicants and 24 months for placed candidates, extended only when a client contract or active job order requires it. Write the exception approval into the same document so nobody improvises.
- 04
Configure automated purge jobs inside the ATS rather than relying on manual cleanup
Platforms built for small recruiting teams, such as Harbor or JazzHR, expose retention rules in settings; larger enterprise stacks may require a support ticket. Either way, the deletion must run on a schedule, not on someone's memory.
- 05
Run a quarterly reconciliation between the ATS and every downstream system
Pull a record count by class from the ATS, then compare against the CRM, the outreach tool, and any compensation or placement module holding candidate identifiers. Flag variance above 2 percent for manual review.
- 06
Log each purge cycle with date, record counts, and the operator who executed it
This log is the artifact you hand a client during a compliance review. Without it, a deletion claim is unverifiable and the agency absorbs the risk.
- 07
Review the schedule whenever a client contract renews or a new jurisdiction enters scope
Retention windows drift as staffing clients expand into new states or countries. Tie the review to the contract renewal calendar so it happens on a known date rather than after an incident.