Merging Phase 1 studies before Phase III
How a mid-size pharma sponsor used AIRA to consolidate two standalone clinical pharmacology studies into one integrated protocol - in days, not weeks.
The sponsor already knew the right strategic move was to merge the studies. The challenge was executing that merge quickly and cleanly - without weeks of drafting, inconsistencies across documents, or avoidable operational burden that could delay Phase III.
Not "should we merge?" - but "can we merge without chaos?"
Even with a scientifically sound plan, merging standalone studies typically creates:
- Weeks of drafting and reconciliation across protocols, schematics, and regulatory documentation
- High risk of inconsistencies - objectives, endpoints, SoA, eligibility, rationale, terminology - across sections and versions
- Misalignment across functions as feedback arrives in parallel across email threads, comments, and meetings
- Hundreds of hours of expert work for research, operational de-duplication, and protocol writing - often with multiple review cycles
If nothing changed, the sponsor risked:
- Extended timelines before Phase III
- Increased operational complexity from duplicated operational components
- Redundant site activation and recruitment effort
- Higher cost and higher protocol amendment exposure
A sequential, inconsistency-prone process
- Manual consolidation of multiple protocol schemas into one coherent structure
- Rebuilding a unified schedule of activities, then re-checking every section that depends on it
- Iterative, sequential reviews - clinical pharmacology → operations → regulatory → medical writing - each creating new inconsistencies
- Repeated research to confirm regulator-aligned language and expectations across the integrated design
The result is often weeks of drafting, plus multiple cycles of rework to restore internal consistency.
AIRA as an integration and authoring engine
Inputs uploaded into AIRA included: study schematics, regulatory correspondence and advice letters, regulator feedback, clinical pharmacology documentation (PK/PD rationale), and notes from Zoom meetings and reviewer comments.
Restructured the plan into a single integrated protocol
AIRA consolidated the program into one integrated protocol with multiple study arms, built around a unified schedule of activities - designed to preserve scientific integrity while removing duplicated operational steps.
Delivered a coherent first draft in days, not weeks
Instead of ~2 weeks to produce a first workable merged draft, AIRA produced a first integrated protocol draft in ~2 days, with consistent terminology and cross-section logic.
Kept the merge internally consistent as decisions evolved
AIRA continuously checked for coherence across objectives and endpoints, eligibility and exclusion criteria, SoA dependencies, and rationale language aligned to regulatory correspondence. When changes were approved, AIRA updated impacted sections consistently - reducing the typical 'fix one section, break three others' cycle.
Identified and resolved open questions proactively
From Zoom notes, regulatory feedback, and reviewer comments, AIRA detected open questions - especially around SoA integration and protocol dependencies - ran targeted research, suggested evidence-backed resolutions, and rewrote affected sections with clear rationale.
Strengthened feasibility safeguards in the integrated setup
AIRA proactively suggested an additional exclusion criterion appropriate for the merged design. The sponsor accepted and implemented it, strengthening feasibility and reducing downstream amendment risk.
Measured across four dimensions
Quantitative
- Saved weeks of drafting and consolidation work
- Saved hundreds of expert hours otherwise spent on research, manual reconciliation, and repeated review cycles
Decision Quality
- Reduced misalignment risk by maintaining a single coherent rationale across the integrated protocol
- Improved defensibility by aligning text and structure with regulatory feedback and advice documentation
Operational
- Reduced duplicated operational components and SoA complexity vs. running separate protocols
- Reduced review cycles and eliminated scattered 'source-of-truth' confusion
Strategic
- Improved regulatory coherence of the Phase 1 clinical pharmacology package
- Accelerated readiness for Phase III initiation while lowering amendment exposure
The merge risk wasn't the science - it was hidden inconsistencies and dependencies across sections and schedules.
AIRA surfaced where the integrated SoA required downstream updates, clarified what decisions were needed from the team, and propagated updates across the protocol so the merged design remained consistent and regulator-aligned.
We already knew we needed to merge the studies. AIRA made the difference by turning fragmented inputs into a single coherent protocol in days - while keeping the rationale and schedule internally consistent.
- Clinical Development Lead, Mid-size Pharma EU (anonymized)
Highlighted Outcomes
- One integrated protocol with multiple arms under a unified Schedule of Activities
- First workable merged draft delivered in days instead of weeks
- Stronger regulatory defensibility and smoother Phase III readiness
Get Started
Ready to see AIRA in action?
Speak with our team to see how AIRA can support your clinical development program.
Speak with an expert