Why a Governance Charter Must Be Operational
In an adaptive platform trial, governance decisions recur as the trial proceeds: a committee may review information, recommend an action, or make a decision within authority delegated to it. A charter is effective when committee members and other trial personnel can determine, from its text, who is responsible, what the committee may do, how it reaches a decision, and what happens next. General statements such as “the committee oversees the trial” are not enough to guide action when a decision is time-sensitive or disputed.
A charter is a governance document for a particular committee. It should fit within the trial’s applicable protocol, agreements, institutional policies, and regulatory requirements; it does not override them or create authority that has not been properly delegated. The earlier material on decision rights and delegation maps helps distinguish the authority assigned to a committee from responsibilities retained elsewhere. The earlier material on boundaries for independent oversight is also relevant: a charter should describe the committee’s role without collapsing independent oversight into sponsor or operational decision-making.
Before drafting, confirm the committee’s place in the governance structure and the source of any delegated authority. The charter should identify the document or authorized body from which the delegation comes, and it should state any material limits. If those sources are unclear or inconsistent, drafting precise-sounding language will not solve the underlying governance problem. Resolve the authority question first, then write the charter to express it.
From Purpose to a Usable Decision Process
A sound charter connects the committee’s purpose to the decisions and work it is expected to perform. Purpose answers why the committee exists. Scope identifies the matters it handles and those it does not. Authority specifies whether the committee advises, recommends, approves, or makes a decision within delegated limits. These verbs are not interchangeable. “Reviews and advises” should not be read as permission to approve an action.
A practical drafting test is to trace a decision from beginning to end. The committee needs a defined remit, an authorized decision-maker, adequate information, a valid meeting or other permitted process, a recorded outcome, and a route for anything outside its remit. This chain explains why a charter needs more than a list of committee duties: if any link is missing, participants may not know whether a decision is valid or what action follows it.
For example, a committee may be asked to review a proposal and make a recommendation, while another body retains approval authority. The charter should say who receives that recommendation, what information accompanies it, and whether the committee may act before approval. If it cannot approve the proposal, the minutes should not describe the recommendation as an approval. This is not merely a wording preference: the distinction protects accountability and prevents an operational team from acting on an ambiguous record.
State the committee’s purpose, subject matter, and explicit exclusions so that members can recognize when an item is outside scope.
Name the actions the committee may take, distinguish recommendations from approvals, and identify the source and limits of its delegation.
Describe membership, quorum, meeting procedures, voting or consensus rules, conflict handling, and the information needed to act.
Require a record of the outcome, rationale, dissent where relevant, responsible follow-up, and escalation of unresolved or out-of-scope matters.
Worked Example: Turning a Broad Purpose Into a Defined Remit
Hypothetical setting. A platform has an executive committee responsible for operational decisions. A proposed charter says only, “The committee oversees the conduct of the platform and makes decisions as needed.” This wording does not identify which decisions belong to the committee, which are reserved elsewhere, or what “oversees” permits.
Step 1: Identify the work the committee is intended to perform. Suppose its assigned role is to coordinate operational implementation of decisions already authorized by the proper decision-maker. That is narrower than deciding whether a treatment arm should be added or whether an efficacy conclusion is warranted.
Step 2: Separate activity from authority. “Coordinates implementation” describes work; it does not grant authority to approve the underlying action. The charter should identify the source of the implementation authority and state that approval of decisions outside this remit remains with the designated authority.
Step 3: Draft an operational clause. A more usable clause is: “The Executive Committee coordinates implementation of actions approved by the body holding the relevant decision authority, monitors assigned operational deliverables, and refers matters outside its delegated remit to the designated authority. It does not independently approve actions reserved to that authority.” The named body and source document should be inserted in the final charter rather than left implicit.
Check the clause. A member can now distinguish implementation from approval, and an operational team can identify where an out-of-scope proposal goes. The charter is still incomplete until it also specifies meeting, record, and escalation procedures, but the central purpose-authority ambiguity has been reduced.
Membership, Meetings, and Decision Records
Membership clauses should identify the roles needed for the committee’s work, how members are appointed, who chairs, and who may attend without voting. If a role is required for particular decisions, state that requirement. “Relevant experts will attend as needed” is difficult to apply consistently; a stronger provision names the roles or expertise required and explains who determines whether the requirement is met.
A charter should also state how a committee can conduct valid business. Define quorum in terms that can be checked: which voting roles must be present, how vacancies or recusals affect the count, and whether participation remotely counts. State how members receive meeting materials, how meetings are called, and whether urgent decisions may be made outside a meeting. If written or electronic decisions are permitted, specify how members are notified, how they register a vote, and how the result is recorded.
Choose a decision method deliberately. Consensus can support joint ownership but may become ambiguous if “consensus” is not defined or if one member’s objection prevents closure without a stated route forward. Voting can produce a clear result but requires a defined threshold and rules for abstentions and ties. A committee may use different methods for different kinds of decisions, provided the charter identifies the method for each and does not imply authority beyond the committee’s remit.
Worked Example: Making Quorum and Voting Unambiguous
Hypothetical setting. A scientific committee has seven voting members: a chair, two clinicians, two statisticians, and two patient representatives. The draft charter says, “A majority constitutes quorum, and decisions are made by consensus or vote.” It does not say whether “majority” means a majority of all members or those present, whether the chair votes, or how the two methods relate.
Step 1: Define the denominator. If quorum is a majority of the seven appointed voting members, the minimum is four, because \(7/2=3.5\) and a whole-number attendance count must exceed 3.5. The charter can state “at least four voting members” to avoid an interpretive dispute.
Step 2: Protect required representation. Suppose the committee’s approved governance arrangement requires at least one clinician and one statistician for scientific recommendations. The quorum clause should say so explicitly. With four members present, quorum would therefore require both the numerical threshold and those specified roles.
Step 3: Choose a decision rule. For this example, the charter could require an attempt at consensus, followed by a recorded vote if consensus is not reached. It should define the voting threshold, such as a simple majority of votes cast by eligible members present, and state how ties are handled. If a tie means no recommendation is made, the matter should be recorded as unresolved and referred through the stated escalation route.
Step 4: Check a meeting. If the chair, one clinician, one statistician, and one patient representative attend, the count is four and the required roles are present, so the defined quorum is met. If the vote is two in favor and two opposed, there is no simple majority. Under the proposed rule, the committee records that it made no recommendation and escalates the unresolved matter rather than reporting a decision.
This example assumes that the committee’s appointing authority has approved the membership and voting arrangements. A charter writer should not invent a quorum rule that conflicts with those arrangements.
Conflicts of Interest and Escalation
A charter should make conflict handling a routine part of committee procedure. At minimum, it should require members to disclose relevant interests, identify who receives and assesses disclosures, and specify how participation is managed when a conflict is identified. Possible measures include restricted access to an item, non-participation in discussion, recusal from voting, or replacement for that item. The applicable measure depends on the governing policy and circumstances; a charter should identify the decision process rather than assume that disclosure alone resolves every concern.
The charter must explain how a recusal affects quorum and the decision record. Otherwise, a committee may either proceed without a valid quorum or avoid documenting why a member did not participate. The record should state the relevant procedural action without disclosing unnecessary sensitive information. Members should also know how to raise a concern about another member or about the committee’s ability to act impartially.
Escalation is needed when an issue exceeds delegated authority, required quorum cannot be achieved, a conflict prevents valid deliberation, the committee cannot reach the required decision, or an urgent matter cannot wait for the ordinary process. A useful escalation clause identifies the trigger, the recipient, the material to be transmitted, a timeframe, and what happens while the matter is pending. It should not suggest that escalation automatically resolves the issue or transfers authority to an unspecified person.
Worked Example: Writing an Escalation Route for an Unresolved Item
Hypothetical setting. A committee must provide a recommendation within five working days. At its meeting, a declared conflict leaves only three eligible voting members, but its charter requires four for quorum. The committee therefore cannot make a valid recommendation at that meeting.
Step 1: Identify the trigger. The trigger is not simply disagreement; it is failure to meet the charter’s quorum requirement after conflict-related recusals. The minutes should state that quorum was not met and no recommendation was made.
Step 2: Name the route. Assume the governance structure designates the committee’s appointing authority to arrange a properly constituted review. The charter should name that role or body and provide a contact route, rather than saying only “refer the issue upward.”
Step 3: Specify the handoff and timing. The committee secretary transmits the item, relevant materials, attendance and recusal status, and the reason quorum was not met to the designated authority within one working day. The receiving authority must acknowledge receipt and determine the next permitted process before the five-working-day deadline.
Step 4: State interim handling. Until a valid decision is made, the committee must not treat the item as approved or direct implementation. If delay creates a safety or other urgent concern, the charter points to the applicable urgent reporting route. This clause creates a clear handoff without granting the recipient authority that has not been assigned.
Diagnostics, Alternatives, and Limits
Review a draft by testing it against realistic scenarios, not just by checking whether each heading exists. Can a newly appointed member tell what the committee may decide? Can the chair determine quorum after a recusal? Can the secretary tell how an urgent written decision is recorded? Can an operational team distinguish a recommendation from an approval? If the answer depends on informal custom or personal interpretation, the charter needs clearer language or a reference to a controlled governing document.
| Document or approach | Primary function | How it differs from a charter |
|---|---|---|
| Governance charter | Defines one committee’s remit, authority, composition, procedures, safeguards, and escalation | Integrates these arrangements for that committee |
| Decision-rights or delegation map | Shows which bodies hold or receive decision authority across the governance structure | Provides cross-committee allocation; the charter gives one committee’s operating detail |
| Standard operating procedure | Gives repeatable instructions for a process, often across multiple groups | Usually focuses on process execution rather than defining a committee’s mandate |
| Terms of reference | May describe a committee’s remit and membership | Terminology varies; confirm whether it includes the authority and procedural detail required of the charter |
The charter should complement, not duplicate or contradict, the protocol, delegation documents, agreements, and applicable procedures. It may refer to a controlled document for detailed workflows, but the reference should identify the document clearly and the charter should still state the committee’s essential authority and escalation route. A charter can establish clarity only within the authority and constraints of the documents above it.
Common warning signs include undefined verbs such as “oversee” or “manage”; no distinction between advisory and decision-making roles; quorum defined without handling recusals; consensus mentioned without a fallback; and escalation phrased as “as appropriate.” These phrases are not automatically wrong, but they become risks when they leave members unable to determine what action is valid. A final review should test the text against scenarios involving absent members, conflicts, ties, urgent requests, and out-of-scope proposals.
Check Your Understanding
Answer each question using the charter principles above. Solutions follow the questions.
- A charter says a committee “reviews proposals and provides approval.” What ambiguity should be resolved, and how?
- There are nine appointed voting members, and quorum is defined as a majority of appointed voting members. What minimum attendance is required? What else might the charter need to specify?
- A member recuses from an item, leaving too few eligible members for quorum. Should the committee vote anyway? What should happen instead?
- Give two details, beyond the phrase “escalate unresolved issues,” that an effective escalation clause should include.
- Why should a charter identify the source and limits of delegated authority instead of simply listing committee duties?
Solutions. (1) “Reviews” and “provides approval” may conflict: the text must clarify whether the committee advises, recommends, or has approval authority, and identify the source and limits of that authority. (2) A majority of nine is at least five, since more than 4.5 members are required; the charter should also specify required roles, how recusals affect quorum, and whether remote participation counts. (3) No. The committee should record that quorum was not met and no valid vote occurred, then use the specified escalation or reconvening route. (4) Examples include naming the recipient, stating a timeframe, specifying what records are sent, and defining interim handling while the issue is pending. (5) Duties do not themselves establish authority. Identifying the delegation source and limits helps prevent an advisory or operational role from being mistaken for approval power and makes out-of-scope matters traceable to the proper decision route.