Estimate the time needed to complete a form
Use a real test and the form’s own performance data instead of promising a fixed time from its question count.
Select a screenshot to enlarge it.
Steps
- Ask a few representative testers to complete the entire intended path, including media, uploads, and optional explanations.
Use the intended date and device filters. The example metrics are not a performance benchmark. - Record the range of times and revise confusing or unnecessary questions.
Set the intended date and device filters. These empty-demo metrics are not a performance benchmark. - After collecting suitable data, inspect Results → Insights → Average completion time with the intended filters.
- Use a realistic estimate on the welcome screen and update it when the form changes.
Check before you rely on it
A branched form can have several completion times. Describe an approximate range when paths differ.
If you need help
A tiny sample or only incomplete responses is a weak basis for a time promise.
Contact support with the relevant screen, time, and a redacted description. Keep credentials and private respondent information out of screenshots.