The mistake was almost never substantive. The regulatory coordinators were correct on the merits. The mistake was linguistic.

Site leadership at most academic medical centers, community hospitals, and integrated health systems is composed of people whose careers were forged in clinical care, hospital operations, financial management, or institutional politics. Few of them came up through clinical research. Even fewer have read an ICH guideline. When a regulatory coordinator presents a request framed as "we are out of compliance with Section 2.2.2 of Annex 1," what the dean hears is "the regulatory person wants more headcount." The dean is not being callous. The dean is genuinely trying to allocate scarce resources, and nothing in the citation tells the dean why this request should outrank the catheterization lab's request, or the new electronic health record module, or the recruitment package for an oncologist.

The previous lesson examined how to define roles and allocate workflow within a regulatory team. Those structures are the substance the regulatory coordinator must now communicate. This lesson is about the communication itself: the translation skill that turns a regulatory imperative into a business case site leadership can act upon. An RC who cannot perform this translation will operate perpetually under-resourced, and — perhaps more painfully — will blame leadership for failing to see what was, in truth, never shown to them in a language they could read.

The mistake was almost never substantive. The regulatory coordinators were correct on the merits. The mistake was linguistic.

Site leadership at most academic medical centers, community hospitals, and integrated health systems is composed of people whose careers were forged in clinical care, hospital operations, financial management, or institutional politics. Few of them came up through clinical research. Even fewer have read an ICH guideline. When a regulatory coordinator presents a request framed as "we are out of compliance with Section 2.2.2 of Annex 1," what the dean hears is "the regulatory person wants more headcount." The dean is not being callous. The dean is genuinely trying to allocate scarce resources, and nothing in the citation tells the dean why this request should outrank the catheterization lab's request, or the new electronic health record module, or the recruitment package for an oncologist.

The previous lesson examined how to define roles and allocate workflow within a regulatory team. Those structures are the substance the regulatory coordinator must now communicate. This lesson is about the communication itself: the translation skill that turns a regulatory imperative into a business case site leadership can act upon. An RC who cannot perform this translation will operate perpetually under-resourced, and — perhaps more painfully — will blame leadership for failing to see what was, in truth, never shown to them in a language they could read.