Conflicting trial status stalled go/no-go reviews: CTMS, eTMF & finance unified

Overview

Portfolio governance at a global pharma slowed because trial status was reported inconsistently and compliance obligations required careful evidence handling. Teams reconciled conflicting CTMS updates with eTMF artifacts and finance forecasts in spreadsheets, and Regulatory and Safety weighed in late. Intelligex connected the electronic Trial Master File (eTMF), Clinical Trial Management System (CTMS), and finance forecasts into a governed model and surfaced a stage?gate dashboard with an approval workflow that captured Regulatory and Safety sign?offs. Go/no?go decisions drew from the same evidence with clear audit trails, which reduced rework and avoided compliance issues.

Client Profile

• Industry: Biopharmaceuticals
• Company size (range): Global R&D and commercial footprint
• Stage: Late?stage pipeline with active global studies
• Department owner: Strategy, Analytics & Executive Leadership (Portfolio & R&D Strategy)
• Other stakeholders: Clinical Operations, Regulatory Affairs, Pharmacovigilance/Safety, Biostatistics, Finance/FP&A, Quality/GxP, Legal & Compliance, IT

The Challenge

Portfolio committees needed a single view of trial progress, risk, and investment outlook. In practice, CTMS reflected milestones and enrollment with varying data hygiene by region, eTMF housed essential documents and inspection readiness artifacts, and Finance maintained long?range forecasts and scenario plans. Exports were merged in slide decks, status definitions drifted across teams, and evidence for stage?gate decisions was gathered manually. Regulatory and Safety reviews arrived after recommendations were drafted, often forcing rework when an inspection?critical document or signal was missing.

Compliance obligations raised the stakes. Electronic records and signatures had to meet expectations under Good Clinical Practice and electronic records rules, and audit trails needed to bind decisions to the exact artifacts and data versions used. Leaders wanted to keep core systems but align them under a governed view with clear gate criteria, role?based access, and recorded sign?offs.

Why It Was Happening

Identity, timing, and ownership were fragmented. Study and country codes differed between CTMS and eTMF, milestone calendars were out of sync, and finance models referenced program IDs that did not map cleanly to protocol versions. Trial status and risk labels varied by team, which led to plausible but incompatible summaries. Evidence lived as links and attachments without a structured pathway to confirm completeness before go/no?go meetings.

Governance arrived late. Stage?gate packets were assembled in slides without required citations or e?signature steps. Safety signals and regulatory considerations were reconciled after a recommendation was drafted, and there was no lightweight approval path that enforced who needed to sign off, in what order, and on what basis. Without a single operating layer, committees debated inputs instead of options.

The Solution

We implemented a governed portfolio layer that unified CTMS status, eTMF artifacts, and finance forecasts in a conformed model, and exposed a stage?gate dashboard with embedded evidence and approvals. CTMS milestones and enrollment fed standardized status views; eTMF contributed document completeness and inspection?readiness signals; Finance forecasts provided scenarios and budget posture. Role?based access controlled detail, and an approval workflow captured Regulatory, Safety, and Finance sign?offs with e?signature and reason codes. Nothing was replatformed: CTMS, eTMF, and finance systems remained systems of record, while the orchestration aligned identity, calendars, rules, and review.

• eTMF integration for artifact completeness, essential document status, and inspection?readiness signals (for example, Veeva Vault eTMF)
• CTMS integration for study, country, and site milestones, enrollment, monitoring visits, and protocol amendment status
• Finance forecast alignment for program budgets, cash flows, and scenario tags mapped to studies and protocols (Oracle EPM Documentation)
• Conformed analytics model with mastered program, study, and country IDs and harmonized calendars in Snowflake
• Transformation logic and validations for identity joins, stage definitions, and evidence checks in dbt
• Stage?gate dashboard in Power BI with risk flags, budget context, and drill?through to artifact lists and CTMS events
• Approval workflow in ServiceNow capturing Regulatory, Safety, and Finance sign?offs with comments and change logs
• Role?based access via identity groups so Clinical, Regulatory, Safety, Finance, and executives see the right level of detail (Okta Groups)
• Audit trails for gate decisions, data versions, evidence citations, and electronic signatures aligned to 21 CFR Part 11
• Policy and definitions catalog referencing Good Clinical Practice guidance (ICH E6(R2))

Implementation

• Discovery: Mapped CTMS entities and milestone conventions, eTMF structures and completeness metrics, and Finance forecast models and scenario tags. Cataloged program and study identifiers, protocol versioning practices, and existing gate criteria. Reviewed recent portfolio packets to identify recurring reconciliation and late compliance edits.
• Design: Defined the mastered program?study mapping, harmonized calendars, and stage definitions. Authored evidence checks for essential documents and monitoring events. Designed the stage?gate dashboard, risk flags, and drill paths. Specified approval paths for Regulatory, Safety, and Finance with reason codes and e?signature requirements, and documented data?retention and audit policies.
• Build: Implemented scheduled feeds from CTMS, eTMF, and Finance into Snowflake; built dbt transformations for identity joins, stage logic, and validations; developed Power BI dashboards with certified datasets and drill?through to artifact lists; configured ServiceNow forms, queues, and approvals; and wired role?based access and audit logging.
• Testing and QA: Replayed prior gate decisions to validate status alignment and evidence checks, reconciled protocols and country?level calendars, verified artifact completeness signals against eTMF, and exercised approval flows with Regulatory and Safety. Confirmed that audit trails captured data versions, sources, comments, and signatures.
• Rollout: Launched read?only dashboards in parallel with slide?based packets, then enabled approvals for a pilot set of programs. Expanded by therapeutic area and region as teams validated behavior. Maintained a manual exception path for urgent safety or regulatory actions with post?review documentation.
• Training and hand?off: Delivered quick guides for Clinical and Portfolio teams on stage definitions and drill?throughs, for Regulatory and Safety on evidence checks and approvals, and for Finance on scenario alignment. Assigned stewardship for program mappings, definitions, and gate criteria with a regular change?control cadence.

Results

Portfolio committees opened a single dashboard that reflected CTMS status, eTMF completeness, and Finance scenarios under shared definitions. Regulatory and Safety sign?offs were captured in the flow, and each recommendation linked to the exact artifacts and data versions used. Conversations centered on options and risk rather than reconciling inputs, and compliance reviews no longer triggered last?minute rework.

Operational friction eased. Status drift decreased because identities and calendars were harmonized, and evidence checks highlighted gaps before packets were assembled. Approvals and audit trails created confidence for inspections and internal reviews, while Finance and Clinical aligned earlier on scenario impacts. Decisions moved with clearer visibility and fewer cycles.

What Changed for the Team

• Before: Trial status and evidence lived in slides and email threads. After: A governed dashboard showed stage, risk, and evidence with drill?through to CTMS and eTMF context.
• Before: Regulatory and Safety reviewed late. After: A gate workflow required their sign?offs with comments and e?signatures.
• Before: Program and study IDs varied by system. After: A mastered mapping aligned identities and calendars across tools.
• Before: Evidence checks were manual. After: Automated completeness and inspection?readiness checks flagged gaps early.
• Before: Audit trails were hard to assemble. After: Decisions carried data versions, citations, and approvals in one record.

Key Takeaways

• Unify CTMS status, eTMF evidence, and finance scenarios under a mastered identity and shared calendar to ground portfolio choices.
• Move governance into the flow with stage?gate dashboards and required Regulatory and Safety approvals.
• Encode stage definitions and evidence checks in transformations; definitions in code reduce drift and rework.
• Bind decisions to data versions and artifacts with audit trails aligned to electronic records expectations.
• Keep core clinical and finance systems; layer orchestration, approvals, and role?based access rather than replatforming.

FAQ

What tools did this integrate with?
We connected the client’s CTMS for milestones and enrollment, the eTMF for essential document completeness (for example, Veeva Vault eTMF), and finance forecasts from Oracle EPM. Data landed in Snowflake, transformations and checks ran in dbt, dashboards were delivered in Power BI, and approvals executed in ServiceNow with access governed by Okta groups.

How did you handle quality control and governance?
We harmonized program and study identities and calendars, encoded stage definitions and evidence checks in dbt, and certified datasets in Power BI. A gate workflow required Regulatory, Safety, and Finance approvals with comments and e?signatures. Audit trails captured data versions, sources, and approvers to align with 21 CFR Part 11 and referenced Good Clinical Practice guidance (ICH E6(R2)).

How did you roll this out without disruption?
We ran the governed dashboard alongside slide?based packets while teams validated mappings, stage definitions, and evidence checks. After trust was established, we enabled the approval workflow for a subset of programs and expanded progressively. Core systems and processes stayed intact; the operating layer orchestrated consistency, access, and approvals on top.

How did you address regulatory requirements and electronic signatures?
Approval steps used e?signature and role?based controls, with time?stamped records and change logs. Evidence links pointed to eTMF artifacts and CTMS events accessible by permission, and the system stored version stamps to support inspection readiness, aligning to electronic records expectations under 21 CFR Part 11.

How were protocol changes and deviations handled?
Protocol amendments and deviations flowed from CTMS and were tagged in the conformed model. The dashboard highlighted impacted milestones and evidence checks, and the approval workflow required Regulatory and Safety to acknowledge the change before the next gate. Finance scenarios linked to the updated protocol context so impacts were visible in the same view.