Skip to content

25 August 2026 · TechSlideITS

Lab report turnaround: where the hours actually go

Patients judge a lab on how quickly the report arrives. Very few labs know which stage of their own process is the slow one.

Ask a lab how long a routine report takes and you get a number. Ask which part of the process consumes it and the answer is usually a guess.

That matters, because the analytical time — the test itself — is often the smallest component.

The stages, and where time hides

Collection to receipt

Samples collected at a camp, a collection centre, or a ward do not travel continuously. They travel in batches, when transport is available.

A sample collected at 9am that leaves at 1pm has consumed four hours before the lab has seen it. This is usually the single largest block, and it is invisible to the lab because their clock starts at receipt.

Receipt to processing

Registration, labelling, sorting. Fast when it works, and a bottleneck when one person does it alongside other duties.

Processing

The actual analytical time. Fixed by method and instrument, and the part everyone assumes is the constraint.

Result to verification

Results have to be reviewed before release. Where verification depends on one pathologist who is also consulting, results queue — and they queue in bursts, because that person reviews when they get a gap.

This is frequently the second-largest block and the most improvable, because batching verification into two or three defined slots is often faster than doing it whenever possible.

Verification to delivery

Printing, WhatsApp, email, or a patient travelling to collect. Delivery method decides whether a verified report reaches the patient in minutes or the next day.

Manual result entry

Worth separating out. Where analyser results are read from an instrument display and typed into a system, two things happen: it takes time, and it introduces transcription errors in the one place where an error is most serious.

Instrument integration removes both. Whether it is worth it depends on volume and on which analysers you run, but the error argument usually carries more weight than the time argument.

Measure before improving

Take fifty routine samples and record five timestamps: collected, received, processed, verified, delivered.

Most labs are surprised twice — by how much sits in collection-to-receipt, and by how much sits in verification. Neither is the test itself.

What tends to help, in order

  1. More frequent sample pickups, even if smaller — this usually beats every other change
  2. Defined verification slots rather than ad-hoc review
  3. Electronic delivery as the default, with collection as the exception
  4. Analyser integration where volume justifies it
  5. Separating urgent from routine so priority samples are not stuck behind a batch

What to promise

A lab that knows its actual distribution can promise a realistic time and meet it. A lab quoting an average will miss it roughly half the time, which is what damages reputation.

Quoting a time you meet consistently is worth more commercially than quoting a faster one you miss.

If you want to see turnaround measured by stage, see our pharmacy and lab system or book a demo.

FAQ

Frequently asked questions

Five stages: collection to receipt, receipt to processing, the analytical processing itself, result to verification, and verification to delivery. The test is often the smallest of the five — collection-to-receipt and verification queues are usually the largest.

Because samples travel in batches when transport is available, not continuously. A sample collected at 9am that leaves at 1pm has consumed four hours before the lab has seen it — and it is invisible to the lab, because their clock starts at receipt.

Usually by batching verification into two or three defined slots rather than reviewing whenever a gap appears. Where verification depends on one pathologist who is also consulting, results queue in bursts, and defined slots are often faster than ad-hoc review despite feeling less responsive.

It depends on volume and which instruments you run, but the stronger argument is error rather than time. Typing results read from an instrument display introduces transcription errors in the place where an error matters most.

One it meets consistently rather than the fastest it has achieved. A lab quoting its average will miss it roughly half the time, and missed promises damage reputation more than a slightly longer honest commitment does.

Want ERP that fits your business?

Book a free demo and see how TechSlideITS ERP works for your industry.

Chat on WhatsApp
Lab Report Turnaround: Where the Hours Go | TechSlideITS