The Evidence Chain Is the Product

by Priya NairClinical and Regulatory Correspondent, HMND

Cell and gene therapy flexibility looks generous on paper until someone has to prove what happened to one batch, in one room, at one time, across the software stack that carried it. The past week’s guidance pressure keeps pointing to the same fault line, where manufacturing reality meets the record that claims to describe it.

The batch record carries the case

FDA’s 2026 flexibility language makes the point plainly enough for anyone still selling slogans: sponsors may justify fewer PPQ lots, and in some cases batches can be designed for concurrent release, but only inside a structure that still has to stand up as CMC evidence. The batch record, then, becomes the argument, because release decisions, deviation handling, and later comparability all hang off what that record can show and when it can show it.

A clean release file is doing more than listing assay results. It is tying identity, dose, viability, in process controls, and the release certificate to a contemporaneous history that can survive review without a person in QA needing to reconstruct the day from three different screens and a memory that is already tired.

Where the handoff breaks

Picture a manufacturing floor at 11:40 p.m., an autologous run sitting in hold because the deviation lives in one quality module, the electronic batch record sits in another, and the lab system has the potency result in a state that nobody can call final without a second pass. The people are not careless. The systems are fragmented.

That is where flexibility turns sour. A sponsor can promise faster access and a leaner PPQ story, but the promise collapses if the CMC system of record, the electronic batch record layer, and the deviation workflow do not agree on version, status, and ownership at the moment a release decision is made. The result is an inspection trail with holes in it.

Validation is the quiet gatekeeper

Validated software is a small phrase with a large appetite. FDA’s guidance and the surrounding industry commentary keep coming back to the same demand, that release tests, manufacturing records, and the systems carrying them must be attributable, contemporaneous, accurate, and auditable, which is a modest sentence until you have to prove it after an interface failure or a late data correction. The security boundary matters too, because once the quality record, the lab result, or the execution log crosses from one system to another, the handoff itself becomes part of the evidence chain.

Operators already know the trap. “The system is validated” can mean only that the pain was documented carefully. A better question is whether the master batch record, the MES or EBR, the LIMS, and the QMS share a controlled identity and a controlled state model, so that a late deviation, a re test, or a release override cannot drift off into a side channel that looks tidy on a dashboard and ugly in an audit.

The hard part is not agility. The hard part is owning the interface where science hands off to software and software hands back a claim about a product that may already be on its way to a patient.

If that interface is sitting on your desk, hello@example.com is where the conversation starts.