Make your forms easier to finish

Start with the job of the form

A form is a request for someone’s time. Before redesigning it, write the exact outcome it must support. An email signup needs a deliverable and a way to deliver it. A detailed project estimate may need more context. Those are different jobs and should not start with the same list of fields.

For each field, ask: “What decision will we make with this answer before replying?” Keep necessary fields, move later questions to a later step, and remove questions nobody uses. Reducing fields is a design hypothesis to test, not a guarantee that conversions will rise.

Make the next action predictable

Place a short explanation above the form. Say what people receive, what happens after submission, and whether a response takes time. Use a button that describes the action: “Send my enquiry” or “Email me the checklist.” Avoid a vague label when you can name the outcome.

Give every input a visible label. A placeholder disappears when typing starts, so it should provide an example rather than carry the only instruction. Mark optional fields and show any format requirement before the person makes an error.

For longer workflows, group related questions under plain-language headings. Show one task at a time, but allow people to return to previous sections without losing their answers.

Design for mistakes and small screens

Try the form with an incomplete email address, a long name, and a phone-sized screen. A useful error identifies the problem and explains how to fix it. Keep valid answers when another field fails. After success, confirm that the request was received and explain the next step.

• Use the appropriate email, number, or URL input where it fits.
• Make labels and buttons easy to tap.
• Check keyboard navigation and visible focus.
• Keep essential instructions outside collapsed help panels.
• Test the full journey, including any confirmation email.

Measure completion, then read the context

Pick a consistent measure, such as completed enquiries divided by visits to the enquiry page. Keep the date range and audience source alongside the number. If you count sessions in the denominator, label it as a session-based rate and use the same definition in future reviews.

Change one meaningful thing first: a field, a label, or an explanation. Watch for unintended outcomes such as incomplete enquiries that create extra follow-up work. A higher completion rate is useful only if the submissions still support the form’s purpose.