Regulatory Coordinator

Full course · Inspection Readiness and Regulatory Quality Management

Portfolio compliance dashboards: maintaining visibility into regulatory status across all active studies — Inspection Readiness and Regulatory Quality Management

Portfolio compliance dashboards: maintaining visibility into regulatory status across all active studies

Teaches how to design dashboards that surface meaningful information (not just data), how to determine update frequency, and how to use dashboard data to drive resource allocation decisions. The dashboard is not a report -- it is a decision support tool.

22 min

The mental model breaks at scale

There is a threshold -- and in my experience it falls somewhere between six and ten active studies -- beyond which no regulatory coordinator can maintain an accurate mental model of where every study stands across every compliance domain. Below that threshold, a competent RC can hold it all in working memory: the amendment for Study 004 submitted last Tuesday, the delegation log update needed for Study 007, the overdue training documentation in Study 002. Above it, things slip. Not because the RC is careless or disorganized, but because the human capacity for simultaneously tracking independent status items has a ceiling, and 20 active studies across six regulatory domains produces 120 distinct compliance states. Nobody holds 120 items in working memory. Nobody.

And yet this is precisely the situation many RCs face. A busy academic medical center running 18 to 25 concurrent protocols expects a single regulatory coordinator -- or a small team -- to maintain visibility into all of them. The consequences of lost visibility are not abstract. A lapsed IRB approval is a protocol deviation. An expired delegation log entry means a staff member may be performing tasks they are no longer authorized to perform. A missed IND safety report deadline is a regulatory violation. These are not hypothetical risks; they are the predictable results of asking a human being to track more information than human cognition permits, without providing the tools to extend that cognition.

This lesson addresses that gap. Module 5 built the quality management system -- the SOPs, the metrics, the trend monitoring, the improvement mechanisms. Module 6 takes that quality infrastructure and applies it at portfolio scale. And the first requirement of portfolio-level quality oversight is visibility: the ability to see, at a glance, where every study stands and where attention is needed most.

The portfolio compliance dashboard is that visibility tool. But I want to be precise about what a dashboard is and what it is not. A dashboard is not a report. A report presents historical data for review; a dashboard presents current status for decision-making. A report is read carefully; a dashboard is scanned quickly. A report answers "what happened?"; a dashboard answers "what needs my attention right now?" This distinction matters, because the design principles for reports and dashboards differ fundamentally, and confusing them produces tools that serve neither purpose well.

What you will learn3 objectives

By the end of this lesson, you will be able to:

Design portfolio compliance dashboards displaying regulatory status across key domains for every active study, aligned with ICH E6(R3) Section 3.10.1.4 risk communication requirements
Apply visual hierarchy and exception-based design principles to surface compliance concerns requiring action rather than burying them in undifferentiated status displays
Evaluate dashboard data to make risk-proportionate resource allocation decisions per Principle 7, directing quality oversight attention to the studies and domains where compliance risk is highest

Progress saves itself — finish reading and this lesson completes

Continue with the Regulatory Coordinator track

The mental model breaks at scale