Survey Completion Time Calculator

Turn question counts into reliable field time estimates. Adjust for skips, pauses, and page weights. Share exports, compare runs, and brief your team quickly.

Includes all items and screens you expect participants to see.
Used to apply a slower answering pace.
Estimated percent of items bypassed via branching.
Choose a pace model that matches your instrument design.
Typical range: 8–18 seconds.
Typical range: 35–90 seconds.
Use your panel average if available.
Include prompt, options, and help text.
Open items often include longer instructions.
Tap, think, and navigation time beyond reading.
Add expected pauses for long surveys.
Captures grids, media, routing, and cognitive load.
Applies a small speed adjustment for interaction cost.
Controls min/max range for respondent differences.
CSV PDF
Tip
Use ±20% variability for mixed audiences and devices. Use ±10% for tightly controlled lab sessions.

Example data table

Use the examples below to sanity-check your inputs before fielding.

Scenario Total Q Open Q Skip % Method Typical Most Likely
Quick brand pulse 12 1 5 Seconds per question 2:00 – 3:30
Product usage tracker 28 3 15 Seconds per question 6:00 – 9:00
Customer feedback deep-dive 45 10 25 Words per minute 10:00 – 15:00
Policy compliance assessment 75 12 30 Words per minute 18:00 – 28:00

Calculation history

Your last 50 runs are saved locally in this session for exports.

Timestamp Method Total Q Open Q Skip % Break (min) Complexity Device Min Most Max P90 Avg sec/Q
No runs yet. Submit the form to generate results.

Formula used

Seconds-per-question model
Best for stable instruments with consistent item formats.
EffectiveClosed = ClosedQ × (1 − SkipRate)
EffectiveOpen = OpenQ × (1 − SkipRate)
BaseSeconds = (EffectiveClosed × SecClosed) + (EffectiveOpen × SecOpen)
AdjustedSeconds = BaseSeconds × Complexity × DeviceFactor + BreakMinutes × 60
Min/Max = AdjustedSeconds × (1 ± Variability)
Words-per-minute model
Useful when stem length and help text drive time.
Words = (EffectiveClosed × WordsClosed) + (EffectiveOpen × WordsOpen)
ReadingSeconds = (Words ÷ WPM) × 60
BaseSeconds = ReadingSeconds + (EffectiveTotal × EntryOverhead)
AdjustedSeconds follows the same multiplier rule.

Percentiles shown are simple positions within the min–max range, designed for planning rather than strict distributional modeling.

How to use this calculator

  1. Enter total questions and open-ended count to reflect instrument structure.
  2. Estimate skip rate from routing and quotas, then add break minutes for long surveys.
  3. Choose a pace model. Use seconds-per-question for uniform items, or words-per-minute for text-heavy screens.
  4. Set complexity for grids, media, and cognitive effort, then pick the primary device.
  5. Press Submit to show results under the header. Export CSV or PDF for briefs and monitoring.

Why completion time is a key quality metric

Completion time influences dropout, straightlining risk, and sample cost. Field teams often target a median duration under ten minutes for general audiences, while specialized studies can run longer. A stable overall estimate helps set incentives, screeners, and quotas with fewer revisions. When expected time exceeds fifteen minutes, consider splitting modules or adding breaks.

How question mix changes expected duration

Closed items are usually faster because choices are visible and bounded. Open-ended items add typing, cognitive load, and re-reading. This calculator separates closed and open counts so you can model both. In many online panels, one open item can consume time comparable to three to five closed items, depending on instruction length and validation rules. Longer open prompts can amplify time variance and increase late-stage exits.

Routing, skips, and the effective question count

Branching reduces exposure, but it also increases navigation overhead and can create longer paths for some segments. The skip rate converts total questions into an effective count that reflects typical routing. Use a conservative skip estimate when quotas force respondents into long sections. For early planning, a ten to twenty percent skip rate is common in multi-path surveys. Review logics after launch, because rare paths can still impact service levels.

Device and complexity adjustments for real users

Mobile respondents face smaller screens and slower text entry, so time often rises even when the script is unchanged. Complexity captures grids, media playback, looping, and heavy validation. A complexity factor above 1.15 is reasonable for matrix-heavy designs, while 0.90 fits short, simple flows. Pair device and complexity to avoid underestimating peak durations. If you translate languages, retest because reading speed and layout can shift.

Using ranges and percentiles for planning

Respondent speed varies, so a single number can mislead scheduling. The variability setting produces a practical min and max range, then derives planning percentiles inside that range. Use the most likely time for dashboards, P75 for staffing, and P90 for strict time limits. Export results to CSV for scenario comparisons and stakeholder sign-off. Treat extreme speeders as a quality signal, not a time goal.

FAQs

1) Which method should I choose?

Use seconds-per-question when items are uniform and stable. Use words-per-minute when stems, help text, or compliance language drives reading time. If unsure, run both and compare.

2) What is a good default for closed-item seconds?

For standard single-choice items, 10–14 seconds is a practical starting point. Increase it for grids, multi-selects, or images. Calibrate with pilot logs when available.

3) How should I set the skip rate?

Estimate the percent of items an average respondent will not see due to routing. If quotas push many respondents into long paths, lower the skip rate to stay conservative.

4) Why does mobile increase time?

Mobile entry is slower, scrolling increases, and attention shifts more often. Even when reading speed is similar, interaction overhead rises. The device factor accounts for this practical friction.

5) Are the percentiles statistically exact?

They are planning approximations derived from the min–max range, not a fitted distribution. Use them to communicate risk and scheduling buffers, then refine with field timing data.

6) How do I validate my estimate?

Pilot with a small sample, record timestamps, and compare the observed median to the calculator’s most likely value. Adjust seconds, WPM, and complexity until the estimate matches reality.

Related Calculators

Survey Response RateMargin of ErrorConfidence Interval SurveySurvey Completion RateNet Promoter ScoreSurvey Participation RateResponse DistributionNonresponse Bias CheckSurvey Variance CalculatorSurvey Mean Score

Important Note: All the Calculators listed in this site are for educational purpose only and we do not guarentee the accuracy of results. Please do consult with other sources as well.