Plain language improves government forms by cutting the reading effort a resident has to spend on every label, instruction, and error message, which produces fewer mistakes, fewer incomplete submissions, and fewer calls to a service counter. The change is mostly mechanical: familiar words, one idea per question, instructions placed before the field, and error messages that say what to do next.
Most people never touch a federal form. They apply for a building permit, a parking permit, a library card, a food license, a birth certificate, a housing benefit, or a change of address through a city or county office, usually on a phone, often in a second language. Those are the forms worth rewriting first.
Table of Contents
- What Is Plain Language in a Government Form?
- How Plain Language Improves Government Forms
- Which Parts of a Government Form Need the Most Clarity?
- How Do You Write Questions People Can Answer Correctly?
- How Can Teams Test Whether a Form Is Plain?
- What To Measure Before and After a Rewrite
- Where Does Plain Language Need Extra Care?
- What Does a Better Government Form Look Like?
- What Are the Common Mistakes to Avoid?
- Frequently Asked Questions
- Why is it important to use plain language?
- What are the government’s plain language guidelines?
- What are the six principles of plain language?
- Is plain writing a civil right?
- Does the Plain Writing Act apply to state, county, and city forms?
- How do you measure if a form is in plain language?
- Conclusion
What Is Plain Language in a Government Form?
Plain language on a form means the reader can tell, without a dictionary and without a second reading, what is being asked, what format the answer takes, and what happens after they submit it.
That is different from simplified writing, which often strips away detail, and different from informal writing, which drops the formality that makes an official document feel official. Simplifying a benefit application by removing the eligibility rules is a legal problem. Rewriting “the applicant must demonstrate continuous residency” as “you must have lived in the county for the last 12 months” is a plain language win. Nothing important left the page.
Clarity matters here because the reader is often doing three things at once: figuring out the rules, finding the right field, and worrying about whether a wrong answer costs them something. Every unnecessary phrase competes with those tasks.
How Plain Language Improves Government Forms
Here is how plain language improves government forms in practice. Six changes account for most of the difference, and each one shows up as a number an agency can watch.
- Fewer wrong answers. When a question asks one thing, the answer that comes back matches the question. Combined questions produce combined answers that staff then have to untangle.
- Fewer skipped fields. Optional and required fields stop looking identical when the required marker is a word rather than a red asterisk nobody has explained.
- Higher first-time submission rate. USCIS writer-editor Kathryn Catania has reported individual offices seeing roughly a 20% increase in properly submitted forms after plain language rewrites, along with smaller customer service backlogs and shorter follow-up calls.
- Fewer avoidable contacts. A clear instruction line answers the question at the moment it arises, which is cheaper than a phone call that answers it ten minutes later.
- Wider access. Plain sentences help readers with limited English proficiency, low literacy, dyslexia, and screen reader users at the same time, because the sentences themselves get simpler.
- Faster staff processing. Staff read the same answers repeatedly. Answers that arrive complete and legible shorten review and reduce the back-and-forth letters.
| Change made | Effect on the resident | Effect on the agency |
|---|---|---|
| One question per field | Answers the question as asked | Fewer clarification letters |
| Instruction above the field, not below | Reads it before typing | Fewer rejected submissions |
| Plain error messages that name the fix | Corrects the field immediately | Fewer repeat contacts |
| Examples with real formats | Knows what to enter | Shorter review queue |
| Eligibility stated in everyday words | Knows whether to apply at all | Fewer ineligible applications |
| Consistent labels for the same idea | Recognizes the same field each time | Less rework between forms |
One caveat worth stating plainly: readability scores on their own prove very little. A page can score well and still be organized in the wrong order. Practitioners who work on this consistently say testing with real users is the part that cannot be skipped.
Which Parts of a Government Form Need the Most Clarity?
The form title, eligibility statement, individual questions, required fields, document requests, consent language, deadlines, and next steps are where readers get stuck. Each has a recognizable failure pattern.
| Form element | Common problem | Plain language fix |
|---|---|---|
| Title | “Form 14B-77 (Rev. 3/19) — Multi-Family Structural Alteration Application” | “Apply to change the structure of a building with more than one home” |
| Eligibility | Copied straight from the code chapter | One plain sentence, then a link to the full rule |
| Question | “Have you or any household member previously applied for this benefit?” | “Did you apply for this benefit before? Include applications by anyone in your home.” |
| Required field | Red asterisk, no explanation | “Required” in the label itself |
| Document request | “Provide substantiation of identity” | “Upload a photo ID: driver license, passport, or state ID card” |
| Consent | Two paragraphs of dense legal text with no summary | A one-line summary in plain words, then the full text in a details section |
| Deadline | “Within 10 business days of the date of determination” | “Within 10 business days after you get a letter telling you your application was approved” plus the date |
| Next steps | Nothing after submit | A confirmation page naming the reference number, the review timeline, and who to contact |
How Do You Write Questions People Can Answer Correctly?
A question is answerable when a resident knows what a good answer looks like without guessing at the shape of the field.
Use one idea per question. “Have you or any household member previously applied for this benefit?” should be “Did you apply for this benefit before?” and a separate question for other household members.
Use specific time frames. “In the last three years” beats “recently,” and “since January” beats “in the applicable period.”
Use active voice and plain verbs. “The City will review your application within 10 business days” is easier to follow than “Your application will be subject to review by the City.”
Make answer choices match how people talk. People say “I rent” and “I own it,” not “tenure status: lessee or fee simple.” When you must keep a technical term, put the everyday version first and the technical version in parentheses after it.
How Can Teams Test Whether a Form Is Plain?
Testing a form is a six-step loop, and the order matters. Skipping straight to a readability score is the most common mistake.
- Audit. Pull the live form, its instructions, and the confirmation and error messages. List every field label, every paragraph longer than two sentences, and every acronym on the page.
- Rewrite. Apply the six changes above one at a time. Have a subject matter expert verify factual accuracy after the rewrite, not before it, which is where most internal objections come from.
- Check readability. Run a Flesch-Kincaid pass on the instructions. A working target is sentences of 15 to 20 words and a grade level of 8 to 10 for public-facing instructions.
- Run task-based usability testing. Five to eight people who have never seen the form. Give each a real task, such as “apply for a permit to add a second bathroom,” and watch. Do not help.
- Review accessibility. Confirm every field has a programmatic label, required fields announce their state to a screen reader, and error text is tied to the field that caused it rather than sitting in a banner at the top of the page.
- Check your support data. Pull the six weeks of calls, emails, and returned applications. Look for the same questions repeating, which is a measurement you already have.
What should you ask test participants? Ask them to say out loud what they think the form is asking before they answer anything. That one question exposes a label that is ambiguous, an instruction that sits in the wrong place, or a deadline they misread. Afterwards, ask what they expected to happen next, because that is where most forms end without an answer.
What To Measure Before and After a Rewrite
| Metric | What it tells you |
|---|---|
| First-time submission rate | Whether the form was understood the first time |
| Returned or incomplete applications | Which fields and instructions still fail |
| Average time on task in testing | Where effort is going |
| Support contacts per 100 submissions | Whether the page answered the question |
| Error message frequency per field | Which fields need work next |
| Help text or FAQ page views | Resident questions the form still provokes |
Take the baseline before you change anything, then compare the same weeks after launch. Seasonality matters: a permit form will behave differently in January than in May.
Where Does Plain Language Need Extra Care?
Some language has to stay precise, and rewriting it is a legal and subject matter decision rather than a writing one.
Legal notices, consent language, and liability waivers usually have to carry specific wording. Ask your attorney whether a plain language summary can sit above the required text, with the original one click away. In many programs the summary is what readers actually use, and the legal text exists to satisfy a review requirement rather than to inform.
Health and safety questions need plain wording without losing their warning. “Do you have a condition that affects your breathing?” is clearer than “Do you have any pulmonary compromise,” and neither is a diagnosis. Emergency reporting forms are the hardest case: the language has to be plain, and it has to work for a frightened person on a bad connection.
Financial applications carry the most damage from vague wording, so those get the most scrutiny. When a program has a strict legal definition of income or household, keep the definition in the instructions and restate it in the plainest words the definition allows, then add one worked example.
Forms copied verbatim from regulatory text are where jargon usually comes from. Cutting the copy is a decision for policy and legal staff, not a writing shortcut, and the rewrite should not happen without them in the room.
What Does a Better Government Form Look Like?
Here is a short municipal form, rewritten. The original is a real pattern: a form code, a title in code language, a dense eligibility paragraph, and a submit button with no next step.
Before. “Form P-204 (Rev. 08/22). Structural Alteration Permit Application. Applicant must confirm that the proposed alteration is consistent with applicable provisions of the Uniform Building Code as adopted by the municipality and that no work commences prior to issuance of a permit. Failure to complete all required fields will result in return of application.”
After. “Apply to change the structure of a building. You need this permit if you are moving a wall, adding a load-bearing beam, or adding a bathroom that needs plumbing. Do not start work until your permit is issued. We check each application against the building code the city has adopted. If a required field is empty, we send the application back, which adds about two weeks.”
The second version is longer than the first, which surprises people. That is usually the trade: plain language adds the words that make a rule usable, and it removes the sentences that made the original hard to follow.
The rest of the structure matters as much as the sentences. Use short headings that describe sections in the resident’s terms, group related fields together, and put an example format in the help text next to date and identification fields. Show progress, such as “Step 2 of 5,” so people know the form ends. Write confirmation messages that name the reference number, the expected review time, and the next action, whether that is a payment, an inspection, or nothing at all. And write error messages as instructions: “Enter your date of birth as month, day, year” beats “Invalid input.”
What Are the Common Mistakes to Avoid?
Hiding the requirement in a paragraph. A deadline buried in sentence four is a missed deadline. Put it in a field label or a bold line of its own.
Using terminology without explanation. “Verification of residency” means a document that proves where you live. Say both, in that order.
Combining questions. Each additional clause in a question produces an additional wrong answer.
Vague error messages. “Invalid entry” tells the resident nothing about what to change. Name the field, the problem, and the fix.
Inconsistent labels. If one field says “Date of birth” and the next says “DOB,” the resident stops trusting both.
Collecting fields nobody uses. Every field is an abandonment risk. Delete the ones no downstream process reads.
Assuming digital access. A plain language form still needs a paper path, a phone path, and staff who can fill it in with the resident. Most people ask for help at a counter, and that conversation is part of the form.
Frequently Asked Questions
Why is it important to use plain language?
Because a form nobody understands cannot be completed correctly. Plain instructions, clear labels, and one question per field reduce wrong answers, skipped fields, and returned applications, and they cut the calls a service center fields about the same confusion. Residents get decisions faster, and agencies spend less staff time on clarification. It also widens access for readers with limited English proficiency, low literacy, or assistive technology.
What are the government’s plain language guidelines?
For federal agencies, they come from the Plain Writing Act of 2010, which requires clear Government communication the public can understand and use, plus OMB guidance and a designated Plain Language Coordinator in each agency. In practice the guidance points to familiar words, short sentences, active voice, and organization built around what the reader needs to do. Many states, counties, and cities have adopted similar rules by policy, even where no statute applies.
What are the six principles of plain language?
Six principles cover most form problems. Put the reader’s goal first and organize around it. Use familiar, everyday words instead of jargon. Keep sentences short and put one idea in each one. Use active voice and concrete verbs. Use lists, headings, and white space so content is skimmable. And check your work by asking real users to complete a real task, because readability scores catch sentences, not structure.
Is plain writing a civil right?
It is not framed that way in law. The Plain Writing Act of 2010 requires federal agencies to write clear public communications, and courts have treated language access and access to public services under other statutes and constitutional principles. Advocacy groups often describe plain language as an access right, and agencies that treat it that way tend to fund it better. Practically, the requirement is real, though it does not reach regulations themselves.
Does the Plain Writing Act apply to state, county, and city forms?
No. The Plain Writing Act applies to federal agencies, and it does not cover Congress, regulations, or documents that must contain specific legal language. Local agencies are bound by state rules where they exist, by their own council policies, and by accessibility obligations that apply regardless. That gap is why a city permit form can be far harder to follow than a federal benefits form, and why local teams need their own mandate to change it.
How do you measure if a form is in plain language?
Combine a readability check with real use. Run a Flesch-Kincaid pass and aim for sentences of 15 to 20 words and a grade level around 8 to 10 on public instructions. Then watch five to eight first-time users complete a real task without help. Finally, compare support data before and after: first-time submission rate, returned applications, and support contacts per 100 submissions tell you whether the rewrite actually changed anything.
Conclusion
Start with one form that gets heavy traffic and causes frequent callbacks. Write down the three elements residents ask about most, rewrite those with real applicants in the room, then test the new version with five people who have never used it. That single cycle will tell you more than any style guide, and it is small enough to finish this quarter.
