Why Decision Authority Must Be Explicit
An adaptive trial may require an interim review followed by a decision about continuing, stopping, or modifying part of the study. Even when the statistical rule is fully prespecified, the documents must make clear who sees the relevant information, who interprets or recommends action, and who can authorize that action. If those responsibilities are left implicit, a sound design can still be implemented inconsistently or expose confidential interim results to people who should remain blinded.
This tutorial focuses on documenting those responsibilities across the protocol, committee charter, and role specifications. It does not prescribe one universal committee structure. The appropriate arrangement depends on the adaptation, the information needed to assess it, the trial’s operational structure, and applicable regulatory expectations. The goal is a coherent chain of responsibility consistent with the prespecified adaptation rules.
Three Functions, Three Questions
A useful way to draft role language is to separate three functions. First, review: who receives which interim materials, and what is that person or committee expected to assess? Second, recommendation: who communicates a proposed course of action, and to whom? Third, authorization: who is empowered to approve implementation, subject to the protocol, applicable requirements, and any required approvals?
The distinction matters because reviewing confidential data does not automatically confer authority to change a trial. Similarly, a committee can be empowered to recommend stopping for safety without being the entity that formally authorizes the sponsor to stop enrollment. If a committee is intended to have binding authority, the governing documents should say so directly and define its scope rather than relying on vague language such as “the committee will decide.”
The protocol should explain the overall governance arrangement and its relationship to the prespecified adaptation. A committee charter can define the review body’s membership, information access, deliberation, and recommendation process in more detail. Role specifications can identify the responsibilities of particular functions—for example, the independent statistician who prepares the review output or the sponsor officer who receives a recommendation. Across documents, the same action should not appear to have different owners.
| Function | Question to answer | Typical documentation detail |
|---|---|---|
| Review | Who examines the interim information? | Review body, data access, timing, and scope of review |
| Recommendation | Who advises what action should follow? | Whether advice is advisory or binding, and its recipient |
| Authorization | Who can approve implementation? | Named role or body, authority limits, and required conditions |
| Execution | Who carries out an authorized action? | Operational function responsible for putting it into effect |
Execution is included to prevent a further ambiguity: the person authorized to approve an action may not be the team that changes enrollment procedures or communicates with sites. This tutorial concerns how that responsibility is specified, not how subsequent decisions or their audit trails are recorded.
Specify Independence and Information Access
“Independent” should describe an operational arrangement, not merely a committee label. Documentation should explain how reviewers are separated from decisions that could be influenced by access to interim comparative results. Relevant details include whether members have operational responsibilities in the trial, whether they have financial or other interests that could affect impartiality, and how potential conflicts are identified and managed. Independence is evaluated in context; no single organizational chart proves it by itself.
The charter should define the information reviewers need to perform their task. For example, a review may require treatment-specific efficacy or safety summaries, while staff managing recruitment may need only an operational recommendation that does not disclose comparative results. The documents should distinguish those access levels and identify the function responsible for preparing and transmitting review materials. Access should be no broader than needed for the assigned task.
A role specification should also make clear what an information recipient may do with the information. A reviewer may assess whether a prespecified criterion is met; a statistician may run a specified program; an operational team may implement an authorized change without seeing the interim treatment comparison. Such boundaries protect the intended separation between review and conduct. The underlying statistical decision rule remains the one stated in the protocol and analysis documentation; assigning a reviewer does not grant discretion to invent a new rule.
Worked Example: Mapping Roles for an Interim Safety Review
Suppose a hypothetical trial has a planned review of unblinded safety summaries after 120 participants have completed the first four weeks of follow-up. The charter assigns review to an independent safety committee. The sponsor’s clinical operations team remains blinded to comparative safety summaries.
Review. The charter identifies the committee as the review body, specifies the four-week follow-up cutoff, and states that the independent statistician prepares and securely provides the treatment-specific summaries. This identifies both the reviewer and the information path.
Recommendation. The committee may recommend continuation, a pause, or stopping under the protocol’s safety framework. The charter states that recommendations go to the sponsor’s designated safety officer. It does not imply that the committee’s review role alone changes trial conduct.
Authorization and execution. The protocol states that the sponsor safety officer is the designated role to authorize a pause within the sponsor’s assigned responsibility, subject to applicable requirements. The clinical operations lead then carries out the authorized pause. The operations team receives the instruction needed to act, not the confidential comparative summaries.
This arrangement is coherent because each function has a named owner and each handoff is explicit. If the intended design instead gave the committee binding authority to pause enrollment, the documents would need to state that authority and define how it operates; the example’s sponsor-authorization arrangement should not be assumed to apply universally.
Align the Protocol, Charter, and Role Specifications
The documents serve different purposes, but they should describe one governance system. The protocol should state the adaptation and the essential allocation of responsibilities in a place accessible to the trial team and reviewers. The committee charter should elaborate the committee’s composition, remit, access, and recommendation process. Role specifications should assign practical duties to positions or functions, including who prepares materials and who receives recommendations.
Consistency is more important than repeating identical prose in every document. A protocol can refer to a charter for procedural detail, but it should not leave a material authority question answerable only by inference. Conversely, a charter should not appear to override the protocol’s prespecified adaptation rule. Where a document uses a term such as “decision,” define whether it means a committee recommendation, a sponsor authorization, or a formal determination under a specified rule.
Worked Example: Resolving Ambiguous “Decision” Language
Consider a hypothetical protocol stating, “The independent committee will decide whether the study continues.” The charter says, “The committee will advise the sponsor,” while a role specification says that the sponsor’s trial director approves changes to enrollment.
Identify the conflict. “Will decide” suggests binding committee authority, but “will advise” makes the committee’s role advisory. The role specification assigns approval to the trial director. A reader cannot reliably determine who has final authority.
Resolve the intended arrangement. Assume the intended arrangement is that the committee reviews unblinded results and recommends continuation or stopping, while the sponsor’s designated officer authorizes implementation. The protocol can then say that the committee makes a recommendation under the prespecified criteria and that the designated sponsor officer authorizes implementation, subject to applicable requirements. The charter can describe how the committee forms and communicates its recommendation. The role specification can identify the sponsor officer and the operational function that acts after authorization.
Check the result. The committee’s recommendation is not mislabeled as implementation authority; the sponsor’s authority is visible; and the operations function is not asked to decide based on information it does not receive. If the intended arrangement was instead that the committee’s determination is binding, the documents must consistently establish that different arrangement.
A Justification: Why the Role Chain Supports Reliable Implementation
The governance chain can be checked by tracing an action from the information to the person carrying it out. Let a prespecified criterion produce a review question; the reviewer evaluates the relevant evidence; the assigned body communicates a recommendation or determination; an authorized role approves implementation where required; and an operational function carries it out. Each transition should have an identifiable owner and a defined output.
This is a justification for explicit role documentation, not a statistical proof of trial validity. If a link is missing, the next role may have to infer whether it can act. If a reviewer is also responsible for operational outcomes that could be affected by the unblinded information, impartiality or blinding protections may be weakened. If authorization is assigned to nobody, a recommendation may be mistaken for an approved change. Making each link explicit reduces those ambiguities while leaving the prespecified statistical rule unchanged.
Identify the person or committee responsible for assessing interim information and state the scope of the review.
Specify who receives confidential interim results, who prepares them, and what information other functions receive.
Say whether the review produces advice, a recommendation, or a binding determination, and name the recipient.
Name the role empowered to authorize implementation and the function responsible for carrying it out.
Confirm that the protocol, charter, and role specifications do not assign contradictory powers or imply access inconsistent with the intended blinding.
Diagnostics, Alternatives, and Limitations
A practical diagnostic is to select each possible interim outcome—such as continue, pause, stop, or implement a prespecified modification—and ask the same questions: who reviews the evidence, who makes the recommendation or determination, who authorizes action, and who executes it? Then ask who receives the confidential information and who receives only an operational instruction. An unanswered question, two competing answers, or an implicit handoff signals a documentation gap.
Another diagnostic is to compare the verb used with the authority intended. “Reviews,” “advises,” “recommends,” “determines,” and “authorizes” are not interchangeable. If the committee is advisory, describing its recommendation as the final decision is misleading. If it has delegated binding authority, calling its output merely advice understates that authority. The documents should use precise verbs and describe any limits.
There are several reasonable governance approaches. A committee may make an advisory recommendation and leave authorization with the sponsor; a committee may have delegated authority for a defined action; or different bodies may handle safety and efficacy reviews. The choice should fit the design and applicable requirements. No single arrangement is automatically superior, and committee independence does not by itself establish that the adaptation is statistically valid or properly prespecified.
The principal limitations are organizational and jurisdictional. A role description cannot resolve a conflict of interest that is not managed in practice, guarantee that confidential information remains restricted, or substitute for required regulatory or ethics approvals. Nor can clear authority language repair a decision rule that is ambiguous or not adequately specified. Governance documentation supports implementation; it does not replace sound design, statistical justification, or applicable oversight.
Common Mistakes
- Equating review with authority. Wrong reasoning: “The committee sees the interim results, so it decides the adaptation.” Correction: access and authority are separate; state the committee’s assigned output and who can authorize action.
- Calling a body independent without explaining the arrangement. Wrong reasoning: “The charter uses the word independent, so the review is independent.” Correction: describe relevant separation from trial conduct, information access, and conflict management.
- Using “decision” without defining it. Wrong reasoning: assume every reader knows whether a decision is advice or approval. Correction: name the decision-maker and distinguish recommendation, determination, authorization, and execution.
- Giving operational staff unnecessary interim detail. Wrong reasoning: “Everyone implementing the change needs the full review packet.” Correction: provide the information needed to execute the authorized action while protecting confidential interim results where appropriate.
- Relying on one document to correct another silently. Wrong reasoning: assume the charter automatically resolves contradictory protocol wording. Correction: align the documents so the assigned authority is explicit and consistent.
Check Your Understanding
Answer each question, then compare your reasoning with the solutions.
- A committee reviews unblinded interim summaries and sends advice to the sponsor. Does that fact alone establish that the committee can authorize an enrollment change? Explain.
- A protocol says the committee “determines” whether to stop, while its charter calls the recommendation advisory. What is the documentation problem?
- Name two details that help make an independence statement meaningful rather than merely a label.
- Why might the operations team receive an implementation instruction rather than the committee’s full interim review materials?
- List the roles or functions that should be traceable from interim review through implementation.
Solutions. (1) No. Reviewing information and advising the sponsor do not by themselves confer implementation authority; the documents must identify who authorizes the change. (2) “Determines” implies a binding or final role, whereas “advisory” does not. The documents must state which arrangement is intended and align the language. (3) For example, specify separation from trial operations, identify relevant conflict-management procedures, and define access to interim information. (4) To provide what is needed to carry out an authorized action while limiting unnecessary access to confidential comparative results and protecting blinding. (5) Identify who prepares and reviews the interim information, who recommends or makes a determination, who authorizes implementation where required, and who executes it.