beginner

Survey Health

Use the Survey Health panel in the builder to review completion time, logic issues, privacy reminders, and design suggestions before you launch

8 min readUpdated September 17, 2026

Survey Health

Survey health is a live checklist in the Survey Builder. As you design, it estimates how long the survey may take, flags broken or risky logic, reminds you when a question may collect personal information, and surfaces practical design suggestions that can reduce dropout or poor data.

Use it alongside Preview and Survey Team Collaboration so you catch issues before respondents do.

Where to find it

Open any survey in the Survey Builder. In the top bar, to the left of Tools, look for the Survey health control (a clock, warning, or alert icon with a short label).

The control appears when there is an estimated completion time to show or at least one finding to review. If nothing needs attention and no time estimate is available, the control stays hidden.

Collapsed pill labels

What you seeWhat it means
~8 min or 8 minA compact typical completion time
≥2 minA minimum time when a maximum cannot be estimated yet
Needs reviewOne or more logic or privacy findings need attention
3 tipsAdvisory design suggestions only (no blocking logic or privacy alerts)
Count badgeExtra findings when a time label is already shown

Click the control to open the Survey health panel.

What your plan includes

Note

Logic and Privacy checks are available in every Survey Builder. Completion time estimates and Survey experience suggestions require the Survey Quality Control entitlement on your subscription. If your organization does not have access, you will still see logic and privacy findings but not length estimates or methodology tips.

The same entitlement also powers Survey Response Quality Scoring after fielding. Builder guidance helps you prevent issues upstream; response scoring reviews completed cases in analytics.

Finding groups

The panel organizes results into five groups:

GroupWhat it covers
Completion timeEstimated survey length (typical minutes and range), question and page counts, and notes when logic or unlimited timers make a maximum hard to estimate
Survey setupStructural issues that block reliable length estimates — for example incomplete answer choices, duplicate choice labels, or circular logic paths
Survey experienceAdvisory methodology suggestions — long surveys, dense copy, long choice lists, matrix burden, open-text overload, auto-advance burden, trailing information steps, and similar
PrivacyReminders when a question may collect personal information
LogicBroken or risky rules — missing destinations, self-loops, stale targets, empty conditions, backward skips, and conflicting skip paths

Severity levels

Each finding uses one of three severity levels:

LevelMeaningExamples
ErrorLikely to break routing or trap respondentsSkip points to a deleted question, logic cycle, missing skip destination
WarningMay cause confusion, drop-off, or unreliable estimatesBackward skip, incomplete answer choices, elevated survey length
InfoAdvisory — worth reviewing but not necessarily wrongLong choice list, dense question text, most questions required

Errors and warnings tint the top-bar control red or amber. Info-level suggestions use a calmer blue tone.

Completion time estimates

When your account includes Survey Quality Control and the survey path can be estimated, the Completion time group shows Estimated completion time with a range (for example 6–9 min).

The note below the estimate explains:

  • Whether most respondents see the same questions, or whether skip logic and randomization may change length by path
  • How many questions and survey pages are included in the estimate
  • Why a maximum cannot be calculated yet — for example logic errors, circular skip paths, or questions with no set time limit

Fix Logic errors first when the panel says a maximum cannot be estimated until logic issues are resolved.

Survey experience suggestions

Methodology suggestions are advisory. They highlight design patterns that often correlate with dropout or poor data — not hard errors.

Common suggestions include:

  • Survey length — the survey may feel too long, or some respondents may take much longer than others because of branching
  • Dense copy — a question has a lot of text to read before answering
  • Long choice lists — many answer options on one screen
  • Matrix burden — a large grid with many rows, columns, or cells
  • Open-text overload — many written-response questions in one survey
  • Early demanding question — a required long-text question within the first few questions
  • Required density — most questions are required with few optional skips
  • Demanding questions together — several high-effort questions back to back
  • Complex task load — multiple grids, rankings, or interactive tasks in one survey. Conjoint is counted as high-burden (about 8–18 seconds per task) when length estimates are on your plan
  • Trailing information step — the last step before completion is information-only with no question
  • Auto-advance burden — auto-advance may not give respondents enough time to review an answer
  • AI follow-up variability — AI probing on a long-text question can add unpredictable time

Dismiss a suggestion

You can dismiss an individual Survey experience suggestion for your current browser session when it does not apply to your study design. Click the X on that finding.

Dismissals are temporary — they reset when you close the browser tab or window. You cannot dismiss logic errors, privacy reminders, or completion-time notes.

Privacy reminders

Privacy findings appear when a question type or wording may collect personal information — for example contact forms, signatures, file uploads, video or audio capture, or open-ended prompts that ask for identifiable details.

These are reminders, not blockers. Review whether you need the data, how you will use it, and how long you will keep it. Open the question Properties panel to adjust settings or remove the question.

Logic checks

Logic findings run for every builder session. They include:

  • Rules that point to deleted questions
  • Incomplete conditions — a rule exists but condition details are missing
  • Conditions that reference a deleted question
  • Skip rules with no destination, a deleted destination, or a destination that loops to the same question
  • Backward skips that send respondents to an earlier question
  • Multiple skips from one question without clear mutual exclusivity
  • Circular skip paths that may prevent completion

Remove an outdated rule

When a logic rule still points at a question that no longer exists, you may see Remove outdated rule. Use it to delete that orphaned rule in one step without hunting through every question.

Jump to a finding

Click a finding to jump to the related question. Quali-Fi opens the right builder context:

  • Open question — selects the question on the canvas
  • Review logic — opens the logic editor for that question
  • Review question settings — opens Properties for privacy or setup issues

If you are in script mode, switch to Visual mode first — the builder cannot jump to findings from script mode.

Some findings list related labels (answer choices, skip destinations, or condition values) so you can see what triggered the alert without opening every rule.

What to do with findings

Tip

Treat Survey health as a pre-launch QA pass: fix errors first, then warnings, then decide which info suggestions matter for your methodology.

Before you distribute:

  1. Clear all Logic errors — broken routing corrupts data or traps respondents
  2. Resolve Survey setup warnings that affect answer choices or length estimates
  3. Review Privacy reminders against your consent and data-retention plan
  4. Use Completion time to set respondent expectations in invitations or screeners
  5. Address Survey experience suggestions that conflict with your quality goals, or dismiss ones you have already considered

After fielding, use Survey Response Quality Scoring to review completed responses with explainable quality scores in analytics.

Related documentation

Was this article helpful?