Home / Insights / Quality control

Westgard rules explained for POCT teams

Quality controlPublished 2026-09-039 min readVendor-neutral

What each Westgard rule detects, which kind of error it points to, how rules combine into a multirule, how sigma decides which rules you need, and what to do on the ward when one fires. Written for point-of-care coordinators and quality managers.

In brief

  • A Westgard rule is a decision rule applied to control results plotted on a Levey-Jennings chart: it defines what pattern counts as a rejection.
  • Rules differ in what they catch: 1-3s and R-4s respond to random error; 2-2s, 4-1s and 10x respond to systematic error (shift or trend).
  • A multirule combines several rules so that false rejections stay low while error detection stays high. The sigma of the method decides how many rules you need.
  • When a rule fires: stop reporting on that device, do not simply repeat until it passes, find the cause, fix it, re-run, and document the whole thing.

The chart first

A Levey-Jennings chart plots each control result in time order against the mean and standard deviation established for that control material on that analyser. Lines at plus and minus 1, 2 and 3 SD turn the chart into a set of zones. A Westgard rule is a statement about where points fall in those zones: how far, how many in a row, in which direction. The rules are named N-L, meaning N control observations exceeding the limit L, so 1-3s reads as one observation beyond 3 SD.

The mean and SD must come from your own data on that instrument, typically at least 20 runs over 20 days after the material is introduced, not from the manufacturer's insert. A chart built on the wrong SD will either fire constantly or never.

The rules, one at a time

The classic rules as described by Westgard and colleagues. Your scheme may use a subset.
RuleReads asWhat it signals
1-2sOne control beyond 2 SDA warning only. Around 5% of good runs exceed 2 SD by chance, so on its own this rule rejects too often. Use it as the trigger to check the other rules.
1-3sOne control beyond 3 SDRejection. A single large deviation, most often random error: a bubble, a short sample, a mis-pipetted control.
2-2sTwo consecutive controls beyond the same 2 SD limit (both high or both low)Rejection. Systematic error: something has shifted. Applies across two levels in one run, or the same level across two runs.
R-4sWithin one run, one control above 2 SD and another below 2 SD (a range of 4 SD)Rejection. Random error, usually a problem with the run itself.
4-1sFour consecutive controls beyond the same 1 SD limitRejection. A small systematic shift, often a calibration or reagent-lot drift.
10x (also 8x, 12x)Ten consecutive controls on the same side of the meanRejection. A persistent bias that is not large enough to trip the SD rules but is real.
7TSeven controls trending in one directionRejection in some schemes. A drift, for example reagent deterioration or a temperature problem.

Which rule catches which error

Analytical error comes in two kinds. Random error is scatter: results are imprecise but centred on the truth. Systematic error is bias: results are consistently high or low, as a shift (a step) or a trend (a slope). The rules divide along the same line:

  • Random error: 1-3s and R-4s. Look for a one-off cause in the run: sample handling, clot, bubble, short sample, a control vial that was not mixed.
  • Systematic error: 2-2s, 4-1s, 10x, 7T. Look for something that changed and stayed changed: a new reagent or control lot, a calibration, a maintenance event, a temperature change, a firmware update.

This is why the rule that fired is worth recording. It points the investigation.

Multirules and why 1-2s is a warning

A single 1-2s rejection rule has an unacceptable false-rejection rate: with two controls per run, roughly one run in ten would be rejected with nothing wrong. Westgard's insight was to combine rules so that the false-rejection rate stays around 1% while the probability of detecting a medically important error stays high. The classic multirule uses 1-2s as a warning that triggers inspection of 1-3s, 2-2s, R-4s, 4-1s and 10x; if none of those is violated, the run is accepted.

Rules can be applied within a run (across levels) and across runs (the same level over time). A 2-2s across the two levels in one run points at the run; a 2-2s on the same level across two runs points at the analyser or the lot.

How many rules do you need? Ask sigma

Not every analyte needs the full multirule. The sigma metric, (TEa minus absolute bias) divided by CV, measures how much room a method has before its errors become clinically significant, and Westgard Sigma Rules translate it into a QC design:

Westgard Sigma Rules, summarised. Sigma is calculated per analyte from your own CV, your bias (from EQA or a comparison) and the TEa you have adopted.
SigmaRulesControls
6 or more1-3s alone2 per run (N=2)
51-3s, 2-2s, R-4sN=2
41-3s, 2-2s, R-4s, 4-1sN=4 (or N=2 in two runs)
Under 4Full multirule including 8x or 10xN=6 or more, and more frequent QC

The practical consequence for POCT: a high-sigma analyte such as sodium on a good blood-gas analyser can be controlled with 1-3s and two controls, and applying 2-2s and 4-1s to it just generates false rejections on a ward at 3 a.m. A low-sigma analyte needs the multirule and the investigations that come with it.

What to do when a rule fires

  1. Stop

    Do not report patient results from that analyser for the affected analyte until the rejection is resolved. If the device supports lockout, this is what lockout is for.

  2. Do not just repeat

    Repeating the control until it passes is the most common wrong response. It converts a rejection into a false acceptance and leaves the cause in place. One repeat to rule out a handling error is reasonable; a passing repeat does not close the investigation on its own.

  3. Read the rule

    1-3s or R-4s: look inside the run. 2-2s, 4-1s or 10x: look for what changed. Check lots, calibration, maintenance, temperature, the control vial's opened date and storage, the operator.

  4. Fix, then re-run

    Correct the cause (new control vial, recalibrate, service, retrain) and run controls again. The repeat is evidence only when the cause has been addressed.

  5. Assess patient impact

    If the error was systematic, decide with the medical lead whether results since the last acceptable QC need review or repeat.

  6. Document

    The run, the rule, the cause, the action, the repeat and who did what. This record, not the chart, is what the assessor asks for; it is also what feeds a non-conformance if one is needed.

Special cases in POCT

  • Electronic QC and internal checks on some devices verify the electronics, not the reagent. They do not replace liquid QC; they change how often liquid QC is needed. Follow the manufacturer and your IQCP where you have one.
  • Unit-use devices (strips, cartridges) have QC on each lot and each new box or shipment rather than each run, and the rules are applied over those events.
  • Many operators, one device means the operator is a variable. A pattern of rejections that follows a person rather than a device is a training finding, not an analyser finding.
  • Monthly review: ISO 15189:2022 expects QC data to be reviewed at a defined frequency and acted on. A monthly summary of runs, rules fired, failures and reviews, signed by the reviewer, is the usual evidence.

Where software helps

Everything above can be done on paper and a spreadsheet, and many services do. The parts software does better are the ones that depend on being there when the control was run: capturing the value from the analyser rather than a transcription, applying the rules at that moment, holding the device until someone has looked, attaching the review to the run, and turning the month into a summary. Catenix quality control does that, records the rule that fired, links the failure review to a non-conformance when one is warranted, and, through the Statistics Workbench, calculates sigma per analyte so the rule set can be chosen deliberately.

Questions people ask

Is a 1-2s violation a rejection?

Not on its own. About one good result in twenty falls outside 2 SD by chance. Treat 1-2s as a warning that triggers a check of the other rules; reject only when one of those is violated.

Should we use the manufacturer's SD from the control insert?

No. The insert gives a range across many laboratories and instruments. Establish your own mean and SD on your analyser, normally from at least 20 results over 20 days, and review them when lots change.

Can we apply Westgard rules to unit-use POCT devices?

Yes, applied over the QC events you run (per lot, per shipment, per interval), with the number of rules chosen from the sigma of the analyte and the guidance in your IQCP if you have one.

How do we choose between 8x, 10x and 12x?

They are the same rule at different sensitivities; more observations means fewer false rejections and slower detection. Pick the one your scheme or sigma design specifies, and keep it consistent across devices of the same model.

This article is general guidance for laboratory and point-of-care professionals. It is not a substitute for the standards themselves, your accreditation body's requirements or the analyser manufacturer's instructions for use. Catenix does not interpret clinical results and provides no clinical decision support.

Take it with you

The buyer's guide, in your inbox.

Nine pages on what POCT connectivity is, the standards in plain English, the cost of doing it by hand and eight questions to ask any supplier.

Get the POCT connectivity buyer's guide

Nine pages, vendor-neutral: what connectivity is, the standards in plain English, the cost of doing it by hand and eight questions to ask any supplier. The PDF also opens directly from the downloads page; leave an email only if you want it in your inbox.

We use your email only to send the guide and, if you ask, to follow up once. No newsletter. See our privacy notice.

Thank you. The guide is on its way. You can also open it now.
That did not send. Open the guide directly or email contact@catenix.com.

See it done in software.

A 30-minute walkthrough on a live tenant, with your analysers and your allowable-error limits.