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? | Rescaled Sums of z Scores, Persistent Bias and Multianalyte Patterns

One proficiency score can look harmless while a laboratory shows a small bias in the same direction across many analytes. The rescaled sum of z scores, RSZ, adds signed z scores and divides by the square root of their count. It is designed to reveal coherent directional patterns.

This is why mathematics matters in quality systems: weak signals can accumulate. The method works only when the scores are suitably comparable and their dependence is understood.

Full chapter index

Chapters 1–3 · Understand the question
  1. The pattern question
  2. A worked example
  3. Why not divide by four
Chapters 4–7 · Reproduce the example
  1. Signs can cancel
  2. Independence is critical
  3. Comparable scoring scales
  4. Selection after seeing results
Chapters 8–13 · Check assumptions
  1. Missing data
  2. A second worked pattern
  3. Long-term and multianalyte use
  4. Relationship to a control chart
  5. Relationship to SSZ
  6. A classroom activity
Chapters 14–18 · Explore applications
  1. Spreadsheet workflow
  2. Coding workflow
  3. Misconceptions
  4. Guidance for students and parents
  5. Careers and applications
Chapters 19–23 · Study and verify
  1. Connection to recent articles
  2. Practice questions
  3. Frequently asked questions
  4. Useful next reading and source checks
  5. Closing perspective

CHAPTER 1 OF 23 · Understand the question

1. The pattern question

Back to contents

Let z_1 through z_L be proficiency z scores for L results. RSZ = sum(z_i)/square root of L.

If scores are independent standard normal variables under a suitable null model, their sum has variance L, so division by square root of L returns unit variance.

Contents · Next chapter

CHAPTER 2 OF 23 · Understand the question

2. A worked example

Back to contents

Suppose four analyte scores are 1.2, 0.8, 1.5 and 0.5. Their sum is 4.0 and square root of 4 is 2.

RSZ = 4/2 = 2.0. Every score is positive, so the combined statistic reveals a consistent upward tendency.

Score 1Score 2Score 3Score 4Sum
1.20.81.50.54.0
Four signed proficiency scores.

Contents · Previous chapter · Next chapter

CHAPTER 3 OF 23 · Understand the question

3. Why not divide by four

Back to contents

The mean score would be 1.0, but its standard deviation under independence is 1/square root of L. Multiplying the mean by square root of L gives RSZ.

Dividing the sum by L answers a different descriptive question.

QuantityCalculationResult
LCount scores4
sqrt(L)sqrt(4)2
RSZ4/22.0
Rescaled sum calculation.

Contents · Previous chapter · Next chapter

CHAPTER 4 OF 23 · Reproduce the example

4. Signs can cancel

Back to contents

Scores 1.2, -0.8, 1.5 and -0.5 sum to 1.4, giving RSZ = 0.7. Large mixed-direction errors can cancel.

Use the sum of squared z scores or individual plots to detect non-directional excess scatter. RSZ is intentionally sensitive to consistent bias.

Contents · Previous chapter · Next chapter

CHAPTER 5 OF 23 · Reproduce the example

5. Independence is critical

Back to contents

Analytes from one sample may share preparation, calibration, blank or instrument effects. Positive correlation makes the variance of the sum exceed L, so the simple RSZ can look more extreme than the independence model predicts.

Use a covariance-aware statistic or a documented scheme procedure when scores are correlated.

Contents · Previous chapter · Next chapter

CHAPTER 6 OF 23 · Reproduce the example

6. Comparable scoring scales

Back to contents

Each z score should have a meaningful assigned value and sigma_pt. Combining scores from unrelated schemes, rounds or purposes can create a number without a coherent interpretation.

Predefine which analytes enter the sum and how missing results are handled.

Contents · Previous chapter · Next chapter

CHAPTER 7 OF 23 · Reproduce the example

7. Selection after seeing results

Back to contents

Choosing only positive scores inflates RSZ. Selecting analytes after inspection destroys the reference distribution.

The set must be declared independently of the observed signs.

Contents · Previous chapter · Next chapter

CHAPTER 8 OF 23 · Check assumptions

8. Missing data

Back to contents

If one analyte is missing, L changes. A missing result caused by measurement failure may be informative and should not disappear without documentation.

Report included analytes, exclusions and the reason for each.

Contents · Previous chapter · Next chapter

CHAPTER 9 OF 23 · Check assumptions

9. A second worked pattern

Back to contents

For z scores -1.7, -0.9, -1.2 and -0.6, the sum is -4.4 and RSZ = -2.2. The negative sign indicates a coherent low tendency.

Investigate shared calibration or preparation effects rather than treating four scores as unrelated.

Contents · Previous chapter · Next chapter

CHAPTER 10 OF 23 · Check assumptions

10. Long-term and multianalyte use

Back to contents

RSZ can combine analytes within a round or comparable scores across time, but those designs have different dependence structures. Round-to-round material changes can break comparability.

State the axis of aggregation.

Contents · Previous chapter · Next chapter

CHAPTER 11 OF 23 · Check assumptions

11. Relationship to a control chart

Back to contents

Plot RSZ by round to monitor directional changes. Control limits require a justified dependence and stability model.

A chart supports investigation; it does not prove a cause.

Contents · Previous chapter · Next chapter

CHAPTER 12 OF 23 · Check assumptions

12. Relationship to SSZ

Back to contents

The sum of squared z scores, SSZ = sum(z_i squared), ignores direction and reacts to large magnitudes. Under independence it can be compared with a chi-square reference with L degrees of freedom.

RSZ and SSZ answer complementary centre and spread questions.

Contents · Previous chapter · Next chapter

CHAPTER 13 OF 23 · Check assumptions

13. A classroom activity

Back to contents

Give students sets of four signed scores. Compare individual magnitudes, RSZ and SSZ. Create one set with consistent small bias and one with alternating large signs.

Ask which statistic detects which pattern.

Contents · Previous chapter · Next chapter

CHAPTER 14 OF 23 · Explore applications

14. Spreadsheet workflow

Back to contents

Use one row per declared score with analyte, round, sign, inclusion status and reason. Sum included scores, count L and divide by square root of L.

Calculate SSZ in a separate column and never hide the individual scores.

Contents · Previous chapter · Next chapter

CHAPTER 15 OF 23 · Explore applications

15. Coding workflow

Back to contents

Validate the prespecified set, handle missingness explicitly and calculate both RSZ and score covariance when available. Test four scores summing to four to obtain RSZ=2.

Return inclusion metadata with the number.

Contents · Previous chapter · Next chapter

CHAPTER 16 OF 23 · Explore applications

16. Misconceptions

Back to contents

RSZ is not an average proficiency grade. A near-zero value can hide large opposing scores. A large value does not identify the shared cause.

Independence is an assumption, not a default truth.

Contents · Previous chapter · Next chapter

CHAPTER 17 OF 23 · Explore applications

17. Guidance for students and parents

Back to contents

Students can connect sums, variance addition, square roots and correlation. Ask why four independent unit-variance scores have a sum SD of two.

Parents can encourage inspection of the component scores. Aggregates should invite questions, not replace evidence.

Contents · Previous chapter · Next chapter

CHAPTER 18 OF 23 · Explore applications

18. Careers and applications

Back to contents

Combined scores can support laboratory trend monitoring, sampling proficiency and multianalyte quality review. The transferable skill is aggregating weak signals while respecting dependence.

Use the Mathematics Learning Hub and How Mathematics Works for broader learning.

Contents · Previous chapter · Next chapter

CHAPTER 19 OF 23 · Study and verify

19. Connection to recent articles

Back to contents

The Birge-ratio guide checks overall uncertainty consistency. The PT z-score guide defines each component score.

Contents · Previous chapter · Next chapter

CHAPTER 20 OF 23 · Study and verify

20. Practice questions

Back to contents

Calculate RSZ for 1,1,1,1 and for 2,-2,2,-2. Compute SSZ for both sets. Add a fifth zero score and explain how the denominator changes. Assume pairwise correlation 0.25 and explain why square root of L is no longer the correct SD of the sum.

Contents · Previous chapter · Next chapter

CHAPTER 21 OF 23 · Study and verify

21. Frequently asked questions

Back to contents

### Why divide by square root of L? Under independence, variances add to L, so the sum's standard deviation is square root of L.

### Can opposite errors cancel? Yes. That is why individual scores and SSZ remain important.

### Can I combine any z scores? No. They need a coherent design, comparable meaning and declared dependence assumptions.

### Is RSZ a formal pass/fail score? Only if the governing programme defines and validates such a rule.

Contents · Previous chapter · Next chapter

CHAPTER 22 OF 23 · Study and verify

22. Useful next reading and source checks

Back to contents

Use the Eurachem sampling-uncertainty workshop example, which shows RSZ as sum z divided by square root of n, the IAEA XRF comparison discussion and the Eurachem PT guide. The worked scores are original.

Contents · Previous chapter · Next chapter

CHAPTER 23 OF 23 · Study and verify

23. Closing perspective

Back to contents

RSZ shows how several modest signed signals can reveal a shared direction. Mathematics makes the accumulation fair under stated assumptions and reminds us to inspect correlation, selection and every component score.

Contents · Previous chapter · Mathematics Learning Hub

Extended practice laboratory

Practice case 1: Sum four positive scores

Setup: Use the article’s RSZ example and change one declared input for case 1. Task: Recalculate from raw values, preserve units and state which scoring 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: Sum alternating signs

Setup: Use the article’s RSZ example and change one declared input for case 2. Task: Recalculate from raw values, preserve units and state which scoring 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: Compute SSZ

Setup: Use the article’s RSZ example and change one declared input for case 3. Task: Recalculate from raw values, preserve units and state which scoring 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: Add a zero score

Setup: Use the article’s RSZ example and change one declared input for case 4. Task: Recalculate from raw values, preserve units and state which scoring 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: Add a fifth positive score

Setup: Use the article’s RSZ example and change one declared input for case 5. Task: Recalculate from raw values, preserve units and state which scoring 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: Reverse all signs

Setup: Use the article’s RSZ example and change one declared input for case 6. Task: Recalculate from raw values, preserve units and state which scoring 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: Average instead of rescale

Setup: Use the article’s RSZ example and change one declared input for case 7. Task: Recalculate from raw values, preserve units and state which scoring 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: Check variance of the sum

Setup: Use the article’s RSZ example and change one declared input for case 8. Task: Recalculate from raw values, preserve units and state which scoring 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: Introduce positive correlation

Setup: Use the article’s RSZ example and change one declared input for case 9. Task: Recalculate from raw values, preserve units and state which scoring 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: Introduce negative correlation

Setup: Use the article’s RSZ example and change one declared input for case 10. Task: Recalculate from raw values, preserve units and state which scoring 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: Select only positives

Setup: Use the article’s RSZ example and change one declared input for case 11. Task: Recalculate from raw values, preserve units and state which scoring 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: Prespecify analytes

Setup: Use the article’s RSZ example and change one declared input for case 12. Task: Recalculate from raw values, preserve units and state which scoring 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: Handle missing data

Setup: Use the article’s RSZ example and change one declared input for case 13. Task: Recalculate from raw values, preserve units and state which scoring 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: Combine two rounds

Setup: Use the article’s RSZ example and change one declared input for case 14. Task: Recalculate from raw values, preserve units and state which scoring 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: Plot RSZ by round

Setup: Use the article’s RSZ example and change one declared input for case 15. Task: Recalculate from raw values, preserve units and state which scoring 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: Inspect component scores

Setup: Use the article’s RSZ example and change one declared input for case 16. Task: Recalculate from raw values, preserve units and state which scoring 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: Find cancellation

Setup: Use the article’s RSZ example and change one declared input for case 17. Task: Recalculate from raw values, preserve units and state which scoring 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: Find persistent bias

Setup: Use the article’s RSZ example and change one declared input for case 18. Task: Recalculate from raw values, preserve units and state which scoring 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: Compare Birge ratio

Setup: Use the article’s RSZ example and change one declared input for case 19. Task: Recalculate from raw values, preserve units and state which scoring 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: Compare a control chart

Setup: Use the article’s RSZ example and change one declared input for case 20. Task: Recalculate from raw values, preserve units and state which scoring 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: Check comparable sigma_pt

Setup: Use the article’s RSZ example and change one declared input for case 21. Task: Recalculate from raw values, preserve units and state which scoring 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: Audit inclusion metadata

Setup: Use the article’s RSZ example and change one declared input for case 22. Task: Recalculate from raw values, preserve units and state which scoring 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 pass-fail overclaim

Setup: Use the article’s RSZ example and change one declared input for case 23. Task: Recalculate from raw values, preserve units and state which scoring 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 dependence-limited conclusion

Setup: Use the article’s RSZ example and change one declared input for case 24. Task: Recalculate from raw values, preserve units and state which scoring 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.