A form’s cost includes more than typing. A question can require finding a document, consulting another person or clarifying a price condition. Spreading those questions across screens preserves the same work unless their necessity changes or resumption becomes possible. Progression merits investment when it reduces repetition without degrading the request or purchase the business needs to handle.
A mandatory question can be doing later sales work
The Baymard survey published through Statista for the United States in 2025 identifies several checkout difficulties: account creation appears as an interruption reason in 19%, a long or complicated process in 18% and website errors in 15%. This supplies a reference for online purchases rather than a universal form-abandonment rate or estimate for B2B registrations.
US checkout: requirements and errors interrupting the task
Four reasons in the Baymard 2025 series, after excluding people merely browsing or not ready to buy.
Tap or hover for details. All values are also available in the data table.
Collapse notes
Baymard Institute / Statista. The statistic lists 1,026 adults without publishing the exact filtered question base. Multiple responses must not be added. Exact fieldwork dates are unknown. These are US checkout reasons rather than registration-form or professional-enquiry outcomes. The current primary source covers another edition; historical values come from the Statista 2025 table.
Explore the data table
| Category | Reports the reason |
|---|---|
| Account required to purchase | 19.0% |
| Long or complicated process | 18.0% |
| Website errors or crash | 15.0% |
| Total unavailable in advance | 14.0% |
Information needed to deliver a service has a different function from information enriching sales classification. If both block the first step, the customer does work that may be unnecessary for their current objective. Simplification starts by assigning a decision and moment to each answer. An optional question needs to be genuinely skippable while the next step continues to function.
Some information should not be postponed. If a condition determines that the offer cannot be delivered, discovering it late wastes earlier answers. An informed departure can be the correct result. Ease should not be measured by moving people forward only to exclude them through a requirement known at the beginning.
Stages follow dependencies; screen count follows afterwards
The W3C multi-page forms guide recommends grouping controls into logical stages and showing progress, including recognition of optional stages. This is organisation and accessibility guidance rather than evidence that adding screens always increases conversion. Separating delivery and payment can make sense in a purchase because each choice requires different information.
A stage heading should make its completed work recognisable. An answer changing the route also changes which information remains valid. Automatically retaining an incompatible combination can create a delivery error; clearing everything without explanation creates repetition. Continuity needs to state what remains and what requires review under the new selection.
Device adds context without explaining abandonment on its own
The operational Salesforce Research series published through Statista for the third quarter of 2025 records 77% of baskets without completed orders on computers and 84% on mobile devices in its all-industry aggregate. This is broader commercial context than the form. It does not identify departures caused by fields or assign the gap to screen size.
Salesforce Q3 2025: baskets without orders across all industries
Two devices, the same published aggregate. Share of baskets not resulting in completed orders.
Tap or hover for details. All values are also available in the data table.
Collapse notes
Salesforce Research / Statista, international operational data from observed retailers. Published “all verticals” aggregate; selected categories are not averaged. Exact basket/site counts and weighting are not disclosed in the statistic. This does not measure registration forms or B2B applications, or establish a causal device effect. It supplies context rather than a form-performance target.
Explore the data table
| Category | Baskets without orders |
|---|---|
| Computer | 77.0% |
| Mobile | 84.0% |
Designing a return route needs to address what that context leaves open: switching applications to consult information or continuing later on another device. Saving progress can support that work, but it needs appropriate access to the information and current conditions. An expired draft or changed offer requires an explanation when the person returns.
Saving, submitting and acceptance are different states
The form needs to name the state reached. Saving a section permits later continuation; submitting delivers the request; acceptance confirms a service condition. A positive message combining those moments can make somebody expect a consequence that has not occurred. It also lets marketing count preparation as a conversion before operations can handle it.
A return preserves valid answers without making every visit another application. When several people contribute information, waiting for review differs from leaving because of an error. Explaining who acts next separates active time, coordination and abandonment, and avoids promising completion minutes that omit necessary external work.
Final review preserves the opportunity to correct
British guidance on checking answers lets people review before submitting and return to edit information. Its context is public services. The commercial application preserves an essential distinction: reading the summary does not submit it. The final action needs to describe the commitment somebody is about to make.
Changing one answer should not erase unrelated answers. When a detail determines later responses, the process identifies that dependency and requests the necessary review. A field error requires local correction; an incompatible condition needs another route; an uncertain submission outcome needs service confirmation before repetition. These are different tasks requiring different instructions.
Useful completion includes what follows submission
Reporting follows distinct operations within a cohort and window appropriate to the work. Conditional routes retain their scope: a legitimately omitted stage is not abandonment. Recent drafts need time for resumption and repeated visits do not multiply outcomes. The business can compare valid submissions with eligible starts while retaining pending work and the coverage it cannot reliably link.
When submissions rise together with returns for missing information, simplification moved part of the cost into review. Investment needs to remove unused questions, bring forward requirements preventing pointless work and preserve correction. A progressive form accelerates when it completes the promised task with less repetition, rather than gets more people into an operation that then needs reconstruction.
In this article
Marian Vasile
Marian Vasile is a MarTech and growth professional. His work spans product marketing, SEO, paid advertising and deep online tracking, including behavioral analytics and attribution.