Fill out enough paperwork and you start to hear the questions as statements. Emergency contact, relationship to applicant: we expect you to have a family shaped like ours. Employer name and work phone: we expect you to have one job, with a desk. Previous address, five years: we expect your life to have been stable. Every required field tells users what a system recognizes and what it ignores. That is the whole idea this essay unpacks, because once you see it, no form ever looks neutral again.
The form is the message
An application is usually the first conversation between a person and an institution, and the institution wrote both sides of it in advance, the way whoever picks a default quietly wins the argument. The applicant learns what counts as a household, what counts as income, what counts as a name. There is no box for explaining. When your situation fits the fields, the form is invisible, a five-minute chore. When it does not fit, the form becomes a small tribunal, and it rules against you before any human has read a word.
A housing form that cannot handle shared custody creates avoidable friction. The parent whose children live with her Thursday through Sunday is a household of three or a household of one depending on which box she checks, and the wrong guess can mean a smaller apartment or a fraud flag. The designers did not decide that split families matter less. They just never imagined one, and the form ships the designers' imagination out to everyone.
What Congress cut from the student aid form
The federal student aid application, the FAFSA, spent decades as the canonical bad form: over a hundred questions standing between teenagers and college money. Research kept showing that the form itself, not eligibility, kept low-income students from aid. In December 2020 Congress passed the FAFSA Simplification Act, a full overhaul that took effect with the 2024-25 form: far fewer questions, tax data pulled directly from the IRS instead of retyped by hand.
Two deletions deserve a close look. The old form asked about drug convictions and about Selective Service registration, and both questions could cost an applicant aid. Neither had anything to do with financial need. They were values statements wearing the costume of data collection, teaching a generation of applicants that federal help was conditional on a clean record and a registration card. Congress removed them, which is also a values statement. Forms teach people what the system values, and edits to a form are edits to the lesson.
Plain language is policy, not polish
The same logic applies to wording. The Plain Writing Act of 2010 requires federal agencies to write public-facing documents clearly, and it exists because unclear writing functions as a filter. A benefits notice that only a lawyer can parse has not informed the public. It has selected for people who can afford lawyers, or who have the spare hours and confidence to decode it. Complexity is regressive. It taxes exactly the people with the least slack, while fluent, well-resourced applicants glide through.
This is why I resist calling form reform cosmetic. Nothing about eligibility changed when agencies rewrote notices in plain English, and yet who successfully claims a benefit changes, which is the outcome the underlying law was supposed to produce. The form is not the wrapping around the policy. For the person filling it out at a kitchen table, the form is the policy.
Reading a form like an audit
You can reverse-engineer an institution's assumptions from its paperwork in a few minutes. Here is what I look at.
- The required fields. Each asterisk is a claim that the process cannot proceed without this fact. Test the claim: would the decision actually change if this box were blank?
- The fields that are missing. No place for a second caregiver, a nickname the person actually uses, a phone that is shared. Absence marks the lives the designers never pictured.
- The failure path. What happens to an incomplete submission? Silent rejection punishes confusion. A phone call treats it as a conversation, and a predictable process feels humane even when the answer is no.
- The penalty language. Count the warnings about fraud and perjury, then count the sentences that explain your rights. The ratio tells you whether the institution sees an applicant or a suspect.
- The time and documents demanded. Pay stubs, notarized letters, in-person verification during office hours. Every requirement is cheap for someone and expensive for someone else, and the expensive side is rarely consulted.
The repair rule is short. Remove fields that do not change the decision. Every question a form asks should earn its place by altering an outcome. Anything else is curiosity with a badge, collecting data because collecting is easy and deleting requires a meeting.
The next form on your desk
Most readers will never redesign a federal application, but nearly everyone administers some small form: a volunteer signup, a rental application, a school pickup list, a club membership sheet. Take the one you own and cut a single question that does not change any decision you make. Then find one person whose situation your form handles badly, a hyphenated name, a shared address, a nonstandard family, and add or reword one field so they fit without explaining themselves. Small edits, but they change the opening message your institution sends. People read it more carefully than anything on your website.