Bell Statistics

What is family-wise error rate?

The family-wise error rate is the probability of making at least one false positive across a whole set of tests. It rises quickly with the number of comparisons, which is why a per-test threshold of 5% does not mean a 5% chance of being wrong overall.

Notation
FWER
Also called
FWER, experiment-wise error rate, overall type I error
Allon Korem

Written by Allon Korem

Chief Executive Officer

Last updated

In plain English

A single test at the 5% level has a 5% chance of a false positive. Run twelve independent tests at that level and the chance that at least one comes back significant when nothing is happening is not 5% but 46%. The family-wise error rate is that overall figure — the probability of at least one false alarm across a set of tests — and the gap between it and the per-test rate is what makes multiple comparisons a problem rather than a technicality.

Controlling it means adjusting the per-test threshold so the overall rate lands where you intended. The Bonferroni correction is the simplest route: divide the target rate by the number of tests. Holm's step-down procedure controls the same quantity with uniformly more power and is essentially free to implement, so there is little reason to prefer plain Bonferroni once you know it exists.

The question that decides everything here is what counts as a family, and it is a judgement rather than a calculation. Every test the organisation runs this year is not a family in any useful sense — correcting at that scale would make nothing significant. The workable convention is the set of tests that bear on one decision: the metrics in one experiment's readout, or the arms of one multi-arm test. Draw it too wide and you lose all power; too narrow and the correction stops meaning anything.

FWER control is strict by design, and that strictness is appropriate when any single false positive is costly — a safety claim, a regulatory submission, or a change that would be expensive to reverse. It becomes counterproductive on an exploratory panel of twenty diagnostic metrics, where insisting on a 5% chance of any error at all leaves you unable to detect anything real.

That is where the false discovery rate comes in as the alternative. Instead of bounding the probability of any error, it bounds the expected proportion of your significant findings that are wrong — a weaker guarantee with substantially more power, and the better fit for screening. The choice between them is about consequences: FWER when one mistake matters, FDR when you are prioritising a list.

The formula

One expression governs the whole subject, and the numbers it produces are the argument for correcting at all.

The rate
FWER = P( at least one false positive )

Across the family of tests, under the assumption that all the nulls are true.

Independent tests
FWER = 1 − ( 1 − α )^m

m = 5 gives 23%; m = 12 gives 46%; m = 20 gives 64%. Correlated tests give somewhat less.

Bonferroni control
α_per test = α / m

Guarantees FWER ≤ α for any dependence structure. Conservative when tests are correlated.

Holm's step-down
compare p₍ᵢ₎ against α / ( m − i + 1 ), ascending, stop at the first failure

Same guarantee, uniformly more power — see the ANOVA calculator for the multi-arm case.

Worked example

An experiment reports one primary metric and eleven secondary metrics. The primary is flat. Two secondaries come back with p-values of 0.011 and 0.038. The team wants to know whether either is a finding, and applies three approaches to the same twelve p-values.

Tests in the family
12
Uncorrected FWER
1 − 0.95¹² = 46%
Smallest two p-values
0.011 and 0.038
Bonferroni threshold
0.05 / 12 = 0.0042 — neither survives
Holm: first threshold
0.05 / 12 = 0.0042 — stops immediately, neither survives
Benjamini-Hochberg at 5%
0.011 ≤ (1/12) × 0.05? No — neither survives

Neither result survives any correction, and finding two significant p-values among twelve is close to what chance predicts.

The 46% row is the one to sit with: before any data was collected, this readout had nearly a coin-flip chance of producing at least one significant secondary on a change that did nothing. Observing two is unremarkable. All three corrections agree here, which is worth noting because they often do not — Holm and Benjamini-Hochberg are usually more permissive than Bonferroni, and the fact that even the most powerful of them rejects both p-values says the evidence is genuinely thin. What should happen next is that the 0.011 result, if it is substantively interesting, becomes the pre-registered primary metric of a follow-up experiment. What should not happen is reporting it with its uncorrected p-value and a note that it was exploratory, which is how a 46% chance of noise becomes a line in a quarterly review.

Common misconceptions

If each test uses a 5% threshold, the overall error rate is 5%.
That is the per-test rate. Across twelve tests the chance of at least one false positive is 46%, and it climbs from there. The whole reason FWER has a name is that these two quantities differ by a large factor as soon as more than a couple of tests are involved.
You should correct across every test your team runs.
That would make almost nothing significant and is not what anyone means by a family. The workable definition is the set of tests bearing on a single decision — the metrics in one readout, or the arms of one experiment. Where exactly to draw it is a judgement, and drawing it explicitly before analysis is what stops it being drawn to suit the result.
Bonferroni is the standard way to control FWER.
It is the simplest and it is dominated by Holm's step-down procedure, which controls exactly the same quantity with uniformly more power and no additional assumptions. Bonferroni's real virtue is that it can be done in your head. If software is doing the arithmetic, Holm is strictly better.

Frequently asked questions

How do I decide what counts as a family of tests?
The set of tests that bear on one decision. For an experiment readout that is usually the metrics being used to decide whether to ship; for a multi-arm test it is the comparisons against control. Guardrail metrics are conventionally treated as a separate family with their own thresholds, since they answer a different question. Decide the boundary before analysis, because deciding it afterwards is another degree of freedom to exploit.
When should I control FWER rather than the false discovery rate?
When any single false positive is costly — a safety or compliance claim, or a change that would be expensive and embarrassing to reverse. FDR is the better choice for screening and exploratory panels, where you are prioritising a list and can tolerate a known proportion of the flagged items being wrong. The question is what one mistake costs relative to missing real effects.
Does correlation between the tests change the calculation?
Yes — correlated tests produce a lower family-wise error rate than the independent formula suggests, because they tend to be significant together. Bonferroni and Holm remain valid under any dependence structure and become conservative when correlation is high, so they cost power you did not need to give up. Permutation-based corrections exploit the observed correlation directly and are worth the effort when the tests are strongly related.

Related terms

  • Alpha spending

    Divide the 5% across your planned looks — strict early, lenient at the end, and the schedule is fixed before you start.

  • Bonferroni correction

    Divide alpha by the number of tests — bulletproof, arithmetic you can do in your head, and strictly beaten by Holm.

  • False discovery rate

    Bound the share of your wins that are wrong rather than the chance of any error — the right trade on twenty metrics.

  • Multiple comparisons

    Test enough things and something will look significant — the arithmetic, and the four fixes.

Calculate it

  • One-way ANOVA

    Three or more independent groups on one continuous outcome — size it, then run the F test.

  • Chi-square test

    Test a contingency table of counts for association — any number of rows and columns.

Knowing the term is the easy part

Applying it to a live measurement problem is the part that goes wrong. If you are designing an experiment, reading a result you do not trust, or trying to work out what your marketing actually caused, that is the work we do.

References