What Is Candidate Disposition in Hiring? (HR Audit Rules)

Candidate disposition is the recorded outcome of an employer’s review of a job applicant, such as moving forward, rejecting, withdrawing, or accepting an offer. There is no single U.S. federal disposition code or retention rule for every employer. Accurate records should show when a decision was made, what job-related criteria supported it, and which retention and notice rules apply.

Have you ever seen an applicant-tracking system show “closed” without explaining why? That small status can matter if a candidate asks about a decision or an agency reviews the hiring process. Clear disposition records help employers explain decisions, spot process gaps, and follow the rules that apply to them.

Candidate Disposition in Hiring: Definition, Status Codes & Compliance Framework

Candidate disposition is the documented result of a hiring decision at a particular stage. It may show that an applicant is still under review, has withdrawn, or will not move forward. Good records connect the decision to job-related criteria. The law does not require one universal set of status codes.

A disposition is more than a label in an applicant tracking system (ATS). It is part of the record of how an employer handled an application. “Rejected” may describe the outcome, but on its own it does not explain when the decision happened or what evidence supported it.

A useful record usually includes:

• Candidate’s current status and the hiring stage reached
• Decision date and, where relevant, the date the status was entered
• Specific reason tied to a published or documented job requirement
• Supporting evidence, such as interview ratings or assessment results
• Person or role authorized to make the decision
• Any required process notes, stored with appropriate privacy controls

Which disposition codes should employers use?

A disposition code is a short label for an applicant’s status or outcome. Employers can choose their own codes, but they should define them, use them consistently, and make sure each code means one clear thing. A code should not hide the actual reason for a decision.

Codes such as “bad fit” or “not a culture fit” are hard to audit because they do not identify a measurable job requirement. If an employer uses a broad code for reporting, it should retain the specific explanation elsewhere in the record.

What makes a reason job-related?

A job-related reason connects the decision to a real requirement for the role. It should reflect information gathered through the hiring process, not a guess or an unrelated personal detail. Criteria should be clear before they are used to compare candidates.

For example, “did not meet the required typing speed on the stated test” is more specific than “not strong enough.” A vague note is not automatically unlawful, but it makes it harder to show that the employer applied fair, consistent criteria.

Disposition Records, Retention Periods & FCRA Adverse-Action Requirements

Hiring records should show the decision, its date, the stage reached, and the job-related basis. Employers must also apply the retention period that fits their organization and circumstances. When a consumer report affects a hiring decision, federal law may require notices before and after the adverse action.

There is no single retention timeline for every employer or hiring record. The periods below are federal benchmarks, not a complete review of state or local rules. Employers should confirm which rules apply to their size, status, location, and contracts.

Under the Title VII record rule, covered employers generally keep hiring and personnel records for at least one year from the record’s creation or the personnel action, whichever is later. The federal-contractor rule generally sets a two-year period, with the listed one-year exception. A pending matter can require longer retention. A legal hold should pause routine deletion of relevant records.

What if a background report affects the decision?

A consumer report can include a background or credit report obtained from a consumer reporting agency. If an employer may reject, withdraw, or otherwise take adverse action based in whole or in part on such a report, the Fair Credit Reporting Act (FCRA) requires steps before and after the decision.

Before taking adverse action, the employer must provide the candidate with a copy of the report and the prescribed summary of rights. The candidate should have a reasonable opportunity to review the report and respond. The federal statute does not set one universal waiting period. State or local law may add requirements.

If the employer then takes adverse action, it must provide the required final notice. This generally includes the reporting agency’s contact details and information about the candidate’s rights to dispute the report and request another copy. Relevant provisions include 15 U.S.C. § 1681b(b)(3) and § 1681m(a). Employers should follow their legal process and applicable local rules rather than treating an ATS rejection code as a substitute for notice.

HR Audit Workflow: Consistency, Documentation & Disparate-Impact Review

An HR audit checks whether hiring records are complete, consistent, and supported by job-related evidence. It compares what the ATS says with interview, test, and decision records. A sound review also looks for patterns that may point to unequal effects, late entries, or reasons that changed after the decision.

I use a simple sequence: set the rules, record decisions, test the records, then correct gaps without erasing history. This approach makes the process easier to explain and reduces the risk of inconsistent notes.

Step 1: Set controls before recruiting

Define approved status codes and what each one means. Identify who can make or approve a selection decision, and document the criteria for the role before reviewing candidates. Limit system access to people who need it, and set retention rules based on employer type and location.

For each role, establish how interviewers will rate the same criteria. If a qualification is required, state that clearly. Avoid adding new criteria after seeing a candidate’s results unless there is a sound, documented reason and the change is applied fairly.

Step 2: Record decisions promptly

Enter the outcome close to the time the decision is made. Keep the decision date separate from the entry date if they differ. Link the reason to evidence, such as a scored interview question or a stated license requirement.

Do not include speculation, protected-class information, or personal remarks that are unrelated to the job. If an accommodation or other sensitive process note is needed, restrict access as appropriate and follow applicable privacy rules. A disposition record should explain the decision, not expose confidential details unnecessarily.

Step 3: Reconcile and test the records

Compare ATS entries with interview notes, assessment results, and offer records. Look for missing dispositions, duplicate candidates, unexplained status changes, and decisions entered long after the hiring stage ended.

Useful internal measures include:

• Completion rate: applicants with a final disposition divided by applicants who reached a closed stage
• Timeliness: median days between the decision and its ATS entry
• Reason-code quality: percentage of decisions with a specific, supported reason
• Consistency: whether candidates assessed against the same criteria received similar treatment

These measures are process checks, not legal safe harbors. A high completion rate does not prove that decisions were fair, and a low number of days does not prove that records are accurate. Review the underlying evidence.

Step 4: Review outcomes and correct errors

Title VII can raise a concern when a neutral selection rule disproportionately excludes people in a protected group and the rule is not job-related and consistent with business necessity. See 42 U.S.C. § 2000e-2(k). An outcome review can help identify patterns for closer examination. It does not, by itself, prove discrimination or establish that a process is lawful.

When correcting a record, do not overwrite the old entry or backdate a new one. Add a dated, attributable correction that explains what changed and why. Preserve the original entry and supporting records. If a complaint, charge, investigation, or lawsuit arises, stop routine deletion of relevant materials and follow the applicable legal hold.

Employment Outcomes, Candidate Communications & Audit-Ready Reporting

A complete hiring process connects the ATS outcome to any required candidate message and supporting record. Employers should close each application with an accurate status, communicate in line with policy, and retain evidence under the right rules. Audit-ready reporting should show what happened without overstating what the records prove.

Candidate messages do not need to reveal confidential information about other applicants. They should, however, avoid contradicting the employer’s records. If a consumer report played a role, the required FCRA steps are separate from a routine rejection email.

Illustrative audit scenarios

These examples are hypothetical. They show how a disposition record can improve, not replace, a careful hiring process.

Scenario 1: Unclear “fit” reason. An ATS shows “not a fit” after an interview, while interviewers used different criteria. The audit flags a weak explanation and inconsistent evaluation. The employer should not invent a reason after the fact. It should preserve the original record, document the issue through a dated correction, and review whether the criteria were applied consistently.

Scenario 2: Background-report concern. A candidate is marked “rejected” after a report raises a question about information relevant to the role. Before making the adverse decision, the employer follows the FCRA pre-adverse process, gives the report and rights summary, and allows a reasonable chance to respond. If it proceeds, it sends the required final notice and records each step.

Scenario 3: Role canceled. Several candidates are marked “not selected,” though the employer canceled the position before choosing anyone. The audit identifies that the code does not match the event. The employer corrects each record with an attributable audit trail and records that the role was canceled.

The practical standard is simple: a reviewer should be able to understand the stage, decision, timing, and job-related basis without guessing. If records cannot support that explanation, investigate the gap rather than filling it with a convenient code.

Conclusion: Candidate disposition is both a hiring status and an evidence trail. Use clear codes, document decisions promptly, retain records for the period that applies, and follow FCRA steps when consumer reports affect decisions. Audit for missing or inconsistent entries, and preserve a traceable history when making corrections.

What does candidate disposition mean in hiring?
It is the recorded outcome of an applicant’s review, such as continued consideration, withdrawal, rejection, or offer acceptance. It should identify the hiring stage and support the decision with job-related information.

Is there a federal candidate disposition code employers must use?
No. There is no single federal code list for all employers. Employers should define clear codes and apply them consistently while meeting the laws that apply to their organization.

What should a candidate disposition record include?
It should include the status, decision date, hiring stage, and a specific reason tied to job criteria. Supporting notes, such as interview ratings, can help explain the basis.

How long must hiring records be kept?
The period depends on the employer and situation. Covered Title VII employers generally keep records for at least one year. Covered federal contractors generally keep them for two years, with a one-year exception for certain smaller contractors.

Does “not a culture fit” count as a valid disposition reason?
It is too vague to explain a hiring decision on its own. A record should identify the job-related criterion and evidence used, rather than rely on a broad personal judgment.

What is a pre-adverse-action notice?
It is a notice given before an employer takes certain adverse actions based in whole or in part on a consumer report. The employer must provide the report and the required summary of rights.

Does the FCRA set a fixed waiting period before rejecting a candidate?
The federal statute does not set one universal waiting period. The candidate must have a reasonable opportunity to respond, and state or local rules may set additional requirements.

Can an employer change a disposition after an audit?
Yes, if the entry is wrong, but the employer should not erase or overwrite the original. Add a dated correction with the reason and the person responsible, preserving the record of the change.

What should an employer do when a complaint or lawsuit is pending?
Preserve relevant records and pause routine deletion when required. Follow the applicable retention rules and legal hold instructions rather than relying only on the normal destruction schedule.

(This article was written by one of our staff writers, Nathan Sterling. Visit our Meet the Team page.)