Survey Completion Time Estimate
“How long will this take?” is the silent question every respondent asks. This guide helps you estimate completion time based on question types, then design your survey to keep drop‑off low.
“How long will this take?” is the silent question every respondent asks. This guide helps you estimate completion time based on question types, then design your survey to keep drop‑off low.
A reliable estimate doesn’t require complex math. The key is weighting question types differently and adding a small buffer for reading and navigation.
Example buckets: single-select multiple choice, multi-select, rating scale, matrix/grid, and free-text.
Use the table below as a baseline and adjust for your audience. Free-text and grids add time quickly.
Always take it on mobile. A survey that feels easy on desktop can feel slow on a phone.
These are planning numbers — not universal truth. Use them to avoid underestimating surveys with many open-ended or grid questions.
| Question type | Typical seconds | Notes |
|---|---|---|
| Single-select (MCQ) | 6–10s | Faster when options are short and familiar. |
| Multi-select | 10–15s | Slower because respondents evaluate more options. |
| Rating scale / Likert | 7–12s | Be careful with long labels and too many points. |
| Matrix / grid | 30–45s | Feels heavy on mobile; consider splitting into separate questions. |
| Short free text | 20–30s | Respondents think and type; quality varies. |
| Long free text | 45–60s | Use sparingly; best for motivated audiences. |
Put question counts in one column and seconds per question in the next, then sum:
TotalSeconds = Σ(Count_i × Seconds_i) + IntroSeconds + (Pages × 2)
Convert to minutes by dividing by 60, then round up when you display it to users.
Most surveys can be cut by 30–50% while improving data quality. The trick is removing low-signal questions and restructuring the ones you keep.
Matrix questions are time-expensive and error-prone on mobile. Keep only the highest-signal items.
Ask “Did you contact support?” before showing support questions. Ask “Was this delivered?” before showing delivery questions.
If a question is useful but not critical, mark it optional and place it near the end.
Instead of three free-text questions, use one prompt that captures the “why” (and route follow-up interviews separately).