Technical Examination of Bias and Fairness in Machine-Learning Models: Groups, Metrics and Limitations

Technical illustration of bias and fairness metrics for machine-learning models

Why technical fairness analysis must define the decision context, groups, reference labels, metrics and limitations before interpreting group differences.

By Mathias Ellmann English version: 21 October 2026

AI & Machine Learning

A technical fairness analysis does not begin with the statement that a model is fair or unfair. The examination question, group definitions, data state, reference outcomes, model outputs, metric and comparison criterion must first be fixed so that any measured difference has a traceable technical meaning.

Short answer

Bias and fairness are not a single technical metric. NIST treats AI bias as a broader socio-technical topic and distinguishes systemic, statistical and human sources of bias. A technical model examination can then measure concrete group differences such as selection rates, true-positive rates, false-positive rates or group-specific accuracy.

A practical examination chain is: technical question → possible effect or harm → group definitions → data state → reference labels → model output → group metrics → uncertainty → technical interpretation → limitation. The measured result remains separate from a legal discrimination assessment or other normative conclusion.

Analysis chain From a fairness question to a bounded technical finding
1 Question Specify the effect, population and groups.
2 Evidence Fix data, reference labels, outputs and thresholds.
3 Metrics Calculate group-level rates and uncertainty consistently.
4 Limits Separate measured differences, causes and normative assessment.

1. Concepts and examination context

The term bias has several meanings

In a technical context, bias can describe systematic statistical distortion. In broader AI discussions, however, the term is also used for organisational, social and human influences. A technical report should therefore not state that “bias exists” without identifying what was actually measured or observed.

NIST Special Publication 1270 distinguishes systemic, statistical and human bias and explicitly treats AI bias as a socio-technical issue rather than reducing it to model parameters, training data or one fairness metric. Statistical bias can be relevant while still representing only one part of the broader issue.

A fairness question needs a concrete decision context

Before metrics are selected, the examination should define the decision or prediction process, target population, possible effect or harm and relevant group attributes. A metric without that context can be calculated correctly while answering the wrong question.

Group definitions must be technically reproducible. The source of group attributes, handling of missing values, category combinations and any exclusions should be documented because those choices directly affect the measured subgroup results.

2. Group comparison and technical measurement basis

Overall metrics can hide differences between groups. A model can have a strong overall accuracy while producing materially different false-positive or false-negative rates in defined subgroups. An aggregate score therefore does not automatically answer a group-specific examination question.

Group metrics should use the same technical definition

When groups are compared, the same metric definition and calculation procedure should be applied to each subgroup. Fairlearn's MetricFrame provides one technical structure for evaluating metrics overall and by group, including differences, ratios and bootstrap-based confidence intervals.

Selection rate measures the share of positive predictions

Selection rate is the proportion of cases for which the model produces the designated positive prediction. It can be useful for demographic-parity-style comparisons, but equal selection rates do not establish that all groups experience equal error patterns or equal outcomes in a broader sense.

True-positive and false-positive rates require suitable reference labels. If those labels are inaccurate, incomplete or conceptually unsuitable, the group metrics inherit that limitation. The label-generating process is therefore itself part of the evidence basis.

Differences can be expressed as absolute differences or ratios. The chosen representation should be documented and interpreted together with group counts; an apparently large percentage difference in a very small subgroup can carry substantial statistical uncertainty.

3. Fairness criteria and metric selection

The choice of fairness metric is part of the examination criterion

Demographic parity, equalized odds and equal opportunity answer different statistical questions. Hardt, Price and Srebro formulate equalized odds and equal opportunity for supervised classification. Satisfying one criterion only establishes the relationship defined by that criterion; it does not prove the absence of disadvantage, identify causes or provide a legal assessment.

The metric should therefore be derived from the concrete examination question. If the concern is unequal positive selection, selection rates may be relevant. If the concern is different error treatment conditional on reference outcomes, true-positive and false-positive rates can become more relevant. No single metric is universally “the fairness metric.”

Construct validity limits fairness metrics

Fairlearn emphasizes the importance of construct validity: a technically precise metric can still be a weak representation of the underlying real-world concept. The examination should ask whether the chosen observable variables, labels and metrics actually represent the effect or harm that the analysis is intended to address.

4. Uncertainty, subgroups and aggregation

Uncertainty should remain visible in group metrics

Group metrics are estimates based on finite samples. Fairlearn supports bootstrap confidence intervals for MetricFrame, allowing estimates to be viewed together with uncertainty. Small groups can otherwise create apparently precise differences that are poorly supported by the available data.

Multiple group attributes create more granular subgroups

Combining group attributes can reveal differences hidden by broader aggregation. At the same time, the number of cases per combination can become small or zero. A subgroup that is absent from the examined data cannot yield a supportable empirical group metric from that data.

Aggregation choices should therefore be documented. Results for broad groups and intersectional subgroups can answer different questions. With many groups and metrics, the number of statistical comparisons also increases and should be considered when interpreting isolated differences.

5. Causes, limitations and separation from legal assessment

Fairness metrics are not a causal analysis

A measured difference establishes that a defined metric differs between groups. It does not by itself establish why the difference exists. Possible contributors include data composition, reference labels, model behavior, thresholds, selection mechanisms or the wider application context.

A group difference therefore does not automatically prove a model defect. Conversely, the absence of a difference on one selected metric does not establish the absence of all harms, other group effects or other relevant fairness concerns.

Representativeness and fairness remain different areas of examination. Representativeness concerns population, sampling, coverage and distributions; fairness analysis concerns defined group differences in outputs, performance or effects. Bias is broader still and should not be reduced to any one group comparison.

Technical fairness measurement and legal discrimination analysis must remain separate

A technical examination can document groups, selection rates, true-positive and false-positive rates, other performance metrics and uncertainty. Whether a measured difference is legally impermissible or normatively unjust requires a separate standard. NIST and Fairlearn provide technical and socio-technical frameworks; they do not replace binding law or case-specific legal assessment.

6. Documentation and technical synthesis

Practical documentation structure for a fairness analysis

Examination questions

Is the fairness analysis technically supportable?

  • Is the decision situation and target population defined?
  • Are relevant group attributes and group definitions documented?
  • Is the same metric definition applied consistently across groups?
  • Are group sizes, case counts and statistical uncertainty visible?
  • Is the selected fairness metric justified by the examination question?
  • Are subgroups, aggregation effects and multiple attributes considered?
  • Are observed differences kept separate from hypotheses about their causes?
  • Are technical fairness measurement, broader assessment and legal discrimination analysis kept separate?

Constructed example

A classification model prioritises incoming service cases. Two previously defined customer segments are evaluated separately. Segment A receives a positive prediction in 55% of cases, while Segment B receives one in 35%, so the selection rates differ.

Using an independently reviewed reference label, the groups show similar true-positive rates but different false-positive rates. Demographic-parity-style and equalized-odds-style measurements therefore provide different information about the same model state.

The technical finding is not simply “the model is unfair.” It documents the groups, metrics, differences, case counts, reference outcomes and limitations. The example is entirely constructed and is not a real engagement, legal assessment or court appointment.

Sources and technical basis

  • Scientific original paper Moritz Hardt, Eric Price and Nati Srebro: Equality of Opportunity in Supervised Learning, NeurIPS 29 (2016), especially Section 2 and Definitions 2.1 and 2.2. The paper defines equalized odds and equal opportunity and assumes suitable target values and group information. Open source.
  • Official NIST publication NIST Special Publication 1270: Towards a Standard for Identifying and Managing Bias in Artificial Intelligence, used for socio-technical framing of systemic, statistical and human bias. Open source.
  • Official NIST resource NIST: AI RMF Playbook – Measure, used as additional technical basis for measurement, context and limitations. Open source.
  • Technical reference Fairlearn: Fairness in Machine Learning, used for socio-technical fairness, categories of harm and construct validity. Open source.
  • Technical reference Fairlearn: Common fairness metrics, used for demographic parity, selection rates, equalized odds and equal opportunity. Open source.
  • Technical reference Fairlearn: fairlearn.metrics.MetricFrame, used for overall and by-group metrics, differences, ratios and bootstrap confidence intervals. Open source.
  • Author's technical literature Mathias Ellmann: Von Modellen zu Entscheidungen in Machine Learning mit Python, providing technical background on evaluation, metrics, test data, classification and model interpretation. Open source.
  • Author's methodological framing Examination question → possible effect or harm → groups → data state → reference → model output → group metrics → uncertainty → interpretation → limitation.

Further reading

Critical review and methodological limitation

Group differences can arise from the model, data composition, label definitions, measurement error, thresholds or sample composition. A single fairness metric therefore does not establish a general normative conclusion.

  • Data versus model cause: group differences can originate in selection, measurement or labeling before the model is applied.
  • Metric conflicts: different fairness criteria can be simultaneously incompatible or differently relevant to the intended use.
  • Separate technical and normative questions: technical findings describe measurable differences; deciding which distribution is just or legally permissible requires a separate normative standard.
Examination rule: Do not state a fairness conclusion more broadly than the defined groups, metrics, reference labels and tested system state support. Keep causes, harms and legal evaluation separate unless they are independently examined.

Translation and methodological scope

This English article is based on the reviewed German V1 source article. The translation preserves the technical meaning, methodological distinctions, source status and stated limitations. It does not strengthen technical findings into legal conclusions and does not treat technical references as proof of compliance or suitability for a specific system.

Source relationship: The corresponding German article remains the reference baseline during English V1 development. Open the German source article.

Author's technical literature and publications

The following works provide additional technical and methodological context. They do not replace required primary sources, standards, manufacturer documentation or other independent specialist sources. Unpublished manuscripts, drafts and teaching materials are deliberately not presented here as public sources.

Mathias Ellmann, IT expert

Data Science & AI Assessments

Technical examination of data quality, model validity, reproducibility, bias, robustness and documented AI-system behaviour.

Explore this assessment service