But consider what that simple request means at a site running 14 active studies with the same principal investigator. If the CV is filed in every study's regulatory binder -- the approach many sites take by default -- the site maintains 14 copies of one document. When the investigator adds a new publication or board certification, someone must update all 14 copies. When the IRB for one study requests the current CV during continuing review, the version in that study's binder must match the version in all the others. And when a new study opens with that same investigator, a 15th copy is created, filed, and added to the coordination burden.

Multiply this across every record that is not unique to a single study -- laboratory certifications, equipment calibration records, medical licenses, institutional standard operating procedures, facility documentation -- and the scale of the problem becomes clear. A site with 14 studies is not managing 14 filing systems. It is managing 14 filing systems plus a shadow layer of duplicated records that must be synchronized across all of them, with no architectural framework governing how that synchronization works.

This is the problem that the distinction between study-level and site-level records solves. And it is, in my view, one of the most underappreciated architectural decisions a regulatory coordinator makes -- because the consequences of getting it wrong are not dramatic. They are chronic. The site does not fail an inspection over a misclassified CV. It slowly accumulates version discrepancies, wastes coordinator hours on redundant filing, and creates an infrastructure that grows more fragile with every study added to the portfolio.

But consider what that simple request means at a site running 14 active studies with the same principal investigator. If the CV is filed in every study's regulatory binder -- the approach many sites take by default -- the site maintains 14 copies of one document. When the investigator adds a new publication or board certification, someone must update all 14 copies. When the IRB for one study requests the current CV during continuing review, the version in that study's binder must match the version in all the others. And when a new study opens with that same investigator, a 15th copy is created, filed, and added to the coordination burden.

Multiply this across every record that is not unique to a single study -- laboratory certifications, equipment calibration records, medical licenses, institutional standard operating procedures, facility documentation -- and the scale of the problem becomes clear. A site with 14 studies is not managing 14 filing systems. It is managing 14 filing systems plus a shadow layer of duplicated records that must be synchronized across all of them, with no architectural framework governing how that synchronization works.

This is the problem that the distinction between study-level and site-level records solves. And it is, in my view, one of the most underappreciated architectural decisions a regulatory coordinator makes -- because the consequences of getting it wrong are not dramatic. They are chronic. The site does not fail an inspection over a misclassified CV. It slowly accumulates version discrepancies, wastes coordinator hours on redundant filing, and creates an infrastructure that grows more fragile with every study added to the portfolio.