Liquid handling robot selection: decks, tips and throughput

Specifying robotic liquid handling systems

1. Draw the deck before you compare instruments. Lay out every labware position the method needs at once: source plates, destination plates, reagent troughs, tip racks, a waste chute and any on deck device such as a shaker, a magnet or a heater. Count the positions. Most methods fail the deck test long before they fail the speed test, and a platform that needs the operator to reload mid run is not walk away automation.
2. Decide air displacement against positive displacement. Air displacement covers the majority of aqueous work and uses cheap disposable tips. Positive displacement handles viscous, volatile and dense liquids that defeat an air cushion. Mixed workloads usually justify a platform that accepts both, or an honest decision that the difficult liquids stay manual.
3. Cost the tips, not just the instrument. Filter tips, conductive tips for liquid level sensing and low retention surfaces each carry a per run cost that quickly exceeds the depreciation on the machine. Ask what a year of the intended run rate costs in consumables, and whether the platform accepts a second source of tips or locks you to one.
4. Test error recovery with a deliberate failure. During the demonstration, pull a tip rack, block a channel or remove a plate and watch what the software does. The question is whether the run pauses recoverably with the plate state recorded, or aborts and leaves you unable to say which wells were dispensed. That behaviour, not throughput, decides whether the machine can run overnight.
5. Check the data path and the audit trail. Confirm how the run log leaves the instrument, whether it records per well what was aspirated and dispensed, and whether user actions are attributable. If the results will ever support a regulated decision, electronic record and signature expectations apply to the instrument software as much as to the laboratory system it feeds.
6. Separate scheduling from method writing. Ask who will write methods after the vendor's engineer leaves. A platform that only the supplier can reprogram becomes a fixed function machine within a year. Look for a method editor a scientist can learn, and budget the training rather than hoping.

The deck is the real constraint on a robotic liquid handler

Throughput on paper is a function of channels and speed. Throughput in practice is a function of how many plates, tip racks and reagent reservoirs fit on the deck at once, because every reload is a human interruption and every interruption ends walk away operation. A method that needs one more tip rack than the deck holds is a method that cannot run overnight, whatever the instrument brochure says.

Model the worst method you intend to run, not the average one. Automation is bought for the long unattended runs, and those are the ones that consume deck space. If the vendor cannot lay out your method on their own deck diagram during the sales process, that is the answer.

What liquid handler automation really requires to run unattended

Three things make a run safe to leave: liquid level detection so the machine knows a reservoir is empty, clot and blockage detection so a failed aspiration is caught rather than propagated, and a recovery model that pauses with state preserved instead of aborting. Without them the machine is a fast pipette that still needs a person standing next to it.

Ask to see the log from a failed run rather than a successful one. A good platform tells you exactly which wells were completed, which were not and why, and lets the method resume. A weak one tells you the run ended.

When liquid handling automation systems are the wrong purchase

Automation pays when a defined protocol is repeated often enough that setup time is amortised, and when the variation between operators is costing you data. It does not pay when protocols change weekly, when sample numbers are small, or when the bottleneck is upstream of pipetting entirely.

A dispenser that fills plates with one reagent, or a plate washer that removes a genuinely tedious step, often recovers more scientist time per unit cost than a full workstation. Size the solution to the bottleneck you measured, not to the one the category implies.

Common questions

How many channels does a liquid handling machine actually need?

Fewer than most buyers assume. Eight channels plus a plate handling head covers a very wide range of plate work; ninety six and three hundred and eighty four channel heads pay off only when the same transfer is repeated across many plates. Deck capacity limits throughput long before channel count does.

Is an automated colony picker the same class of machine as a pipetting robot?

No. Colony picking and single cell dispensing are imaging and selection problems with a pipetting step attached, and the instruments are specified on optics, picking accuracy and viability rather than on transfer volume. Buying a liquid handler and expecting it to pick colonies is a common and expensive mistake.

What does a liquid handling robotics quotation usually leave out?

Tips and labware for the intended run rate, method development time, a service contract, the qualification visit and any on deck devices the method needs. The instrument line is often the smaller half of the first year cost.

Should the platform be validated?

If its output supports a regulated decision, yes, and the requirement should be written into the purchase. Installation, operational and performance checks are cheaper to specify before delivery than to retrofit after the first audit finding.

Browse by service class

• Compare Gene synthesis on advertised prices