← All articles
Protocol Optimisation

Five Liquid Handling Protocol Errors That Silently Ruin Assay Reproducibility

Most liquid handling protocol failures don't throw an error. The robot runs to completion, the plate looks fine, and the problem only shows up days later as inexplicable noise in your data. Here are the five gaps we see most often when reviewing submitted protocols.

1. Tip reuse across reagents with different viscosities

Reusing tips between a buffer and a glycerol-heavy reagent without an intervening wash or tip change introduces carryover that's inconsistent across wells — worse in some positions than others depending on dispense order.

2. Volume rounding below the instrument's accurate range

Most liquid handlers report a "minimum volume" spec, but accuracy degrades well before that floor. A protocol calling for 2 µl dispenses on a pump rated accurate down to 1 µl is technically valid and silently imprecise.

3. Missing pre-wet or pre-rinse steps for hydrophobic plates

Skipping a pre-wet step on certain plastics causes the first few dispenses in a run to behave differently from the rest — a systematic, position-dependent error that's easy to miss in a single-run QC check.

4. Plate-to-plate Z-height assumptions

Protocols written against one lot of plates sometimes hard-code a Z-offset that doesn't hold for a different plate lot or vendor, leading to inconsistent immersion depth and bubble formation.

5. No gap analysis between assay parameters and instrument liquid classes

This is the most common one: the assay was designed independently of the instrument's calibrated liquid classes, so the protocol ends up using a generic class that wasn't validated for the actual reagent being dispensed.

None of these show up as a script error. They show up as a 15% CV that nobody can explain. Catching them requires a structured review against the specific instrument and reagents — not just a syntax check.

ProtocolPilot generates optimised, ready-to-run scripts for Tecan and Hamilton from your assay parameters — flagging dead volume, labware, and liquid class gaps before you run a single tip.

Try ProtocolPilot →