EU GMP names two people for every live computerised system, and both are roles that get refilled when the person leaves. The project to build that system has a champion instead, and I’ve watched projects dissolve with the champion while the business still needed the system.
Some pharma companies validate their systems with millions of pages, others with thousands, and the FDA passes both. The page count measures what the company believes compliance is. The inspector is grading something else.
A model vendor’s deprecation notice names the replacement and tells you to test against it before the retirement date, so every criterion written inside that window was written knowing the answer. Device regulators already settled what counts instead: criteria dated before the change.
Paper GMP records don’t allow an empty box: you cross it out, write N/A, initial it, date it. The database that replaced the form has a type for the empty box, and it spells four different absences the same way. Every count you run picks one of the four for you.
Warehouse operations checks its records against the shelf on a rotating schedule and knows its match rate. A data stack checks records against records, so it can agree with itself completely and still be wrong about what’s in the freezer.
Last month’s GxP post ended on an open question about agent-written changes swamping per-change assurance. Manufacturing hit that wall a hundred years ago and wrote down its answer, and the answer has an entry fee agent pipelines can’t pay yet.
The agent pitch prices a change by what it costs to produce. A validated GxP system never priced changes that way, and the regulated world already renegotiated the real price once, before agents showed up.
Storage is cheap, so the instinct is to keep everything. In a regulated shop that instinct is a second way to be out of compliance, because some records you’re required to destroy on a clock.
Every governance program is built to add definitions and none of them can retire one. In a regulated shop that gets worse, because the instinct to keep every record gets misread as a ban on ever deprecating a definition. They’re different objects.
The samples post ended on seating a data steward. This is what you build around that seat in a regulated life sciences org: the roles you actually need, the order to do it in, and why the regulation is the only budget argument that ever works.