Practical guide

Incomplete responses: preserve what happened, not what you wish happened

Last materially reviewed 2026-10-01

Quick answerAn unfinished entry is not a completed survey and a blank is not a negative answer.
What to know

Keep completion status

A respondent may answer one question and leave another unanswered. Preserve that distinction in the review dataset. Do not fill blanks with zeros, neutral ratings or guessed explanations. A partial response can contain useful context, but it may not belong in every calculation that uses complete responses. Define inclusion rules before looking for a favorable result.

What to know

Verify where partial data goes

Yay! Forms documents an option for sending incomplete responses to integrations after inactivity, with the timer resetting as answers continue. That is a data-handling behavior to inspect, not a reason to enable it automatically. Check the respondent notice, destination, access and whether later completion creates or updates a record. Do not assume the exported or integrated copy is identical to the final response.

What to know

A fictional reconciliation

A survey has ten completed forms and three partial entries. Two partial entries contain the first rating; the third contains only an introduction step. Report the count used for each question rather than claiming thirteen completed surveys. If a downstream sheet has fifteen rows, investigate identifiers and updates before calling the difference extra respondents.

What to know

Retain uncertainty

You may not know why someone stopped. A long question, interruption or lack of relevance are hypotheses, not observed causes. Use a harmless form-path check to investigate behavior; do not label a person disengaged or dissatisfied simply because an entry is incomplete.

What to know

Check update versus duplicate behavior

A downstream row may be an earlier version of the same response rather than another respondent. Compare stable identifiers and documented update behavior before counting rows. If the available export lacks enough information to reconcile them, state the limitation. Do not merge by a person’s name or a similar comment without an appropriate basis. Keep a separate working reconciliation note so that later reviewers can understand why a row was included, excluded or left unresolved.

Continue when useful

Next: Export review

Check identifiers, question meaning, missing values and dates—not just whether the file opens.

Open Export review →

Sources used for this page

These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.

  1. Yay! Forms incomplete-response integrations — Merchant documentation · yayforms.com · Merchant-controlled · checked 2026-10-01