Most form advice argues about aesthetics. The argument is settled by one number: your completion rate. Of the people who saw question one, how many reached the end? Everything below is judged against that and nothing else.
A form is not a page. It is a short conversation in which one side does all the work and gets nothing until the last screen. Every rule here lowers the cost of a single turn in that conversation: fewer decisions, less typing, less doubt about what happens after the button.
The rules are ordered roughly by how much they move the number. Apply the first five to a form you already have live and you will feel the difference before you finish reading the rest.
1. Ask one thing per screen
A screen with six fields asks the reader to plan. They scan it, estimate how long this is going to take, and then decide whether to start at all. A screen with one question asks for one answer, and that decision is small enough to make without thinking. This is the whole argument for conversational forms: the reader is never looking at more than one thing.
One question per screen also gives you something a stacked page cannot. Every question becomes its own step, so you learn exactly where people stop. A field buried in a long page is invisible in your data; a step is not.
A single "Your details" screen with name, email, phone, company and a message box → five screens, one question each, with the message box last.
1 →
What should we call you?
First name is plenty.
2. Put the label above the field
Labels set beside a field make the eye travel sideways, and they are the first thing to break on a narrow screen. Labels above the field keep one vertical reading line: question, input, next action. The eye never leaves the column, and the layout survives a 375px phone without a second set of rules.
Keep the label short and literal. "Work email" beats "Please enter your work email address below." If the field genuinely needs an explanation, that is help text sitting under the label, not a longer label, and not a tooltip the reader has to hunt for.
"Please enter your work email address below:" with the input floating to its right → label "Work email", help text "We'll send the invoice here", input directly underneath.
3. Never use the placeholder as the label
A placeholder vanishes the moment someone types. From that point the field has no name, so anyone who pauses, gets interrupted, or comes back to check an answer has to delete their own text to see what was being asked. Placeholder text is also low contrast by convention, which makes it hard to read in the seconds it exists.
Use a real <label> tied to the input, and use the placeholder for format, not meaning: an example, a unit, a date shape. If the placeholder is the only thing naming the field, the field is unlabeled.
A gray box reading "Company" and nothing else → label "Company", placeholder "Acme Inc.", both still visible while the reader types.
4. Use the right input type on mobile
The wrong field type costs the reader taps. A phone number in a plain text box gives them the letter keyboard and no country code. A date in a plain text box gives them three chances to type a format you will later reject. Picking the right question type changes the keyboard, the validation and the error message in one move.
Upform ships 21 question types for exactly this reason. If you are unsure which one a question wants, the survey question types guide walks through all of them.
| What you are asking for | Question type to use |
|---|---|
| An email address | Email (format check, email keyboard) |
| A phone number | Phone Number (country flag, dial code, keypad) |
| A quantity or budget | Number (numeric keypad, no letters) |
| A date | Date (a picker, not three boxes) |
| A street address | Address (sub-fields you can switch off) |
| A CV or portfolio | File Upload (allowed types and a size cap) |
5. Ask for the easy thing first
Order your questions by effort, not by the shape of your database. The first question sets the reader's expectation of the entire form. If it is "Tell us about your project" above an empty text area, a lot of people never type a character. If it is "What's your first name?", they answer in two seconds and are now a person who has started something.
This is not a trick, it is sequencing. People finish what they have begun, and a cheap first answer is the cheapest possible beginning. Keep the open-ended questions for the middle, once the form has earned the typing.
Question one: "Describe your requirements in detail" → question one: "What should we call you?", with the detail question at step four.
6. Kill the optional fields
An optional field still costs a decision. The reader has to read it, judge whether it applies to them, and choose to skip it. Ten optional fields is ten small taxes levied on somebody who was only trying to leave you an email address. If nobody on your team has read an answer to a field in three months, delete the field.
The honest test is ownership. For every question, name the person who reads the answer and say what they do with it. If you cannot name them, the question is curiosity, and curiosity belongs in a follow-up email rather than between a reader and a submission.
Every question you ask is a question somebody can decide not to answer.
An 11-field contact form where six fields are marked optional → four required questions and one "Anything else we should know?" at the end.
7. Explain why you need the sensitive thing
Phone number, budget, company size, date of birth. These are the questions where people stop, and rarely because the question is hard. They stop because they are guessing what you plan to do with the answer. One line of help text answers the guess before it turns into an exit.
Be specific about the use, not reassuring in general. "So we can call you back within one business day" works. "Your privacy is important to us" does not, because it says nothing the reader can check. If the honest answer is that a salesperson will call, say so and let people opt in with their eyes open.
"Phone number *" → "Phone number, only used to confirm your delivery slot. No sales calls."
8. Make errors specific and inline
An error banner at the top of a form that says "Please correct the errors below" turns your reader into a search party. Put the message next to the field it belongs to, name the actual problem, and describe what a correct answer looks like. Never phrase it as the reader's fault.
Validate when someone leaves a field, not on every keystroke. Telling a person their email is invalid while they are typing the third letter of it is noise, and noise trains people to ignore the real message later. Keep the error on screen while they fix it, and clear it the moment the answer is valid.
"Invalid input" in red at the top of the page → under the field: "That date has already passed. Pick a date after 23 September."
9. Never reset the form
Nothing loses a submission faster than an error that wipes what somebody already typed. Keep every answer, keep the file they uploaded, and move focus to the one field that needs changing. The same rule applies to going backwards: a back button must show the previous answer exactly as it was left, not an empty box.
This matters most on a phone, where a cleared form usually means a lost respondent rather than a patient retype. It is one of the quiet advantages of multi-step forms over a single long page: answers already given stay in place as the reader moves forward and back.
A failed validation returns an empty form and a red banner → every answer stays as typed, with the cursor placed in the single field that needs a fix.
10. Size touch targets for thumbs
Most forms are completed on a phone held in one hand. A choice rendered as a 16px radio dot is a target you have to aim at. A choice rendered as a full-width row you can tap anywhere is not. Give every option, button and checkbox a tap area of at least 44px tall and the full width of the column it sits in.
Keep the primary action reachable too. A next button parked at the bottom of a long scroll is worse than a sticky bar at the bottom of the screen, where the thumb already rests. Published Upform forms use full-width targets and a sticky back and next bar on mobile for this reason.
A row of small radio dots with "Submit" below the fold → full-width option rows 52px tall and a sticky back/next bar.
11. Show progress, and make it honest
A progress indicator is a promise. If the bar reads 80% while four screens remain, you have not encouraged anybody. You have taught them that the form lies, and the next number they see will be discounted. Count steps, not effort, and let a long question count as exactly one step like everything else.
Short forms are often better with no indicator at all. Below about five questions a bar mostly draws attention to the existence of a queue. Upform can draw progress as a bar, as dots, or as a percentage, and you can switch it off per form.
Honest progress
Question 3 of 5. The bar moves one fifth per screen, every screen, and it arrives at 100% on the last question rather than on the thank-you page.
12. Let the keyboard do the work
People who fill in a lot of forms barely touch the mouse. Enter should move to the next question. Shift and Enter together should make a new line inside a long-text answer rather than submitting it. Arrow keys should move through options, and single keys should choose them: A, B and C on a single choice, Y and N on a yes/no, 1 to 9 on a rating.
Keyboard support is also the cheapest accessibility work you will ever do, because a form that can be completed without a pointing device is usually a form that behaves for a screen reader as well.
Tab, tab, tab, reach for the mouse, click Next → type the answer, press Enter, next question. Press A to choose the first option.
13. Use logic instead of length
The longest form in the world is the one that asks everybody everything. Branch instead. Ask the qualifying question first, then show only the questions that follow from the answer. A solo freelancer and a 500-person company should not walk through the same six screens, and neither should a returning customer and a stranger.
Upform's conditional logic handles this with 20 operators and four actions (show, hide, jump and end form), so one form can serve four audiences while each of them experiences a short one.
One 18-question form that everybody completes → a four-question path for individuals and a nine-question path for teams, branching from the same first answer.
14. Write the button as the action
"Submit" describes what your database does. "Send my brief", "Book the call", "Get my quote" describe what the reader gets. A label written from the reader's side removes the last half-second of doubt about what the button will do, which is exactly where hesitation lives.
Keep one primary action per screen. A second button of equal visual weight, like "Save draft", "Reset" or "Start over", asks the reader to make a choice at the precise moment you want them to continue. If a secondary action must exist, make it a quiet text link.
"Submit" next to a same-size "Reset" → "Send my brief" on its own, with "Back" as a plain link.
15. Say what happens after submit
The screen after the button is the one most teams never write, and it is the one that decides whether people trust you enough to wait. Confirm you have the answers. Say who will reply, and by when. Give one useful next step: a booking link, a document, a way to reach a human. If a confirmation email is coming, say so, or people will submit the form twice.
Upform's Thank You step can carry that message or redirect to any URL you choose, so a finished form can hand somebody straight to a calendar, a download or a contact form for a different team.
"Thanks! Your response has been recorded." → "Got it, Marta. Ana will email your quote by Thursday. Need it sooner? Reply to the confirmation now sitting in your inbox."
Accessible forms are not a separate project
Accessibility work gets postponed because teams imagine it as a phase. In a form it is four habits, and none of them costs you a design decision. Most of what follows is already implied by the fifteen rules above.
- Every field has a real label tied to the input, not a placeholder standing in for one.
- Focus order follows reading order, and the focus ring is always visible. Never remove an outline without putting something clearer in its place.
- Text clears the contrast minimum against its background, including help text, placeholder text and error messages, which are the three people forget.
- Nothing is carried by color alone. Pair the red border with words, and the green tick with a message somebody can read aloud.
A form that passes those four is easier for everyone, not only for people using assistive technology. Because Upform's design controls expose the text, background, button and card colors directly, you can check your contrast before you publish rather than after somebody complains. The longer version of this, including keyboard testing and error announcements, is in the form accessibility guide.
Measure it, then change one thing
None of these fifteen rules deserves a meeting. Publish the form, wait for a real sample of responses, and read the drop-off. Your data beats anyone's rule of thumb, including this page's.
Find the question that loses people. Upform's Results tab gives views, starts, submissions, incomplete responses, completion rate and average completion time, plus a per-question drop-off funnel with color-coded severity, so the worst step is obvious without a spreadsheet.
Change exactly one thing about it. Reword it, move it later, make it optional, or swap it for a question type that takes one tap instead of typing. One change per round, or you will never know which change worked.
Compare like for like. Read the next stretch of responses against the last one of similar size, and check the desktop and mobile split separately. A question that behaves on a laptop is often the exact reason phones quit.
If the funnel shows people leaving in the same place every time, read form abandonment next; if you want a method for tracking the number over time, form conversion rate covers the arithmetic. Both lean on what form analytics already records for every form you publish, on the free plan included. When you get to writing the questions themselves rather than laying them out, the survey questions library has examples you can lift.