Why the language matters
Words like fake, fraud, and verified carry weight. If an ATS labels a candidate as fake, recruiters may treat that label as a decision rather than a signal. That creates legal, ethical, and candidate-experience risk, especially when the underlying evidence is probabilistic or incomplete.
Hiring data is messy. Candidates mistype profile links, change email addresses, update LinkedIn after applying, or use privacy-focused tools. A warning can be useful in those cases. A definitive fraud label is too strong.
What an integrity warning should do
A good warning answers three questions: what was noticed, why it may matter, and what the recruiter should review next. It does not replace judgment. It does not hide the reason. It does not automatically move or reject the candidate.
This makes the warning actionable. The recruiter can open the candidate profile, inspect the signal, and decide whether to ask a follow-up question, verify a profile, request a work sample, or proceed normally.
The signals that fit this model
Application integrity warnings work best for signals that are concrete and reviewable: disposable email domains, suspicious profile links, unsafe URLs, profile brand impersonation, repeated CV fingerprints, repeated application answer patterns, velocity from the same metadata, and mismatches between claimed profiles and application content.
The signal should be narrow enough to explain. "This link uses an unexpected LinkedIn-like domain" is useful. "This candidate is suspicious" is not. Specific signals make it possible for recruiters to verify or dismiss the warning quickly.
How recruiters should respond
The first step is to treat the warning as a prompt, not a conclusion. Review the candidate card, open the details panel, and read the explanation. Then check the underlying material. If a link looks wrong, verify the URL. If application answers appear copied, ask for concrete examples. If the profile is inconsistent, ask the candidate to clarify the discrepancy.
Document what happened. If the warning was a false positive, the candidate should continue normally. If the verification reveals material misrepresentation, the decision should be based on the verified misrepresentation, not the warning itself.
Why this is safer for compliance
Many recruiting teams are already cautious about automated decision-making. Integrity warnings fit that caution because they are advisory and reviewable. They support human oversight, provide explainable context, and avoid presenting a machine-generated signal as a final employment decision.
That approach also fits the broader pattern Treegarden uses for AI in recruitment: advisory scores, manual review, auditability, and clear language. The product helps recruiters decide where to spend attention without pretending that automation can judge candidate honesty on its own.
Review applications with context
Treegarden helps recruiters manage high-volume pipelines with advisory AI, application integrity warnings, and human review built into the hiring workflow. Book a demo
Frequently Asked Questions
Why not call it fraud detection?
Because most signals are indicators, not proof. Fraud detection language can overstate certainty and create poor decisions. Integrity warning is more accurate.
Can an integrity warning reject a candidate automatically?
It should not. The safer model is warning-only, with a recruiter reviewing the signal before any decision is made.
What should be shown to recruiters?
Show a clear warning icon, a short label, and an explanation of the specific signal so the recruiter knows what to verify next.