Gather Workflow Facts Before Discussing a Contamination Concern

A lab lead calls you in a panic because a sample set came back contaminated, and the first question out of their mouth is "where did this come from." Answering that question before you have the facts is the fastest way to damage trust with a customer and to hand the lab bad information for its own investigation. The skill here is not diagnosing a source. It is running a fact gathering conversation that helps the laboratory move into its documented investigation process with better information than it had before you called.

Why This Conversation Goes Wrong

A contamination event creates pressure to say something confident right away. The lab lead is stressed, a run may be delayed, and they want an answer they can report up the chain. As a field application scientist, you feel that pressure too, especially if you know the platform well and want to sound competent. The trap is guessing at a cause from a single symptom, then having the lab act on that guess before real records confirm anything. Name a likely source based on incomplete information and you can send a team down the wrong path, delay the real fix, and leave your company on the hook when that guess turns out wrong. The right posture on this call is calm and specific, not fast.

How To Prepare Before You Respond

Before you say anything about cause, gather the observable facts. Ask what the team actually saw, not what they think it means. Ask when the issue was detected and during which run. Ask which materials, reagents, and lots were involved. Ask what changed recently in the protocol, the environment, or the staff on shift. Ask what records still exist.

1. What was observed, described in plain terms, not in terms of a suspected cause.
2. When the issue was detected and which run or batch it affected.
3. Which materials, reagents, and lot numbers were in use at the time.
4. What changed recently, including new staff, new equipment, or a modified protocol step.
5. What records survive, including shift notes, environmental observations, and preparation timestamps.

Do not treat missing records as a failure on the customer's part. A shift log that was not saved is simply a fact you both need to work around, not a mistake to point out. Your job is to help the lab find what does exist and route the review to the right owner, usually a quality lead or the research team running the study. If you have already worked with this customer on earlier planning, the approach in Plan a Discussion About Control Materials Around the Customer’s Study Design carries over here too. Gather the structure of the study before you talk about what might have gone wrong inside it.

What To Say On The Call

Keep your language plain and keep your uncertainty visible. State what you can and cannot say, then move straight into the questions.

The lab lead opens with, "Can you just tell us where this contamination came from." You answer, "I cannot point to a source from what I know right now, and guessing would not help your investigation. Let's capture what happened before we talk about why." The lead pushes back a little, "We need something to tell our director today." You say, "That's fair, and here is what we can hand them today. Walk me through what the team observed, when it showed up, and which lot of reagent was running." The lead describes the symptom and confirms the run number, then adds, "The shift handoff log from that night did not get saved." You respond, "That's still useful to know. Does the technician who ran that shift have a preparation record with a timestamp." The lead checks and comes back with, "Yes, she has that in her notebook." You close with, "Good. Get that record to your quality lead along with the run conditions we just listed. That gives them a real starting point for the investigation, and I will support whatever they need from our side."

Notice what the exchange does. It never assigns a cause. It separates what was seen from what might explain it. It names the next owner, in this case the quality lead, and it ends with a concrete next step rather than a technical conclusion you are not ready to make.

Mistakes To Avoid

The most common mistake is filling silence with a guess. If the lead goes quiet waiting for an answer, resist the urge to offer a theory just to have something to say. A second mistake is treating the fact gathering as an interrogation. Ask questions the way you would ask a colleague for help, not the way an auditor asks for evidence. A third mistake is skipping the handoff. Gather good information and then let the call end without naming who owns the investigation next, and the lab is left with data and no path forward. A fourth mistake is downplaying the urgency the lead feels. Acknowledge that they need to report something today, then show them what they can report, a clear set of facts, not a false conclusion.

How To Practice And Score This Conversation

A manager can build a practice case with details left deliberately incomplete, a missing log here, a contradictory timestamp there, so the trainee has to work for the full picture instead of assuming it. Score the trainee on three things. Did they separate observation from assumption in their own words. Did they ask for records in a way that reads as respectful rather than accusatory. Did they end the call by naming a clear next owner and next step rather than a diagnosis.

DealSpeak lets you run this exact scenario against an AI counterpart that plays a stressed lab lead, pushes back the way a real one would, and scores your response against those same three points. Pair it with the wider set of Biotechnology practice conversations and new field application scientists get a fuller picture of the calls they will actually take, from planning a study's control materials to handling a contamination scare mid study. The same discipline that helps you map intake before proposing a platform evaluation, covered in Map Sample Intake Before Proposing a Platform Evaluationapplies here too. Understand the situation before you propose an answer.

A contamination call will always feel urgent, and the lead on the other end will always want a fast answer. Give them something better instead, a clear record of what is known and a clear path into the lab's own investigation. That is more useful than a guess, and it is the version of this call that holds up once the real cause comes out.