Readability and Plain Language

Plain-Language Rewrite Plan

Plan a reader-centered rewrite of complex content while protecting required meaning, legal or technical precision, decisions, conditions, and exceptions.

Free editable Markdown · Plain-language editors, public-sector writers, and content designers · Updated July 30, 2026

Download Markdown

Accessible HTML preview

Blank template

The downloaded file contains the same fields in editable Markdown.

Reader and task

Source asset and version: [Enter]
Intended reader: [Describe situation, not a demographic stereotype]
Reader's main question: [Write in their likely words]
Decision or action: [What must they understand or do?]
Prior knowledge: [What can reasonably be assumed?]
Context or stress factors: [Time pressure, device, language, consequences]
Known comprehension barrier: [Describe evidence or observation]

Meaning inventory

Required outcome: [State]
Mandatory facts: [List]
Conditions and eligibility rules: [List]
Deadlines and effective dates: [List]
Risks or consequences: [List]
Exceptions: [List]
Rights and choices: [List]
Necessary technical or legal terms: [Term, definition, approved use]
Meaning owner: [Name and approval date]

Rewrite map

Duplicate for each source passage.

Passage ID and original purpose: [Enter]
Reader problem: [Unknown actor / Dense condition / Jargon / Poor order / Other]
Required meaning: [Copy from inventory]
Planned change: [Move / Split / Define / Replace / List / Example / Delete]
Draft plain-language version: [Write]
Meaning risk to check: [Describe]
Expert reviewer: [Name/role]

Structure and language checks

The direct answer or required action appears before background detail.
Actors and responsibilities are named clearly.
Sentences express one manageable relationship without severing conditions.
Necessary terms are defined once and used consistently.
Headings and lists help readers predict and scan the content.
Examples are labeled and do not imply broader rights or results.
Help, error recovery, and escalation routes are easy to find.

Comprehension test and approval

Participants and relevant context: [Describe respectfully]
Find task: [What must they locate?]
Explain task: [What must they restate?]
Action scenario: [What decision must they make?]
Observed errors or hesitation: [Record]
Revision made: [Describe]
Meaning review: [Reviewer, version, date]
Final editorial approval: [Reviewer, version, date]
Next review trigger: [Policy change, user evidence, scheduled date]

How to use this template

Define the reader situation, primary decision, context, and barriers to understanding.
Extract mandatory facts, conditions, exceptions, terms, and risks with subject-owner approval.
Plan a reader-first order and specific wording or format changes for each difficult passage.
Test important tasks and explanations with representative readers and record failures.
Complete meaning, accessibility, editorial, and subject review before publishing.

Start with the reader's decision and required meaning

Plain language is not merely shorter wording. Identify who will use the content, what they need to decide or do, what they likely know already, and what may cause stress or confusion. Extract the statements that must survive revision: eligibility conditions, deadlines, risks, rights, obligations, technical constraints, and exceptions. Ask the subject owner to approve this meaning inventory before rewriting. Then place the answer or required action where readers need it, not where the source document's internal history happened to put it. A reader-centered order often begins with “what this means for you,” followed by steps, conditions, examples, and routes for help.

Replace avoidable complexity while preserving useful terms

Prefer familiar words, active constructions, concrete actors, and verbs that show what happens. Break long sentences where each new sentence can retain a clear relationship to the original rule. Define necessary terms at first use and keep them consistent; replacing every technical term with a loose synonym can make a page less precise. Turn dense conditions into headings, lists, tables, or step sequences only when that format accurately represents the logic. Examples can clarify a rule, but label their limits so readers do not treat one scenario as the entire policy. Never hide an unfavorable condition in a note merely to make the main text sound simpler.

Test comprehension, not only readability scores

A grade-level or sentence-length metric can flag passages for review, but it cannot determine whether readers understand a deadline, exception, or consequence. Ask representative users to find information, explain it in their own words, and choose a next action from realistic scenarios. Note where they hesitate, infer the wrong condition, or miss a recovery route. Reconcile their feedback with the approved meaning inventory and expert review. If the rewrite must fit an interface, test labels, errors, and nearby context as part of the task. Record what changed and why so future maintainers do not restore familiar but confusing language.

See the fields in context

Fictional example: library card renewal

Willow Library and its rules are invented. This example must not be used as actual library policy.

Reader question: “Can I renew online if my card has expired?”
Required meaning: Fictional cards expired fewer than 30 days may be renewed online; older cards require an in-person identity check.
Rewrite plan: Put the 30-day decision first, define the two paths, then explain which imaginary documents the second path needs.
Comprehension test: Two fictional participants initially missed the cutoff when it appeared in a note, then identified the correct route after it became a heading.
Approval: The imaginary policy owner checked that the clearer wording preserved the exception.

Frequently asked questions

Does plain language mean removing all technical terms?

No. Keep terms readers need to act accurately, define them where they first matter, and avoid introducing several labels for the same concept.

What reading level should I target?

Choose language for the real audience and task. Metrics can locate complexity, but comprehension testing and accurate meaning are more informative than one universal score.

Can a legal or policy sentence be rewritten?

Often, but the approved wording and process depend on the organization and jurisdiction. Preserve the source and require qualified review when meaning could change rights or obligations.

How should disagreements between readers and experts be handled?

Investigate the exact misunderstanding. Revise presentation without altering the rule, or ask the policy owner whether the underlying rule itself needs clarification.