Why the Interfaces Need Deliberate Governance
An adaptive platform may operate under a master protocol, add or close treatment arms, and involve more than one sponsor. Its governance must connect those operational changes to the ethics committees and regulators with authority over the relevant research, products, sites, or participants. If an arm changes, for example, the change may affect shared protocol text, arm-specific materials, participant information, and the submissions required in several jurisdictions.
Coordination can make these processes consistent and efficient, but it does not make an approval portable across authorities or move a sponsor's obligations to a platform committee. The practical task is to make clear who prepares, submits, tracks, communicates, and confirms implementation, while retaining the accountability assigned to each sponsor under applicable law and the trial's arrangements.
Separate the Authorities, Then Map the Work
Ethics committees review research from an ethical perspective, including matters such as participant protections and consent materials. Regulatory authorities may assess or authorize a trial, product, or change under their jurisdiction. The exact remit, submission route, terminology, and required sequence differ among jurisdictions; in some settings, functions or processes may be combined. A platform should therefore map the actual authorities and requirements that apply, rather than assume that one approval substitutes for another.
Begin with the trial's governance arrangements and applicable local requirements. For each relevant change or communication, record the authority, responsible sponsor, operational submitter, affected documents and sites, required decision or notification, and the evidence needed before implementation. A coordinating sponsor, secretariat, or regulatory operations team may assemble a common package or transmit it where permitted. Each sponsor should still be able to establish which obligations apply to its trial responsibilities and confirm that those obligations have been met.
This mapping complements, rather than replaces, the earlier material on amendment approval in master protocols and change control for platform documents. Those processes determine how a proposed change is governed and controlled internally. The external interface asks which ethics committees and regulators must receive it, through which route, and what must happen before the change is used at a site.
| Interface element | Governance question | Evidence to retain |
|---|---|---|
| Authority and jurisdiction | Which committee or regulator has a role for this trial, change, product, or site? | Applicable authority and jurisdiction identified in the submission plan |
| Accountable sponsor | Which sponsor is accountable for the relevant trial or product obligations? | Named sponsor and documented responsibility allocation |
| Operational submitter | Who prepares and transmits the package, and is that route permitted? | Submission assignment and transmission record |
| Decision and implementation | What decision, acknowledgement, or other condition is required before use? | Authority response and implementation clearance for affected sites |
| Communication | Who informs sites and other affected parties, and when? | Approved communication and distribution record |
A useful distinction is between accountability and task execution. A sponsor may assign a qualified team or service provider to prepare documents and make a submission. Such delegation can allocate work, but the sponsor should maintain oversight, know the status, address deficiencies, and ensure required obligations are fulfilled. A platform-level arrangement cannot by itself change the legal identity of the responsible sponsor.
Coordinate Packages and Decisions Across a Live Platform
A submission plan should connect the proposed change to every affected version and recipient. A platform-wide amendment might alter shared eligibility criteria or the master consent framework; an arm-specific change might affect only one intervention and its materials. Either may also require local adaptation. The fact that a change is classified internally as platform-wide or arm-specific does not, by itself, determine what an authority must receive.
For each affected jurisdiction, the team should establish the applicable route and timing, including whether a prior decision, notification, or other step is required before implementation. It should identify the exact document versions being submitted and the sites or participants affected. Approval or acknowledgement for one recipient must not be treated as evidence that all other required recipients have completed their review.
Identify whether it affects shared platform documents, a particular arm, sites, participant-facing materials, or more than one sponsor's responsibilities.
For each applicable jurisdiction, determine which ethics committee and regulatory authority must be engaged and what route and sequence apply. Confirm the assignment with the responsible sponsor and appropriate local expertise.
Use controlled document versions, check consistency among the protocol and related materials, and specify which arms and sites the change affects.
Record the operational submitter and accountable sponsor, submission date, authority correspondence, questions, responses, and outstanding conditions.
Check the required status for each affected authority and site under applicable requirements, then distribute the authorized version and document who has received it.
The justification for this sequence is straightforward. A change can be implemented safely and lawfully only if the relevant version is clear and the required external conditions have been satisfied. If the team instead distributes a version as soon as one recipient responds, the response may not cover other authorities, sites, or sponsors. Recording each dependency makes the readiness decision auditable and reduces the chance of an unapproved or inconsistent version entering use.
Worked Example: Adding an Arm in Two Jurisdictions
Suppose a fictional platform has sites in Jurisdictions North and South and sponsors A and B. Sponsor B proposes adding an arm at three North sites and two South sites. The proposed change modifies the master protocol, an arm-specific appendix, and participant information. No country-specific legal rule is assumed here; the sponsors must verify the actual requirements in each jurisdiction.
Map accountability and work. Sponsor B is identified in the governance arrangement as responsible for the new arm's relevant sponsor obligations. A platform secretariat can compile the shared protocol package and track transmissions if authorized to do so. The plan names the responsible sponsor for each submission, the permitted submitter, and the authority and sites concerned. The secretariat's administrative role does not make it the sponsor.
Map the recipients. The team checks which ethics committees and regulators have a role for each set of sites and whether any review or other step must occur before activation. It records those requirements separately for North and South. A response from an authority in North is not recorded as clearance for South.
Control the documents. The package identifies the same master protocol version and arm appendix for every intended recipient, with participant information adapted only where necessary and controlled as a distinct version. The submission log records which version went to each recipient and any questions or conditions.
Set the implementation gate. Before activating any site, the responsible sponsor checks the required decisions or other conditions for that site's jurisdiction and confirms that the site has the appropriate final materials. If one South review remains outstanding, the team does not infer readiness there from completed North steps. This conclusion follows from the scope of each recipient's authority and the recorded requirements, not from a general assumption that every change always needs the same sequence.
Communications, Exceptions, and Operational Diagnostics
External communication should have a clear path in both directions. The submission plan identifies who receives authority correspondence, who assesses its implications, who drafts a response, and who approves it for transmission. It also identifies who informs affected sites and sponsors of decisions or conditions. Where a question affects a shared document or multiple sponsors, the relevant governance route should reconcile the response without obscuring which sponsor is responsible for its own obligations.
Urgent situations require particular care. Applicable rules may provide specific routes for urgent changes intended to protect participants, or may set different reporting or implementation requirements. The governance plan should direct staff to the responsible sponsor and appropriate local expertise promptly. It should not assume that urgency creates a general exemption from review, notification, or documentation requirements.
Useful diagnostics are operational rather than merely procedural. Warning signs include a submission log with no named accountable sponsor; different protocol versions recorded as current by different sites; an authority question with no assigned owner; a site told to implement before required status is confirmed; or a platform office treated as the sponsor solely because it transmitted documents. Such discrepancies call for clarification and correction before the team represents a change as ready.
A common mistake is to reason, “The coordinating sponsor submitted the amendment, so all sponsors have fulfilled their responsibilities and every site may proceed.” That conclusion does not follow. Submission proves, at most, that a package was transmitted through a particular route. It does not establish that every relevant authority received the correct version, that required decisions or conditions were met, or that each sponsor has discharged its applicable responsibilities.
Choosing a Coordination Model and Recognizing Its Limits
A centralized model can use one coordination team to maintain a common document set, submission calendar, and correspondence log. This can reduce duplication and make cross-jurisdiction dependencies visible. Its weakness is that a single workflow may conceal local differences or leave sponsors uncertain about who is accountable. Centralization works only when local requirements, sponsor assignments, and escalation routes remain explicit.
A decentralized model gives each sponsor or local team more direct control over its submissions. That can support jurisdiction-specific expertise and clearer ownership, but it can also produce inconsistent versions, missed dependencies, or conflicting communications. A hybrid model often combines a shared platform package and tracker with sponsor-specific decisions and local confirmation. None of these models is automatically compliant or superior: the appropriate arrangement depends on applicable requirements, trial agreements, operational capacity, and the scope of the change.
Coordination also has limits. An internal tracker cannot replace an authority's decision, and a platform governance decision cannot override a requirement imposed by law or an approval condition. Nor does one sponsor necessarily control another sponsor's submission obligations. The interface is therefore a mechanism for clarity and reliable handoffs, not a substitute for competent local advice, sponsor oversight, or the authority's own remit.
Check Your Understanding
Answer each question using the governance principles above. Brief solutions follow the questions.
- A platform secretariat transmits a sponsor's amendment package. Does transmission alone establish that the sponsor's responsibilities are complete? Explain.
- A change has received a decision from the ethics committee serving one jurisdiction, while a required review in another remains pending. What should the team conclude about implementation in the second jurisdiction?
- Name two checks that help prevent a site from using an inconsistent amendment version.
- Give one advantage and one risk of a centralized submission-coordination model.
- An authority sends a question about a shared protocol document. What should the governance process establish before a response is sent?
Solutions. (1) No. Transmission is a task, not proof that all applicable obligations are fulfilled; the sponsor retains accountability and should oversee status and required follow-up. (2) The team must not infer readiness in the second jurisdiction from the first jurisdiction's decision. It should follow the second jurisdiction's applicable requirements and hold implementation there until the required conditions are met. (3) For example, reconcile the version identifier in the submission log with the controlled master document, and confirm that the site received the version authorized for its use. (4) Centralization can improve consistency and visibility of dependencies; it can also obscure local differences or accountability if sponsor assignments and jurisdiction-specific routes are not explicit. (5) The process should assign ownership for assessing the question, identify affected sponsors and documents, reconcile any shared-document implications, define who approves the response, and track its transmission and outcome.