What Balance Summaries Can Tell You
Minimization and covariate-adjusted response-adaptive allocation use information about patient profiles to guide assignment. After allocation, a natural question is whether the treatment groups look similar on the baseline covariates that informed the design. Summaries can answer that descriptive question: they show the observed differences in covariate means, proportions, distributions, or profile counts between arms.
They do not show whether one treatment works better, whether the allocation algorithm was valid, or whether the groups would have been identical under another assignment sequence. In particular, a balance summary is not outcome evidence. Treatment outcomes must not be used to turn a description of baseline covariates into a claim about treatment benefit.
A useful assessment begins with a defined set of baseline covariates, consistent coding across arms, and a clear denominator for every summary. Covariates should be measured before treatment assignment and chosen for clinical or design reasons, rather than selected after looking for differences. Report missing values as well as observed values, and make clear whether each summary uses all assigned participants or only those with that covariate recorded. Changing the analysis set from one covariate to another can make comparisons misleading.
Standardized Differences
A raw difference is easy to understand in the covariate's original units, but its size depends on those units. A difference of 2 years in age cannot be directly compared with a difference of 2 points on a laboratory scale. A standardized difference expresses the difference relative to a standard deviation, making it possible to compare the scale of imbalances across covariates. It is still descriptive, not a test statistic.
For a continuous baseline covariate \(X\) in two arms, let \(\bar{x}_A\) and \(\bar{x}_B\) be the arm-specific sample means and \(s_A\) and \(s_B\) the sample standard deviations. A common standardized difference is the mean difference divided by the root-mean-square of the two standard deviations:
The sign gives the direction of the difference under the stated arm order; the absolute value gives its size in standard deviation units. Always show or state which arm is subtracted from which. This version uses the observed spread within each arm and does not require the population variances to be equal. If a covariate is extremely skewed or has important outliers, a mean and standard deviation alone may not adequately describe its distribution, so inspect distribution summaries as well.
For a binary covariate, let \(\hat{p}_A\) and \(\hat{p}_B\) be the proportions with the specified characteristic in the two arms. One common standardization uses the average of the two Bernoulli variances:
The denominator is a scale for the binary variable, not the standard error of the difference in proportions. Therefore, this statistic is not a z-statistic and should not be compared with a significance-test cutoff. Other conventions for standardizing binary variables exist; a report should state which one it uses and apply it consistently.
Worked Example: Standardizing a Continuous-Covariate Difference
In a hypothetical two-arm trial, baseline symptom scores are recorded before assignment. Arm A has \(n_A=40\), mean score \(\bar{x}_A=18.6\), and standard deviation \(s_A=0.40\). Arm B has \(n_B=40\), mean score \(\bar{x}_B=18.5\), and standard deviation \(s_B=\sqrt{0.21}\), approximately 0.4583 points. Calculate the standardized difference, taking A minus B.
The observed mean difference is \(18.6-18.5=0.10\) points. The standardizing denominator is:
Thus,
Arm A's mean is 0.10 score points higher, a difference of about 0.2325 standard deviation units under the stated convention. This describes the observed baseline difference; it does not imply a treatment effect or show that the groups are statistically different.
Binary and Multi-Category Covariates
For binary covariates, report the arm-specific counts and proportions alongside the standardized difference. That makes the direction and practical meaning visible and lets a reader check denominators. For a multi-category covariate, such as disease stage, a single mean is generally inappropriate. Show the counts and proportions for every category in each arm, and compare the category proportions one by one. Those differences are constrained: if categories exhaust all possibilities, their signed proportion differences sum to zero. A small difference in one category can therefore be offset by differences elsewhere.
The category-specific standardized differences can use the binary formula, treating each category as an indicator. These values help compare the scale of differences, but they are not independent: membership in one category rules out membership in the others. Do not interpret a collection of such values as separate tests.
Worked Example: Comparing a Binary Covariate
Suppose a hypothetical trial has 50 participants in each arm. At baseline, 20 participants in A and 25 in B have a specified risk factor. The proportions are \(\hat{p}_A=20/50=0.40\) and \(\hat{p}_B=25/50=0.50\). Taking A minus B, the raw difference is \(-0.10\), or 10 percentage points fewer in A.
Using the stated binary standardization, the denominator is:
The standardized difference is:
The risk factor was less common in A by 10 percentage points, corresponding to about 0.2020 of this binary variable's standard deviation. The underlying counts matter: a proportion of 0.40 could arise from 20 of 50 or 4 of 10, and those settings have different amounts of information. The standardized difference itself is not a measure of uncertainty.
Look Beyond One Number: Distributions and Profiles
Mean differences can miss distributional features. Two arms can have the same mean but different spreads, skewness, or tails. For continuous covariates, include useful summaries of spread, such as standard deviations or quantiles, and inspect a plot or other distributional summary when the shape matters. For categorical covariates, show the full category distribution rather than only an overall average or a selected category. These checks are especially relevant when the allocation procedure targeted only particular covariates or summaries.
A patient profile is a combination of covariate levels, such as stage II disease and age 65 years or older. Profile counts can show whether the groups contain similar numbers of participants in clinically meaningful combinations. They also reveal sparse or empty combinations that marginal summaries hide. However, a large number of possible combinations can produce many tiny cells. Profile tables should therefore focus on prespecified, interpretable combinations and include denominators; they should not be read as evidence about outcomes within those profiles.
Worked Example: Marginal Balance Can Hide Profile Imbalance
Consider a hypothetical study with 40 participants per arm and two binary baseline covariates: younger versus older age, and lower versus higher disease stage. Each arm has 20 younger and 20 older participants, and 20 lower-stage and 20 higher-stage participants. The marginal distributions match exactly. The joint profile counts, however, are:
| Baseline profile | Arm A | Arm B |
|---|---|---|
| Younger, lower stage | 16 | 4 |
| Younger, higher stage | 4 | 16 |
| Older, lower stage | 4 | 16 |
| Older, higher stage | 16 | 4 |
For example, A has \(16+4=20\) younger participants and B has \(4+16=20\); both arms also have 20 lower-stage participants. Yet the younger/lower-stage profile makes up \(16/40=0.40\) of A and \(4/40=0.10\) of B, a 30-percentage-point difference. The same contrast appears in the older/higher-stage profile, in the opposite direction.
This table demonstrates why marginal balance does not guarantee balance in combinations. It does not establish that the allocation procedure failed: the observed profile counts must be interpreted in light of the design and its random assignments. It does show that marginal summaries alone do not describe every feature of the observed covariate composition.
A Practical Assessment
A sound report makes the descriptive comparison reproducible and limits its claims to what was measured. A compact workflow is:
List the baseline covariates and meaningful profiles before comparing arms. State how missing or unavailable measurements are displayed.
Give counts and denominators for categorical variables, and means and spread summaries for continuous variables. Add distribution information when a mean and standard deviation could be incomplete.
Use a declared formula, preserve the arm order for signed values, and report raw differences in their original units as well.
Review important joint covariate patterns, then describe observed similarities and differences without claiming outcome benefit, equivalence, or proof of successful randomization.
A standardized difference near zero means that the particular summary being standardized is close between arms. It does not certify balance on every feature of a covariate distribution, every covariate combination, or unmeasured characteristics. Rules of thumb such as treating an absolute standardized difference below 0.10 as “small” are conventions, not universal thresholds. Their relevance depends on the covariate, design, and scientific context; a value above a rule-of-thumb threshold is a prompt to describe and consider the difference, not a significance result.
Why Balance Tests Are Not the Main Diagnostic
A common alternative is to compute a p-value for each baseline comparison. Such a p-value depends strongly on sample size: a small observed difference can produce a small p-value in a very large trial, while a potentially consequential difference can produce a large p-value in a small one. Repeating tests across many covariates also creates a collection of results that is difficult to summarize. A non-significant p-value does not establish equivalence or prove balance.
For this purpose, descriptive summaries are generally more informative: raw differences express the size in context, standardized differences put different measurement scales on a common scale, and distribution or profile summaries show features a single number omits. These approaches complement one another rather than compete. A standardized difference cannot replace a distributional check, and a profile table cannot replace clear marginal summaries.
This distinction is especially important after adaptive allocation. The algorithm may deliberately respond to observed covariate profiles, but its assignments remain subject to the randomization mechanism. The resulting balance is a property of the particular realized allocation, not a deterministic guarantee. Thus, neither an imperfect balance table by itself nor an apparently excellent one proves that an algorithm was correctly implemented. Implementation records and allocation probabilities address different questions from descriptive balance summaries.
Common Mistakes and Limits
- Treating a standardized difference as a test statistic. It is a descriptive difference divided by a scale, not a standard error or p-value. Do not use it to claim statistical significance.
- Calling a small value proof of equivalence. A small value applies to the measured summary and observed sample. It does not establish equivalence on all covariates or unmeasured factors.
- Reporting only means. Equal means can conceal different spreads, tails, or profile compositions. Pair mean comparisons with appropriate distribution summaries.
- Reporting only marginal balance. Matching totals for individual covariates can conceal differing joint profiles, as the example shows.
- Ignoring denominators or missingness. A percentage without its denominator is hard to interpret, and different missing-data patterns can make arm summaries incomparable.
- Using balance as outcome evidence. Baseline summaries describe covariate composition. They do not show treatment efficacy, safety, or a causal effect.
Balance assessments also have finite-sample limits: chance differences can remain even when allocation is properly randomized, and small samples can make profile counts unstable or sparse. They describe observed covariates, not every possible source of prognostic variation. The appropriate conclusion is therefore specific and restrained: state which summaries were close, which differed, and what dimensions the assessment did not capture.
Check Your Understanding
Answer each question, then compare with the solutions below.
- In a continuous-covariate standardized difference, what does the sign indicate, and what does the absolute value indicate?
- Two arms have proportions 0.20 and 0.30 for a binary covariate. Using the binary formula in this tutorial, calculate the standardized difference taking the first arm minus the second.
- Why can equal marginal counts for two covariates fail to show whether their joint profiles are similarly represented?
- Does a standardized difference below 0.10 prove that the arms are equivalent on that covariate? Explain.
- Why should a balance table not be used as evidence that one treatment is more effective?
Solutions. (1) The sign shows the direction under the stated arm order; the absolute value gives the size in standard deviation units. (2) The denominator is \(\sqrt{\{0.20(0.80)+0.30(0.70)\}/2}=\sqrt{0.185}\approx0.4301\). The difference is \(0.20-0.30=-0.10\), so \(d_X=-0.10/0.4301\approx-0.2325\). (3) Marginal counts summarize each covariate separately and omit how their levels occur together; joint profile counts can differ even when each marginal distribution matches. (4) No. It is a descriptive rule of thumb for one standardized summary, not proof of equivalence or balance on all distributional features. (5) A balance table summarizes baseline covariates, not treatment outcomes; it cannot establish a treatment effect.