Forms are legislation with a text field
Why government form design is not really form design, and what changes when you accept that every field is downstream of an instrument somebody has to enforce.
The most common mistake in government form design is treating the form as an interface problem. It looks like one. It has fields, labels, validation, a submit button. Everything about it invites the usual toolkit.
But a public-sector form is not asking questions because a designer chose them. It is asking because an instrument requires the answer, a registry process depends on it, and a downstream system will reject the application if it is malformed. The field is the visible end of a chain of obligations.
Three consequences
One: you cannot remove a field by deciding it is unnecessary
You can only remove it by finding who needs it and why, and getting that need retired or satisfied elsewhere. "We cut the form from 40 fields to 12" is either an excellent piece of policy work or a story that ends with a registry team re-keying the missing information from phone calls.
Two: error messages are a legal interface
The generic advice is to write plain-language errors. The specific advice is harder: write the error against the actual rejection reason, in language the applicant can act on, without misstating the requirement. Those three constraints conflict often enough that each significant error message is its own small design problem.
Three: the mental model mismatch has to be resolved deliberately
The legislation, the internal process and the applicant’s understanding all mean something slightly different by the same noun. Someone has to decide which one the interface speaks. If nobody decides, the interface speaks the internal process — because that is who wrote the requirements — and the cost of the mismatch is quietly transferred to the person with the least ability to absorb it.
What this changes about the work
- Research includes the processing side. The registry staff know precisely which fields generate rework. That is the highest-yield research hour available and it is routinely skipped.
- The Digital Service Standard is a floor. Alignment is necessary and does not by itself produce a form that can be completed.
- Accessibility is not a review stage. It is the constraint that a form which must be usable by everyone with a legal entitlement is not optional in the way a marketing site’s is.
A form that is easy to fill in and impossible to process has moved the work, not removed it.