|Articles|April 1, 2011

Applied Clinical Trials

  • Applied Clinical Trials-04-01-2011
  • Volume 20
  • Issue 4

Sponsor Oversight of CROs

The perennial sponsor complaint: "Outsourcing costs too much." The perennial CRO response: "If you didn't assign so much internal resource to manage us, it would be cheaper."

The perennial sponsor complaint: "Outsourcing costs too much." The perennial CRO response: "If you didn't assign so much internal resource to manage us, it would be cheaper."

Well, it's true and both groups acknowledge it. Over 90% of sponsor and CRO respondents indicate that resources are assigned to oversee outsourced studies. While CROs and sponsors agree that oversight may be excessive, they do not agree on the consequences. In ISR's Staff Quality and Models report, 78% of CROs believe that oversight increases the amount of time necessary to complete a clinical trial compared to only 25% of sponsors. Sponsors hold what may be considered contradictory beliefs regarding their oversight of CROs. They believe their own oversight to be excessive; however many believe there are benefits too. Nearly half of the sponsor respondents indicated oversight reduces time; 53% believe it either reduces costs or has no impact on costs; and 77% believe it increases data quality.

From ISR's perspective, the size, global scope, and complexity of today's clinical trials are justification enough for a degree of oversight. Pharma's business challenge is identifying when enough is enough; the point when investing in more oversight no longer returns a better clinical trial. Service providers' business challenge is to better understand why sponsors insist on oversight, and then develop systems, training, and people to arrive at the right balance.

This is an evolving issue and having a better understanding of development outsourcing models as well as sponsor and service provider oversight rationale are important first steps to increasing trial efficiency and lowering industry clinical development spending. Achieving the right oversight balance can have profound effects on both individual development programs and companies.

—Industry Standard Research, www.ISRreports.com

Articles in this issue

over 15 years ago

Business and News Update April 2011

over 15 years ago

Demystifying Asian Trials

over 15 years ago

Academic Strength in Germany

over 15 years ago

Imaging CROs in Asia

over 15 years ago

Mining for Words: The Case for NLP

over 15 years ago

MENA: The Dawn of a New Era

over 15 years ago

Darwin at Work: Trial Technology

Related to this article

© photon_photo - © photon_photo - stock.adobe.com
Standardized measurement across five oncology centers found that clinical research coordinators rated eSource-enabled workflows positively (Overall Mean Satisfaction 5.79 of 7), with reduced manual entry and electronic data transfer earning strong marks, while perceived reduction in sponsor and monitor queries lagged as the one domain below threshold.
Where the Industry Is Headed as Clinical, Operational, and Real-World Data Connect
In this video interview, Rajneesh Patil, global head of AI, digital, and innovation in clinical development at Syneos Health, describes the industry’s trajectory toward a unified intelligence orchestration environment—and explains why the future isn’t one model that knows everything, but a trusted system that brings the right evidence to the right human decision.
What Expanding AI Ecosystems Mean for Sponsor Complexity and Oversight
In this video interview, Rajneesh Patil, global head of AI, digital, and innovation in clinical development at Syneos Health, argues that CROs must act as orchestrators rather than aggregators—and that the real test of any AI ecosystem is whether it reduces sponsor coordination burden or just hands it back to them.
Where AI Governance in Clinical Development Falls Short
In this video interview, Rajneesh Patil, global head of AI, digital, and innovation in clinical development at Syneos Health, identifies three recurring failure modes in AI governance frameworks—and explains why responsible AI must be an ongoing operating discipline, not a one-time approval gate.