Disparate impact is a legal doctrine originating in U.S. employment law that prohibits facially neutral policies, practices, or algorithms that disproportionately harm members of a protected class, such as those defined by race, color, or gender, regardless of intent. In machine learning, it serves as a primary quantitative fairness metric to detect unintentional discrimination, where a model's selection or approval rate for a disadvantaged group is substantially lower than for a privileged group.
Glossary
Disparate Impact

What is Disparate Impact?
A legal doctrine and quantitative fairness metric that identifies facially neutral practices which disproportionately harm members of a protected group, often measured by the 80% rule.
The standard quantitative test is the 80% rule (or four-fifths rule), where a selection rate for a protected group that is less than 80% of the rate for the group with the highest selection rate constitutes evidence of adverse impact. This is a threshold for triggering a deeper audit, not a definitive measure of illegality, and is distinct from Disparate Treatment, which requires proof of intentional discrimination.
Core Characteristics of Disparate Impact
Disparate impact is a legal doctrine and a quantitative fairness metric that identifies facially neutral policies or algorithms that disproportionately harm members of a protected group. It focuses on the effects of a practice, not its intent.
The 80% Rule (Four-Fifths Rule)
The primary quantitative benchmark for identifying disparate impact, originating from the Uniform Guidelines on Employee Selection Procedures (1978). A selection rate for a protected group that is less than 80% of the rate for the group with the highest selection rate is evidence of adverse impact.
- Formula: (Selection Rate of Protected Group) / (Selection Rate of Highest Group) < 0.80
- Example: If a hiring algorithm advances 60% of male applicants but only 30% of female applicants, the ratio is 0.50, signaling a potential violation.
- Statistical Significance: Courts may also require that the disparity is statistically significant, often at the p < 0.05 level.
Business Necessity Defense
Once a plaintiff establishes a prima facie case of disparate impact, the burden shifts to the defendant to prove the challenged practice is job-related and consistent with business necessity. The practice must be predictive of or significantly correlated with important elements of work behavior.
- Validation: Employers must demonstrate the practice is properly validated, often through content, criterion, or construct validity studies.
- Title VII: Codified in the Civil Rights Act of 1991, which explicitly placed the burden of proof for business necessity on the employer.
Less Discriminatory Alternative
Even if an employer proves business necessity, a plaintiff can still prevail by demonstrating that a less discriminatory alternative exists that serves the employer's legitimate interest equally well but with a less severe disparate impact.
- Refusal to Adopt: The employer's refusal to adopt such an alternative is treated as a violation.
- Algorithmic Context: In ML, this often involves re-training a model with a fairness constraint or using a different feature set that achieves comparable accuracy with reduced group disparity.
Disparate Impact vs. Disparate Treatment
A critical legal distinction separates these two forms of discrimination. Disparate treatment is intentional discrimination—an employer knowingly treats an individual differently because of a protected characteristic.
- Disparate Impact: Unintentional; a neutral policy has a disproportionately adverse effect.
- Proof of Intent: Disparate impact does not require proof of discriminatory motive. It is an effects-based doctrine.
- Legal Origin: Disparate impact was established by the Supreme Court in Griggs v. Duke Power Co. (1971).
Proxy Variables & Indirect Discrimination
A model can cause disparate impact even without direct access to a protected attribute like race or gender. This occurs through proxy discrimination, where a non-protected feature serves as a stand-in.
- Classic Proxy: Zip code or neighborhood strongly correlates with race due to historical housing segregation.
- Algorithmic Redlining: Using a proxy like browser history or purchasing patterns to offer different credit terms to different groups.
- Detection: Requires auditing feature importance and correlation matrices between model inputs and protected attributes.
Measuring Disparate Impact in ML
Beyond the 80% rule, modern fairness toolkits implement statistical measures to quantify disparate impact in classification models.
- Demographic Parity Difference: The difference in positive prediction rates between groups. A value of 0 indicates perfect parity.
- Disparate Impact Ratio: The ratio of positive prediction rates. A value of 1.0 indicates no disparate impact.
- Tooling: Libraries like Fairlearn, AIF360, and TensorFlow Fairness Indicators compute these metrics directly from model predictions and sensitive attribute data.
Frequently Asked Questions
Clear, technical answers to the most common questions about the legal doctrine and quantitative measurement of disparate impact in algorithmic systems.
Disparate impact is a legal doctrine under U.S. anti-discrimination law that identifies facially neutral policies or practices which disproportionately harm members of a protected group, even without discriminatory intent. Established by the Supreme Court in Griggs v. Duke Power Co. (1971), it shifted the focus from intentional discrimination to the statistical consequences of employment and lending practices. In the algorithmic context, a model that uses no protected attributes directly but produces significantly different approval rates across racial or gender groups may still violate disparate impact law. The legal framework follows a three-step burden-shifting process: the plaintiff must first establish a prima facie case by showing a statistically significant disparity; the defendant must then demonstrate the practice is job-related and consistent with business necessity; finally, the plaintiff can still prevail by showing a less discriminatory alternative exists that the defendant refused to adopt.
Disparate Impact vs. Disparate Treatment
A comparison of the two primary legal theories of discrimination under U.S. employment and fair housing law, distinguishing between facially neutral policies with discriminatory effects and intentional differential treatment.
| Feature | Disparate Impact | Disparate Treatment |
|---|---|---|
Legal Definition | A facially neutral policy or practice that disproportionately harms members of a protected group, regardless of intent. | Intentional differential treatment of an individual based on their membership in a protected class. |
Discriminatory Intent | ||
Facially Neutral Policy | ||
Primary Legal Test | The 80% rule (Four-Fifths Rule) and statistical significance testing of adverse impact ratios. | The McDonnell Douglas burden-shifting framework requiring proof of discriminatory motive. |
Burden of Proof | Plaintiff must demonstrate a statistically significant disparity; burden shifts to defendant to prove business necessity. | Plaintiff must establish a prima facie case of intentional discrimination; defendant must articulate a legitimate, non-discriminatory reason. |
Employer Defense | Business necessity and job-relatedness; the challenged practice is essential to the business and consistent with business necessity. | Legitimate, non-discriminatory reason for the adverse action; plaintiff must then prove pretext. |
Remedial Action | Modify or eliminate the discriminatory policy; adopt an alternative practice with less disparate impact that still serves business needs. | Cease discriminatory behavior; provide back pay, reinstatement, or compensatory damages to the affected individual. |
Governing Statute (U.S.) | Title VII of the Civil Rights Act of 1964 (as amended in 1991); Fair Housing Act. | Title VII of the Civil Rights Act of 1964; 42 U.S.C. § 1981; Age Discrimination in Employment Act. |
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
Disparate impact is one of several legal and quantitative fairness doctrines. These related concepts form the core vocabulary of algorithmic fairness auditing.
Disparate Treatment
The intentional and explicit differential treatment of individuals based on their membership in a protected class. Unlike disparate impact, which concerns facially neutral practices with discriminatory effects, disparate treatment requires proof of discriminatory intent. In machine learning systems, this can manifest when a model is given direct access to a protected attribute like race or gender and uses it to make decisions. This is the most straightforward form of discrimination under U.S. law and is almost always illegal.
The 80% Rule (Four-Fifths Rule)
The primary quantitative benchmark for identifying disparate impact, established by the Uniform Guidelines on Employee Selection Procedures (1978). A selection rate for a protected group that is less than 80% of the rate for the group with the highest selection rate constitutes evidence of adverse impact.
- Formula: (Selection Rate of Protected Group) / (Selection Rate of Reference Group) < 0.80
- Example: If 60% of male applicants are approved and only 30% of female applicants are approved, the ratio is 0.50, signaling a potential violation.
- Limitation: This is a rule of thumb, not a statistical significance test. It can be unreliable with very small sample sizes.
Proxy Discrimination
A form of algorithmic bias where a facially neutral feature serves as a stand-in for a protected attribute, allowing disparate impact to occur indirectly. Common proxies include:
- Zip code as a proxy for race due to residential segregation.
- Credit history as a proxy for socioeconomic status.
- Name or linguistic patterns as proxies for ethnicity or gender.
Simply removing protected attributes from a model—a naive approach called fairness through unawareness—is insufficient because machine learning models can reconstruct sensitive information from correlated proxies.
Demographic Parity
An independence-based fairness criterion requiring that a model's positive prediction rate be equal across all groups defined by a protected attribute. Also known as statistical parity.
- Formal Definition: P(Ŷ=1 | A=a) = P(Ŷ=1 | A=b) for all groups a, b.
- Key Trade-off: This criterion ignores the ground truth labels. If base rates of a qualified outcome differ between groups, enforcing demographic parity may require selecting unqualified individuals from one group while rejecting qualified individuals from another.
- Relationship to Disparate Impact: Demographic parity is the mathematical formalization of the outcome sought by disparate impact doctrine.
Equalized Odds
A separation-based fairness metric requiring a classifier to have equal true positive rates and equal false positive rates across different sensitive groups. This is stricter than equal opportunity, which only constrains true positive rates.
- Formal Definition: P(Ŷ=1 | Y=y, A=a) = P(Ŷ=1 | Y=y, A=b) for y ∈ {0,1}
- Implication: The model's errors must be distributed equally across groups. A qualified individual has the same chance of being selected regardless of group membership, and an unqualified individual has the same chance of being erroneously selected.
- Use Case: Preferred in high-stakes domains like criminal justice where both false positives and false negatives carry severe consequences.
Algorithmic Recourse
The ability for an individual negatively affected by an algorithmic decision to understand the reasons and take actionable steps to reverse that decision in the future. This concept is directly tied to disparate impact remediation.
- Key Components:
- Actionability: The recommended changes must be under the individual's control (e.g., 'increase income by 20%' is not actionable; 'reduce credit utilization below 30%' is).
- Counterfactual Generation: Systems like FACE or DiCE generate minimal changes to input features that would flip a negative decision to positive.
- Legal Context: The EU's GDPR Article 22 grants a right to meaningful information about the logic involved in automated decisions, making recourse a regulatory requirement.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us