Not "why is it useful." Not "why do sites post it on job boards." Why does it exist as a distinct, named function -- a role with its own job descriptions, its own competency frameworks, its own career trajectory -- when as recently as the early 2000s, no one at most investigator sites carried that title or anything resembling it?

The answer is not that someone decided the job was important and created it. The answer is that operational reality made it inevitable. The regulatory environment grew so complex, trial volume at sites expanded so dramatically, and the consequences of regulatory failure became so severe that the work could no longer be absorbed by the people who had been handling it informally. The principal investigator could not do it. The clinical research coordinator could not do it -- not reliably, not at the scale that modern site operations demand. The work required its own person, its own systems, its own professional identity.

The previous three lessons established what the regulatory function is: the complete obligation set under E6(R3), the systems-level infrastructure that obligations demand at portfolio scale, and the layered regulatory frameworks that converge on the site's desk. This lesson asks how the function grew to the point where it required dedicated staffing. And that story unfolds across three regulatory eras -- each one adding weight that the existing site structure could not carry.

Not "why is it useful." Not "why do sites post it on job boards." Why does it exist as a distinct, named function -- a role with its own job descriptions, its own competency frameworks, its own career trajectory -- when as recently as the early 2000s, no one at most investigator sites carried that title or anything resembling it?

The answer is not that someone decided the job was important and created it. The answer is that operational reality made it inevitable. The regulatory environment grew so complex, trial volume at sites expanded so dramatically, and the consequences of regulatory failure became so severe that the work could no longer be absorbed by the people who had been handling it informally. The principal investigator could not do it. The clinical research coordinator could not do it -- not reliably, not at the scale that modern site operations demand. The work required its own person, its own systems, its own professional identity.

The previous three lessons established what the regulatory function is: the complete obligation set under E6(R3), the systems-level infrastructure that obligations demand at portfolio scale, and the layered regulatory frameworks that converge on the site's desk. This lesson asks how the function grew to the point where it required dedicated staffing. And that story unfolds across three regulatory eras -- each one adding weight that the existing site structure could not carry.