One Result Is a Snapshot: Why Baselines and Trends Matter in Lab Data

The Number Without a Story

A result comes back a little higher than usual. Is it a problem? A blip? The start of something?

Without history, nobody can say. The number might be perfectly normal for that sample point, or it might be the first step in a change that has been building for months. Looking at it alone, you cannot tell which.

An unlikely book makes this point well. Common Sense Labs by Ken Berry and Kim Howerton is a consumer guide to personal blood tests, not a book about testing laboratories, and nothing here is health advice. But a few of its general ideas about measurement apply to any lab that reports numbers.

Testing Is a Tool

The authors put it simply:

"The testing is simply a tool, not the end goal."

(Ken Berry and Kim Howerton, Common Sense Labs, Introduction)

For a testing lab, that is a useful reminder. Clients do not want a number for its own sake. They want to know what is happening at their site, well or process. A single result answers a narrow question. A history of results answers the one they actually care about.

One Result Is Not a Conclusion

In a section titled "Don't Panic," the authors write:

"Risk factor does not mean diagnosis."

(Common Sense Labs, "Don't Panic")

They are talking about personal health, but the logic carries over. One unusual result is a signal worth looking at, not a verdict. It could reflect a real change. It could also reflect sampling, handling, or ordinary variation.

That is exactly why labs already run controls, duplicates and reviews. Keeping each sample point's history in view adds one more layer: it lets the reviewer see whether a result is unusual for that point, not just unusual in general.

What a Baseline Gives You

A baseline is simply the record of what "normal" has looked like for a particular sample point, method or instrument over time. It does not tell you what to do. It gives you something to compare against.

With a baseline you can:

• Tell a blip from a shift. One high reading after years of steady results looks different from a slow climb over several quarters.
• Spot drift in your own process. A control that creeps in one direction over weeks can point to an instrument or reagent issue before it fails outright.
• Give clients context. A report that shows a result next to its own history is easier to understand than a number on its own.

What counts as a meaningful change, and what action it calls for, depends on the method, the matrix, your QC program and any regulatory requirements that apply. Those decisions belong to qualified staff and your quality system, not to a chart.

Perfection Is Not the Point

In their wrap-up, the authors offer a line worth keeping on the wall of any QA office:

"Improvement is the goal; perfection is not required."

(Common Sense Labs, "Wrapping Up")

Trend tracking does not need to start as a perfect statistical program. It can start with making sure every result is stored with its sample point, date and method, so that history is available when someone needs it.

A Simple Starting Checklist

1. Record results consistently. Same sample point names, same units, same method identifiers, every time.
2. Keep history in one place. If past results live in old spreadsheets or paper files, a trend is hard to see.
3. Show history during review. Let the reviewer see recent results for the same point before release.
4. Watch your controls over time, not just pass or fail on the day.
5. Write down what "unusual" means for your lab, through your own QC program, so reviewers are not guessing.

A single result is a snapshot. A history is a story. Good lab data management makes the story easy to read.

---

Quotes are from Ken Berry and Kim Howerton, Common Sense Labs (Introduction, "Don't Panic" and "Wrapping Up"), a consumer health book. This post applies only its general ideas about measurement and is not medical, clinical or regulatory advice.