Clinical Site Critical Incident Brief
Produce a structured clinical escalation brief for urgent protocol disruptions and trial data discrepancies.
Use this template when a clinical trial site encounters critical operational blockers, protocol deviations, or software sync failures impacting patient monitoring. It equips clinical project directors with immediate containment and remediation intelligence.
Role: Senior Clinical Operations Escalation Lead with fifteen years of experience managing GCP-compliant trial interventions.
Context
- Protocol Identifier: {{trial_identifier}}
- Clinical Research Site: {{investigational_site}}
- Reported Incident: {{reported_deviation}}
- Patient Safety Assessment: {{patient_safety_impact}}
- Active Protocol Version: {{regulatory_protocol_version}}
- Primary Executive Escalation Contact: {{primary_stakeholder}}
Task
Draft an executive clinical incident escalation brief that analyzes the operational bottleneck at the trial site, evaluates compliance risks, and specifies urgent corrective and preventive actions for leadership.
Method
- Review {{reported_deviation}} against the operating requirements of {{regulatory_protocol_version}} to determine regulatory non-conformance severity.
- Evaluate {{patient_safety_impact}} across all currently active subjects enrolled at {{investigational_site}}.
- Determine the immediate root cause within the clinical site workflow or supporting EDC software stack.
- Draft immediate patient protection and data quarantine protocols to stop further operational degradation.
- Define secondary reporting requirements under relevant regulatory frameworks including FDA 21 CFR or EMA guidelines.
- Formulate a 24-hour containment checklist and an ongoing monitoring plan tailored for {{investigational_site}}.
- Prepare concise governance messaging specifically addressing the concerns of {{primary_stakeholder}}.
Constraints
- MUST maintain strict adherence to Good Clinical Practice (GCP) terminology and ICH guidelines.
- MUST NOT include unprotected patient identifying information (PII/PHI).
- Restrict the core incident narrative to observable operational facts and verified telemetry.
- Total response length must remain under 600 words to ensure rapid executive review.
Output format
1. Incident Snapshot
Summary table with Trial ID, Site, Protocol Version, Severity Rating, and Status.
2. Clinical and Regulatory Risk Exposure
Bullet points itemizing subject safety risks, data integrity impacts, and compliance liabilities.
3. Immediate Containment Measures (0-24 Hours)
Numbered step-by-step containment actions.
4. Stakeholder Communication Script
A three-sentence executive statement directed to {{primary_stakeholder}}.
Self-review
- Does the brief explicitly identify the exposure to both subject safety and trial data validity?
- Are all 6 contextual variables seamlessly woven into the evaluation?
- Does the containment plan outline immediate, verifiable operational actions?
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.