All articles
11 February 20265 min readGuideWorkflowTips

Tracking a protocol at the bench without losing your place

Where in a multi-step protocol people actually lose track, why paper checklists fail at exactly those points, and what to do instead when your hands are full.

A scientist in gown and gloves using a pipette at the bench

Nobody loses their place in a five-step protocol. People lose their place in the twenty-minute gap in the middle of a five-step protocol, when they leave the bench, answer something, come back, and cannot remember whether they added the enzyme before or after the buffer.

The three places tracking fails

  1. Waiting steps, because the protocol stops being in front of you the moment you walk away from it
  2. Repeated steps, because "wash three times" has no visible state — the second wash and the third look identical
  3. Parallel samples, because the step you are on is per-sample, and the protocol is written as though there is only one

A paper checklist handles none of these well. It handles the first badly because it stays on the bench while you leave; the second badly because ticking a box three times requires you to remember how many times you have ticked it; and the third badly because there is one column and six tubes.

Make the waiting step hold your place

The most reliable fix is also the least clever: attach the timer to the step rather than to the clock. A countdown that is named for what it is waiting on — "lysis, 20 min" — tells you where you were when it goes off. A bare 20:00 on a bench timer tells you only that twenty minutes have passed, which you already knew.

This is the whole reason a lab multi-timer is a different thing from a kitchen timer. It is not that you need more countdowns. It is that each countdown needs to carry a label, so the alarm restores the context instead of just interrupting you.

Give repeated steps a visible count

Anything you do "three times" needs somewhere to put the number. A tally counter is unglamorous and completely effective: one tap per wash, and the count is in front of you rather than in your head, where it competes with everything else you are holding.

The same applies to anything you are counting under a scope or off a plate. Counting is easy; remembering the count while doing something else is not.

Track per sample, not per protocol

When you are running six samples through the same protocol, the unit of progress is the sample, not the step. Written as a single checklist, step four means nothing until you also know which tubes have had it. Written as a grid — samples down, steps across — the state of the whole run is visible at a glance, and the tube you missed is the row with the gap.

Keep the record where the work happened

Tracking that lives on a scrap of paper gets transcribed later, and transcription is where errors enter. If the counts, the timings and the deviations are captured where you did the work, the write-up is a summary rather than a reconstruction — and reconstruction is the part that quietly costs you a repeat experiment.

Keep reading