Decision question and experiment protocol · Lesson 9

A working agreement between sponsor, analyst and operator

16 min read

Lesson objectives

  • Allocate responsibilities when a sponsor requests an urgent change during a preserved comparison.
Reading tools

Before the kickoff meeting, the sponsor sends a short request: obtain a quick result, then decide on expansion. The analyst understands data needs and the operator knows delivery capacity, but nobody has recorded who may change wording during the trial. A week later, staff receive conflicting instructions. The sponsor requests more messages, the analyst wants a stable intervention and the service lead stops a send suspected of exposing information. This lesson begins with that operational conflict. You will write an agreement identifying decision owners, consultation points and a safe path for necessary changes. The agreement supports responsible execution and must be understandable during a busy shift. Its value is whether the team can act appropriately when priorities differ.

Start with decisions rather than job titles. List what will happen: eligibility confirmation, allocation generation, message preparation, data-extract approval, result interpretation and expansion approval. Add urgent harm containment and nonurgent intervention changes. In a small team one person may hold several roles, but each decision still needs an identified owner. Ask who has information, who has authority and who executes the action. Staff may send messages without permission to alter the contact list. Analysts may calculate effects without authority to accept an economic loss. This distinction produces a clearer agreement than a long name table equating meeting attendance with ownership. Put a specific action beside each name so a substitute colleague can take over.

Make a change request evaluable before approval. State reason, affected component, people exposed and proposed timing. Record whether the requester has seen arm-level outcomes and whether eligibility, exposure or outcome definitions change. Correcting spelling without altering meaning differs from adding a guaranteed-seat promise. The new statement may need service and privacy review and may change the mechanism being measured. The analyst explains implications for the question and comparison; the operator explains whether parallel versions or a uniform transition can be delivered. The authorized person decides after these consequences are visible. Preserve earlier and later versions so reviewers can identify what each cohort received rather than infer a stable intervention from one unchanged project title.

Specify which information each role needs and when. Eligibility staff may need request details without seeing the next arm. A safety lead may need complaint counts and sufficient detail for containment without receiving a daily efficacy dashboard. The sponsor may need recruitment progress and follow-up dates while repeated inspection of the benefit contrast remains governed by the plan. Organize information around tasks, recording who sees what, when and why. Review these needs when responsibilities change or a risk emerges. If someone receives information outside their intended role, log what was seen, its timing and possible consequences. That record supports interpretation of subsequent changes instead of treating early inspection as though it never occurred.

Stopping authority needs a specific testable action. “Tell the manager” may be too slow during an active disclosure. State who disables sending, who verifies that it stopped and how minimum service continues. Define the next review time and restart conditions. An operator may pause a sending task while a system administrator must close a still-accessible link. Mapping the full effect exposes that difference before an incident. Use synthetic records to test stopping and retain the result against an explicit expectation. Also verify that current-service delivery remains available afterward. The rehearsal shows that containment is an operational decision with consequences, rather than a line in a plan assumed to work when needed.

Agree with the sponsor on what regular updates mean. Recruitment, record completeness, faults and schedule status can be reported without releasing the outcome contrast before its planned review. Use a short template so the sponsor knows what to expect. When extra analysis is requested, record purpose and timing before undertaking it. A legitimate request may consume resources needed for the primary extract. Show cost and schedule consequences, then let the authorized person prioritize. This differs from concealing an operational problem affecting study safety, which requires direct escalation under the agreement. Distinguishing the two reduces surprises and makes deferred essential work an explicit resource decision rather than a personal disagreement between analyst and management.

Separate checking arithmetic from accepting a management tradeoff. A colleague can verify net cost and denominators, while valuing user time may require sponsor judgment. A service owner can confirm operational feasibility without establishing effectiveness. Record the scope of each approval beside its owner. If everyone writes only “approved,” an unchecked calculation may be attributed to an administrative signature, or an analyst's view mistaken for operating permission. Use concrete descriptions such as checked denominators, authorized channel use or accepted extension cost. This makes a signature's consequence understandable and allows focused review when one component changes. It preserves role responsibility without exaggerating what was examined.

Review the agreement with those implementing it under pressure. A daytime analyst may understand it differently from a shift operator who misses meetings. Give the operator three brief requests: move sending time, remove a record following an objection and stop a defective link. Ask who has authority and what evidence is retained in each case. If several calls are needed merely to discover the decision owner, the agreement remains ambiguous. Clarify action names and contact routes before launch. Avoid adding signatures merely to feel reassured: each review needs a purpose and timeframe. A long chain may delay urgent containment without adding a useful check. Rehearse the authorized short path for serious risks and the normal path for changes that can wait.

Teams sometimes change while the trial keeps the same name. A new analyst needs the estimand, transformation rules, plan version and record of which results have been disclosed. They should distinguish descriptive findings from answers to the primary question. A new operator needs replay cases and observations, not only a general task list. They can run the pathway personally and document any difference requiring repair. Preserve limits of earlier evidence: an operator's success under developer supervision does not establish that a substitute can work independently. This does not require restarting every study. The agreement identifies changes requiring targeted verification and permits reuse of identical components with a record of who checked them, under which version and conditions.

Include a way to handle disagreement that remains after data review. If sponsor and analyst differ over acceptable uncertainty, the analyst records evidence strength and what remains unestablished. The sponsor chooses an action within their authority and safety constraints. The agreement need not turn every scientific judgment into an administrative decision or vice versa. A temporary action may retain current service until a more precise sample is available. Another may allow a limited verification with a review date where procedures permit. The distinction between acting under uncertainty and claiming the evidence resolved it should remain visible. Record material objections clearly and the reason for the subsequent decision. The institution can then learn if expectations fail rather than rewriting the agreement's history afterward.

Finish with a short daily-use agreement linked to details. Staff need the current procedure, revision identifier, escalation route and stopping point. Reviewers need a path from that short version to plans, records and changes. If two files conflict, specify the authority and reconciliation route before sending continues. Ask an unfamiliar colleague to find an answer. The time needed to locate the current version reveals a handover problem that your personal familiarity may conceal. Keep the operational presentation simple while retaining detailed evidence for authorized users. The agreement then becomes usable daily practice and preserves decision memory when people are absent or management priorities change.

Lesson summary

A working agreement between sponsor, analyst and operator.