
From task list to operating system: how regulatory operations differ from regulatory tasks
Establishes the conceptual distinction that defines the RC track: the difference between executing regulatory tasks for one study and operating the regulatory system for a site's full portfolio
The system that nobody built
Picture a site running a single Phase II study. The coordinator handling regulatory tasks keeps a personal spreadsheet with key dates: IRB continuing review due in March, annual safety report in June, the next amendment likely arriving in September. She sets calendar reminders two weeks before each deadline, pulls the required documents, assembles the package, routes it for the investigator's signature, and submits it to the IRB. The system -- if you can call it that -- lives in her head and in her calendar. And it works. It works well, in fact, because one study generates a manageable number of deadlines with predictable intervals between them.