Why this matters
Every form field is a cost, paid when the visitor is least sure the quote is worth it. Asking for everything up front loses people who would happily have answered later.
This exercise applies the guide to forms that convert, which works backwards from the next step, and the guide to trust and proof elements, which pairs proof with the decision it supports. It also touches the guide to landing page speed and mobile, because a slow form on a phone loses people before they type.
The current form
Movewise Removals is a fictional household removals firm. Every quote request goes to an estimator, who phones to book a free video or home survey and then gives a fixed price. A rough price needs only the two postcodes, the size of the home and the move date; the survey settles everything else.
Movewise Removals: the form and last month's figures
| Order | Field or element (all required except the tick box) |
|---|---|
| 1 | Title (Mr, Mrs, Ms, Dr) dropdown |
| 2 | First name / Last name |
| 3 | |
| 4 | Phone (must be 11 digits, no spaces) |
| 5 | Alternative phone |
| 6 | Full current address, five lines |
| 7 | Full new address, five lines |
| 8 | Moving date |
| 9 | Property type dropdown |
| 10 | Number of bedrooms |
| 11 | List every large item (free text) |
| 12 | Floor and lift access at each address |
| 13 | Packing service? / Storage needed? |
| 14 | Budget dropdown |
| 15 | How did you hear about us? |
| 16 | "Send me offers" tick box, ticked by default |
| 17 | Picture puzzle to prove you are human |
| 18 | "Reset" and "Submit" buttons side by side |
Labels are placeholder text inside the fields. The only error, "Invalid input", appears at the top and clears the form.
| Measure | Last month |
|---|---|
| Quote page visits | 1,900 (72% on phones) |
| Visitors who started the form | 410 |
| Forms submitted | 48 |
| Completion (submitted ÷ started) | 48 ÷ 410 ≈ 12% |
| Submit attempts that failed validation | 95, of which 71 on the phone field |
| Last field touched before abandoning, most common | List every large item, then Budget |
| Phone page load: largest element shown after | 5.8 seconds; an autoplay video sits above the form |
Proof the firm has but does not show: an independent review rating with several hundred reviews, trade association membership, goods-in-transit insurance, a fixed-price promise after the survey, and the estimator's name and photo.
Deciding what each field earns
The next step is the estimator's call, so a field earns its place only if that call needs it or the request would be routed wrongly without it. What the survey settles can wait; what nobody uses can go. Group what remains in the order people would give it, with labels above fields and validation that accepts real input.
Proof belongs where the doubt is: "is the price real?", "who will ring me?", "are my things safe?". Place it in the same phone screen as the button. Read the form's CVRShare of visits or clicks that convert. as completions over starts, not visits.
Task
- Mark every field keep, defer or drop, with a reason tied to the estimator's call.
- Write the new field order and decide whether a short multi-step form would help.
- Rewrite the labels, and write error messages for the phone, email and postcode fields.
- Choose three proof elements, where each goes and which doubt it answers.
- Name the speed fix the form needs on phones, and what you would measure after launch.
Worked answer
Movewise Removals: field decisions
| Field | Decision | Reason |
|---|---|---|
| Title | Drop | The call does not need it |
| First and last name | Keep, as one "Your name" field | The estimator needs a name to call |
| Keep | Survey link goes by email | |
| Phone | Keep, relaxed validation | The call needs it; accept spaces and +44 |
| Alternative phone | Drop | Rarely used; doubles the effort |
| Current and new addresses | Defer; ask postcodes only | Postcodes give price and coverage; the survey takes full addresses |
| Moving date | Keep, with "not sure yet" option | Availability; many lack an exact date |
| Property type and bedrooms | Keep bedrooms; defer property type | Bedrooms size the job |
| Large items, access, packing, storage | Defer to the survey | Top abandonment field; the survey settles it |
| Budget | Drop | Fixed-price quotes; second most abandoned field |
| How did you hear | Drop | Campaign tracking answers this better |
| Offers tick box | Keep, unticked and separate | Consent must not be pre-ticked or bundled |
| Picture puzzle | Replace with a hidden spam check | Excludes some people |
| Reset button | Remove | Nobody means to clear it |
Result: seven inputs instead of twenty or more, in two short steps.
Order and steps. Step one asks the two postcodes, bedrooms and move date: easy, impersonal questions that build momentum. Step two asks name, email and phone, then the unticked offers box and a "Get my free quote" button. Each step fits a phone screen.
Labels and errors. Visible labels above each field, such as "Postcode you are moving from". Errors sit next to the field and explain the fix:
- Phone: "Enter a phone number so the estimator can call to book your survey. Spaces are fine."
- Email: "Enter an email address like name@example.co.uk so we can send your survey link."
- Postcode: "Enter the full postcode so we can check we cover the area. Capitals and the space are optional."
On any error, the form keeps everything already typed.
Proof beside the form. The review rating with its count, linked to the independent site, answers "are they any good?". The fixed-price promise with its condition answers "is the price real?". The estimator's name and photo with a line on when they will call answers "who will ring me?". Membership and insurance go near the benefits, linked to where they can be checked.
Speed. Replace the autoplay video with a sized still image, then check Core Web VitalsGoogle's user experience metrics. field data, not a test on office wi-fi.
Measurement. Track starts, each step, submissions and failed attempts by field, with survey bookings per request as the lead-quality guardrail.
Common mistakes
- Deferring by deleting. Deferred questions still need a home: the survey.
- Keeping budget "for qualification". A fixed-price firm learns nothing from it.
- Proof at the bottom of the page. On a phone it is not seen at the moment of doubt.
- Judging on completions alone. Requests that never book a survey are not an improvement.
Test yourself next in the checkpoint on forms, trust and mobile speed, or return to the beginner conversion optimisation level page.
