Bell Statistics

What is alpha spending?

Alpha spending distributes an experiment's error budget across a fixed schedule of interim analyses, so each look uses a stricter threshold and the total false-positive rate stays at the level intended. It is what makes planned early stopping legitimate.

Also called
group sequential design, spending function, O'Brien-Fleming boundary, Pocock boundary, interim monitoring
Allon Korem

Written by Allon Korem

Chief Executive Officer

Last updated

In plain English

An experiment has a fixed budget of false-positive risk, conventionally 5%. A single test at the end spends all of it in one look. Alpha spending divides that budget across a planned schedule of interim analyses — perhaps four looks at 25%, 50%, 75% and 100% of the target sample — so each check uses a stricter threshold than 0.05 and the total across all of them still comes to 5%. Stopping early becomes legitimate because the arithmetic was arranged for it in advance.

The shape of the spending function is a genuine design choice. An O'Brien-Fleming boundary spends very little early and most at the end: the first look might require p below 0.0001, the last close to 0.045. That means early stopping happens only for dramatic effects, and the final analysis is barely penalised relative to a fixed test. A Pocock boundary spends evenly, using the same threshold at every look — around 0.016 for four looks — which makes stopping early much easier and costs noticeably more power at the end.

For most product experiments O'Brien-Fleming is the better default, and the reason is asymmetric. Stopping early is a bonus rather than the objective; what you cannot afford is a large power penalty on the final analysis, which is where the majority of experiments will actually be decided. Pocock earns its place when early stopping is genuinely valuable — when continuing is costly or ethically difficult, which is why it appears more often in clinical trials than in product work.

The schedule has to be set before the experiment starts, and this is where implementations most often go wrong. Adding an unplanned look, or shifting the timing of a planned one after seeing interim data, breaks the arithmetic the boundaries were computed from. Modern spending-function formulations are more forgiving about the exact timing than the original group-sequential tables, but the number of looks and the spending shape must still be committed in advance.

Compared with always-valid inference, this is the more efficient option for a small number of planned checkpoints and the more rigid one. Alpha spending gives you four or five looks with less sample premium; always-valid inference gives unlimited unplanned looks for 20 to 40% more data. The choice follows from how the organisation actually operates rather than from which is theoretically superior.

The formula

A spending function says how much of the budget has been used by each point. The boundaries follow from it.

The constraint
Σ α_k = α, across all planned looks

The total error budget is fixed. A spending function decides how it is distributed.

O'Brien-Fleming spending
α(t) = 2 − 2Φ( z_{α/2} / √t )

t is the fraction of planned sample. Very strict early, close to the fixed threshold at the end.

Pocock spending
α(t) = α · ln( 1 + (e − 1) t )

Roughly even across looks. Easier early stopping, more power lost at the final analysis.

Typical four-look boundaries
O'BF: 0.0001, 0.004, 0.019, 0.043 Pocock: 0.018 at every look

Both total 5% — see the sample size calculator for the fixed-horizon comparison.

Worked example

A team plans a test needing 200,000 users per arm and wants the option to stop early. They compare four-look O'Brien-Fleming and Pocock boundaries against a fixed-horizon design, simulating both a true 6% lift and no effect at all.

Fixed horizon
200,000/arm, one look at p < 0.05
O'BF boundaries
0.0001 / 0.004 / 0.019 / 0.043
Pocock boundaries
0.018 at each of four looks
Real effect: O'BF stops early
31% of runs, mean 148,000/arm
Real effect: Pocock stops early
58% of runs, mean 121,000/arm
Power at full horizon: fixed / O'BF / Pocock
80.0% / 79.2% / 74.6%

Pocock stops early far more often and gives up 5.4 points of power at the horizon. O'Brien-Fleming stops early half as often and costs almost nothing.

The last row is the decision. Pocock's higher early-stopping rate looks attractive until you notice what it costs on the experiments that do not stop — 74.6% power against 80%, which means one experiment in twenty that would have found a real effect now misses it. Since most experiments run to the horizon, that penalty applies to the majority while the benefit applies to the minority. O'Brien-Fleming inverts that: it stops early only when the effect is large enough to be obvious, and preserves essentially full power for everything else. For product experimentation, where continuing a test costs calendar time rather than anything serious, that is the right trade. Pocock makes sense when continuing is genuinely expensive or harmful — a clinical trial where patients are receiving an inferior treatment — which is a situation product teams rarely face.

Common misconceptions

Alpha spending lets you check the results whenever you want.
It permits a fixed number of pre-planned looks at boundaries computed for that schedule. Unlimited unplanned monitoring is what always-valid inference provides, at a higher sample cost. Adding an extra look to an alpha-spending design invalidates the boundaries it was built on.
Pocock boundaries are better because they make early stopping easier.
Easier early stopping is bought with power at the final analysis, where most experiments are actually decided. Pocock can cost five or more points of power at the horizon. It is the right choice when continuing is genuinely costly; for ordinary product tests O'Brien-Fleming preserves nearly all the power and still allows stopping on a dramatic result.
You can add an interim analysis if something unexpected comes up.
Not without recomputing the design, and not at all once you have seen the data that prompted the idea. The boundaries derive from the number and timing of looks, so an unplanned check spends error budget that was not allocated. If genuinely unplanned monitoring is needed, that is an argument for an always-valid design from the start.

Frequently asked questions

Should I use O'Brien-Fleming or Pocock boundaries?
O'Brien-Fleming for most product experiments. It spends almost nothing early, so it stops only for dramatic effects, and the final analysis retains nearly the power of a fixed-horizon test — which matters because most experiments reach the horizon. Pocock makes early stopping much easier and costs several points of power at the end; choose it when continuing an experiment is genuinely expensive or harmful.
How many interim analyses should I plan?
Three to five is the usual range. Each additional look consumes budget and increases the penalty at the final analysis, with diminishing returns in stopping opportunity — the difference between four looks and twelve is small in practice. Space them at meaningful fractions of the planned sample, such as 25%, 50% and 75%, rather than by calendar convenience.
What happens if we miss a planned interim analysis?
Modern spending-function formulations handle it: the function is defined over the information fraction, so a look that happens at 55% rather than 50% simply spends the amount allocated to that point. Skipping a look entirely is also fine, since unspent budget carries forward. What is not recoverable is adding an unplanned look, which spends budget that was never allocated.

Related terms

  • Always-valid inference

    Statistics that stay honest under continuous monitoring — you may stop whenever you like, and it costs about a third more traffic.

  • Family-wise error rate

    The chance of at least one false alarm across the whole set — 5% per test becomes 46% across twelve.

  • Peeking problem

    Look often enough and something crosses the line — checking daily for a fortnight turns 5% into roughly 25%.

  • Sequential testing

    How to look at a running test without breaking it — and what peeking costs when you do not.

Calculate it

  • A/B test sample size

    Size a two-proportion experiment before you launch, then read the lift and its interval once it lands.

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.