Adaptable by Design: Preparing RTSM for Protocol Change 

Building RTSM Around the Reality of Protocol Change 

Clinical trial protocols provide the foundation for study execution, but they do not eliminate uncertainty. Future clinical decisions, emerging cohort requirements, evolving dosing approaches, and protocol-driven expansion opportunities can all shape where a study needs to go next.

For sponsors, the challenge is not only supporting what is defined at launch. It is designing an RTSM strategy that can support evolving protocol needs while maintaining operational continuity and governance.

With the right approach, flexibility can be designed in, not traded for control. Future states can be planned for and activated through a governed, validated pathway when the protocol requires them.

Designing for Growth Before Every Detail Is Defined 

At study startup, certain requirements are approved and clearly defined. Others may depend on decisions that have not yet been made, including cohort progression, dose selection, arm activation, or future protocol amendments.

Designing only for the current protocol state may appear efficient initially, but it can create dependencies later if expected changes require significant redesign. A more adaptable approach considers both what is known and what is reasonably anticipated.

The system needed to support where trials were likely to go next, not only what was defined at launch. That meant designing with several known areas of potential change in mind:

• Emerging cohort requirements 
• Evolving dosing approaches
• Future clinical decisions
• Protocol-driven expansion opportunities 

Rather than treating change as an exception, the design approach anticipated likely future states and created governed pathways for them. The objective was controlled adaptability: protocol-authorized, role-based, validated, audit-trailed, and change-controlled.

Configuration, Not Coding 

When a protocol amendment affects RTSM, the technical design of the system becomes particularly important.

If a protocol amendment requires code, the path can involve a new build, a new validation cycle, and a new risk window for a system already live.

Because the capability was configured, the later change became the activation of an option that was already validated, not a new release.

This was not a shortcut on validation. The validation happened earlier, for the range of likely futures, so adaptability became a property of the architecture rather than an exception to it.

In this model, a future arm, dose level, or workflow remains inactive until the appropriate authorization is in place. Activation can then follow the same governance framework as the rest of the RTSM environment, including role-based access, documented approvals, audit trails, and change control.

Purpose-Built Flexibility Without Sacrificing Control 

Flexibility and control do not need to be in tension. In a well-designed RTSM strategy, they can be built on the same foundation of validation, governance, and operational clarity.

Configurable RTSM capabilities can turn “configure it later” from an operational risk into a validated option from day one.

Flexible treatment arm assignment

Treatment arms, randomization structures, and future dosing strategies could be established independently, allowing future options to be built into the design and associated after approval.

Patient-level dose control

Patient-level dose control could support protocol-authorized dose changes through role-based access, centralized with the medical monitor in Phase 1 and shifting to sites as the study matured.

Configurable workflows 

Permissions, review pathways, audit visibility, and validation requirements should reflect the sponsor’s operational model. Configuration can help the underlying system adapt without weakening those controls.

A consistent site experience

Sites should not have to absorb unnecessary complexity simply because trial logic changes behind the scenes. Maintaining familiar and usable workflows can support more consistent execution as the study evolves.

Different Stakeholders, One System 

Across a clinical trial, different stakeholder groups often define “the system can’t slow us down” in different ways. Each group needs confidence that RTSM can support change without creating a different system for every operational need.

Medical monitors may need patient-level dose authority. Clinical operations may need protocol implementation speed. Biostatistics may need confidence in randomization and arm structure. Sites need one clear workflow, no matter what changes upstream. Supply and forecasting teams need integration that supports planning without unnecessary platform constraints.

Every stakeholder needed a different lever, without needing a different system. That is why the RTSM design had to align permissions, validation, audit visibility, and review pathways with sponsor operations.

A Closer Look: Phase 1 vs. Phase 3, Same Platform, Different Playbook 

The operating realities of an early-phase study can differ significantly from those of a global confirmatory trial.

In Phase 1, the study may involve small numbers, high stakes, and details that are not finalized at launch. Dose levels, cohorts, and arms may be undefined at build and activated as decisions land, with control staying centralized through the medical monitor.

In Phase 3, the structure is often more fixed, but scale and geography become the risk. A global confirmatory study may involve up to 20 countries and 200+ sites running the same protocol logic at once, with country activation, site activation, resupply, and forecasting operating at scale.

The design principle remains the same: RTSM should reflect how the study actually operates while providing controlled pathways for change. The configuration may differ across phases, but governance, traceability, and operational clarity remain central.

Operational Continuity as Clinical and Protocol Needs Evolve 

Success is not flexibility for its own sake. The goal is an RTSM strategy that can support diverse trial requirements while helping clinical and operational teams stay aligned as studies evolve.

A strong configuration-led approach can help reduce dependency on RTSM redesign, support controlled implementation of protocol changes, preserve operational continuity across amendments, and keep RTSM readiness aligned with clinical decision-making.

The result is greater operational continuity as clinical and protocol needs evolve. When likely future requirements are anticipated early, teams are better positioned to adapt without compromising governance, traceability, or control.

Three Lessons Learned 

1. Plan for Evolution

Design with expected future protocol scenarios in mind. By risk-assessing likely changes up front, teams can identify what should be configured early and what can be activated later through controlled pathways.

2. Govern Flexibility

Enable change through validation, permissions, auditability, and change control. Adaptability should remain part of the governed system architecture, not an exception to it.

3. Preserve Continuity

Maintain a stable operational framework as clinical and logistical complexity increases. Where possible, changes beneath the surface should not create unnecessary disruption for sites and other end users.

Building for Change Without Losing Control 

Clinical trials will continue to change as evidence develops and new decisions are made. RTSM cannot remove that uncertainty, but it can be designed to respond to it more effectively.

The strongest systems are not simply built for the requirements available on day one. They are built with an understanding of how the study may evolve, which decisions are likely to occur, and what governance will be required when they do.

By combining advance planning, configurable architecture, and controlled activation, sponsors can create an RTSM foundation prepared to support protocol evolution while maintaining the oversight, traceability, and operational discipline that clinical development requires.