Skip to content
AI.info

Responsible AI

Bias Is More Than Biased Data

Distinguish statistical, human, historical, institutional, and deployment bias across the lifecycle of an AI system.

By the end you can

Comparison

Dataset balancing, Model debiasing, or Process redesign?

Dataset balancing changes the training data. Model debiasing changes the objective. Process redesign changes the decision that was being made in the first place.

The third repair has a dated public record. On 17 August 2020 the UK Government and Ofqual withdrew the standardisation model used to award GCSE, AS and A level grades, and awarded centre assessment grades instead. Ofqual's own later evaluation put figures on what the withdrawn model had done. For A level entries the calculated grade matched the teacher's grade in 59% of cases. It came out lower in 39%, and higher in just over 2%. The Secretary of State for Education, Gavin Williamson, said that day: “We worked with Ofqual to construct the fairest possible model, but it is clear that the process of allocating grades has resulted in more inconsistency and unfairness than can be reasonably resolved through an appeals process.”

Note what was not done. Nobody rebalanced the entry data. Nobody added a fairness constraint to the objective. The decision rule itself was retired, by the body that had the authority to retire it. That authority is the resource process redesign needs and the other two repairs do not. The Office for Statistics Regulation reviewed the episode in March 2021 and found that all four UK regulators' approaches had failed to command public confidence. Its lesson: “a statistical model might not always be the best approach to meet your need”.

FigureComparison · 3 columns

Dataset balancing

Changes representation in the training data.

  • Can reduce sampling imbalance
  • Does not repair biased targets or institutions
  • May distort prevalence if applied carelessly
  • Needs context-specific evaluation

Model debiasing

Constrains representation, error, or prediction behavior.

  • Can address a defined statistical criterion
  • May trade errors or reduce calibration
  • Cannot choose the social objective alone
  • Requires monitoring after deployment

Process redesign

Changes the decision rule or service itself.

  • Can remove harmful proxies and bottlenecks
  • May create more durable equity
  • Requires organizational authority
  • Example: redesign unnecessary availability requirements

Example

The motherhood penalty, measured before any model is in the room

The disadvantage a recruiting model would learn is measurable before the model exists. Matched résumés measured it. An audit study published in the American Journal of Sociology in 2007 sent 1,276 of them to 638 employers over 18 months. Childless women received 2.1 times as many callbacks as equally qualified mothers: 6.6% against 3.1%. A paired laboratory experiment ran alongside the audit. Mothers were recommended for hire 47% of the time, non-mothers 84%. Mothers were rated about 10% lower on competence, and offered starting salaries $11,000 (7.4%) lower. The authors' own reading of the audit arm: “The results suggest that real employers do discriminate against mothers.” No algorithm took part in any of it.

Now train a screening model on decisions of that kind. Balance the dataset by gender. Check that aggregate accuracy by gender comes out level. It can. The model will still favour candidates with uninterrupted career histories. That is the pattern the process it learned from rewarded.

  • Historical structure: Career interruption reflects unequal care responsibilities and labor-market opportunity. The audit study priced it directly: 6.6% callbacks for childless women against 3.1% for equally qualified mothers, on matched résumés.
  • Measurement choice: Résumé continuity is treated as evidence of commitment. In the laboratory arm that same signal cost mothers about 10% on rated competence. People made those judgements, before any predictor was fitted to anything.
  • Organizational norm: The role is designed around an avoidable availability assumption, and the assumption carries a figure. Evaluators reading equivalent credentials offered mothers starting salaries $11,000 (7.4%) lower.
  • Model behavior: The predictor faithfully learns the chosen proxy. A 47%-against-84% gap in hire recommendations is exactly the regularity a ranking model would be rewarded for reproducing, and reproducing it is what accuracy on such labels means.
  • False closure: Balanced data and aggregate metrics conceal the institutional source of disadvantage. Nothing about the 1,276 résumés was unbalanced — they were matched by design. The penalty was still 2.1 times.

Nine sources, and the repair depends which one

Bias is a systematic tendency. It can arise from history, institutions, measurement, sampling, labeling, modeling, interfaces, human judgment, or deployment. Harmful bias can persist when data are balanced and protected attributes are absent. Naming which of the nine sources is at work is what decides whether the repair belongs to the dataset or to the process.

The cleanest measured case of that sits in a hospital. A 2019 study in Science dissected a commercial health-risk algorithm affecting millions of patients. Its data were not unbalanced. The fault was in the target: the system used health costs as the proxy for health need. Correcting that target variable would have raised the share of Black patients identified for extra care from 17.7% to 46.5%. Same algorithm class, same patients, a factor of 2.6 in who gets care — turning on which quantity the model was asked to predict. The authors close their abstract with the general point: “We suggest that the choice of convenient, seemingly effective proxies for ground truth can be an important source of algorithmic bias in many contexts.”

NIST distinguishes systemic, computational and statistical, and human-cognitive sources of bias. The categories interact. An institutional rule shapes the labels. The model amplifies the pattern. Operators then read the output through expectations they already hold.

Skip the diagnosis and the team rebalances a sample it owns, while a cost proxy it never questioned keeps moving 17.7% against 46.5% of the care.

Steps

Biased is a claim about an allocation

Before any mechanism is traced, name the benefit or burden being allocated. “Biased” is a claim about an allocation rather than about a matrix.

Step 1 has a worked example on a federal docket. iTutorGroup's tutor-application software was programmed to reject female applicants aged 55 or older and male applicants aged 60 or older. The EEOC sued the company on 5 May 2022. Every slot in the allocation is filled. The benefit is a tutoring job. The burden is automatic rejection at the screening step. The affected group is a class of more than 200 applicants, and the consequence was decided rather than argued. A consent decree entered 8 September 2023 carried $365,000, a five-year term and a bar on requesting dates of birth before an offer. It was the agency's first settled hiring-discrimination suit over recruitment software. Timothy Riera, Acting Director of the EEOC's New York District Office: “Everyone loses when employers engage in age discrimination. Hundreds of applicants lost out on employment during a difficult time for job seekers, and iTutorGroup's students lost the opportunity to learn English from highly qualified and experienced tutors.”

Step 5 has one too. Run PredPol's published algorithm on Oakland drug-arrest records and it flags neighbourhoods that already carried about 200 times more drug-related arrests than the rest of the city. Lum and Isaac did exactly that in 2016 and reported it in Significance. The model would target Black residents at roughly twice the rate of white residents, and other non-white residents at about 1.5 times the white rate. Survey-estimated drug use was roughly equal across racial groups. Patrols follow the flags. Arrests follow the patrols. Those arrests are the records the next fit is trained on. In their own phrase, the system reinforces what is already in the data “rather than correcting for the apparent biases in the police data”. That is what step 5 is watching for, and it is why steps 1 and 5 belong to the same review.

FigureProcess · 5 steps
  1. 1. Define the decision

    Name the benefit, burden, error, or opportunity allocated.

  2. 2. Trace the mechanism

    Follow history, data, labels, model, interface, and human action.

  3. 3. Test alternatives

    Compare remeasurement, process redesign, model controls, and non-AI options.

  4. 4. Evaluate distribution

    Measure relevant groups, intersections, contexts, and downstream outcomes.

  5. 5. Monitor feedback

    Track how decisions alter future data, access, and institutional behavior.

Analogy

A tilted playing field measured with a precise ruler

Every runner can be timed accurately on a field that slopes toward one lane. Better measurement describes the difference precisely and leaves the race as unfair as it was.

The health-risk algorithm was a ruler of exactly that quality. It predicted the quantity it had been asked to predict, health costs, and health costs had been put in the place of health need. The share of Black patients identified for extra care stood at 17.7% until somebody changed the target rather than the estimator. A slope can be seen and surveyed. The tilt in a hiring or lending system is made of several histories at once, pulling in different directions. That is why the review below starts by naming the decision, not by looking for a gradient.

Technical precision cannot compensate for an unjust rule or institutional structure.

Visual

Four sources, one allocation, one remedy layer

Systemic, statistical, cognitive, interactional: four sources of bias feed one allocation decision, and the remedy is chosen in a fifth layer of law, alternatives and stakeholder goals.

Two of those layers now meet in a statute. The EU AI Act of 2024 writes them down article by article. Article 10(2)(f) requires that training, validation and testing data sets for high-risk AI systems undergo “examination in view of possible biases”. Article 10(2)(g) requires measures to detect, prevent and mitigate any biases so identified. Article 10(5) permits the processing of special-category personal data strictly for bias detection and correction. That is the statistical node made mandatory.

Article 14(4)(b) reaches the cognitive node by name. Human-oversight measures must enable the person assigned to oversight “to remain aware of the possible tendency of automatically relying or over-relying on the output produced by a high-risk AI system (automation bias), in particular for high-risk AI systems used to provide information or recommendations for decisions to be taken by natural persons”. Automation bias here is not a bullet in a training deck. It is a numbered article of a regulation. That is what the remediation layer looks like once a legislature has written in it.

FigureProcess · 5 steps
  1. 1

    Systemic and institutional

    Rules, incentives, resource distribution, history, and organizational practice.

  2. 2

    Statistical and computational

    Sampling, measurement, features, objectives, model assumptions, and thresholds.

  3. 3

    Human cognitive

    Framing, anchoring, stereotypes, automation bias, and selective attention.

  4. 4

    Interaction and deployment

    Interfaces, workload, overrides, feedback loops, and selective labels.

  5. 5

    Remediation context

    Law, stakeholder goals, alternatives, and the actual allocation decision.

Key idea

Systemic, statistical, human: name which one

Calling every difference “bias” makes diagnosis harder. A review should name the reference, the mechanism, the affected group, the consequence, and the normative reason the difference matters. The health-risk algorithm was performing well at the thing it had been built to predict. That made the finding one about the choice of target rather than one about the dataset — a distinction that decides who is asked to fix it. Some differences reflect the task legitimately varying. Others encode unjust conditions. Statistics cannot draw that boundary without legal, domain, and stakeholder judgment.

NIST put a vocabulary around this in March 2022. Special Publication 1270 identifies three categories of bias in AI: systemic, statistical and computational, and human. Use the standard's own words for the first: “Systemic biases result from procedures and practices of particular institutions that operate in ways which result in certain social groups being advantaged or favored and others being disadvantaged or devalued.” Such bias, the publication adds, “need not be the result of any conscious prejudice”. That is why looking for an author of the harm finds nobody and closes the review. Statistical bias comes from sampling, measurement and modelling choices. Human bias enters through the judgement of the people who specify, build, review, approve and finally use the system. Name which of the three is at work.

That is the difference between a diagnosis and a complaint.

An unnamed bias claim cannot be assigned, tested, or refuted, so it survives the review unchanged.

Example

One disparity, four mechanisms

Take one observed disparity and write down every mechanism that could have produced it, before proposing a single fix. Use a real one: the flagged Oakland neighbourhoods carrying about 200 times more drug-related arrests than the rest of the city.

  • Bias map: For that disparity, list the systemic, statistical, human and deployment mechanisms separately — enforcement history and procedure, the arrest record used as the training target, the judgement of whoever set the patrol priorities, and the dispatches the model's own flags produce.
  • Reference question: Write down the baseline the claim is measured against. Lum and Isaac's was survey-estimated drug use, roughly equal across racial groups. Scored against the arrest record instead, the same model looks calibrated.
  • Process alternative: Identify one organizational rule that could change before the model does. The iTutorGroup decree barred requesting dates of birth before an offer. It did not adjust the screening software's thresholds.
  • Feedback loop: Describe how today's decisions shape tomorrow's labels and behaviour: which records the next refresh will hold, and who will have stopped appearing in them at all.

Carry this bias across the AI lifecycle boundary forward

A bias claim needs a stated baseline. A disparity is always measured against some standard, and leaving that standard unwritten hides the whole argument. Every anchored case in this lesson has one and says so. The Science study measured against health need instead of health cost, and the distance between the two baselines was 17.7% against 46.5%. Lum and Isaac measured against survey-estimated drug use, roughly equal across racial groups, rather than against an arrest record concentrated about 200 times over. The résumé audit measured against equally qualified applicants who differed in one thing, whether they were mothers: 6.6% against 3.1%.

Then define when bias across the AI lifecycle requires the team to redesign, restrict, remedy, or retire the system. All four have been done on the record. Ofqual and the UK Government retired a model on 17 August 2020. The consent decree of 8 September 2023 restricted a screening system and remedied the harm, at $365,000 for more than 200 applicants. Article 10(2)(f) of the AI Act requires the examination that is supposed to find these before deployment. Article 14(4)(b) requires that the person watching the output be kept aware of the pull to defer to it.

Key takeaways