RACT Implementation Process

The team implemented RACT using the following approach:

1. Kickoff Workshop: A cross-functional session introduced RACT, scoring methodology, and regulatory rationale. Functional leads from Clinical, QA, Medical, and Data Management participated.
2. Protocol Risk Mapping: Teams reviewed the protocol to identify 35 unique risks including eligibility deviation, endpoint misclassification, AE underreporting, and consent documentation issues.
3. Scoring and Categorization: Each risk was scored based on standardized criteria. Sample entry:

Risk	Probability	Impact	Detectability	RPN	Category
Eligibility violation due to lab timing	4	5	2	40	High
Delayed AE follow-up	3	4	3	36	Medium

High risks (RPN ≥ 40) triggered mandatory mitigation plans such as CRA training, enhanced SDV, and centralized medical review. Templates were adapted from PharmaSOP.

Monitoring Strategy Aligned with Risk Scores

Following RACT scoring, the team linked each risk to a monitoring approach:

• Sites with multiple high-risk scores were prioritized for early CRA visits
• Central monitors reviewed data weekly for key endpoints and AE patterns
• Low-risk sites received reduced SDV schedules, saving approximately 20% CRA time

A Monitoring Strategy Matrix was developed and inserted into the Clinical Monitoring Plan (CMP), making the oversight risk-based and defensible for audits.

Training and Global Alignment

One of the biggest challenges was ensuring all stakeholders understood and correctly used the RACT. The sponsor conducted:

• Train-the-trainer sessions for regional leads
• Translated RACT user guides into 5 languages
• Simulation exercises using mock risk scoring

The result was a globally harmonized understanding of risk criteria. QA audits found 100% compliance with RACT usage at site qualification and SIV stages.

For more regulatory context, refer to the FDA RBM guidance.

Challenges and Solutions

Despite strong planning, the team faced several hurdles:

• Resistance from Sites: Some sites viewed RACT as sponsor micromanagement. Solution: included sites in scoring discussions.
• Version Control Issues: With Excel-based RACTs, file versions were mismatched. Solution: migrated to CTMS-hosted RACT form.
• Disagreement on Scores: Functional teams occasionally disagreed on impact rating. Solution: established an escalation path for score disputes.

Results and Outcomes

• Reduction in Protocol Deviations: 28% fewer deviations than in prior similar trial
• Faster Enrollment: Early risk planning helped activate high-performing sites first
• Regulatory Recognition: EMA auditors praised the “structured and proactive RBM model”

The sponsor now mandates RACT for all Phase II–IV studies.

Lessons Learned and Best Practices

• Start RACT development early during protocol drafting
• Use centralized systems to avoid document control errors
• Train teams using real-life case examples and scoring simulations
• Ensure QA reviews the RACT at key milestones (e.g., SIV, interim analysis)
• Document everything for TMF inspection readiness

Standardization, transparency, and cross-functional alignment are keys to successful RACT implementation.

Conclusion

This case study illustrates the practical application of RACT in a large, complex trial. The structured approach to risk identification and categorization helped prevent deviations, optimize resources, and improve regulatory confidence. As clinical research becomes increasingly global, the need for standardized, traceable, and proactive risk tools like RACT will only grow.

Additional Resources

• PharmaValidation: Risk Assessment Templates and CTMS Integration
• ICH E6(R2) GCP Guidelines on Risk Management