PHARMA LAB · PL-03-004
Electronic pipettes: programs, settings and controls

In this article
An electronic pipette makes piston movement programmable; it does not automatically make every transfer correct. Useful control connects the program, liquid, tip and actual sequence. Before routine use, establish which settings are approved, what evidence supports their suitability and how to identify an interrupted series. A displayed value describes a command, not an independent measurement of the volume delivered.
When is electronic operation useful?
Potential benefits concern repetitive sequences, volume changes and fewer manual piston operations. Assess the whole task: loading tips, reaching vessels, reading the display, charging and handling errors. Weight, grip and the operations actually saved need a trial with intended users; a list of functions is insufficient.
Separate electronic operation from the transfer principle. An electronic pipette may use air displacement; it is not necessarily a positive displacement device. For that choice, see the comparison of air and positive displacement pipettes. The NIST summary covers both distinctions without establishing universal superiority for electronic operation. [1]
Which mode matches the task?
Identify how the particular model works: a single transfer, repeated dispensing from one aspiration, mixing or a stored sequence. Similar names may describe different functions. Check the instructions for automatic stages, required confirmations and the treatment of initial volume, aliquots and final residual liquid.
The following matrix is an original GuideGxP proposal for designing checks, not a mandatory specification. Complete each row with the configuration and acceptance criteria approved before testing.
| Mode | Risk to consider | Settings to identify | Evidence to collect |
|---|---|---|---|
| Single transfer | Incomplete aspiration or unexpected residue | Volume, speeds, pauses and blow-out handling | Performance with the relevant liquid and tip |
| Repeated dispensing | Different aliquots along the series | Aliquot volume, count, initial and final stages | Separate results at the beginning, middle and end |
| Mixing | Foaming, carryover or incomplete homogenisation | Volume, cycles, speeds and vessel | Mixing suitability for the method |
| Stored sequence | Wrong program or skipped step | Identifier, version, order and confirmations | Complete execution and interruption handling |
How should speeds, pauses and volumes be defined?
Start with the intended liquid, volume range, tip and vessels. A speed suitable for one solution may cause incomplete aspiration with another; a longer pause may change contact time or evaporation exposure. These are hypotheses to test, not reasons to select the slowest setting automatically.
Also document immersion, dispensing position and residual-liquid handling when they affect transfer. Programming does not remove these manual actions. If the technique needs changing, consult forward and reverse pipetting with challenging liquids; do not add a final blow-out to a mode that deliberately retains liquid.
Avoid universal speeds, waiting times or cycle counts. Record the units and meaning of settings: an internal numerical level is not necessarily a physical speed comparable across instruments. When selecting volumes, consider both the individual aliquot and the permitted overall aspiration, including any additional volumes specified for the model.
How can the selected program be controlled?
Prepare a record linking the identified instrument, program name or code, procedure revision, volumes, mode, tips and operating conditions. If the device lacks version control or permissions, establish checkable procedural controls: who may change settings, how they are compared with the approved configuration and how temporary settings are recognised.
Before starting, confirm use status, program and sample-to-position mapping. Do not rely on the program left in memory by the previous shift. For GMP work, contemporaneous records and controlled instructions should make relevant actions reconstructable; EU GMP Chapter 4 supplies the documentation framework, not a mandatory pipette log format. [2]
A pipette with memory does not automatically require every feature of a complex computerised system. Assess which data and decisions depend on it. Connectivity, a keypad lock or exported settings do not, by themselves, demonstrate regulatory compliance.
What evidence supports program suitability?
Calibration establishes the metrological relationship under stated conditions; verification compares evidence with defined requirements. Neither is synonymous with adjustment. Calibration in single-transfer mode does not alone demonstrate suitability of all stored modes. Check the settings that could change the outcome of the intended work.
For repeated dispensing, design a comparison that retains aliquot order and covers relevant stages of the series. Do not rely only on the final total: it can conceal unequal aliquots. Define liquids, volumes, replicates, measurement method, relevant uncertainty and criteria before examining results. If using a substitute liquid, explain which properties it represents.
ISO 8655-2:2022 addresses pipettes with selected essential components; ISO 8655-10:2024 includes use, competence and suitability within its scope. The public scopes were checked here; no tolerances or sample sizes are inferred from the unconsulted full texts. [3,4] For multichannel models, also retain channel identity, as discussed in multichannel pipette consistency.
Simulated case: an interrupted series
A series of additions stops after a battery warning. Following restart, a familiar mode appears, but the operator cannot establish whether the last tube received its aliquot. This is a simulated reasoning case, with no experimental results or recovery procedure valid for every model.
The laboratory stops the affected work and preserves the position map, records, observed state and available message. It distinguishes the last definitely completed position from uncertain ones. A device counter, if available, must be interpreted according to its documented operation: a recorded command alone does not prove that liquid reached the correct tube.
Resumption depends on evidence, sample stability and the authorised procedure. Adding another aliquot “just in case” could double the dose; continuing from memory could leave it missing. If uncertainty cannot be resolved, the responsible person decides how to handle affected samples while retaining the deviation and rationale. A restart button does not close the investigation.
How are programs and performance kept under control?
Train operators in program changes, stage recognition, insufficient battery, errors and stopping. An observed exercise should include reconstructing a sequence, not just starting it correctly. Establish a handover that distinguishes completed work from work still required.
After maintenance, component replacement, a relevant update or program change, assess which functions and performance characteristics may have changed. Link intervention, checks and authorisation to return to use. Cleaning and charging follow instructions compatible with the model; do not assume the complete electronic body is autoclavable.
The intended outcome is an identifiable, reproducible configuration supported by evidence proportionate to the task. Return to the Liquid handling and sample preparation hub to place it within the complete workflow.
For the related steps, see: Pipette cleaning and maintenance: criteria and post-service checks; Pipette fleet management: inventory, status and due dates.
Sources and limitations
Sources checked on 30 September 2026. The matrix and case are original GuideGxP contributions. Operating settings require model-specific instructions and local approval.
- NIST, Sander — Volumetric Transfer of Liquids, 2017. Publication record and summary consulted, not the full video.
- EU GMP Chapter 4 — Documentation, 2011 revision, §§4.3, 4.8, 4.29–4.31; version listed in the current index.
- ISO 8655-2:2022, edition 2. Official scope; licensed full text not consulted.
- ISO 8655-10:2024, edition 1. Official scope and status; full text not consulted.
Continue exploring
PL-03-007
Pipette fleet management: inventory, status and due dates
From the register to the bench: identify pipettes fit for use, link interventions to the same instrument and manage due dates and anomalies.
Read the articlePL-03-006
Pipette cleaning and maintenance: criteria and post-service checks
A clean pipette or a smooth piston does not automatically mean it is ready for use. Link each intervention to its risks and required checks.
Read the articlePL-03-005
Pipette tips: compatibility, retention and contamination
A tip that fits is not necessarily equivalent: check sealing, transfer, analyte interactions and cleanliness requirements.
Read the article


