Documenting Query Resolution for Audit Readiness in Clinical Trials

In the world of clinical data management, resolving queries is only half the job—documenting that resolution is what truly ensures regulatory compliance. Properly maintained audit trails for queries are critical for passing inspections by agencies such as the USFDA, CDSCO, or EMA. This tutorial explains how to document query resolution effectively to be audit-ready at all times.

Whether using an EDC system or managing hybrid records, the principles of good documentation apply universally. This includes complete, timely, traceable, and logically organized query information that can withstand scrutiny from regulators or internal QA teams.

Why Documenting Query Resolution Matters

• Demonstrates adherence to GCP and data integrity principles
• Supports reconstruction of trial conduct during audits
• Reduces risk of data rejection or regulatory findings
• Helps monitor site performance and protocol compliance

Regulatory expectations make it mandatory for sponsors and CROs to show complete audit trails for each data point queried and clarified. These must include who created the query, who responded, when, how, and what the final resolution was.

Components of Audit-Ready Query Documentation

1. Unique Query Identifier

Each query must have a unique system-generated ID to ensure traceability throughout its lifecycle.

2. Query Text

Query wording should be clear, specific, and free from assumptions. For example: “The Visit 3 date is earlier than Visit 2. Please confirm if this is correct.”

3. Query Originator and Timestamp

Document who created the query (Data Manager, CRA, automated system) and the exact date/time of creation. This supports accountability and GCP compliance.

4. Site Response

Ensure the response includes sufficient justification or correction. Vague entries like “updated” or “done” are not acceptable without context.

5. Resolution and Closure

The final status must indicate closure, the rationale, and who approved it. In EDC systems, this is typically done by the DM or CRA.

All of this should be tracked within the system’s audit trail, in line with computer system validation requirements.

Using EDC Systems to Ensure Documentation

Modern EDC platforms like Medidata Rave, Oracle InForm, and Veeva Vault EDC offer built-in audit trail features. These should be configured to log:

• All query creation, edits, and closures
• Timestamped user actions
• CRF field changes linked to query resolution
• Historical records even after updates

The audit log should never be editable by users, only viewable under controlled access. Always link audit settings to your Pharma SOP checklist for documentation control.

Step-by-Step: Documenting a Query Lifecycle

Step 1: Query Creation

• Use standardized language from query libraries
• Include CRF page/field reference
• Mention protocol clause if applicable

Step 2: Site Response

• Expect detailed clarification (e.g., “Subject was rescheduled due to adverse event”)
• Avoid vague responses
• Encourage consistent terminology

Step 3: Review and Closure

• Confirm resolution addresses the issue
• Log reviewer name and closure date
• Archive any supporting documents (e.g., email trail, lab report)

Step 4: Export or Archive

Periodically back up audit trail data for long-term archiving. Ensure it aligns with data retention policies and Stability studies documentation protocols.

Common Mistakes and How to Avoid Them

Missing Query Context

Fix: Always describe what triggered the query (field, value, visit, etc.)

Untracked Manual Queries

Fix: Log all off-system queries in a manual query log template

Vague Site Responses

Fix: Train sites using query examples and expected response formats

Incomplete Audit Trails

Fix: Validate EDC settings, test logs during UAT, perform mock audits

Best Practices for Audit-Ready Query Records

• Link queries directly to CRF fields
• Avoid using generic or pre-filled text boxes
• Maintain manual logs for queries outside EDC (e.g., email clarifications)
• Reconcile query status before database lock
• Include query metrics in QA and TMF review cycles

Regulatory Requirements to Keep in Mind

As per ICH E6 (R2) and FDA 21 CFR Part 11:

• Data entries and queries must be attributable, legible, contemporaneous, original, and accurate (ALCOA)
• Audit trails must be secure, time-stamped, and available during inspections
• Electronic signatures must be validated and uniquely assigned

Example Scenario: Audit Trail Query Readiness

During a routine GMP audit process, a CDSCO inspector requested all queries related to adverse event reporting at Site 203. Because the sponsor had well-maintained query logs with clear documentation, they demonstrated compliance swiftly—no findings were issued. This highlights the value of structured query documentation.

Conclusion: Make Documentation a Daily Discipline

Documenting query resolution is not just for audits—it’s a fundamental part of good data governance. From automated audit trails in EDC to well-kept manual logs, every action must be traceable and defensible. With proper training, SOPs, and system design, audit readiness becomes an outcome of everyday best practices. Invest in documentation today to avoid findings tomorrow.

Additional Links:

• GLP compliance
• Stability indicating methods