IRT Commandment #11
I can’t believe I am writing about standards in IRT. It’s the kind of topic that makes me want to yawn. It feels so played out and obvious. It is on the agenda of every IRT conference.
But let’s look at them from a different angle: why we need them and how to avoid making them immutable or a barrier.
IRT Commandment #10
My experience has been that hard stops are almost always overridden when a patient is physically on site. It is in that moment that sponsors recognize the difference between the theoretical world of a written protocol and the real world in which sites and patients operate. This leads to panic and scrambling to override the system or initiate a manual intervention.
IRT Commandment #9
IRT systems exist to support sites in delivering care within the constraints of a protocol. The right drug for the right patient, at the right time, every time.
If a system slows a site down, adds unnecessary friction, or creates confusion, it is not just an inconvenience. It has real downstream impact.
Design with the site in mind. Remember the patient in the room.
Because when usability is sacrificed the system stops serving its purpose.
IRT Commandment #8
You can jeopardize the results of an entire study through inappropriate disclosure of participant treatment assignment.
Most people understand the obvious unblinding risks. Fewer recognize how often unblinding happens indirectly, through combinations of data points, access patterns, or operational shortcuts.
Protecting the blind is not just a system feature. It is a discipline requiring forethought and execution.
IRT Commandment #7
UAT is not just a technical exercise. It is a confirmation that the system is fit for purpose. That accountability belongs with the sponsor.
Even an IRT provider you trust, and who has provided good service, may still have an unconscious bias or built-in conflict.
That is not an accusation. It is simply human nature.
IRT Commandment #6
There’s a question that surfaces sooner or later in many studies:
“This patient was randomized in error; can you just remove them from the list?”
It sounds reasonable. It never is.
IRT Commandment #5
Reconciliation is a heavy resource activity that, under most circumstances, should not be undertaken.
This commandment is part of a larger, consistent story — using the IRT for its primary purposes (Commandment #1), understanding the meaning of the data (Commandment 3), and sending very little data to the EDC (Commandment #4). If you internalize those principles, this one becomes obvious.
IRT Commandment #4
When sponsors limit and standardize what flows between IRT and EDC, they gain consistency, stability, and predictability.
It has been my experience that when each study starts from scratch with determining what data points to send to EDC, you compromise timelines and quality for both IRT and EDC vendors
Consistency is not a luxury. It’s an accelerator.
IRT Commandment #3
In IRT, few misunderstandings create more noise — or more reconciliation work — than confusing Visit Dates with Transaction Dates. Too much time, too much money, and too many human hours are spent trying to force these two dates to match, as if difference automatically implies error.
It doesn’t.
IRT Commandment #2
This one might start a fight
I recognize my opposition to this practice is a bit controversial in the IRT space. This is primarily true because it is common practice and promoted by both sponsors and vendors.
IRT Commandment #1
Every good belief system starts with a first commandment — and in IRT, this is where most heresies begin. Before we debate integrations, reconciliation, or user experience, let’s start simple: what is IRT actually for?
The IRT system is to serve only its primary purposes
Why IRT Needs Its Own Commandments
These aren’t abstract principles. They’re lessons carved out of hard experience, regulatory findings, and trial-by-fire. Each one exists because I’ve watched what happens when it’s broken. Spoiler alert: it’s never good.