Email campaigns
AuraScore 81/100

Clinical Trial Patient Retention Email Sequence Audit Checklist

Audit clinical trial email journeys to ensure patient comprehension, protocol adherence, and IRB/IEC compliance.

Use this checklist to evaluate patient-facing clinical trial onboarding and milestone email sequences. It ensures health literacy standards, consent integrity, and empathy guidelines are met without introducing protocol deviations.

Template

Role: Senior Patient Recruitment Lifecycle Specialist & Clinical Operations Strategist

Context

  • Therapeutic Study Area: {{therapeutic_area}}
  • Trial Phase & Protocol ID: {{trial_phase_protocol}}
  • Target Patient Demographics: {{patient_cohort_demographics}}
  • Institutional Review Board Criteria: {{irb_approval_criteria}}
  • Primary Attrition Trigger: {{dropout_risk_trigger}}
  • Health Literacy & Accessibility Target: {{accessibility_reading_level}}

Task

Produce an operational patient retention checklist to audit automated clinical trial email journeys, preventing patient study dropout, safeguarding informed consent boundaries, and aligning all communications with institutional ethics requirements.

Method

  1. Inspect email readability against {{accessibility_reading_level}} to eliminate complex clinical trial jargon and acronyms.
  2. Verify that sequence timing directly counteracts the identified {{dropout_risk_trigger}} without overwhelming participants.
  3. Audit all message bodies against {{irb_approval_criteria}} to ensure communications remain strictly informational and non-coercive.
  4. Check emergency contact pathways, site coordinator identifiers, and adverse event self-reporting prompts across all touchpoints.
  5. Confirm accessibility standards for {{patient_cohort_demographics}}, including screen reader labels, high-contrast assets, and scalable typography.
  6. Validate that visit reminder emails accurately reflect protocol milestones defined in {{trial_phase_protocol}}.
  7. Review consent preservation notices to ensure participant withdrawal rights are presented transparently without administrative friction.
  8. Ensure secure data collection practices: confirm no Protected Health Information (PHI) is transmitted through open URL parameters.

Constraints

  • Checkpoints MUST strictly enforce non-coercive language around study compensation and participant withdrawal.
  • Checkpoints MUST NOT permit unvetted medical guidance or clinical diagnosis in patient communications.
  • MUST align directly with specific guidelines mandated by {{irb_approval_criteria}}.
  • MUST enforce plain-language readability thresholds matching {{accessibility_reading_level}}.

Output format

Return a structured audit checklist divided into 4 sequential modules:

  1. Module 1: Ethics, Non-Coercion & IRB Boundaries (4 checks)
  2. Module 2: Health Literacy & Plain Language Compliance (3-4 checks)
  3. Module 3: Protocol Adherence & Retention Touchpoint Timing (4 checks)
  4. Module 4: Privacy, Consent & Site Coordinator Accessibility (3 checks) Format each line as: - [ ] [Module-Step] **[Focus Area]**: [Evaluation Protocol] (Metric: [Threshold/Standard])

Self-review

  • Ensure all variables ({{therapeutic_area}}, {{trial_phase_protocol}}, {{patient_cohort_demographics}}, {{irb_approval_criteria}}, {{dropout_risk_trigger}}, {{accessibility_reading_level}}) are actively referenced in check logic.
  • Verify that each checklist item includes a measurable verification standard.
  • Confirm that no clinical operations abbreviations remain unexplained.
AuraScore breakdown
81/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

marketing
marketing-email-campaigns
healthcare-life-sciences
clinical-trials
patient-retention
irb-compliance