Published · 4 min read

The purposes for which personal data are collected should be specified "not later than at the time of data collection." That is paragraph 9 of the OECD's privacy guidelines, adopted on 23 September 1980 and kept in the 2013 revision. Paragraph 7 asks for limits on collection too, but the purpose rule is about timing: the reason has to arrive no later than the question.
Form abandonment is when a visitor starts filling in a form, focusing or typing in at least one field, and leaves without submitting it. Visitors who see a form and never touch it are a separate problem, because there the page never earned the first keystroke.
The person who started a form had already decided it was worth some effort, so each loss is expensive. One founder counted 902 demo submissions and found that "over half of them (56.9%) just vanish before they even finish signing up" (r/microsaas, June 2026), which is one team's multi-step flow and nobody's benchmark.
The standard fix is to cut fields, and most growth teams have done it at least once. The OECD rule puts the test somewhere else. Field count is a proxy for what actually costs you, which is an ask the visitor cannot see a reason for when it arrives, like a phone number requested before the page has said what the product does. A short form with one such field can lose to a longer form where every field is obviously needed, and trimming the others leaves the unexplained one where it was.
Form abandonment rate is form starts minus submissions, divided by form starts. Tools disagree on what a start is (first focus or first keystroke), so check yours before comparing.
The last field touched before leaving is where to look, with one caution: it shows where the visitor gave up, which is not always what made them give up. A visitor who stalled at the phone field may still quit at the button. That gap between where and why is the general problem with conversion friction.
Next to each field on your form, write the one-line reason a visitor would accept for being asked it now, then look for that reason on the page. Any field whose honest reason is "sales wants it", or whose reason appears nowhere the visitor can see, is your candidate. State the reason at the field, or move the field to after the visitor has got something. Before deleting one, find out why it was added; a redesign can quietly break whatever a forgotten field was feeding.
Count still matters. The same OECD text asks for limits on collection, and explaining a field is no licence to add three more. The claim is narrower: purpose explains the losses that count cannot.
When an audit reads a form, an early ask shows up under "is the value clear before the ask?" and an unanswered worry under "are the visitor's anxieties addressed?", two of the human-plane dimensions. Nudgent's own early-access form has two fields, one per step, and each heading gives the reason: "What page do you want audited first?" above the URL field, "Where should we send your first audit?" above the email field. It passes this test easily, which proves nothing about how it converts, and reading a page cannot show where people actually left.
Field analytics will tell you which field people left at. For each field on your form, can the page say, at the moment it asks, why it is asking?
Published benchmarks vary by form type and by how a start is counted, and few state their method, so the useful comparison is your own form against itself over time.
Often because a field asks for something the visitor cannot see a reason to give yet, such as a phone number before the page has said what the product does. Length costs something too, but less than an unexplained ask.
Abandonment counts visitors who started a form and left without submitting it. A visitor who never starts points at the page above the form rather than at the form itself.