At most well-organized sites, this is a 30-minute exercise. At this site, it takes the better part of a day.

The problem is not that the documents do not exist. They do. The problem is that each study's regulatory binder was set up by a different coordinator over a span of several years, and each coordinator organized the binder according to their own logic. In one study, IRB approvals are filed behind Tab 3. In another, they are in a section labeled "Regulatory Correspondence." In a third, they are in a folder within a folder on a shared drive, with no consistent naming convention, and the coordinator who created the folder structure left the institution 14 months ago.

The inspector waits. The site scrambles. And the regulatory coordinator -- the person who should have been managing the infrastructure that prevents this situation -- realizes that the site does not have a records architecture. It has 20 individual filing systems, each built independently, each reflecting one person's organizational instincts at a particular moment in time.

This lesson addresses the structural problem that scenario illustrates. Module 1 established what the site's records infrastructure must contain -- the essentiality framework, the obligations, the temporal patterns. This lesson begins Module 2 by asking the design question: how should those records be organized across a multi-study portfolio? The answer rests on three principles that, in my experience, separate sites that survive inspections comfortably from sites that survive them by luck: standardization, scalability, and retrievability.

At most well-organized sites, this is a 30-minute exercise. At this site, it takes the better part of a day.

The problem is not that the documents do not exist. They do. The problem is that each study's regulatory binder was set up by a different coordinator over a span of several years, and each coordinator organized the binder according to their own logic. In one study, IRB approvals are filed behind Tab 3. In another, they are in a section labeled "Regulatory Correspondence." In a third, they are in a folder within a folder on a shared drive, with no consistent naming convention, and the coordinator who created the folder structure left the institution 14 months ago.

The inspector waits. The site scrambles. And the regulatory coordinator -- the person who should have been managing the infrastructure that prevents this situation -- realizes that the site does not have a records architecture. It has 20 individual filing systems, each built independently, each reflecting one person's organizational instincts at a particular moment in time.

This lesson addresses the structural problem that scenario illustrates. Module 1 established what the site's records infrastructure must contain -- the essentiality framework, the obligations, the temporal patterns. This lesson begins Module 2 by asking the design question: how should those records be organized across a multi-study portfolio? The answer rests on three principles that, in my experience, separate sites that survive inspections comfortably from sites that survive them by luck: standardization, scalability, and retrievability.