Online forms: what to build them with and how to keep completion high

Online forms are the least glamorous part of a business and one of the most consequential: they are how enquiries, applications, orders, bookings and complaints actually reach you. A form that loses a fifth of its submissions loses a fifth of that, silently, with no error message anywhere.

Three things decide whether a form works — its length, how it handles mistakes, and what happens to the data afterwards. The builder you choose matters far less than getting those right.

What to check in a form builder

• Question types that match your data: choice, scale, date, file upload — not everything squeezed into free text.
• Conditional logic, so people only see questions that apply to them. This is the single biggest lever on completion for anything longer than five fields.
• Validation you control: required fields, format checks, and error messages that say what to fix.
• A response inbox that is searchable and timestamped, not just an email per submission.
• Export to CSV or XLS, because sooner or later someone will want the responses in a spreadsheet.
• Limits: close the form on a date or after N responses, so nothing keeps arriving after the deadline.
• Both link and embed publishing, since the same form usually needs to live in an email and on a page.

Ask for one thing per question and nothing you will not use. The fastest way to raise completion is not better design — it is deleting three fields.

Where completion is lost

1. Count the fields. If there are more than seven on one screen, split into sections with a progress indicator or cut some.
2. Validate on blur, not on every keystroke — an error shown while someone is still typing reads as a rejection.
3. Never clear entered data on an error. Retyping is where people give up entirely.
4. Label clearly and mark required fields visibly; "optional" is easier to read than a red asterisk convention nobody remembers.
5. Test on a phone with a real thumb. Small tap targets and a keyboard covering the submit button are why mobile completion drops.
6. Confirm on submit — a visible success state, and an email if the submission matters. Silence makes people submit twice.

Where the responses should go

A form that emails you each submission works until there are twenty of them, at which point your inbox becomes the database and nothing can be counted. Decide up front: responses live in the form tool's inbox, get exported to a spreadsheet on a schedule, or feed a process — a task, a CRM record, an invoice.

The other half of that decision is retention. Form responses are usually personal data; keep what you need for as long as you need it, say so on the form, and delete the rest. An old response archive nobody uses is a liability with no upside.

Ettex Forms covers the build-and-collect loop: a drag-and-drop builder from question blocks, logic and branching, choice, scale, date and file-upload types, multi-step sections with progress, validation for required fields and formats, quotas and limits to close by date or count, custom themes, and publishing by link or embed. Submissions land in a searchable, timestamped response inbox with a live summary, the team can review and process them together, and everything exports to CSV or XLS. Survey, registration and feedback templates ship with it, and forms can be drafted and responses read offline.

Common mistakes

• Asking for a phone number "just in case", which costs submissions from people who do not want to be called.
• One long form where three short conditional paths would do.
• Using free text where a choice list would keep the data usable.
• No spam handling at all, or so much that legitimate submissions get blocked.
• Collecting data with no named owner, so responses arrive and nobody acts on them.

Good online forms are short, forgiving when someone makes a mistake, and connected to something that happens afterwards. Everything else is styling.