The Method Has a Stowaway: Auditing the Bench Habits That Travel With a Transferred Assay

An assay transfer is rarely a clean handover. It arrives as a PDF, a spreadsheet, a box of tubes and a cheerful email saying the method works fine. But the method is not only the document. It is also the shaker with the warm spot, the buffer someone makes on Fridays, the plate-reader setting nobody recorded, and the postdoc who always does the extraction because everyone else gets drift. In UK labs, transfers happen between university groups, core facilities, spinouts, NHS labs and collaborators. The paperwork moves. The shadow protocol moves with it.

The protocol is the least portable part

Written methods strip out context. Add 5 µL sounds precise until you learn that the originating lab used low-retention tips because the standard ones stick. Incubate for 30 minutes sounds fixed until you discover that the shaker runs a couple of degrees warm on the left side. Use the in-house antibody sounds efficient until you ask which clone, which host species and which lot. A transferred assay is a recipe plus a kitchen. If you only inherit the recipe, you inherit surprises.

The practical job is not to reject local tweaks. It is to make them visible. A tweak that is documented, owned and tested is method knowledge. A tweak that lives in someone's memory is a future reproducibility problem with a freezer lid.

Where the shadows gather

Most hidden variation sits in five places. First, equipment: plate-reader gain, centrifuge ramp, incubator temperature, shaker speed, thermal-cycler block. Second, reagents: catalogue numbers, clones, lot numbers, water grade, buffer pH, whether a kit was replaced with a homebrew version. Third, environment: bench temperature, humidity, light exposure, how long plates sit before reading. Fourth, operator choreography: pipetting order, vortexing, quick spins, timing between steps, who does which step. Fifth, data handling: how controls are accepted, how outliers are treated, which spreadsheet is considered the real record.

None of these are glamorous. All of them can move a result. A reagent substitution that seems harmless can shift the dynamic range. A different water source can change a buffer. A new operator can follow every written step and still fail because the written step was never the whole step.

The 45-minute paper pass

Before anyone books bench time, do a paper pass. Put the originating protocol, the transfer protocol and the source lab's last three raw runs side by side. Look for handwritten notes, version dates, appended pages and phrases like as before or standard conditions. Those phrases are where the shadows hide.

Ask for the reagent inventory behind the last successful run. Does the protocol name a catalogue number or just an antibody? Is the water grade stated? Are plate-reader settings captured? Are control acceptance criteria written down or implied? If the answer to any of these is someone's name, you have found a shadow. That is not a scandal. It is a prompt to write it down.

The reagent substitution trap

Equivalent is not identical. A different antibody clone can bind differently. A different polymerase can change yield. A different extraction kit can alter purity. A homebrew buffer can be fine, but only if someone has compared it with the original on the same samples. Ask for a bridging check: old reagent versus new reagent, same samples, same day, ideally same operator and same instrument. It does not need to be a full validation study. It does need to show that the assay still answers the question you are asking.

If the substitution is permanent, update the method and record why. If it is temporary, label it. The dangerous state is a permanent substitution that everyone treats as temporary because nobody wants to own the change.

The bench rehearsal

Run a small transfer verification before the assay becomes routine. Use samples that span the range you care about, plus a reference material if one exists. Include at least two operators if the assay will be run by more than one person. Compare against the originating lab's results or against the expected performance. Check controls, repeatability and the decision threshold. Do not call an assay validated because it worked once. In research terms, call it verified for your purpose. In an accredited or clinical setting, follow your quality system and change-control process. A transfer is not automatically fit for purpose.

The handover conversation

Ask open questions and write down the answers. What do you do that is not in the protocol? What breaks most often? Which step do new people get wrong? Which reagent do you actually use? What would you change if you had the budget? The answers are not complaints. They are tacit knowledge, and they are cheaper to capture now than to rediscover during a audit.

Give the transferred assay an owner, a review date and a one-page shadow protocol. Keep it next to the formal SOP. Fields should include method version, source lab, equipment settings, reagent catalogue and lot, water grade, environmental notes, operator steps, known failure modes, control acceptance, bridging data and the person to call when it drifts. This is not bureaucracy. It is memory.

When to stop calling it transferred and start calling it yours

Red flags include no raw data, no lot traceability, a method that depends on one person, equipment you do not have, a discontinued reagent, or performance that drifts near your decision threshold. If any of those appear, pause. A transferred assay can be a useful starting point and still be a poor fit for your lab. The audit is how you tell the difference before the method quietly becomes the new standard.

A transferred assay is a relationship, not a file. Treat the handover as a conversation, test the bits that matter, and write down the shadows. Your future self, and the next new starter, will thank you.