How to Validate Feasibility Questionnaire Responses in Clinical Trials

The Importance of Validating Feasibility Data

Feasibility questionnaires play a critical role in determining whether a clinical trial site is suitable for participation. However, these tools are only as good as the accuracy of the responses they generate. Self-reported data—if unverified—can lead to unrealistic enrollment projections, infrastructure mismatches, and serious regulatory non-compliance during inspections.

According to ICH E6(R2) and GCP guidelines, sponsors must implement a risk-based approach to trial planning, which includes verification of feasibility assessments. The FDA, EMA, and other global authorities expect documented evidence supporting site claims about patient access, PI experience, prior performance, and infrastructure readiness.

This article provides a step-by-step guide on how to validate feasibility questionnaire responses using cross-verification methods, documentation, risk scoring, and regulatory best practices. Real-world case examples and recommended tools are included.

What Needs Validation in Feasibility Responses?

The following aspects of a typical feasibility questionnaire require validation:

• Patient population estimates
• Investigator clinical trial experience
• Site infrastructure and equipment availability
• Ethics committee and regulatory approval timelines
• Past performance metrics (e.g., enrollment rates, deviation frequency)

These elements are often misreported due to over-optimism, human error, or poor recordkeeping. Therefore, a structured validation process is essential.

Methods for Cross-Validation of Responses

Multiple techniques are used to cross-check the authenticity of feasibility responses:

1. Use of Internal Databases (CTMS, EDC)

Sponsors can retrieve historical trial performance from CTMS to compare with the current feasibility response. For instance, if a site claims it can enroll 60 patients in 6 months, but prior CTMS data shows 20 patients in 12 months for a similar study, this claim warrants further review.

2. Reference to External Registries

Public registries like ISRCTN and ClinicalTrials.gov allow sponsors to validate investigator participation in previous studies and enrollment timelines. Sponsors can match PI names, protocol IDs, and trial dates.

3. Request for Supporting Documents

Sites should provide de-identified hospital records, patient logs, or EHR data to support population claims. For infrastructure, calibration certificates, equipment photos, and maintenance logs should be reviewed.

4. Follow-Up Interviews or Site Televisits

If discrepancies arise, schedule virtual or onsite meetings with the PI or study coordinator to clarify inconsistencies and gather more accurate estimates.

Feasibility Response Verification Table Example

Red Flags That Indicate Validation Is Required

During feasibility review, the following red flags should trigger further scrutiny:

• Patient recruitment claims 2–3x higher than historical benchmarks
• Incomplete PI CV or GCP certification over 3 years old
• Missing documentation for critical equipment (e.g., -80°C freezers, ECG machines)
• Overly short startup timelines without justification
• Sites with previous high deviation rates claiming full protocol compliance

Each red flag should be documented, followed up, and closed before site activation.

Scoring and Risk Categorization of Responses

Validation can be combined with feasibility scoring models to assign a risk category to each site:

Sites categorized as high risk may require additional support or may be excluded from study participation, depending on trial timelines and resource constraints.

Audit Trail and Documentation Requirements

All validation steps must be auditable and retained in the Trial Master File (TMF) or eTMF. Essential records include:

• Annotated questionnaires with reviewer comments
• Emails or notes from follow-up discussions
• Screenshots or documents verifying responses
• Final approval or decision logs by the feasibility committee

This ensures compliance with FDA 21 CFR Part 11 and EMA inspection expectations. Sponsors may also use feasibility-specific document templates for review and version control.

Common Pitfalls in the Validation Process

• Relying solely on site self-assessment without supporting evidence
• Not checking for updated documents like GCP certificates and calibration logs
• Skipping validation due to tight startup timelines
• No SOP or standardized form for feasibility review

To avoid these issues, sponsors should maintain a dedicated Feasibility Review SOP that outlines timelines, reviewer responsibilities, documentation standards, and escalation criteria.

Tools to Support Feasibility Response Validation

• CTMS: For prior site performance records
• eTMF: For document version control and audit trail
• Feasibility Platforms: Veeva Study Startup, Clario, or TrialHub
• Registry Databases: ISRCTN, ClinicalTrials.gov, EU Trials Register
• Dashboards: Power BI or Tableau for response scoring and risk tracking

Conclusion

Validating feasibility questionnaire responses is a critical part of risk-based site selection and trial planning. Relying on unverified data can lead to poor site performance, regulatory findings, and budget overruns. By implementing structured validation workflows, cross-checking with internal and public databases, documenting all review activities, and integrating risk scoring, sponsors and CROs can ensure high data integrity and regulatory compliance. In today’s complex trial landscape, validated feasibility is not just best practice—it’s a regulatory necessity.