A number is a promise
Imagine a lab reports that a bottle of drinking water contains 8 micrograms of lead per litre. A whole chain of decisions hangs on that one number: a parent decides the water is safe, a city decides not to replace its pipes, a regulator decides not to fine anyone. The number is, in effect, a promise that reality matches what the report says. But a measurement method is a long machine of steps — sampling, dilution, instruments, calculations — and any of those steps can quietly lie. So how does anyone earn the right to make that promise?
The answer is that, before the method is ever used for real, someone deliberately tests it — on purpose, in advance, with samples whose true answer is already known. This planned testing is called method validation. It is the difference between "we ran the instrument and got a number" and "we have evidence this method gives the right number."
Two everyday questions: is it true, and is it steady?
Most of validation comes down to two homely questions you already ask in daily life. First: is the answer true? If a bathroom scale always reads 3 kg too high, it is not telling the truth, no matter how confidently it shows the number. In the lab this truthfulness is called accuracy — how close a result is to the real value. Second: is the answer steady? If you step on and off the scale five times and get five wildly different weights, you cannot trust any single reading. That steadiness is precision — how close repeated measurements are to each other.
Quality control vs quality assurance
Validation proves a method is sound once. But labs run thousands of samples over years, and people, reagents, and instruments drift. So two ongoing habits keep the promise alive day after day. Quality control (QC) is the set of checks you run *alongside* real samples — measuring a known sample now and then to confirm the method is still behaving today. Quality assurance (QA) is the bigger umbrella: the whole system of rules, records, training, and audits that makes good results the default, not a lucky accident.
A simple way to keep them straight: QC asks "is this batch good right now?" while QA asks "is our lab set up so that batches are reliably good?" QC catches today's problem; QA prevents tomorrow's. You need both, and the rest of this rung unpacks the tools each one uses.
What a validation actually checks
When a team validates a method, they don't just shrug and say "looks fine." They work through a checklist of named properties — sometimes called performance characteristics — and gather a number for each. You'll meet them all properly in later guides, but here is the shape of the list so the vocabulary stops feeling random.
- How small a trace can it even see, and reliably measure? (limit of detection, limit of quantitation)
- Over what range does signal track concentration in a clean straight line? (linearity, working range)
- Does it find the right amount even buried in a messy real sample? (recovery, accuracy)
- Does it stay calm when small things change — a new analyst, a slightly different temperature? (robustness, ruggedness)
Why this is worth your patience
It is tempting to see all this as bureaucratic ceremony. But every rule in quality work is a scar from a real disaster — a misdosed patient, a contaminated food recall, a wrongful conviction overturned. Quality work is simply the discipline of not fooling yourself, written down so a whole organisation can practise it. Master it, and your numbers earn the one thing a scientist most needs: to be believed.