From Approved Decisions to Coordinated Operations
An adaptive platform trial can have shared procedures, systems, staff, and resources serving multiple treatment arms. A decision may be approved at the appropriate level yet still fail in practice if sites receive inconsistent instructions, shared systems are not updated together, or an arm-specific action disrupts a platform-wide process. An executive committee addresses this implementation problem: it coordinates operational work within authority that has already been delegated to it.
The committee is not a substitute for the steering committee’s strategic oversight, the sponsor’s responsibilities, or independent oversight. Nor is it automatically entitled to decide every question affecting more than one arm. Its remit depends on the platform’s approved governance arrangements. The earlier material on decision rights and delegation maps provides the basis for determining which body may decide, implement, or escalate a particular issue.
This definition separates three activities that can otherwise be confused. Making a decision means selecting an option where the committee has been given that right. Implementing a decision means arranging the approved work, such as issuing instructions, coordinating a system update, and checking completion. Escalating means referring a question to the body authorized to resolve it when the committee lacks authority or cannot safely implement the approved approach as written.
In practice, the executive committee may coordinate operational leads, representatives responsible for shared systems or supplies, and relevant arm teams. Membership and meeting frequency vary by platform. The important feature is not a particular job title or meeting schedule; it is a reliable route for identifying dependencies, assigning implementation tasks, and reporting whether those tasks were completed.
A Practical Test for Operational Authority
A useful way to check a proposed action is to treat the authority requirements as a conjunction: every condition must be met. This is an internal governance test, not a claim that every platform uses the same legal structure or terminology.
The logic is straightforward. If authority has not been delegated, an operational need alone does not authorize the committee to decide. If the action is outside the delegated scope, the committee cannot make it permissible merely by agreeing unanimously. If implementation would contradict an approved decision, the committee must not silently substitute a different policy. Finally, an action that disregards required safeguards or escalation conditions is not a valid implementation under this test. When all four conditions are satisfied, the committee can coordinate the action and document what it did.
The test also distinguishes a problem that can be handled operationally from one that needs a governance decision. For example, arranging a previously approved shared-system update may be implementation. Changing the underlying policy for that system may require a different authority. When the distinction is uncertain, the committee should identify the uncertainty, preserve the approved process where appropriate, and refer the question to the authorized decision-maker rather than treating urgency as a new delegation.
Worked Example: Coordinating an Approved Shared-System Update
Suppose a hypothetical platform has four active arms and an approved decision to move all arms to a revised central laboratory form on the same date. The executive committee has delegated authority to coordinate the rollout, but not to change the laboratory requirements. The planned sequence allows two business days for system configuration, one for validation, and one for distributing instructions to sites. The platform’s operations plan requires the rollout to finish at least six business days before the form is needed.
Check the schedule. The total planned rollout time is:
The schedule leaves \(6-4=2\) business days of contingency before the required date. The committee can assign the configuration, validation, and distribution tasks, then track their completion. The time calculation supports the operational plan; it does not authorize changing the approved form or its requirements.
Check the authority. The update is approved, coordinating the work is delegated, and the task is within the committee’s stated scope. If validation fails, however, the committee should not declare the form acceptable merely to preserve the schedule. It should follow the approved contingency or escalation route. Thus, the committee coordinates implementation but does not convert a failed safeguard into a successful approval.
Handling Issues That Cross Arm Boundaries
A cross-arm issue is an operational problem in which a shared process, resource, system, or instruction affects more than one treatment arm. Examples include a data-capture change that applies platform-wide, a shared laboratory delay, or competition for limited site capacity. The committee’s first task is to establish the scope of the issue: which arms and processes are affected, what approved procedures apply, and whether a single operational response can address the issue without changing arm-specific requirements.
A consistent triage process helps avoid two opposite errors: leaving a platform-wide problem to separate arm teams that may respond inconsistently, and allowing the executive committee to assume decision rights simply because several arms are involved.
Record the affected process, arms, sites, participants or data, and the time sensitivity. Separate verified facts from assumptions.
Identify the approved procedure or decision that applies. Check whether the committee’s delegation covers the operational response being considered.
If the response is within scope and follows the approved instruction, coordinate it. If the response would change a decision, exceed delegated authority, or trigger an escalation condition, refer the issue to the authorized body.
Assign an owner and due date, record the actions and communications, and check whether the issue was resolved consistently across affected arms.
Worked Example: A Shared Site-Capacity Shortfall
In a hypothetical week, one site has 10 appointment slots available for platform visits. Its approved schedule requires 4 slots for Arm A, 3 for Arm B, 2 for Arm C, and 1 for Arm D. A facility problem makes one slot unavailable, leaving 9. The executive committee is delegated to coordinate scheduling, but the approved plan specifies that arm teams must use an escalation route if required appointments cannot be accommodated.
Calculate the shortfall. The planned demand is \(4+3+2+1=10\) slots. Available capacity is 9 slots, so \(10-9=1\) required slot cannot be accommodated under the current schedule.
The committee can confirm the capacity count, notify the affected operational leads, and apply any approved scheduling contingency. If no contingency permits the required visits to be rescheduled safely, the committee must use the specified escalation route. It should not decide on its own which arm loses the slot unless that choice is explicitly within its delegated authority and consistent with the approved policy.
The arithmetic identifies the size of the operational problem; it does not determine whose visit should be displaced. Keeping those questions separate prevents a capacity calculation from being mistaken for a governance authorization.
Monitoring Implementation and Detecting Failure
An executive committee needs enough information to tell whether an approved action has been implemented as intended. Useful operational indicators may include completion dates, the number of sites still awaiting an instruction, unresolved system defects, or the frequency of inconsistent procedures across arms. These measures are not automatically evidence about treatment effects. They are tools for monitoring execution and deciding whether an issue needs correction or escalation.
For indicators to be useful, their definitions and action thresholds should be agreed in advance where feasible. A threshold is a trigger for review or action under the governance process; it is not a universal standard. The committee should also check the denominator and time window. For example, a count of late sites is hard to interpret without knowing how many sites were expected to complete the task and by when.
Worked Example: Detecting Inconsistent Data Coding
Suppose a hypothetical shared data check reviews 120 records from several arms and finds 18 with an inconsistent coding field. The approved operational procedure requires escalation if more than 5% of reviewed records have the inconsistency. The executive committee is authorized to coordinate data-quality follow-up and to apply that escalation rule, but not to redefine the field’s meaning.
Calculate the observed rate.
Because 15% exceeds the stated 5% trigger, the committee should follow the procedure: document the finding, coordinate the authorized data-quality checks, and notify the designated decision-maker. The comparison is \(15\%>5\%\); no statistical test is needed to apply this hypothetical operational threshold.
If the records come disproportionately from one arm or site, the committee should report that pattern rather than describing the problem as uniform across the platform. It should also verify whether the 120 records were selected and coded as the procedure requires. A rate calculated from the wrong records or an unclear denominator may give a misleading operational signal.
Warning signs that coordination is failing include repeated missed deadlines without an owner, different instructions reaching different arms, decisions being implemented before their approval is confirmed, and recurring issues that are discussed but not closed. A useful record should make it possible to reconstruct the issue, authority check, assigned action, due date, completion evidence, and any escalation. Documentation supports continuity when personnel change and helps distinguish a delayed task from a decision that was never authorized.
Comparing Coordination Routes
No single body should be used for every problem. The appropriate route depends on whether the issue is an implementation task, a strategic question, a sponsor responsibility, or a matter assigned to an independent oversight function. The following distinctions are functional; actual delegations must be checked in the platform’s governing documents.
| Route | Best suited to | Boundary to preserve |
|---|---|---|
| Executive committee | Coordinating approved operational work across arms and monitoring completion | Cannot exceed its documented delegation or replace an approval it does not hold |
| Separate arm teams | Carrying out arm-specific tasks within common platform procedures | Should not create inconsistent responses to a shared issue |
| Steering committee | Strategic oversight and decisions assigned to that body | Operational urgency does not make the executive committee a substitute for strategic approval |
| Sponsor or other authorized body | Responsibilities and decisions assigned to the sponsor or another governance authority | Operational coordination does not transfer accountability |
| Independent oversight route | Matters assigned to a genuinely independent oversight function | The executive committee should not absorb or direct independent judgments |
A decentralized approach can be efficient for routine tasks confined to one arm, especially when the procedure is clear. It is less reliable when several arms depend on the same system or when local actions could conflict. Central executive coordination can reduce duplication and inconsistent communication, but it can also create bottlenecks or blur decision rights if every minor task is sent to the committee. Delegation should therefore permit routine implementation at the appropriate operational level while reserving cross-arm coordination and escalation for issues that warrant it.
Common Mistakes and Limitations
- Wrong reasoning: “This problem affects several arms, so the executive committee can decide it.” Correction: Cross-arm reach makes coordination important, but authority still depends on delegation, scope, and applicable approval requirements.
- Wrong reasoning: “The decision was approved, so any action taken to implement it is acceptable.” Correction: Implementation must remain consistent with the approved decision and meet required safeguards. If the approved approach cannot be carried out as written, escalate rather than silently changing it.
- Wrong reasoning: “A missed deadline is just a scheduling issue.” Correction: First determine whether the delay changes what is approved, creates a safety or data-integrity concern, or triggers an escalation condition.
- Wrong reasoning: “One shared procedure means every arm must receive the same operational instruction.” Correction: Coordinate platform-wide elements consistently, but preserve approved arm-specific requirements where they differ.
An executive committee cannot remove uncertainty from unclear delegations, guarantee that sites will follow instructions, or resolve every disagreement among platform participants. Its effectiveness depends on accessible governance documents, timely information, named implementation owners, and a clear route for issues beyond its remit. Operational measures can reveal implementation problems, but they do not themselves confer authority to change trial policy.
Check Your Understanding
Answer each question, then compare your reasoning with the solutions below.
- A shared platform instruction is approved, and the executive committee is delegated to distribute it. What must the committee verify before coordinating distribution?
- A platform has 8 shared appointment slots available and 3 arms require 3, 3, and 3 slots. What is the shortfall, and does the arithmetic alone authorize the committee to select an arm whose appointment will be delayed?
- A hypothetical operational trigger is 4% inconsistent records. In a review of 250 records, 15 are inconsistent. Calculate the rate and state the appropriate response if the committee is delegated to apply the trigger.
- Why is it a mistake to conclude that an executive committee may decide an issue solely because the issue affects multiple arms?
- Name two indicators that could help the committee detect poor implementation, and explain one limitation of each.
Solutions. (1) Verify that distribution is within its delegation, that the instruction is the approved one, that the intended recipients and timing are clear, and that any required safeguards or escalation conditions are met. (2) Required capacity is \(3+3+3=9\) slots; the shortfall is \(9-8=1\) slot. The arithmetic identifies the gap but does not authorize choosing which arm is affected; the committee must use an approved contingency or escalation route. (3) The rate is \(15/250\times100\%=6\%\). Since \(6\%>4\%\), the committee should apply the specified trigger, document and coordinate the authorized follow-up, and escalate as required. (4) Cross-arm scope creates a need for coordination, not automatic decision rights; the committee must check its delegation and refer decisions outside that scope. (5) Examples include the number of sites still awaiting instructions and the proportion of required system updates completed by a due date. The first can omit how many sites were expected to act; the second can conceal uneven completion across arms or sites, so definitions, denominators, and time windows matter.