1 Definitions and notation
False negative rate (FNR) is the fraction of truly positive instances that a test or classification system incorrectly assigns to the negative category. Put differently, it measures how frequently the system “misses” the positive class.
1.1 Confusion matrix terminology
In a binary classification setting, a confusion matrix cross-tabulates model outputs against ground-truth labels:
- True positives (TP): positive cases correctly identified as positive.
- False negatives (FN): positive cases incorrectly labeled as negative.
- True negatives (TN): negative cases correctly identified as negative.
- False positives (FP): negative cases incorrectly labeled as positive.
FNR is computed using the positive ground-truth quantities, so it depends on FN and the total number of actual positives (TP + FN).
1.2 Relationship to sensitivity (recall)
Sensitivity is commonly defined as the proportion of actual positives that are detected. Under the standard binary-definition convention, sensitivity equals TP / (TP + FN), which is the same quantity as 1 − FNR. As a result, FNR and sensitivity are complementary measures: lowering FNR increases sensitivity.
1.3 Relationship to complementary error rate concepts
Because FNR focuses on missed positives, it is often discussed alongside measures that focus on false alarms (such as false positive rate). Different applications weigh these failure modes differently, leading to trade-offs as decision thresholds change.
2 Mathematical formulation
2.1 Formula for false negative rate
2.1.1 Expressing FNR using TP, FN
Let the predicted labels be binary and let the ground truth define which items are truly positive. The false negative rate is:
\[ \mathrm{FNR} = \frac{\mathrm{FN}}{\mathrm{TP} + \mathrm{FN}} \]
The denominator represents the number of actual positives. The numerator counts how many of those positives were incorrectly predicted as negative.
2.2 Alternative expressions using prevalence
If a dataset has prevalence \(p\) (the fraction of all instances that are truly positive), and if a classifier has sensitivity \(s\), then:
- \(\mathrm{FNR} = 1 - s\)
In terms of prevalence and counts over a dataset of size \(N\), the expected numbers satisfy:
- expected actual positives \(= pN\)
- expected false negatives \(= (1-s)pN\)
so: \[ \mathrm{FNR} = \frac{(1-s)pN}{pN} = 1-s \] Prevalence therefore cancels in the FNR definition, which means FNR is not directly determined by how rare positives are; it reflects detection behavior conditional on being positive.
2.3 Units, range, and edge cases
- Units: FNR is dimensionless (a proportion or percentage).
- Range: \(0 \le \mathrm{FNR} \le 1\).
- Edge case (undefined): If there are no actual positives in the evaluation data, then \(TP + FN = 0\) and FNR is not defined. In practice, this occurs when a test set is small or when positives are extremely rare.
3 Estimation from data
3.1 Empirical FNR (from labeled samples)
When evaluation labels are available, the empirical estimate is computed directly from the confusion matrix:
\[ \widehat{\mathrm{FNR}} = \frac{\widehat{\mathrm{FN}}}{\widehat{\mathrm{TP}} + \widehat{\mathrm{FN}}} \]
This estimate treats each actual positive instance as an opportunity to be detected; conditional on being positive, the “event” is being missed.
3.2 Handling class imbalance
Class imbalance affects how many actual positives appear in the sample, which in turn affects the stability of the estimate. Even if FNR itself is defined only over positive instances, imbalanced data can lead to high variance in \(\widehat{\mathrm{FNR}}\) because \(TP + FN\) becomes small. Common approaches include:
- ensuring sufficiently large positive counts in the evaluation set,
- using resampling or stratified splits to preserve prevalence,
- selecting thresholds with the goal of controlling FNR rather than relying on overall accuracy.
3.3 Stratified/conditional FNR estimates
FNR can be computed separately for groups or conditions (e.g., different acquisition settings, demographic categories in non-political quality-control contexts, device types, or patient cohorts in biomedical workflows). These conditional FNR values help reveal whether missed detections are concentrated in specific subpopulations or feature regimes.
Formally, if \(G\) denotes a stratum, then: \[ \mathrm{FNR}(G)=\frac{\mathrm{FN}(G)}{\mathrm{TP}(G)+\mathrm{FN}(G)} \] Interpretation should account for differing sample sizes across strata.
3.4 Confidence intervals for FNR
Because the denominator is the count of actual positives, confidence intervals can be derived using binomial reasoning: conditional on there being \(m = TP + FN\) actual positives, the number of false negatives \(FN\) can be modeled as a binomial outcome with success probability equal to FNR. If \(FN \sim \mathrm{Binomial}(m, \theta)\), then \(\theta\) is the true FNR and \(\widehat{\theta} = FN/m\) is the empirical estimate.
Common interval approaches include:
- exact (Clopper–Pearson) intervals,
- approximate normal intervals for large \(m\),
- Bayesian intervals using beta priors.
Which interval method is appropriate depends on sample size and desired calibration behavior.
3.5 Zero-denominator and undefined scenarios
If a particular subgroup has zero actual positives, FNR cannot be computed. Practical handling options include:
- reporting “not available” for that subgroup,
- aggregating strata when justified,
- using smoothing or model-based estimates (with care, as these can introduce assumptions).
4 Threshold and decision-rule effects
4.1 Threshold-dependent FNR behavior
For many classifiers, outputs are scores (e.g., probabilities or logits). A decision threshold converts scores into class labels. As the threshold changes, the classifier shifts between missing positives and producing more false alarms. Typically, lowering the threshold increases the number of predicted positives, which tends to reduce FN and therefore reduce FNR; raising the threshold often increases FNR.
4.2 Trade-offs with false positive rate
FNR is often inversely related to the false positive rate (FPR) through the choice of threshold. A system that is tuned to avoid false negatives (low FNR) generally risks increasing false positives unless additional constraints or calibration steps are used. The relationship is not fixed for all models, but it is a frequent pattern in practice.
4.3 Operating points and cost-based interpretation
When misclassifications have different costs, decision-making can incorporate an explicit cost structure. For example, if missed positives are particularly harmful, the operating point is chosen to keep FNR below a target level, even if it raises FPR. Conversely, if false alarms are costly, one may accept a higher FNR to reduce FP.
In cost-based terms, the preferred threshold is the one that optimizes expected utility or minimizes expected risk, where the costs correspond to FN and FP consequences.
4.4 ROC and precision-recall context links
- ROC curves: plot TPR (sensitivity) against FPR across thresholds. Since TPR \(= 1-\mathrm{FNR}\), varying FNR is directly linked to the vertical axis of sensitivity.
- Precision-recall curves: emphasize performance on the positive class and can be more informative when positives are rare. While FNR directly measures missed positives, precision-recall visualization helps interpret how missing detections interact with the reliability of positive predictions.
5 Interpretation and use cases
5.1 When FNR is the primary metric
FNR is especially relevant when the cost of missing a true positive is high. Examples (in general terms) include detection tasks where failing to flag an item leads to avoidable downstream failures, such as:
- safety checks that must not overlook hazardous cases,
- monitoring systems where undetected events have significant impact,
- screening pipelines designed to be sensitive before a more detailed follow-up.
5.2 Missed-positive consequences
FNR summarizes one side of the error distribution: it does not describe false alarms, but it quantifies the frequency of missed targets among those that truly require attention. In many operational settings, this is more aligned with risk than overall accuracy, because accuracy can remain high even when the system frequently overlooks positives.
5.3 Comparing models by FNR under constraints
Models may be compared by FNR while enforcing additional requirements, such as an upper bound on FPR or a minimum positive prediction throughput. This approach avoids selecting a model that achieves low FNR at the cost of an unacceptable number of false alarms.
A typical comparison framework might be:
- choose the lowest FNR among models whose FPR does not exceed a specified maximum,
- or choose the smallest FNR achievable at a fixed operational constraint (e.g., maximum alert rate).
5.4 Reporting practices and auditability
Good reporting typically includes:
- the evaluation dataset definition,
- the confusion-matrix counts or at least TP and FN,
- confidence intervals or uncertainty estimates,
- threshold specification (or an indication that the metric corresponds to a particular operating point).
Such practices make it easier to reproduce results and audit behavior across datasets and time periods.
6 Connections to related measures
6.1 Miss rate vs false negative rate terminology
“Miss rate” is a common plain-language synonym for false negative rate in detection contexts. Despite different naming, the underlying concept is the same: proportion of actual positives that are not detected.
6.2 FNR vs false discovery rate
FNR concerns false negatives relative to actual positives. False discovery rate (FDR) concerns the opposite direction: among predicted positives, the fraction that are actually negative. Because their denominators differ, FNR and FDR answer different questions:
- FNR: “How many true positives did we miss?”
- FDR: “When we predicted positive, how often were we wrong?”
6.3 FNR vs specificity
Specificity (also called true negative rate) measures the proportion of actual negatives correctly labeled as negative: \[ \mathrm{Specificity} = \frac{\mathrm{TN}}{\mathrm{TN}+\mathrm{FP}} \] Specificity is connected to false positive rate rather than to FNR. While all are derived from the confusion matrix, FNR and specificity focus on different ground-truth classes.
6.4 FNR vs balanced accuracy
Balanced accuracy averages performance across both classes. A common form for binary classification is: \[ \mathrm{Balanced\ Accuracy} = \frac{1}{2}\left(\mathrm{TPR} + \mathrm{TNR}\right) \] Since \( \mathrm{TPR} = 1-\mathrm{FNR}\), balanced accuracy incorporates FNR indirectly through sensitivity. This can be useful when classes are imbalanced, though it may still be less targeted than reporting FNR alone when missed positives are the dominant concern.
7 Practical considerations
7.1 Data quality and label noise effects
FNR depends on ground-truth labels. If labels contain noise—especially if positives are mislabeled as negatives or vice versa—the computed FNR can be biased. Additionally, inconsistent labeling criteria can create apparent changes in FNR that reflect annotation drift rather than genuine model performance shifts.
7.2 Sampling bias and covariate shift
Evaluation samples may not reflect the conditions under which the model will operate. If the distribution of features among positives changes (covariate shift conditional on the positive class), FNR estimated on historical data may not carry over. Sampling bias can also occur if the evaluation dataset underrepresents certain types of positives.
7.3 Temporal drift and monitoring FNR over time
In deployed systems, underlying patterns can change due to changes in data sources, behaviors, sensors, or processes. Monitoring FNR over time can detect degradation in the system’s ability to identify positive cases. Trend analysis is often paired with periodic recalibration or model retraining.
7.4 Fairness and subgroup performance checks (non-political framing)
Subgroup analysis can be used for quality assurance and reliability. Computing FNR per subgroup highlights whether missed detections are uneven across different cohorts under consistent evaluation rules. When subgroup-specific checks are performed, they are typically framed as measurement quality, safety, or performance equity rather than political or ideological claims.
8 Common pitfalls
8.1 Confusing FNR with false omission rate
The term “false omission rate” sometimes appears in statistical testing contexts, but it can be defined differently and is not interchangeable with FNR in machine learning or detection evaluation. Confusing these meanings can lead to reporting metrics that do not answer the intended question.
8.2 Mixing up “positive” class direction
In binary classification, the choice of which label is treated as “positive” is a convention. FNR relies on that convention: swapping class definitions changes which errors count as false negatives and thus changes the metric value.
8.3 Using accuracy when FNR matters
Accuracy can mask poor detection. For instance, if positives are rare, a model can achieve high accuracy by mostly predicting the negative class while exhibiting a high FNR. When the business or safety goal is to avoid missed positives, FNR (or sensitivity) is more directly aligned.
8.4 Overfitting due to threshold tuning
Selecting a threshold based on repeated testing on the same validation set can overfit the operational point. This may produce overly optimistic FNR estimates. Mitigation strategies include nested cross-validation, using a held-out test set for final reporting, and limiting the number of threshold comparisons.