When a form has to stay long
The forms guide treats every field as a cost the visitor pays and works backwards from the next step, which for a lead form usually means fewer fields. That advice still holds, and a form that can be shortened should be. The diagnosis for high form abandonment finds lead forms that ask more than their offer is worth, and the academy exercise on simplifying a quote form practises the cut on a short form.
This tutorial is for the other case: a form whose questions are mostly required by the decision that follows it. An admissions team cannot assess an applicant without their previous study, an insurer cannot price a policy without the details the price depends on, and a funder cannot judge a grant without the plan it would pay for. Removing those questions does not make the application shorter; it moves them into emails, calls and a second form, and the applicant pays the same cost later and with less warning.
Long applications lose people in recognisable ways: a request for something the applicant does not have to hand, the discovery several screens in that they were never eligible, a session that expires with the work in it, an upload that fails on a phone. The Form Abandonment RateThe share of people who start filling in a form, by entering a first field, but leave without submitting it. shows the loss, and the cost also turns up inside the business, as staff chasing incomplete applications and support contacts asking how to finish.
Where cutting runs out, four other moves remain, and the steps below make each one in turn.
| Move | What it changes | Steps that make it |
|---|---|---|
| Order | What decides eligibility comes first; what a later stage needs waits for that stage; documents come last | The inventory, deferring, eligibility first, documents last |
| Prepare | Applicants know before they begin what they will need, what is optional and what happens afterwards | What to have ready |
| Save | Every answer survives a closed tab, an expired session or a change of device | Short steps, saving and coming back |
| Support | Help sits where people stall, errors explain themselves and nobody is beaten by a clock | Errors, time limits and help; the accessibility checks |
The guide to reducing customer effort lists long forms as one kind of effort a business places on its customers; the aim here is to arrange the effort that cannot be removed. The funnel and checkout section places applications beside the other journeys it covers.
Before you start
- The forms guide and the funnel analysis tutorial, read. This tutorial builds on the forms guide's rules for fields, labels, errors and multi-step layout, and reads the application as a FunnelModel of the customer journey stages. the way the funnel analysis tutorial does. Both are prerequisites.
- The whole application as applicants meet it. Every screen on a phone and a desktop, conditional questions, the confirmation, the emails the form sends and any paper version still in circulation.
- The people who use the answers. Whoever decides applications, the owner of the system that receives them, and the people responsible for compliance and for data protection.
- What the business already knows about the loss. Starts, submissions, any step events, the application system's count of complete applications, support contacts about the form and staff notes on chasing.
- A developer and time booked. Saved progress, step validation and later uploads are back-end work.
The steps
List every question with its owner and its reason
Write every question the application asks into one list, in the order applicants meet it, including conditional questions, declarations, tick boxes and anything asked on a later screen or by email after submission. Then fill in a row for each.
Column What to record Question The wording the applicant sees, with any help text Owner The team or person who reads the answer Used at The stage that needs it: eligibility, assessment, decision, or after acceptance Reason What the answer changes, in one sentence Required by Any rule, policy or contract the owner names, recorded as they state it To hand Whether the applicant knows it, must look it up, or must obtain it from someone else Sensitivity Whether the answer is personal data, could reveal health or another special category, or is free text Questions asked twice, questions nobody claims and questions whose reason is "we have always asked it" show up on the first pass. Resist deleting the last group on sight. Chesterton's fence is the rule for this moment: before removing a question, learn what it was added for and who depends on it today, because an old question may feed a report, a downstream system or a requirement the compliance owner can name. Record the reason either way. The inventory records what the compliance owner says the rules require; it does not interpret them, and nothing in this tutorial is a view on what a regulated application must ask.
Remove or defer what the decision does not need yet
Sort the inventory by the "used at" column. Questions with no owner and no use, once the fence check is done, go. So do repeats, and anything the business already holds is filled in for the applicant. Details that matter only once a place, a policy or a job has been offered move to after the offer, when people have a reason to give them. The sign-up flows guide applies the same rule to account creation: ask now only what the next step needs. The booking flows guide asks only what the appointment needs and gathers anything more through a separate, clearly explained form.
Health questions are a separate decision. As the healthcare industry guide explains, the GDPR places data about health in a special category of Personal DataAny information relating to an identified or identifiable living person, such as a name, email address, location data or an online identifier., with extra conditions on when it may be used, and the guide hands choices about such data to the person accountable for data protection. That person decides whether the application asks health questions at all, and at which stage.
Deferring is not hiding: tell applicants at the start what will be asked later.
Put the eligibility questions first
Some answers end an application whatever comes after them: a course that does not take the applicant's instrument or level, an address outside the area a service covers, a closing date that has passed, an entry requirement the applicant does not meet. Ask those questions first, in a short opening step, and give the outcome at once. Where the rules can be published, put them on the page that opens the application.
When an answer rules someone out, say which rule applied, point to what they could do instead and give a way to ask a person if they think the rule has been applied wrongly.
Contact details come straight after eligibility. The forms guide asks for contact details early, so that someone who stops later still leaves a way to reach them: here, an eligible applicant who stopped part-way, contacted only within the rules in the last step.
Tell applicants what to have ready before they start
Publish a list on the page that opens the application: the documents needed and the forms they can take, the details of referees, dates of previous study or employment, any statement the applicant will write and what it should cover, and which items are optional or can follow later. Say how long completing the application usually takes, measured from the form's own step events rather than guessed, and list the sections in order.
Say what happens after submission as well: who reads the application, how and roughly when the applicant will hear, and what the next stage involves. That is proof at the moment of commitment, which the trust and proof guide places beside the decision it supports.
Write the list as text that can be printed or saved, not as an image, so it works with a screen reader.
Split the form into steps that each fit a screen
Group the remaining questions into steps by subject: about you, previous study or experience, the substance of the application, references, documents, declaration. The forms guide's rules for multi-step forms apply as written there, among them honest progress shown as steps, going back without losing entries and steps short enough for a phone screen.
Long applications need three additions. Show the named steps from the start, so the applicant sees the whole shape rather than a bar. Validate each step when it is submitted, so errors are met one screen at a time rather than all at once at the end. And give long free-text answers room: the guidance beside the field, any length limit stated in words with a live count, permission to draft elsewhere and paste in, and no silent cutting of text that runs over. Conditional questions appear only for the applicants they apply to.
Let applicants save and come back
Save every step when it is submitted, without waiting for the applicant to press a save button, and say on screen that progress has been saved. The route back can be a sign-in or a link sent to the address given in the contact step; whichever is chosen, it must work from a different device, because an applicant may start on a phone and finish at a desk. On return, open the application at the step where the person left and show what is still missing.
Two cautions go with saved progress. Keep personal details out of the return link and every other page address: the guide to keeping personal data out of analytics names an email address in a page address among the routes by which personal data reaches reports nobody meant it for. And decide how long unfinished applications are kept and what happens to them afterwards with the data protection lead, then tell applicants on the save screen.
Ask for documents last, with another way to send them
An upload often depends on something the applicant does not have at that moment: a scan, a file on another device, a letter from somebody else. In the middle of the form it stops everything after it; at the end, once the answers are saved, a failed upload costs nothing already done.
Where the decision allows it, let the application be submitted with documents to follow, show a clear list of what is still outstanding, and let applicants add items later from their saved application. Offer at least one other route the owner can accept, such as sending an item to a named address or bringing it to an interview or audition. State the accepted file types and any size limit in words beside the upload, before anyone chooses a file, and confirm on screen what has been received.
Make failure visible to the business, too. The tutorial on tracking errors and failed actions records each failure as an event with an owner who reads it, so a broken upload shows up in a report rather than in a complaint. Identity and document checks themselves are outside this tutorial.
Write errors, time limits and help for the hardest questions
Errors follow the forms guide: specific, next to the field, in words, with every entry kept. On a long step, add a summary at the top listing each error and linking to its field. Make validation accept what real applicants type, including international phone numbers and names with accents.
The guide to accessibility as conversion work notes that the Web Content Accessibility Guidelines call for no time limit the person cannot extend. Warn before a session ends, offer to extend it, and save so that an expiry never loses an answer. A closing date for applications is a different thing: show it on the opening page and in every reminder.
Help belongs where the question is asked. The inventory, the step events and the support contacts point to the questions people stall on; for each, add a short explanation of what is wanted, an example answer and what to do if the question does not fit the applicant's situation. Give a way to reach a person for what the help cannot answer.
Check the form with a keyboard, a screen reader and a phone
The accessibility guide, summarising the Web Content Accessibility GuidelinesThe W3C's Web Content Accessibility Guidelines, the widely used standard for making web content usable by people with disabilities. as the forms guide lists them, expects every field to have a programmatically associated label, errors to be identified in text, focus to stay visible, the form to work without a mouse and no time limit the person cannot extend. Work through the whole application using only the keyboard, then a screen reader, then a phone in one hand, including the upload, the save-and-return route, any component supplied by someone else and the confirmation. The education industry guide puts the stakes plainly: an inaccessible application form turns applicants away.
Then watch people like the applicants use it. The usability testing tutorial runs sessions with tasks written as goals, including one worth adding here: stop part-way, close everything, and return later on another device. Use test details rather than anyone's real application, as that tutorial's section on consent and test data explains.
Measure each step and follow up within the rules
Send an event for each part of the journey: the form start, each step completed with its number and name, a save, a return, each submission attempt, errors by field, failed uploads and failed submissions, and the submission confirmed by the server. The form tracking tutorial builds the start, step, field-error and confirmed-submission events in Tag Manager, and its error event also covers a submission the server rejects. Saves, returns and submission attempts are custom events of the same kind, named in the tracking plan and agreed with the developers, and failed uploads are recorded as the documents step describes. Count the confirmed submission as a Key EventA GA4 event marked as important to the business, the property's measure of success. once per application, and send no names, free-text answers or other personal details as event parameters.
Follow-up comes with rules. The education industry guide recommends asking for marketing permission and reminder permission as two separate choices. A reminder about the applicant's own unfinished application, which they chose to receive and which promotes nothing, is part of the application; anything that promotes other courses, products or offers is marketing. The list building and consent guide explains what the direct marketing guidance of the UK's Information Commissioner's Office says about when consent is needed, and that every marketing message must let the recipient opt out. None of this is legal advice; the data protection lead settles which messages need which permission before the first one is sent.
What to measure after the redesign
Judge the redesign on complete applications and what follows them, not on submissions alone: a form that lets incomplete applications through faster has moved the work to the staff who chase them. Read the measures below together, by device, and against the same point in the previous application cycle where demand has a calendar.
| Measure | What it shows | Role |
|---|---|---|
| Starts per visit to the opening page | Whether the preparation page invites people in or puts them off | Context |
| Step-to-step rates | Where applicants stop, and whether the stopping point moved | Diagnosis |
| Saves and returns | Whether saved progress is used and how many people come back | Diagnosis |
| Complete applications per start | Whether the form does its job | Primary outcome |
| Failed uploads, failed submissions and errors by field | Where the form still breaks | Guardrail |
| Staff time spent chasing and support contacts about the form | Whether effort moved back to applicants or the business | Guardrail |
| Offers or approvals per complete application | Whether the applications the form now produces are as strong | Guardrail |
The conversion rate calculator turns started, step and complete counts into rates, so each step's conversion rate (CVRShare of visits or clicks that convert.) can be set beside the last cycle's. Reconcile the analytics count of confirmed submissions with the application system's own count before trusting either. Where the volume will not support a controlled test, compare like periods, write down what else changed, and treat the difference as directional rather than proven.
A music college rebuilds its admissions form (illustrative)
Mordavisk College of Music rebuilds its admissions form
Mordavisk College of Music, an invented music college, takes applications online for its performance courses: personal details, education history, a repertoire list, two references, a personal statement and audition recordings. In the last admissions cycle, 1,840 people started the application and 610 submitted it, about 33%, and only 420 of those arrived complete; admissions staff spent roughly two days a week chasing the rest.
The inventory lists 68 questions over 9 screens. It finds 7 asked twice, 12 needed only once an audition place is offered, such as accommodation preferences and an emergency contact, and an upload for 3 recordings on the fourth screen, where step events show 41% of phone users stop. One question nobody could explain, previous instrument teachers, turns out to feed the scholarship panel and stays, with its reason recorded.
The college puts instrument, level and intended start date on the first screen, which tells 150 applicants at once that their chosen course does not take their instrument and points them to one that does. It publishes a list of what to have ready, splits the remaining 49 questions into 6 short steps saved as each is completed, moves the recordings to the end with a link to send them up to 21 days later, adds a warning before a session ends with an option to extend it, and fixes a repertoire table that could not be completed with a keyboard.
In the next cycle, 1,910 people start, 1,120 submit, about 59%, and 980 arrive complete, with most of the rest sending recordings through the link. Step events now show the personal statement losing the most applicants, which becomes the next thing to research. Chasing falls to about half a day a week, and offers per complete application stay level at about 1 in 3, so the extra applications are not weaker ones.
Common mistakes
- Cutting what the decision needs. A question removed from the form and asked by email afterwards still costs the applicant, later and with less warning.
- Deleting a question nobody in the room can explain. Find who relies on it first, and record the reason either way.
- Eligibility at the end. People who were never eligible should learn it on the first screen, not the last.
- Surprise requirements. A document first mentioned part-way through stops the application until it is found.
- Progress that disappears. An expired session or a closed tab should never cost an answer.
- Uploads in the middle. Put documents last, with another way to send them.
- Testing with a mouse alone. Use the keyboard, a screen reader and a phone, and watch real people try it.
- Counting submissions as success. Count complete applications, and check that their quality held.
- Reminders that sell. Keep reminders about the application apart from marketing, with separate permission.
