Why Governance Has Layers
An adaptive platform trial can evaluate several treatments over time while sharing some infrastructure, such as a common control group, data systems, or operational processes. That creates a governance problem as well as a design problem: a decision about one treatment may affect other arms, while a decision about one sponsor’s treatment may have consequences for shared platform operations. If the scope of authority is unclear, a scientifically sound decision can be delayed, inconsistently implemented, or applied beyond the remit of the people who made it.
Governance layers organize responsibility according to the scope of the decision. They are not simply ranks in a single chain of command. Platform-wide governance addresses shared trial arrangements; sponsor-level governance addresses a sponsor’s responsibilities and interests; treatment-arm governance addresses the conduct and evaluation of a particular arm. One decision can touch more than one layer, so a useful governance map shows how those scopes connect.
These definitions describe scope, not a universal allocation of every decision. A platform may have one sponsor or several; sponsors may also have different responsibilities under the applicable trial arrangements. The relevant protocol documents, agreements, governance terms, and applicable requirements determine who may decide and who is accountable in a particular trial. The map developed here is a way to make that allocation visible, not a substitute for those sources.
Scope, Authority, and Accountability
Three questions should be kept distinct. Scope asks what the decision affects: the platform as a whole, one sponsor’s responsibilities, or one treatment arm. Authority asks who is permitted to make, approve, or carry out the decision. Accountability asks who must ensure that the decision is properly considered, documented, and followed through, and who must answer for the relevant responsibilities.
Authority and accountability can connect without being identical. A person or group may be authorized to recommend an action, while a different role has approval authority. A task may be assigned to another party, while the sponsor retains responsibilities that cannot be transferred merely by assigning the task. The precise legal and operational effect depends on the applicable framework; a governance map should therefore record the actual allocation rather than infer it from job titles.
| Layer | Typical scope question | Illustrative subject matter | What the map should make explicit |
|---|---|---|---|
| Platform-wide | Does this affect shared rules, resources, or more than one arm? | Shared control arrangements, common data processes, or platform-wide operating assumptions | Which role can authorize a shared change, and who tracks its effects across arms? |
| Sponsor-level | Does this concern a particular sponsor’s responsibilities or treatment? | That sponsor’s contribution, product-related information, or required sponsor actions | Which sponsor role is responsible, and how does its decision connect to shared operations? |
| Treatment-arm | Is the issue limited to one arm’s conduct or evaluation? | Arm-specific implementation details or review of information about that arm | Who can act for the arm, and when must the issue be referred beyond the arm? |
The examples in the table are illustrative, not automatic assignments. For instance, a change that begins in one arm may affect a shared control or common procedures. Its immediate subject is arm-specific, but its consequences may require platform-wide review. Conversely, a platform-wide process can still require sponsor-level action to implement it for a sponsor’s treatment.
A Practical Method for Mapping a Decision
Start with a specific decision, not a committee name or an organizational chart. State what action is being considered, which people or trial components it could affect, and whether it changes a shared arrangement. Then record the roles that can propose, decide, implement, and monitor the action. Distinguishing these verbs prevents “involved in the decision” from being mistaken for “authorized to decide.”
Write the proposed action in concrete terms, including the trial component or process it changes.
Ask whether the consequences are confined to one arm, concern one sponsor’s responsibilities, or reach shared platform arrangements. Mark every layer that is genuinely affected.
Identify who may recommend, approve, implement, and monitor the action, and who remains accountable for the relevant responsibilities. Check those assignments against the trial’s governing documents and applicable requirements.
Confirm that affected layers are informed or involved as required, that no role is assumed to have authority solely because it has expertise, and that a route exists for unresolved or cross-scope issues.
The logic behind this method is traceability. If a decision has a consequential effect, the map should let a reviewer follow a complete path from the issue to the authorized action and the accountable follow-through. If the path stops at “someone on the trial team,” authority is not established. If a role is named as accountable but has no way to learn that the decision occurred, accountability may be nominal rather than operational. Checking scope first helps reveal these breaks before an action is taken.
Worked Applications
Worked Example: A Change to a Shared Control Process
Hypothetical situation. A platform evaluates three treatments against a shared control. The trial team proposes changing a shared procedure for assigning participants to the control group. The change is intended to improve operations but could affect comparisons in all three arms.
Scope. Although the proposed change arises during one operational discussion, its intended reach is shared. It therefore has a platform-wide scope. Each sponsor may also need to assess implications for its own responsibilities, and each arm’s conduct may be affected.
Authority and accountability map. The trial’s documented governance arrangements must identify who can authorize a change to the shared process. The relevant role responsible for implementing it should be named separately from the authorizing role. The map should also identify how sponsors are notified or involved when their responsibilities or trial contributions are affected, and who checks that implementation is consistent across arms.
Conclusion. It would be insufficient to treat this as an arm-level operational choice merely because one arm raised it. The shared effects call for the platform-wide connection to be checked. The example does not imply that a particular committee must approve the change; that authority must come from the trial’s actual arrangements.
Worked Example: New Information About One Sponsor’s Treatment
Hypothetical situation. A sponsor receives new information relevant to the treatment it contributes to a platform. The information may affect how that sponsor fulfills its responsibilities and could also have implications for the conduct of the corresponding arm.
Scope. The source and immediate responsibility are sponsor-level. The possible effect on one arm adds an arm-level connection. If review concludes that a shared platform process or other arms may be affected, the issue also reaches the platform-wide layer.
Authority and accountability map. The sponsor’s designated role must act through the applicable sponsor process. The map should separately identify who receives and evaluates the information for the arm, who can decide any change to arm conduct, and how a possible shared consequence is raised for platform-level consideration. No role should be assumed to have authority over another sponsor’s responsibilities simply because it coordinates platform operations.
Conclusion. The information should not be classified only by where it originated. Its consequences determine which additional layers must be connected. The sponsor-level origin remains important, but it does not settle every decision prompted by the information.
Worked Example: An Arm-Specific Operational Issue With Wider Consequences
Hypothetical situation. An arm’s recruitment team reports that a site cannot apply one arm-specific procedure as planned. The team proposes a local adjustment. The adjustment may be limited to that arm, but it could also change how the site applies a shared trial process.
Scope. If the adjustment affects only that arm and is permitted by the trial’s arrangements, its scope may remain arm-specific. If it changes a shared process or creates inconsistent treatment across arms, the issue has a platform-wide consequence as well. A sponsor-level connection is needed if the adjustment affects a sponsor’s own responsibilities.
Reasoning. The team should not decide scope from the location where the problem was noticed. Instead, it should compare the proposed change with the processes used by other arms. If the shared process is unchanged, the platform-wide link may not be needed. If it is changed, the map must show the relevant platform authority and how affected sponsor and arm roles are informed.
Conclusion. An arm-specific origin does not guarantee an arm-only decision. The scope follows the effects of the proposed action, subject to the authority specified in the governing arrangements.
Diagnostics, Alternatives, and Limits
A governance map is useful when it exposes ambiguous or disconnected responsibilities. Warning signs include an action with no identifiable approving role; multiple roles each assuming another will act; a sponsor-level responsibility assigned only to a platform coordinator without a documented basis; or an arm decision that changes a shared process without a route for broader review. Another warning sign is a map that names a role but does not say whether it proposes, approves, implements, or monitors.
There are two common but incomplete alternatives. A single-hierarchy view places every role in one vertical chain. It may clarify reporting lines, but it can obscure that an arm-specific issue and a sponsor responsibility have different scopes rather than simply different ranks. A committee-only view lists groups involved in oversight but may not clarify which group has authority, which sponsor remains responsible for its obligations, or how a decision is implemented. A layered scope map complements these views; it does not replace detailed decision-rights descriptions or formal delegation terms.
Governance layers also do not resolve scientific disagreements by themselves. They show where a question belongs and how it is connected to the relevant authority and accountability. They do not establish that a decision is scientifically justified, ethically acceptable, or compliant with applicable requirements. Nor do the labels “platform-wide,” “sponsor-level,” and “arm-level” have a single allocation that fits every platform. Roles, obligations, and approval routes must be verified for the specific trial.
The practical value of layered governance is therefore not more layers for their own sake. It is a clearer account of how a decision moves from the place where an issue arises to the roles authorized to act and accountable for follow-through. That clarity supports consistent operations and makes it easier to detect when a proposed change has consequences beyond its apparent source.
Check Your Understanding
For each question, identify the relevant scope and explain the governance connection. Brief answers follow the questions.
- A proposed change affects a shared process used in every arm. Which scope is directly implicated, and what else should be checked?
- Why are authority and accountability not interchangeable?
- A sponsor receives information about its own treatment, and the information may alter one arm’s conduct. Which layers may be involved?
- What is the weakness in assigning every issue to the arm where it was first noticed?
- Name one limitation of a committee-only governance list.
Solutions. (1) Platform-wide scope is directly implicated; check which sponsors and arms are affected, who can authorize and implement the shared change, and who monitors it. (2) Authority identifies who may act or approve; accountability identifies who must ensure responsibilities are met and answer for the relevant follow-through. (3) Sponsor-level and arm-level scopes are implicated; platform-wide scope may also be involved if shared arrangements or other arms are affected. (4) The place an issue originates does not determine the reach of its consequences, so cross-arm or sponsor responsibilities may be missed. (5) It may list participants without distinguishing who recommends, decides, implements, or remains accountable.