Quick answer: Yes, most applicant tracking systems (ATS) timestamp every stage change and store notes attached to a candidate, giving you a usable audit trail. That is not a legal defense on its own. The system preserves what someone wrote; it does not write the job-related reasoning for you, and an empty “rejected” status protects nobody.
What does an ATS actually record?
The structural facts: when a candidate applied, when they moved stages, who moved them, and whatever text a human typed into a comment or scorecard field along the way.
That’s genuinely useful. Six months after a hire, you can open the record and see the full timeline instead of relying on someone’s memory of a role that’s since filled. What it doesn’t do automatically is explain why a decision was made, unless a person wrote that explanation down at the time.
Is a timestamp the same as documenting a reason?
No, and this is the gap that catches teams out. A system log tells you a candidate was rejected on a given date. It does not tell you why, unless the reason was written into a note or a required field on the way there.
This is covered in full in decision history: document why you chose, which is about building the habit of writing the reasoning down as part of the normal workflow, not after the fact. This post is narrower: it’s about what the software itself preserves once that reasoning exists somewhere in the record.
Does an ATS record help in a discrimination claim?
It helps, but only as much as what’s actually in it. A timestamped log with a real, job-related reason attached is useful evidence. A timestamped log that just says “rejected” with nothing else is barely better than no record at all.
The EEOC received 88,531 new discrimination charges in fiscal year 2024, a 9.2% increase over fiscal year 2023, which was itself the highest year since 2017, according to the EEOC’s FY 2024 Annual Performance Report. If a rejected candidate challenges a decision, “we went with someone else” is not a defense. “Candidate B had three years of experience managing a team this size and candidate A had none, documented at the time” is. The ATS stores the second kind of statement. It can’t invent it for you.
How long does that record actually need to be kept?
Longer than most small teams assume, and the exact answer depends on where you hire.
| Rule | Who it covers | Retention period |
|---|---|---|
| EEOC, 29 CFR 1602.14 | US employers covered by Title VII and the ADA | 1 year from the personnel action, longer if a charge is filed |
| OFCCP, 41 CFR 60-1.12 | US federal contractors with 50+ employees and a contract of $50,000+ | 2 years, or 1 year if under 150 employees or a contract under $150,000 |
| GDPR, Article 5(1)(e) | Employers hiring in the EU | No fixed number. You set and justify a retention period tied to the purpose of processing, and you must honor deletion requests under Article 17 once that purpose ends |
Note the GDPR row doesn’t give you a day count, on purpose. The regulation’s storage limitation principle just says you can’t keep data longer than you need it for, so the burden is on you to pick a period you can defend and write it into your privacy notice. For a specific recommended retention period rather than just the legal principle, see how long to keep job applications under GDPR and RODO.
What a stored record can’t do for you
It can’t replace a human reason, it can’t fix a thin job description that made every candidate look similar, and it definitely can’t decide who to hire. Those are still your job.
What Canvider’s record does is make the habit easier: comments and interview feedback on the candidate store who wrote them and when, so that part never disappears. When a hiring team compares finalists with Decision Helper, they compare 2 to 4 finalists side by side. The comparison and its reasoning are saved with the job so they can reopen them later. The reasoning still has to come from a person. The system just makes sure it doesn’t disappear once it’s written.
What should a small team actually do with this?
Require one sentence of job-related reasoning at every stage change that matters: moving someone to finalist, and rejecting them at any stage past a first screen. That sentence, stored with a timestamp, is the whole audit trail most small teams will ever need.
If you’re building that habit from scratch, start with your next open role rather than trying to backfill every past hire. Decision history has the fuller framework for what to write and what to skip, and rejection email after interview covers turning that same reasoning into something you can actually send the candidate.
Frequently asked questions
Does an ATS automatically create a legal record of why you rejected someone?
It timestamps what happened, like a stage change or a stored note, which helps you reconstruct events later. It does not write the reasoning for you. If nobody typed a job-related reason into the system, there's nothing for the ATS to preserve.
How long do hiring records need to be kept?
In the US, the EEOC requires covered employers to keep hiring records for one year under 29 CFR 1602.14, longer if a charge is filed. Federal contractors follow a separate rule, 41 CFR 60-1.12, requiring two years, or one year for contractors with fewer than 150 employees or a contract under $150,000. In the EU, GDPR's storage limitation principle means you set your own period and can justify it, not a fixed number of months.
Is an ATS record enough to defend a discrimination claim on its own?
No. A timestamp proves something happened and when. It does not prove the decision was fair. You still need an actual job-related reason written down by a human, which the ATS stores but does not generate.