Most government forms are not hard because the questions are hard. They are hard because they were written for the office that processes them, not for the person filling them in. The fix is to turn the form into a guided, step-by-step flow: one decision at a time, in plain language, with every requirement known before the person starts. That is the idea behind EasyBMV, the online vehicle registration service I designed for at GovSoft.
The project
EasyBMV lets people in Ohio complete vehicle registration online, the same day, instead of visiting an office in person. It is a regulated GovTech web app, so every screen has to satisfy the rules behind the paper process while staying simple enough for someone who registers a vehicle once every few years.
GovSoft reports these outcomes for the service:
- 60% more online completions compared with in-person visits.
- 30% shorter wait times at physical offices.
- 90% citizen satisfaction.
Here is what makes a form like this one people can finish.
1. Tell people what they need before they start
The most common reason people abandon an official form is discovering halfway through that they need a document they don’t have to hand. List the documents, numbers and payment method up front, on a short start page. A person who knows what is coming is far more likely to reach the end.
2. One topic per step
A long paper form becomes a series of short steps, each about one thing: the vehicle, the owner, the address, the payment. Short steps feel achievable, errors stay close to the question that caused them, and a clear progress indicator tells people how far they have left.
3. Ask only what applies to this person
Paper forms carry every question for every case, and leave people to work out which sections to skip. A digital flow can branch. Ask the deciding question first, then show only the questions that apply. Every question removed is one fewer chance to give up.
4. Write it in plain language
Official terms belong in the system, not on the screen. Use the words people use, explain any term they must know in one sentence beside the field, and say why a piece of information is needed when it isn’t obvious. Trust matters more in government services than almost anywhere else, and clear wording earns it.
5. Make errors easy to recover from
- Validate as people go, and say exactly what is wrong and how to fix it.
- Accept common formats instead of forcing one, such as dates and numbers typed with or without spaces.
- Never clear what someone has already typed when an error appears.
- Let people go back and change an answer without losing the rest.
6. Show a summary before submitting
Before payment or submission, show everything on one review screen, with a way to edit each section. In a regulated process mistakes are expensive to fix later, often needing a phone call or a visit. A review step catches them while they are still cheap.
7. Design the end, not just the form
The confirmation screen is part of the service. Say clearly that the task is done, what happens next, and what the person should keep, such as a reference number or receipt. Same-day digital registration only feels finished if the last screen says so.
Key takeaways
- List every requirement before step one.
- Split the form into short steps, one topic each, with visible progress.
- Branch so people only see questions that apply to them.
- Replace official jargon with plain language.
- Make every error specific, fixable and non-destructive.
- Review before submit, and make the confirmation clear.
EasyBMV appears on my Work page with the outcomes reported by GovSoft. For how to test a flow like this with real users, see How to conduct a Usability Test.
All posts
