Military units do not become inspection-ready when an inspection is announced. Justin Coffeen explains what that standard looks like applied to a regulatory binder, and why it is less work than the alternative.
What this episode covers
- Standard operating procedures as documented experience rather than arbitrary process
- Why the regulatory framework is the written record of what has gone wrong before
- Reporting timelines understood as decision windows, not deadlines
- Readiness as a continuous state rather than a periodic performance
A rule you understand is followed differently
A procedure that looks arbitrary gets complied with. A procedure whose origin is understood gets followed, which is a different behaviour under pressure.
Justin Coffeen’s account of standard operating procedures is that someone mapped what happens when a step is skipped, and wrote the procedure to prevent a repeat. The document is accumulated experience in compressed form.
Applied to research, that reframes the adverse event reporting timeline. It is not a deadline imposed on a site. It is the window in which a sponsor and a safety monitoring committee can still act on the information.
Readiness costs less than reconstruction
Maintaining a current regulatory binder, source documentation that reconciles with the case report form, and deviations addressed as they arise is steady, unremarkable work spread across the whole study.
Reconstructing all three under time pressure before an announced visit is concentrated, stressful, and produces a worse result, because some of what is missing cannot be recreated honestly at all.
Coffeen’s framing removes the distinction between being reviewed and operating normally. If those two states look different at a site, the difference is the finding.
Standards that survive nobody watching
The durable version of this is not procedural compliance. It is a standard the professional has adopted, which behaves the same whether or not anyone is checking.
That is the part Coffeen describes as genuinely transferable from a medical unit, and the part that no certificate establishes on its own.
For Justin Coffeen the standard is not that a site could pass an inspection if it had to. It is that an inspection arriving unannounced would find the site on an ordinary day.
Transcript
I get asked sometimes what the most transferable thing from my Air Force service was, professionally speaking. And my honest answer is this: it’s the ability to take a regulated framework seriously, not as a constraint you work around, but as the structure that makes the operation work.
In a military medical unit, the procedures exist because someone mapped out what happens when they’re not followed. That’s the origin of a standard operating procedure. It’s not arbitrary process. It’s documented experience. And once you understand that, you follow the procedure differently than you would if you were just complying with a rule someone wrote.
Clinical research has that same architecture. The GCP framework, the protocol structure, the adverse event reporting chains, the documentation requirements, these exist because clinical trials have a history. They have a history of what goes wrong when informed consent isn’t handled properly, what happens when safety signals get underreported, what the consequences are when source data doesn’t match the CRF. The regulatory framework is the documented version of those lessons.
So when I’m working on a protocol and there’s a reporting timeline for an adverse event, I’m not thinking about the deadline as a compliance checkbox. I’m thinking about why that timeline exists, which is that the sponsor and the safety monitoring committee need the information in time to make decisions about participant safety. That’s operational logic, not bureaucratic compliance.
There’s also the piece about being ready for inspection at any time, which the military drills into you pretty thoroughly. You don’t maintain readiness because an inspection is coming. You maintain readiness because readiness is the standard. And when I bring that to a research site, what it looks like in practice is: the regulatory binder is current today, the source documentation reconciles with the CRF today, the deviations are documented and addressed today. Not because a monitoring visit is next week.
I’m based in Lakewood Ranch, Florida, and the Air Force is part of my story in a real way, not as a credential but as an experience that changed how I think about what it means to operate inside a system that has rules for serious reasons.