REDCap Survey Queue

Deep-Dive Guide for Multi-Survey Workflows and Participant Navigation

The Survey Queue allows you to present multiple surveys to participants in a structured, automated sequence. It acts like a “to-do list” of surveys, guiding participants through your study in a controlled and logical order.

Core Principle: The Survey Queue controls what surveys participants see next based on completion status and logic.
Important: Survey Queue is about navigation and sequencing, not sending invitations. It works best when combined with ASIs or Participant List workflows.

What the Survey Queue Does

The Survey Queue displays a list of surveys available to a participant based on defined conditions. Participants will only see:

  • Surveys they have already completed
  • Surveys they are eligible to complete next

This allows you to control progression through a study without requiring multiple links or manual navigation. :contentReference[oaicite:0]{index=0}

How It Works

Each survey in the queue appears based on:

  • Completion of a prior survey
  • Logic based on data values
Key Concept: Survey Queue logic is evaluated at the record level, not within specific events or repeating instances. :contentReference[oaicite:1]{index=1}

Setup Steps

  1. Go to Online Designer
  2. Click Survey Queue
  3. Add surveys to the queue
  4. Define conditions for each survey

Defining Queue Logic

Queue logic determines when a survey becomes available.

Important: You cannot use relative smart variables like [current-event], [next-instance], or [previous-event-name]. :contentReference[oaicite:2]{index=2}

Auto-Start vs Auto-Continue

Auto-Start (Queue Feature)

  • Respects logic
  • Guides participant forward

Auto-Continue (Survey Setting)

  • Ignores logic
Important: Do NOT use Auto-Continue with Survey Queue. :contentReference[oaicite:3]{index=3}

Hiding the Queue

Hiding the queue creates a seamless experience and forces auto-start behavior.

Longitudinal Considerations

Important: Survey Queue is not event-relative—use carefully in longitudinal projects.

Limitations and Common Pitfalls

  • Does not send invitations
  • Logic is record-level only
  • Auto-continue conflicts
Common Mistake: Using Queue instead of ASI.

Best Practices

  • Use for structured workflows
  • Keep logic simple
  • Test fully
Final Takeaway: Survey Queue guides the experience—it does not control delivery.

Quick Setup Checklist

  • Enable surveys
  • Configure Survey Queue
  • Add surveys in correct order
  • Define logic for each survey
  • Enable Auto-Start if needed
  • Hide queue if desired
  • Test full participant workflow