Define Method Handover Questions Before One Scientist Trains Another

A method handover sounds like a simple task, one scientist shows another how to run the assay, and everyone moves on. In biotechnology labs, though, that simple task carries real risk for a field application scientist. When you get pulled into training a new hire on your instrument or your assay kit, you can easily slide into becoming the instructor of record for a document that isn't yours to own. This post walks through how to have the handover conversation well, and how to define the questions that keep responsibility where it belongs.

Why the handover conversation goes wrong

A senior scientist leaves. A supervisor is anxious. The easiest thing for that supervisor to do is ask you, the field application scientist who trained the original scientist, to just repeat that training with the new hire. It sounds efficient. It is also the point where document ownership starts to blur. You did not write the laboratory's local procedure. You do not know which version is current, who approved it, or which steps deviate from your company's approved instructions to fit the lab's own equipment, timing, or staffing. If you agree to certify readiness or teach every step without asking who owns the local instruction, you take on liability that belongs to the laboratory's own quality system.

This pressure gets worse under deadline. A departure date is fixed, a new hire is anxious, and the supervisor wants one clean session that solves everything. Rushing past the ownership question does not save time. It creates a training record that nobody can defend later, and a new hire who cannot tell the difference between what the manufacturer instructs and what the lab decided to change on its own.

Prepare before you sit down

Walk into the handover conversation with a short list already built. Name the approved material you are prepared to teach from, the current version of the product instructions rather than an old printout someone kept on a bench. Identify who owns the local instruction in that particular lab, usually a quality liaison or lab supervisor, since that person is the one qualified to confirm a new hire's readiness under the lab's own process. Find out who the learners are and how much experience each one carries, because a scientist with five years of bench work needs a different session than someone in their first month. Pick one real workflow point to anchor the session, such as sample setup, instrument calibration, or result export, instead of trying to cover an entire protocol in one sitting.

This preparation does two things. It protects the customer's ownership of their own procedures, and it makes the actual training session sharper, because you are teaching to a defined point instead of narrating an entire workflow from memory.

What to say when the supervisor asks for everything

Picture a lab supervisor named Grace at a biotech company. Her senior scientist leaves Friday, and she wants coverage before the position sits empty. She says, "Our senior scientist walks out the door in two days. Can you just show the new hire exactly how to run every step herself?"

You do not want to say no outright, and you do not want to say yes to something you cannot own. You answer, "I can support training using our current approved materials. Before we schedule anything, tell me which local instruction is authoritative for your lab, and who signs off on the new hire's readiness under your process."

Grace pauses, then names her lab's written procedure and points to her quality liaison as the person who confirms competency. She also mentions two new hires, one with three years in a similar lab and one straight out of school. You respond, "That changes how we should run this. Let's pick one workflow point, sample setup is usually the highest value place to start, and I will walk both of them through the approved steps. Your quality liaison should sit in and note anything your local procedure handles differently, since that stays under your ownership, not mine."

That exchange does the real work of the conversation. It gets a document name, a named owner, and a defined scope, all before you agree to a date.

Mistakes to avoid

Do not agree to certify a new hire's readiness yourself. That decision belongs to the lab's own quality process, and putting your name on it creates a record you cannot back up later. Do not let a training session default to whatever printed steps happen to be on the bench. Ask for the current approved version before you teach from it, because outdated instructions cost more time to unwind than they save.

Do not treat one workflow point as a stand in for the whole protocol. If you cover sample setup and the supervisor tells the new hire that everything is now covered, correct that on the spot. Do not skip asking about the learners themselves. Training two people with different experience levels the same way wastes the more experienced person's time and rushes the newer one.

Do not close the session without a written record of what happened. A training date, the names of who attended, the workflow point covered, and the name of the person at the lab who owns follow up all belong in a short note, even an email, sent right after the session.

Practice the conversation and score it

The handover conversation is easy to get wrong the first time it happens live, because the supervisor's request feels reasonable and the pressure to just say yes is real. Run through it before you are in the room. A manager coaching a field application scientist can set up a roleplay where the supervisor pushes for a readiness certificate, then score the response against three things, whether the scientist named the approved material clearly, whether they asked who owns the local instruction, and whether they defined a real workflow point instead of promising full coverage.

A strong answer sounds like this, "We can review the approved materials together and plan a focused session on one workflow point. Your lab's designated owner is the one who evaluates local competency, and I will document what we covered so your team has a record." Anyone can talk through a customer conversation once. Rehearsing it against a live counterpart who pushes back, the way DealSpeak lets a field application scientist do, is what makes the boundary between your job and the lab's ownership feel natural instead of forced in the actual moment. Biotechnology practice conversations built around real scenarios like this one at Biotechnology practice conversations give you a place to run the roleplay before a supervisor ever asks you the question for real.

Handovers are not the only place where an unclear boundary turns into a liability problem. The same instinct to protect ownership and get specific about who is responsible for what shows up when you Lead a Recovery Review After a Missed Service Visitand again when a lab asks you to help them compare platforms and you need to Set Shared Criteria for a Platform Comparison Across Multiple Labs.

A handover conversation done well leaves the lab with a clear document trail and a new hire who knows exactly what was covered and what was not. Do the preparation, ask the ownership question early, and the session that follows takes care of itself.