VIEW THIS AS

Auto mode follows the Route Engine until you choose a viewpoint.

YOU ARE HERE

ROUTE CHECK

CONNECTED TO

WHAT NEXT

Use the canonical route for this room, or HELP if you are unsure.

Why Mathematics? | Variance Inflation Factors, Multicollinearity and Coefficient Stability

Why is mathematics important when predictors overlap so strongly that regression coefficients become unstable? The variance inflation factor measures how much the variance of one coefficient is enlarged by linear relationships among the predictors.

VIF does not judge whether a predictor is valuable. It diagnoses whether the model can separate its contribution from the contributions of other columns in the design matrix.

Did you know? A VIF of 5 means coefficient variance is five times the orthogonal-design benchmark, while its standard error is multiplied by sqrt(5), about 2.236.

Full chapter index

Chapters 1–4 · Understand the question
  1. The separability question
  2. The NIST definition
  3. A worked example
  4. Variance versus standard error
Chapters 5–9 · Reproduce the example
  1. Minimum value
  2. Why pairwise correlation is insufficient
  3. No universal cutoff
  4. Coefficient instability
  5. Causal interpretation
Chapters 10–15 · Check assumptions
  1. Designed experiments
  2. Polynomial and interaction terms
  3. Dummy variables
  4. Perfect collinearity
  5. Prediction versus explanation
  6. Possible responses
Chapters 16–20 · Explore applications
  1. Condition indices
  2. Spreadsheet workflow
  3. Coding workflow
  4. Applications and careers
  5. Connection to recent mathematics articles
Chapters 21–24 · Study and verify
  1. Guidance for students and parents
  2. Practice questions
  3. Frequently asked questions
  4. Useful next reading

CHAPTER 1 OF 24 · Understand the question

1. The separability question

Back to contents

Multiple regression tries to estimate one predictor’s partial effect while holding others fixed. When predictors carry nearly the same information, many coefficient combinations fit similarly and individual estimates become unstable.

Contents · Next chapter

CHAPTER 2 OF 24 · Understand the question

2. The NIST definition

Back to contents

NIST defines VIF_j=1/(1−R_j²), where R_j² comes from regressing predictor j on the remaining predictors. Read the NIST variance-inflation reference.

Contents · Previous chapter · Next chapter

CHAPTER 3 OF 24 · Understand the question

3. A worked example

Back to contents

If the remaining predictors explain 80% of predictor j, R_j²=0.80. Then VIF=1/(1−0.80)=5. Tolerance is the reciprocal, 0.20.

R squaredToleranceVIF
0.80.25
Auxiliary regression.

Contents · Previous chapter · Next chapter

CHAPTER 4 OF 24 · Understand the question

4. Variance versus standard error

Back to contents

VIF multiplies coefficient variance. The standard error multiplier is sqrt(VIF). For VIF=5, the standard error is about 2.236 times the benchmark with no linear dependence.

Variance multiplierSE multiplier
5sqrt(5) = 2.236
Coefficient uncertainty.

Contents · Previous chapter · Next chapter

CHAPTER 5 OF 24 · Reproduce the example

5. Minimum value

Back to contents

When R_j²=0, VIF=1. That is the minimum. Values cannot be below one under the ordinary definition.

Contents · Previous chapter · Next chapter

CHAPTER 6 OF 24 · Reproduce the example

6. Why pairwise correlation is insufficient

Back to contents

A predictor can be approximated by a combination of several others even when no pairwise correlation looks extreme. NIST notes that VIF can reveal higher-order collinearity.

Contents · Previous chapter · Next chapter

CHAPTER 7 OF 24 · Reproduce the example

7. No universal cutoff

Back to contents

Rules such as 5 or 10 are screening conventions. Required precision, sample size, model purpose and predictor meaning determine whether inflation is consequential.

Contents · Previous chapter · Next chapter

CHAPTER 8 OF 24 · Reproduce the example

8. Coefficient instability

Back to contents

Collinearity can make small data changes produce large coefficient changes, including sign reversals. Predictions inside the observed region may remain stable even while interpretation of individual coefficients is weak.

Contents · Previous chapter · Next chapter

CHAPTER 9 OF 24 · Reproduce the example

9. Causal interpretation

Back to contents

VIF does not identify confounding or prove causation. A low VIF cannot repair omitted variables, selection bias or measurement error.

Contents · Previous chapter · Next chapter

CHAPTER 10 OF 24 · Check assumptions

10. Designed experiments

Back to contents

Balanced orthogonal designs can keep VIF near one. Experimental design uses mathematics before data collection to separate effects efficiently.

Contents · Previous chapter · Next chapter

CHAPTER 11 OF 24 · Check assumptions

11. Polynomial and interaction terms

Back to contents

Raw powers and interactions can create collinearity. Centring predictors may improve interpretability and numerical conditioning without changing fitted predictions when the model is transformed consistently.

Contents · Previous chapter · Next chapter

CHAPTER 12 OF 24 · Check assumptions

12. Dummy variables

Back to contents

Including every category indicator with an intercept creates exact dependence. Use a reference level or another full-rank coding scheme.

Contents · Previous chapter · Next chapter

CHAPTER 13 OF 24 · Check assumptions

13. Perfect collinearity

Back to contents

If R_j²=1, the denominator is zero and VIF is infinite. The design matrix is rank-deficient, so unique ordinary least-squares coefficients do not exist.

Contents · Previous chapter · Next chapter

CHAPTER 14 OF 24 · Check assumptions

14. Prediction versus explanation

Back to contents

A model built mainly for prediction may tolerate correlated features with regularisation and validation. A model used to explain individual coefficients needs stronger separability and domain reasoning.

Contents · Previous chapter · Next chapter

CHAPTER 15 OF 24 · Check assumptions

15. Possible responses

Back to contents

Options include collecting more informative data, redesigning measurements, combining variables, using principal components, applying regularisation or choosing a defensible subset. Deletion is not automatic.

Contents · Previous chapter · Next chapter

CHAPTER 16 OF 24 · Explore applications

16. Condition indices

Back to contents

NIST lists condition indices as another multicollinearity diagnostic. They examine the design matrix more globally and complement variable-specific VIFs.

Contents · Previous chapter · Next chapter

CHAPTER 17 OF 24 · Explore applications

17. Spreadsheet workflow

Back to contents

For each predictor, regress it on all remaining predictors, record R², calculate 1/(1−R²) and its reciprocal tolerance. Confirm the same rows and transformations are used.

Contents · Previous chapter · Next chapter

CHAPTER 18 OF 24 · Explore applications

18. Coding workflow

Back to contents

Use a tested design-matrix routine, check rank and intercept handling, and calculate VIF after encoding categories and transformations exactly as fitted.

Contents · Previous chapter · Next chapter

CHAPTER 19 OF 24 · Explore applications

19. Applications and careers

Back to contents

VIF appears in economics, engineering, social science, environmental modelling and machine learning. It helps analysts separate stable prediction from fragile coefficient stories.

Contents · Previous chapter · Next chapter

CHAPTER 20 OF 24 · Explore applications

20. Connection to recent mathematics articles

Back to contents

The weighted-variance guide develops variance reasoning. The confidence-interval guide shows how larger standard errors widen uncertainty.

Contents · Previous chapter · Next chapter

CHAPTER 21 OF 24 · Study and verify

21. Guidance for students and parents

Back to contents

Students should explain the auxiliary R² before quoting VIF. Parents can ask whether the goal is prediction, explanation or causal inference because the remedy depends on purpose.

Contents · Previous chapter · Next chapter

CHAPTER 22 OF 24 · Study and verify

22. Practice questions

Back to contents

  • Calculate VIF for R²=0,0.5,0.9.
  • Convert each VIF to a standard-error multiplier.
  • Explain why low pairwise correlations do not guarantee low VIF.

Contents · Previous chapter · Next chapter

CHAPTER 23 OF 24 · Study and verify

23. Frequently asked questions

Back to contents

### Is VIF a percentage? No. It is a variance multiplier.

### Does high VIF make predictions useless? Not necessarily; coefficient interpretation can be fragile while predictions remain adequate.

### Should I delete the highest-VIF variable? Only after considering purpose, theory and alternatives.

Contents · Previous chapter · Next chapter

CHAPTER 24 OF 24 · Study and verify

24. Useful next reading

Back to contents

Use the Mathematics Learning Hub and compare VIF, tolerance, condition indices and coefficient changes under resampling.

Contents · Previous chapter · Mathematics Learning Hub

Extended practice laboratory

Practice case 1: Choose target predictor

Setup: Use the article’s variance-inflation-factor example and change one declared input for case 1. Task: Recalculate from raw values, preserve units and state which mathematical or design condition changed.

Check: Check the relevant invariant, separate the number from its claim, and name the next diagnostic or source of evidence. Rebuild the relevant counts before interpreting the coefficient, preserve the stated design, and write one sentence separating the numerical result from the claim it can support. Then vary one defensible assumption, calculate again, and explain whether the conclusion changes because of new data, a new reference model, or a new decision purpose. Finish by naming the unit, tolerance, and evidence needed for transfer. Record one graph or table that would expose failure hidden by the summary.

Practice case 2: Regress it on remaining predictors

Setup: Use the article’s variance-inflation-factor example and change one declared input for case 2. Task: Recalculate from raw values, preserve units and state which mathematical or design condition changed.

Check: Check the relevant invariant, separate the number from its claim, and name the next diagnostic or source of evidence. Rebuild the relevant counts before interpreting the coefficient, preserve the stated design, and write one sentence separating the numerical result from the claim it can support. Then vary one defensible assumption, calculate again, and explain whether the conclusion changes because of new data, a new reference model, or a new decision purpose. Finish by naming the unit, tolerance, and evidence needed for transfer. Record one graph or table that would expose failure hidden by the summary.

Practice case 3: Record auxiliary R squared

Setup: Use the article’s variance-inflation-factor example and change one declared input for case 3. Task: Recalculate from raw values, preserve units and state which mathematical or design condition changed.

Check: Check the relevant invariant, separate the number from its claim, and name the next diagnostic or source of evidence. Rebuild the relevant counts before interpreting the coefficient, preserve the stated design, and write one sentence separating the numerical result from the claim it can support. Then vary one defensible assumption, calculate again, and explain whether the conclusion changes because of new data, a new reference model, or a new decision purpose. Finish by naming the unit, tolerance, and evidence needed for transfer. Record one graph or table that would expose failure hidden by the summary.

Practice case 4: Compute one minus R squared

Setup: Use the article’s variance-inflation-factor example and change one declared input for case 4. Task: Recalculate from raw values, preserve units and state which mathematical or design condition changed.

Check: Check the relevant invariant, separate the number from its claim, and name the next diagnostic or source of evidence. Rebuild the relevant counts before interpreting the coefficient, preserve the stated design, and write one sentence separating the numerical result from the claim it can support. Then vary one defensible assumption, calculate again, and explain whether the conclusion changes because of new data, a new reference model, or a new decision purpose. Finish by naming the unit, tolerance, and evidence needed for transfer. Record one graph or table that would expose failure hidden by the summary.

Practice case 5: Take reciprocal

Setup: Use the article’s variance-inflation-factor example and change one declared input for case 5. Task: Recalculate from raw values, preserve units and state which mathematical or design condition changed.

Check: Check the relevant invariant, separate the number from its claim, and name the next diagnostic or source of evidence. Rebuild the relevant counts before interpreting the coefficient, preserve the stated design, and write one sentence separating the numerical result from the claim it can support. Then vary one defensible assumption, calculate again, and explain whether the conclusion changes because of new data, a new reference model, or a new decision purpose. Finish by naming the unit, tolerance, and evidence needed for transfer. Record one graph or table that would expose failure hidden by the summary.

Practice case 6: Compute tolerance

Setup: Use the article’s variance-inflation-factor example and change one declared input for case 6. Task: Recalculate from raw values, preserve units and state which mathematical or design condition changed.

Check: Check the relevant invariant, separate the number from its claim, and name the next diagnostic or source of evidence. Rebuild the relevant counts before interpreting the coefficient, preserve the stated design, and write one sentence separating the numerical result from the claim it can support. Then vary one defensible assumption, calculate again, and explain whether the conclusion changes because of new data, a new reference model, or a new decision purpose. Finish by naming the unit, tolerance, and evidence needed for transfer. Record one graph or table that would expose failure hidden by the summary.

Practice case 7: Compute square-root multiplier

Setup: Use the article’s variance-inflation-factor example and change one declared input for case 7. Task: Recalculate from raw values, preserve units and state which mathematical or design condition changed.

Check: Check the relevant invariant, separate the number from its claim, and name the next diagnostic or source of evidence. Rebuild the relevant counts before interpreting the coefficient, preserve the stated design, and write one sentence separating the numerical result from the claim it can support. Then vary one defensible assumption, calculate again, and explain whether the conclusion changes because of new data, a new reference model, or a new decision purpose. Finish by naming the unit, tolerance, and evidence needed for transfer. Record one graph or table that would expose failure hidden by the summary.

Practice case 8: Try R squared zero

Setup: Use the article’s variance-inflation-factor example and change one declared input for case 8. Task: Recalculate from raw values, preserve units and state which mathematical or design condition changed.

Check: Check the relevant invariant, separate the number from its claim, and name the next diagnostic or source of evidence. Rebuild the relevant counts before interpreting the coefficient, preserve the stated design, and write one sentence separating the numerical result from the claim it can support. Then vary one defensible assumption, calculate again, and explain whether the conclusion changes because of new data, a new reference model, or a new decision purpose. Finish by naming the unit, tolerance, and evidence needed for transfer. Record one graph or table that would expose failure hidden by the summary.

Practice case 9: Try R squared one half

Setup: Use the article’s variance-inflation-factor example and change one declared input for case 9. Task: Recalculate from raw values, preserve units and state which mathematical or design condition changed.

Check: Check the relevant invariant, separate the number from its claim, and name the next diagnostic or source of evidence. Rebuild the relevant counts before interpreting the coefficient, preserve the stated design, and write one sentence separating the numerical result from the claim it can support. Then vary one defensible assumption, calculate again, and explain whether the conclusion changes because of new data, a new reference model, or a new decision purpose. Finish by naming the unit, tolerance, and evidence needed for transfer. Record one graph or table that would expose failure hidden by the summary.

Practice case 10: Try R squared nine tenths

Setup: Use the article’s variance-inflation-factor example and change one declared input for case 10. Task: Recalculate from raw values, preserve units and state which mathematical or design condition changed.

Check: Check the relevant invariant, separate the number from its claim, and name the next diagnostic or source of evidence. Rebuild the relevant counts before interpreting the coefficient, preserve the stated design, and write one sentence separating the numerical result from the claim it can support. Then vary one defensible assumption, calculate again, and explain whether the conclusion changes because of new data, a new reference model, or a new decision purpose. Finish by naming the unit, tolerance, and evidence needed for transfer. Record one graph or table that would expose failure hidden by the summary.

Practice case 11: Inspect pairwise correlations

Setup: Use the article’s variance-inflation-factor example and change one declared input for case 11. Task: Recalculate from raw values, preserve units and state which mathematical or design condition changed.

Check: Check the relevant invariant, separate the number from its claim, and name the next diagnostic or source of evidence. Rebuild the relevant counts before interpreting the coefficient, preserve the stated design, and write one sentence separating the numerical result from the claim it can support. Then vary one defensible assumption, calculate again, and explain whether the conclusion changes because of new data, a new reference model, or a new decision purpose. Finish by naming the unit, tolerance, and evidence needed for transfer. Record one graph or table that would expose failure hidden by the summary.

Practice case 12: Inspect higher-order dependence

Setup: Use the article’s variance-inflation-factor example and change one declared input for case 12. Task: Recalculate from raw values, preserve units and state which mathematical or design condition changed.

Check: Check the relevant invariant, separate the number from its claim, and name the next diagnostic or source of evidence. Rebuild the relevant counts before interpreting the coefficient, preserve the stated design, and write one sentence separating the numerical result from the claim it can support. Then vary one defensible assumption, calculate again, and explain whether the conclusion changes because of new data, a new reference model, or a new decision purpose. Finish by naming the unit, tolerance, and evidence needed for transfer. Record one graph or table that would expose failure hidden by the summary.

Practice case 13: Check design-matrix rank

Setup: Use the article’s variance-inflation-factor example and change one declared input for case 13. Task: Recalculate from raw values, preserve units and state which mathematical or design condition changed.

Check: Check the relevant invariant, separate the number from its claim, and name the next diagnostic or source of evidence. Rebuild the relevant counts before interpreting the coefficient, preserve the stated design, and write one sentence separating the numerical result from the claim it can support. Then vary one defensible assumption, calculate again, and explain whether the conclusion changes because of new data, a new reference model, or a new decision purpose. Finish by naming the unit, tolerance, and evidence needed for transfer. Record one graph or table that would expose failure hidden by the summary.

Practice case 14: Remove duplicate encoding

Setup: Use the article’s variance-inflation-factor example and change one declared input for case 14. Task: Recalculate from raw values, preserve units and state which mathematical or design condition changed.

Check: Check the relevant invariant, separate the number from its claim, and name the next diagnostic or source of evidence. Rebuild the relevant counts before interpreting the coefficient, preserve the stated design, and write one sentence separating the numerical result from the claim it can support. Then vary one defensible assumption, calculate again, and explain whether the conclusion changes because of new data, a new reference model, or a new decision purpose. Finish by naming the unit, tolerance, and evidence needed for transfer. Record one graph or table that would expose failure hidden by the summary.

Practice case 15: Use reference category

Setup: Use the article’s variance-inflation-factor example and change one declared input for case 15. Task: Recalculate from raw values, preserve units and state which mathematical or design condition changed.

Check: Check the relevant invariant, separate the number from its claim, and name the next diagnostic or source of evidence. Rebuild the relevant counts before interpreting the coefficient, preserve the stated design, and write one sentence separating the numerical result from the claim it can support. Then vary one defensible assumption, calculate again, and explain whether the conclusion changes because of new data, a new reference model, or a new decision purpose. Finish by naming the unit, tolerance, and evidence needed for transfer. Record one graph or table that would expose failure hidden by the summary.

Practice case 16: Centre polynomial terms

Setup: Use the article’s variance-inflation-factor example and change one declared input for case 16. Task: Recalculate from raw values, preserve units and state which mathematical or design condition changed.

Check: Check the relevant invariant, separate the number from its claim, and name the next diagnostic or source of evidence. Rebuild the relevant counts before interpreting the coefficient, preserve the stated design, and write one sentence separating the numerical result from the claim it can support. Then vary one defensible assumption, calculate again, and explain whether the conclusion changes because of new data, a new reference model, or a new decision purpose. Finish by naming the unit, tolerance, and evidence needed for transfer. Record one graph or table that would expose failure hidden by the summary.

Practice case 17: Inspect interactions

Setup: Use the article’s variance-inflation-factor example and change one declared input for case 17. Task: Recalculate from raw values, preserve units and state which mathematical or design condition changed.

Check: Check the relevant invariant, separate the number from its claim, and name the next diagnostic or source of evidence. Rebuild the relevant counts before interpreting the coefficient, preserve the stated design, and write one sentence separating the numerical result from the claim it can support. Then vary one defensible assumption, calculate again, and explain whether the conclusion changes because of new data, a new reference model, or a new decision purpose. Finish by naming the unit, tolerance, and evidence needed for transfer. Record one graph or table that would expose failure hidden by the summary.

Practice case 18: Compare condition indices

Setup: Use the article’s variance-inflation-factor example and change one declared input for case 18. Task: Recalculate from raw values, preserve units and state which mathematical or design condition changed.

Check: Check the relevant invariant, separate the number from its claim, and name the next diagnostic or source of evidence. Rebuild the relevant counts before interpreting the coefficient, preserve the stated design, and write one sentence separating the numerical result from the claim it can support. Then vary one defensible assumption, calculate again, and explain whether the conclusion changes because of new data, a new reference model, or a new decision purpose. Finish by naming the unit, tolerance, and evidence needed for transfer. Record one graph or table that would expose failure hidden by the summary.

Practice case 19: Assess prediction goal

Setup: Use the article’s variance-inflation-factor example and change one declared input for case 19. Task: Recalculate from raw values, preserve units and state which mathematical or design condition changed.

Check: Check the relevant invariant, separate the number from its claim, and name the next diagnostic or source of evidence. Rebuild the relevant counts before interpreting the coefficient, preserve the stated design, and write one sentence separating the numerical result from the claim it can support. Then vary one defensible assumption, calculate again, and explain whether the conclusion changes because of new data, a new reference model, or a new decision purpose. Finish by naming the unit, tolerance, and evidence needed for transfer. Record one graph or table that would expose failure hidden by the summary.

Practice case 20: Assess explanation goal

Setup: Use the article’s variance-inflation-factor example and change one declared input for case 20. Task: Recalculate from raw values, preserve units and state which mathematical or design condition changed.

Check: Check the relevant invariant, separate the number from its claim, and name the next diagnostic or source of evidence. Rebuild the relevant counts before interpreting the coefficient, preserve the stated design, and write one sentence separating the numerical result from the claim it can support. Then vary one defensible assumption, calculate again, and explain whether the conclusion changes because of new data, a new reference model, or a new decision purpose. Finish by naming the unit, tolerance, and evidence needed for transfer. Record one graph or table that would expose failure hidden by the summary.

Practice case 21: Consider regularisation

Setup: Use the article’s variance-inflation-factor example and change one declared input for case 21. Task: Recalculate from raw values, preserve units and state which mathematical or design condition changed.

Check: Check the relevant invariant, separate the number from its claim, and name the next diagnostic or source of evidence. Rebuild the relevant counts before interpreting the coefficient, preserve the stated design, and write one sentence separating the numerical result from the claim it can support. Then vary one defensible assumption, calculate again, and explain whether the conclusion changes because of new data, a new reference model, or a new decision purpose. Finish by naming the unit, tolerance, and evidence needed for transfer. Record one graph or table that would expose failure hidden by the summary.

Practice case 22: Collect new data

Setup: Use the article’s variance-inflation-factor example and change one declared input for case 22. Task: Recalculate from raw values, preserve units and state which mathematical or design condition changed.

Check: Check the relevant invariant, separate the number from its claim, and name the next diagnostic or source of evidence. Rebuild the relevant counts before interpreting the coefficient, preserve the stated design, and write one sentence separating the numerical result from the claim it can support. Then vary one defensible assumption, calculate again, and explain whether the conclusion changes because of new data, a new reference model, or a new decision purpose. Finish by naming the unit, tolerance, and evidence needed for transfer. Record one graph or table that would expose failure hidden by the summary.

Practice case 23: Avoid automatic variable deletion

Setup: Use the article’s variance-inflation-factor example and change one declared input for case 23. Task: Recalculate from raw values, preserve units and state which mathematical or design condition changed.

Check: Check the relevant invariant, separate the number from its claim, and name the next diagnostic or source of evidence. Rebuild the relevant counts before interpreting the coefficient, preserve the stated design, and write one sentence separating the numerical result from the claim it can support. Then vary one defensible assumption, calculate again, and explain whether the conclusion changes because of new data, a new reference model, or a new decision purpose. Finish by naming the unit, tolerance, and evidence needed for transfer. Record one graph or table that would expose failure hidden by the summary.

Practice case 24: Write a collinearity conclusion

Setup: Use the article’s variance-inflation-factor example and change one declared input for case 24. Task: Recalculate from raw values, preserve units and state which mathematical or design condition changed.

Check: Check the relevant invariant, separate the number from its claim, and name the next diagnostic or source of evidence. Rebuild the relevant counts before interpreting the coefficient, preserve the stated design, and write one sentence separating the numerical result from the claim it can support. Then vary one defensible assumption, calculate again, and explain whether the conclusion changes because of new data, a new reference model, or a new decision purpose. Finish by naming the unit, tolerance, and evidence needed for transfer. Record one graph or table that would expose failure hidden by the summary.