A Bioprocessing Technician Receives a Clinical Sample That Arrived Without Cold Chain Temperature Documentation. Standard Protocol Requires Rejection and Re-Collection. The Study Coordinator Says “Just Log It as Received and Process It — We Can’t Miss This Window.” What Does the Technician Do?

Quick Answer

When a clinical sample arrives without the required cold chain documentation, and a study coordinator instructs the technician to process it anyway, does following that instruction create a compliance violation?

Yes — in two distinct ways. First, processing a sample that should be rejected under the study protocol constitutes a data integrity violation: the results from that sample are based on a specimen whose chain of custody and storage conditions cannot be confirmed, rendering those results unreliable for their intended clinical purpose. Second, logging the sample “as received” in a way that obscures the documentation gap is falsification of study records — a GCP (Good Clinical Practice) violation with serious regulatory consequences. The study coordinator’s instruction doesn’t change either of those outcomes. Timeline pressure creates the motivation. It doesn’t change the regulatory or scientific reality of what processing an out-of-protocol sample produces.

Pressure Type: Study Timeline Urgency / Data Integrity Protocol

Clinical study timeline pressure creates a specific specimen integrity risk: the window for collecting a particular sample type — often tied to a patient’s dosing schedule, a biological cycle, or a visit protocol — is real and finite. When a sample arrives compromised, the study coordinator faces a genuine dilemma: reject the sample and lose the data point, potentially jeopardizing the study timeline, or process the sample and hope the integrity gap doesn’t affect results. “It’s probably fine” is the rationalization that turns a protocol requirement into a judgment call. The cold chain documentation requirement exists precisely because visual assessment of a sample cannot confirm whether temperature excursions occurred during transport.

The Leader’s Moment — The Study Coordinator

Clinical study coordinator Jennifer Walsh has spent three months coordinating a Phase II oncology study at a regional site. The enrollment is behind, and the sponsor is already asking about the timeline. Today, a critical pharmacokinetic sample arrived from a patient who drove 90 minutes for the visit. The courier’s temperature monitoring device didn’t log correctly during transport — there’s no documentation of the sample’s temperature during the two-hour journey.

Jennifer knows the rejection protocol. She also knows that this patient is one of only eight enrolled at this site, that re-collection at this time point is impossible, and that a missing data point from an already small enrollment will require a protocol amendment and sponsor notification. She calls the bioprocessing lab. “Log it as received and process it. We can’t miss this window. The sample looks fine, and it was only two hours.”

She is making a clinical judgment call that the sample is probably uncompromised. She doesn’t fully register that she is also asking the technician to falsify a study record.

The Technician’s Moment — The Receiving Lab

Bioprocessing technician David Park receives Jennifer’s call. He looks at the sample. It looks fine — proper color, no visible deterioration, still within the processing window. He looks at the receiving log. The cold chain field has no data. The study protocol he has posted in the receiving area specifies: samples without complete cold chain documentation must be rejected and flagged for protocol deviation reporting.

Jennifer is the study coordinator and has authority over study decisions. She’s asking him to process a sample that his protocol tells him to reject. He thinks: It probably is fine. She would know the clinical consequences of rejection better than he does. His job is to process samples, not to override clinical decisions.

He processes the sample and logs it as “received per protocol.” Six months later, during a sponsor audit, the auditor identifies a gap in the cold chain documentation. The study data from this sample is flagged. The investigation reveals the log entry. David and Jennifer both face GCP compliance findings. The sample data is excluded from the analysis.

Choice AProcess the sample and log it as received per Jennifer’s direction. She has clinical authority over study decisions. The sample looks fine. His job is processing, not overriding coordinators.

Choice BDecline to process and document the rejection per protocol — flagging it as a cold chain documentation deviation. Notify Jennifer of the rejection and the protocol deviation report. Offer to escalate to the lab director or sponsor medical monitor if Jennifer wants to request an exception through the proper protocol deviation process.

Choice CProcess the sample but log the cold chain documentation gap accurately — noting that the sample was processed despite missing documentation per coordinator direction. At least the record reflects the actual situation.

Choice ADirected processing as she did. She has clinical authority over study decisions and made a reasonable judgment that the sample was likely uncompromised.

Choice BContacted the sponsor medical monitor or lab director immediately to report the cold chain documentation gap and request an emergency protocol deviation decision — documenting the request, the response, and the clinical rationale in the study records. Any decision to process a non-protocol-compliant sample must be made through the protocol deviation process with sponsor authorization, not through an informal instruction from a coordinator to a technician.

Choice CAccepted the protocol rejection and documented it as a protocol deviation — notifying the sponsor, filing the deviation report, and working with the clinical team to determine whether a protocol amendment is needed to address the courier documentation gap going forward.

The Right Calls

For David: Choice B — Reject per protocol and document. Choice C is better than A but still creates a problem.

Choice A processes a sample that the protocol requires to be rejected — creating a data integrity exposure regardless of the sample’s actual condition. Choice C is better than A because at least the record is accurate, but processing a sample that should be rejected is a protocol violation, whether or not it’s documented accurately. Choice B follows the protocol, creates the correct documentation trail, and — critically — opens the door for Jennifer to pursue the legitimate exception process through proper channels. A protocol deviation request submitted to the sponsor medical monitor may result in authorization to use the sample, which is a legitimate path. “Just process it” is not.

For Jennifer: Choice B — Escalate to the sponsor immediately for a protocol deviation decision.

Choice A bypasses the protocol deviation process and replaces a documented sponsor decision with an informal clinical judgment call. Choice C accepts the outcome with proper documentation, which is honest but forfeits the possibility that the sponsor might authorize processing with appropriate caveats. Choice B is the right path: the study coordinator doesn’t have unilateral authority to override sample rejection criteria, but the sponsor’s medical monitor does — through the protocol deviation process — and a prompt call may result in a documented authorization that protects the sample’s usability, the data, and both David and Jennifer from GCP findings.

The sample probably is fine — and that’s exactly why the protocol exists.

Most samples that arrive with cold chain documentation gaps are probably within acceptable temperature ranges. The cold chain documentation requirement exists for the minority of cases where the sample was actually temperature-compromised, because visual inspection cannot distinguish between a compromised and an uncompromised sample in most cases. A protocol that applied only when the sample was obviously degraded would not protect the integrity of study data. The protocol applies to undocumented situations precisely because the risk is invisible.

“Just log it as received” is an instruction for record falsification, not a clinical decision.

Jennifer may have understood herself to be making a clinical judgment call about sample viability. What she asked David to do was log a sample “as received per protocol” when it was not received per protocol. That instruction is a request to create a false study record — regardless of the clinical judgment behind it. The distinction matters because the GCP violation David faces is not for processing a potentially compromised sample. It is for creating a false record of receipt.

The technician’s authority over their own documentation is absolute, regardless of the coordinator’s clinical authority.

Jennifer has clinical authority over study decisions within the protocol’s framework. She does not have authority over David’s log entries. A study coordinator can request that a sample be processed — they cannot instruct a technician to log it as received per protocol when it was not. The documentation is David’s responsibility and his compliance exposure. No coordinator instruction transfers that exposure to someone else.

Why is cold chain documentation required for clinical study samples, and what happens when it’s missing?

Cold chain documentation confirms that a biological sample was maintained within specified temperature ranges from collection through processing. For most clinical study biomarker and pharmacokinetic samples, temperature excursions above the acceptable range can degrade the analytes being measured — producing results that don’t reflect the patient’s actual biological state. Missing documentation means the sample’s temperature history is unknown. ICH E6(R2) Good Clinical Practice guidelines and FDA 21 CFR Part 312 require that samples be handled according to the protocol and that deviations be documented. Processing a sample without the required documentation or a documented sponsor authorization is a GCP deviation.

What is the protocol deviation process, and how does it apply to a sample with missing cold chain documentation?

A protocol deviation is any departure from the approved study protocol. When a sample arrives with a cold chain documentation gap, the study coordinator should immediately notify the sponsor’s medical monitor or clinical operations team, document the circumstances (arrival time, sample appearance, courier failure details), and request a documented authorization decision — which may include processing the sample with a protocol deviation note, rejecting the sample, or requesting re-collection if possible. This process creates a documented record of the decision, the rationale, and the sponsor’s authorization — which protects the data, the site, and the individuals involved.

Can a technician be held responsible for a GCP violation if they processed a sample per a coordinator’s instruction?

Yes. GCP compliance responsibilities are role-based and personal. A bioprocessing technician who creates a false study record — including a log entry stating that a sample was received per protocol when it was not — is personally responsible for that documentation, regardless of whether a coordinator instructed it. During a sponsor audit or FDA inspection, “the coordinator told me to” is not an accepted defense for a false record entry. The FDA’s enforcement discretion may focus on the coordinator, but the technician’s personal exposure is real. Declining to create a false record and documenting the deviation correctly is both the compliant and the personally protective action.

How to Use This Scenario in Training

Recommended for clinical study coordinators, bioprocessing technicians, laboratory staff, and CRA/CRM teams. Most effective when the study coordinator and laboratory technician audiences are trained together — the coordinator sees that their clinical authority does not extend to the technician’s documentation, and the technician sees that the coordinator may not have understood what they were asking. Cross-reference with the existing Biotech & Pharma compliance cluster for organizations building comprehensive clinical research compliance programs.

This scenario demonstrates the timeline-driven pressure applied to the data integrity protocol by the Decision Readiness Engine™. Decision-ready clinical staff recognizes that documentation integrity is a personal compliance responsibility that a coordinator cannot transfer — and that the protocol deviation process exists specifically to handle urgent situations in which an exception may be warranted with proper authorization.

More Safety & Hazard Compliance Scenarios