Verify the candidate's evidence, not whether the prose sounds like AI

Polished applications made authorship a bad hiring question

Recruiters are receiving more polished, standardized applications while still needing to decide whether the person can do the job. The tempting response is to detect AI writing. That substitutes a noisy authorship guess for the evidence question the assessment should have asked in the first place.

A July 31 discussion in r/recruiting captured the pressure: high application volume, automated submissions, and uncertainty about whether a simple disclosure question would produce a useful answer. The Australian Public Service Commission's 2026 guidance takes a more operational route. It asks agencies to set consistent expectations for candidate AI use while protecting fair, effective, merit-based recruitment.

Candidate AI use covers different behavior with different stakes. Editing a resume for clarity is not the same as receiving hidden real-time answers during an assessment intended to measure independent judgment. Using an approved assistive tool is not the same as fabricating work history. Generating a first draft is not the same as claiming a credential. A single yes-or-no “used AI” field collapses these distinctions.

The defensible objective is evidence integrity. HR must know which capability each stage measures, what assistance is allowed, which evidence supports the job criteria, and what proportionate follow-up will resolve a real gap. The process should work even when no one can prove who typed each sentence.

Publish a different AI rule for each assessment stage

Start by writing the purpose of the stage in one sentence. A resume gathers claims about experience. A cover letter may test motivation or communication. A take-home exercise may test analysis under realistic resource conditions. A live work sample may test unaided reasoning, collaboration, or tool use. The AI rule follows that purpose.

Tell candidates the rule before the stage starts. Name permitted tools, disclosure expectations, prohibited help, time, data handling, accommodation path, and the consequences of a confirmed breach. Use plain language and an accessible format. The ICO's March 2026 recruitment guidance stresses that people should understand when automated processing affects them, how to obtain information, and when human involvement is available.

Do not make applicants surrender private chat histories or personal devices to prove compliance. That collects unrelated personal information, creates inconsistent burdens, and can expose health, family, political, or confidential employer data. Design the assessment so capability can be validated from the work and a bounded follow-up.

Replace style suspicion with a job-evidence matrix

For each criterion, cite what the candidate actually submitted or demonstrated. Mark the evidence as supported, partially supported, not shown, or conflicting. Keep a separate list of unverified signals. A detector score, generic phrasing, unusual fluency, metadata, or a reviewer's intuition belongs in that signal list until independent evidence confirms something relevant.

{
  "criterion": "explains a financial variance",
  "assessment_purpose": "job-related analysis and communication",
  "candidate_evidence": "paragraph 3 and attached worksheet",
  "status": "partially_supported",
  "verified_facts": ["worksheet totals reconcile"],
  "unverified_signals": ["tone differs from interview email"],
  "gap": "candidate reasoning behind driver selection",
  "next_step": "10-minute structured explanation and one revision"
}

This structure improves ordinary selection quality, not only AI cases. It shows whether the assessment contains enough evidence, prevents a polished narrative from outweighing weak substance, and gives the panel a consistent reason for follow-up. It also creates an audit record if a candidate asks how a concern was resolved.

Keep identity, qualification, and capability questions separate. Verify a degree through the approved credential process. Verify employment through the approved background-check process. Verify authorship-sensitive capability through a work sample or explanation. Do not use a broad “fraud” label when the evidence supports only one narrower question.

Use the least intrusive verification that answers the real question

1. Clarify: ask the candidate to explain two choices, assumptions, or sources in the submitted work.
2. Modify: provide a small new constraint and ask for a revision plus the reason for the change.
3. Reproduce: run a short equivalent work sample under clearly stated tools and conditions.
4. Corroborate: verify a specific experience, credential, or portfolio claim using the established process.
5. Escalate: only when facts indicate identity fraud, material misrepresentation, or a clear policy breach, route the case to authorized HR, legal, privacy, or security reviewers.

The ladder should be standardized. Comparable candidates with the same evidence gap receive the same follow-up and rubric. Do not create a harder test only for candidates whose first language, disability-related assistive technology, education, or writing style triggers a reviewer's suspicion.

A good follow-up is adjacent to the original task, not a memory quiz. Ask an analyst to explain why a driver mattered and revise the model when an assumption changes. Ask a recruiter to prioritize a new constraint in a sourcing plan. Ask a writer to edit for a different audience. This tests understanding and adaptation without demanding that the candidate reproduce identical prose.

Ask for validation without making an accusation

The communication should name the capability and next step, not speculate about authorship. For example: “As part of our standard review for this role, we ask candidates to discuss two decisions in the work sample and make one short revision. You may use the resources listed in the original instructions. Please contact us if you need an accommodation or an alternative format.”

If a rule concern exists, state the documented fact and invite a response: “The instructions for this stage did not permit real-time external assistance. Our process log indicates an external response was submitted during the timed session. Before we decide how to proceed, we would like to understand what occurred.” Do not say “our AI detector caught you.”

The European Commission's July 2026 Article 50 guidelines make transparency newly salient for many AI interactions from August 2, although employment systems also sit within a broader and changing high-risk framework. HR teams should maintain a jurisdiction matrix rather than applying one global legal conclusion. The stable operational principle is earlier and clearer disclosure, not a buried “AI may be used” line.

Reserve policy-breach findings for authorized human adjudication

A policy-breach finding requires four things: a clear rule supplied before the assessment, reliable evidence of behavior covered by that rule, a chance for the candidate to explain, and a human reviewer with authority and training. If any element is missing, record a policy or evidence gap instead of misconduct.

Human review is meaningful only when the reviewer sees source evidence, applies a written standard, can disagree with a tool or prior reviewer, records a reason, and has enough time. Monitor outcomes by stage and relevant group where lawful: follow-up rate, pass rate, reversal, appeal, accommodation, technical failure, and time. Disparities require investigation even when the process has a human signature.

EEOC guidance warns that algorithmic employment tools can screen out people with disabilities and that employers need a reasonable-accommodation process. Background checks and third-party reports bring additional equal-treatment, notice, consent, and adverse-action duties. A candidate-authenticity project cannot quietly become a broad data-enrichment program.

Common failure modes

Implement the workflow in four weeks

Week 1 - Inventory. List every recruiting stage, tool, assessment purpose, existing AI statement, data flow, jurisdiction, accommodation route, and decision owner. Suspend detector-only or undisclosed practices while the inventory is incomplete.

Week 2 - Rules and evidence. Classify candidate AI use as permitted, disclosure-required, restricted, or prohibited for each stage. Build the job-evidence matrix and one equivalent validation for each important capability. Review the rules with talent, hiring managers, counsel, privacy, accessibility, and employee representatives where applicable.

Week 3 - Candidate and reviewer materials. Publish plain-language instructions, permitted resources, disclosure wording, accommodation contact, and review path. Train reviewers to separate verified facts from signals, avoid AI-authorship claims, and record job-related reasons.

Week 4 - Pilot and audit. Run the process on a bounded set of roles. Sample cases independently. Measure follow-up, pass, reversal, appeal, accommodation, technical failure, time, and candidate feedback. Stop if the workflow creates unequal burdens, exposes sensitive data, or produces detector-led decisions.

Link this process to the AI interview vendor approval workflow, recruiting pilot evaluation skill, resume-screening risk guide, and HR AI output release gate. Candidate-use rules do not replace controls over the employer's own AI.

Frequently asked questions

Should HR ask candidates whether they used AI?

Ask only when the answer is relevant to a published stage rule or the capability being assessed. Define what counts as AI use and how the disclosure will be used. A broad yes-or-no field without context produces inconsistent and low-value data.

Can we reject a candidate who admits using AI?

Do not treat disclosure itself as a reason. Apply the published rule, confirm the facts, assess the job-related evidence, consider accommodation and consistent treatment, let the candidate respond, and use authorized human review. Obtain jurisdiction-specific advice for consequential decisions.

Can an AI detector be one signal?

Even as a signal, it can bias review and create an undisclosed burden. If the organization retains one, document its limitations, prevent automatic action, hide the score from initial reviewers where possible, and require an independent job-related validation that would be fair without the detector.

What if the role itself expects employees to use AI?

Design an AI-enabled work sample. Score problem framing, prompt or tool choices, source verification, judgment, correction, confidentiality, and final output. Do not ban the tool the job requires and then claim the assessment predicts performance.

How long should we retain the verification record?

Use the organization's approved recruiting-record schedule and applicable law. Keep the minimum needed to show the rule, evidence, review, communication, outcome, and appeal. Do not retain unnecessary prompts, personal-device data, or inferred sensitive traits.