What does a reportable test actually cost you?
Ask most laboratories what a test costs and they will quote the reagent price. But a released result is the sum of many things, and the parts nobody counts are usually the ones eating the margin.
Margin rarely leaks evenly. A handful of tests, running far over what they should cost, usually drains more than the rest combined. The trick is finding them before they find your bottom line.
When a laboratory’s margin is thinner than it should be, the instinct is to tighten everything: trim reagent use across the board, lean on every supplier, squeeze every line. It feels thorough, but it usually misses the point. Lost margin almost never leaks evenly across a test menu. It concentrates. A handful of tests, running far over what they should cost, typically drains more than every well-behaved test combined. Trim everywhere and you spread effort thinly across tests that were never the problem, while the real offenders carry on undisturbed. The job is not to economise broadly. It is to find the few high-variance tests doing the damage and fix those.
The difficulty is that the worst offenders do not announce themselves. A test running thirty per cent over its expected cost looks, on the bench, exactly like one running on target. The variance lives in the consumption, not the workflow, and consumption is invisible unless something is measuring it.
A high-variance test hides for the same reasons true cost is hard to see at all. The over-consumption is spread across many runs, each one slightly off, so no single instance looks alarming. The cause might be an over-issue at the bench, a reagent price that crept up, a sample type that triggers frequent repeats, or wastage from short-dated stock. Each cause sits in a different record, and none of them is tied back to the specific test it inflated.
So the lab sees only the aggregate: margin is down. It does not see that one or two tests are responsible for most of the shortfall, because nothing connects the scattered consumption back to the test that drove it. Without that connection, every test looks equally suspect, and the lab ends up investigating all of them or none of them.
Trimming across the board is not just inefficient, it can be harmful. Lean too hard on a test that was already running on target and you risk cutting into the quality of the result, the controls, the repeats a borderline sample genuinely needs. Effort spent policing well-behaved tests is effort not spent on the ones bleeding money. And because the broad squeeze never names a cause, it rarely fixes anything: the high-variance test keeps running over, and the margin keeps leaking, while everyone feels they have been working hard at the problem.
Margin does not leak evenly, so you should not chase it evenly. Find the few tests running far over their expected cost, name what is driving each one, and fix those. The rest will look after themselves.
Veona Cost Per Reportable Test compares each test’s expected cost against what its runs actually consumed, and flags the variance. The tests running well over their expected cost rise to the top, ranked, so the lab sees at a glance which few are responsible for the shortfall. And because the actual cost is built from real stock draws, the flag comes with its driver named: an over-issue, a reagent price rise, repeats, or wastage. The lab does not just learn that full blood count is running seventeen per cent over, it learns the over-run is quality-control over-consumption and wastage, not the reagent.
That turns a vague worry into a short, specific list of things to fix. We explain how that expected-versus-actual comparison is built in computing cost from real stock draws. The point of variance flagging is to put the lab’s limited attention exactly where it pays back, instead of spreading it across a menu that mostly does not need it.
The reason naming the driver matters is that it tells you what to do. If the variance is a reagent-price rise, the answer is to reprice or renegotiate supply, not to lecture the bench. If it is an over-issue, the fix is a workflow correction. If it is repeats on a particular sample type, the answer is a pre-analytical change. Each driver points to a different, specific action. A bare variance number cannot do that. It only worries you. A variance with its cause attached tells you precisely where to spend the next hour.
In a market where reagents are imported and dollar-priced, and where margins leave little room for error, the high-variance test is especially dangerous. A single test quietly running over cost, driven by an FX-led reagent rise nobody flagged, can erase the profit on a much larger volume of well-priced work. The lab cannot afford to find that out at the end of the quarter, and it cannot afford to chase it by trimming everywhere.
Finding the offenders early, with their cause named, lets a lean lab spend its scarce attention exactly where it changes the bottom line. Once the offenders are named, the next move is usually repricing the menu on the real cost.
See the high-variance tests surfaced and ranked, each with its driver named. Book a demo and we will find the leaks in your own menu.
Ask most laboratories what a test costs and they will quote the reagent price. But a released result is the sum of many things, and the parts nobody counts are usually the ones eating the margin.
A planned cost tells you what a test should consume. The real stock draws tell you what it did. The gap between them is where a lab finds the money it has been losing without knowing.
A reportable test is built from a recipe: reagents, the controls it shares, the wastage it carries, and a slice of overhead. Most labs know the first ingredient and guess at the rest.
We will tailor a demo to how your hospital, clinic, or lab actually runs, offline behaviour, payments, reporting, and all.