The Gold Standard of Plain Language Content Design Services | Findable Information and Clear Decisions

Plain language content design helps people find, understand and use information to make their real decisions. It does not mean changing an accurate contract into a misleading slogan. The gold standard is reader-centred writing joined to verified rules, usable page structure, understandable actions and ongoing maintenance.

This guide follows fictional Brooklane Workshops, where a parent’s reasonable question about cancellation and refunds is obscured by ceremonial language. It applies ISO 24495-1:2023 to the full content journey: defining the reader, structuring essential conditions, rewriting text, designing forms and links, testing comprehension and correcting inconsistencies.

The specialist scope differs from Public Sector Plain Language Communication, which addresses public administration, and Digital Accessibility Testing Services, which evaluates technical criteria. Media Localisation Services addresses connected languages. This article focuses on cross-sector content design that people can act upon.

Four checks before approving text

• **Relevant:** Does the material answer a real reader’s question?
• **Findable:** Can the reader get to that answer without decoding internal organisation?
• **Understandable:** Are the terms, conditions and actors clear?
• **Usable:** Can the reader confidently take the right next step?

Practical reading index

21-chapter practical index

1. People need to know what to do, not admire the complexity of the notice

A fictional private arts provider, Brooklane Workshops, offers short Saturday pottery classes. Its booking page states: ‘Fees are non-returnable except where service provision cannot be effectuated pursuant to the applicable scheduling provisions.’ A parent reads the notice but cannot determine whether a cancelled class will be refunded or rescheduled. The staff themselves disagree, and several people contact support only after paying.

The gold standard of plain language content design is relevant information that people can find, understand and use for their actual decisions. It is not childish vocabulary or a mechanical reduction in sentence length. Clear writing needs accurate source rules, a task-based structure, trustworthy examples, meaningful links and real comprehension testing. Brooklane Workshops is fictional; its unclear refund notice illustrates how language problems become service and fairness problems.

Back to chapter index · Continue to chapter 2

2. Define the reader and the decision before rewriting

A brochure, booking form, safety notice and legal disclosure may all require a different degree of detail and formality. Plain language begins with a reasonable account of who will read the material, what they know already and which action or decision the content supports. A reader may be busy, anxious, unfamiliar with the service or reading in a second language.

For Brooklane, the important decisions are whether the parent is eligible to book, what a lesson costs, how to reschedule and what happens if the provider cancels. A copywriter who rewrites random sentences without identifying those questions may create more pleasant language while preserving confusion. Start by gathering representative enquiries and identify what readers need first, before planning headlines or redesigning visual style.

Back to chapter index · Continue to chapter 3

3. Use the four governing principles in the published ISO standard

ISO 24495-1:2023 establishes principles and guidelines for plain language documents. The four governing principles are that readers get the information they need, find it easily, understand it and can use it. These dimensions are connected: a clear sentence about the wrong topic does not provide good service.

The standard covers primarily textual printed or digital information across many written languages, with examples in English. It intentionally does not replace technical digital-accessibility standards. A private workshop booking page and a formal application notice can draw from the same principles while using different content. An organisation should not advertise an entire website as independently ISO-certified simply because its writers consulted one standard.

Back to chapter index · Continue to chapter 4

4. Make essential terms visible before someone commits

Material conditions should be available before payment, application or another significant step. A cancellation charge hidden at the end of a long document does not become understandable because the paragraph itself uses short words. The content hierarchy should reflect the reader’s decision rather than the internal order in which departments drafted clauses.

For Brooklane, show fees, lesson dates, included materials and the main cancellation conditions beside the booking decision, with an appropriately detailed policy link. Explain whether the client or provider initiated a cancellation because those situations may have different contractual consequences. The copywriter must obtain the real business policy from an authorised owner and must not invent generous terms for the sake of a friendly tone.

Back to chapter index · Continue to chapter 5

5. Replace unnecessary jargon while keeping necessary distinctions

Technical terms can be useful when they are standard, precise and explained. The goal is not to ban vocabulary that some readers need. Instead, avoid internal abbreviations or ceremonial language where ordinary words communicate the same rule. If a legal or technical term must remain, define it once and show its consequence for the reader.

The fictional phrase ‘service provision cannot be effectuated’ could often be replaced by a statement about a class the provider cannot run, but only after the policy owner confirms what events fall into that category. A writer should preserve distinctions such as cancellation, rescheduling, refund, credit and transfer rather than treat them as synonyms. A short misleading sentence is worse than a slightly longer accurate one.

Back to chapter index · Continue to chapter 6

6. Put the action in a clear sentence with the responsible person

Passive voice is sometimes useful when the actor is unimportant or unknown, but a long chain of passive clauses can obscure who must act. Readers need to know who submits a form, who reviews a request, what happens next and how long a step may take. Prefer specific verbs where doing so preserves accuracy.

A notice saying ‘proof of payment shall be provided’ leaves open who should provide it and where. A clearer version might say, ‘Email your receipt to the bookings team,’ if that is truly the required method. Do not specify a channel or deadline that the service cannot support. Make each instruction a truthful action, with the object, conditions and relevant response route near it.

Back to chapter index · Continue to chapter 7

7. Separate decisions into small but meaningful steps

A long paragraph may combine eligibility, price, evidence requirements and dispute handling. Splitting the paragraph can help only if readers retain the relationship among those ideas. Headings and ordered steps should reflect a real process rather than arbitrary word-count targets.

For a workshop booking, separate choosing a class, confirming the fee, making payment and requesting a change. A parent should not have to read the refund policy repeatedly to understand the confirmation screen. Use logical groups and state what the user needs at that moment, while preserving a route to full terms. W3C’s cognitive accessibility guidance on helping users focus recommends short critical paths and necessary task information, although it is supplemental guidance rather than a new mandatory WCAG criterion.

Back to chapter index · Continue to chapter 8

8. Give headings the questions readers actually ask

Heading hierarchies help people skim, search and use assistive technology. A title such as ‘Miscellaneous Administrative Provisions’ is less useful than ‘What happens if we cancel your class?’ when that is the relevant question. Navigation should match the reader’s vocabulary and the content’s real purpose.

The booking page could use clear sections for class fees, changing a booking, when refunds apply and how to contact staff. Meaningful HTML heading structure is as important as font size or bold styling. If the same policy is used in an email, ensure links and section names remain consistent. A good content design lets someone reach the answer without reading every unrelated policy paragraph.

Back to chapter index · Continue to chapter 9

9. Use numbers, dates and conditions in a checkable way

Words such as soon, reasonable, normally and sometimes can hide important uncertainty. When a service has a specific price, deadline or response target, state it accurately with its units, time zone or relevant basis. Where the policy genuinely allows discretion, say what that discretion concerns instead of inventing a false guarantee.

For Brooklane, ‘request a change at least 48 hours before your scheduled class’ is clearer than ‘prior to commencement’ if the business actually follows that rule. If the deadline is not a full 48 hours but closes at a particular office time, the wording must reflect that. A copywriter should verify conditions with the owner and test examples across weekends and holidays before publishing. Precision supports simplicity.

Back to chapter index · Continue to chapter 10

10. Use examples that reveal the actual edge cases

An example can make a conditional rule easy to understand, but it can also create an unsupported promise. Write examples for the most common and most consequential cases, including what happens when a client cancels, the provider cancels or a booking is rescheduled more than once.

An illustrative statement might say, ‘If we cancel your class, you can choose another available session or a refund,’ but only when the real agreement grants those options. A scenario about customer no-shows may lead to a different result. Mark examples as examples when the contract needs broader conditions. A user should be able to distinguish a typical case from the complete rule without requiring legal training.

Back to chapter index · Continue to chapter 11

11. Avoid double negatives and hidden exceptions

Sentences built from several nots, unlesses and excepts are difficult to follow. They become more risky when a missing word reverses a right or obligation. Sometimes a short table showing the main situations is clearer than a sequence of nested conditions in a single paragraph.

Review every exception against the original approved policy. The statement ‘No refunds unless the provider has not failed to deliver’ is grammatically possible but practically confusing. Split conditions into explicit scenarios, each with its outcome and any limits. Retain necessary legal meaning even when the surface text becomes simpler. The editorial objective is a reader who can predict the right outcome, not merely a formula producing shorter sentences.

Back to chapter index · Continue to chapter 12

12. Make form labels and errors describe the user’s next step

Plain language extends beyond articles into buttons, form fields, validation messages, menus and confirmation notices. A form can contain excellent instructions while its control labels use internal terms nobody recognises. Users need to understand what to enter and how to recover when something is wrong.

At the workshop checkout, ‘Participant age’ is more meaningful than ‘Age parameter’ and an error should explain which value needs correction without exposing private information. W3C cognitive guidance on understandable controls describes predictable labels and clear instructions. Its patterns support inclusive design but do not replace formal WCAG testing. Verify the actual form completion rather than evaluating the text in a detached document.

Back to chapter index · Continue to chapter 13

13. Write links that tell readers where they will go

Generic links such as ‘click here’ or ‘more information’ may force users to inspect surrounding paragraphs to understand the destination. Descriptive link text helps people who navigate by screen reader link lists, skim on mobile or return after a break.

The link beside a refund summary might say ‘Read the full cancellation and refund policy’ rather than ‘details’. Ensure the destination actually contains the promised information and is current. Avoid making a notice sound definitive when the linked page contradicts it. Good content governance checks labels and target pages together; a sensible link phrase is no help when it leads to an outdated version.

Back to chapter index · Continue to chapter 14

14. Design tables and lists for genuine comparison

Tables can clarify prices, conditions and outcomes, while lists help readers follow a sequence. But tables with complex merged cells may be difficult to navigate on mobile or through assistive technology. Choose structures that match the information rather than decorate the page with grids.

For Brooklane, a short two-column list of cancellation scenario and available response can be easier to use than a dense legal paragraph. W3C’s accessible tables tutorial explains proper data-header relationships. If a table is necessary, make the headers meaningful and check responsive layouts. A screenshot of a pricing table is not the same as accessible structured content.

Back to chapter index · Continue to chapter 15

15. Preserve accuracy when translating plain-language content

An English rewrite can be clear yet difficult to adapt if key terms remain unexplained, dates are ambiguous or examples rely on cultural knowledge. Multiple language editions should share one approved source meaning while allowing natural expression. A literal translation of an English idiom may be less understandable than a careful equivalent.

Work with competent translators and reviewers, providing a glossary of booking terms and necessary conditions. If one language page says refunds are possible after provider cancellation while another says only credits are available, the product is inconsistent. The eduKate Media Localisation guide addresses connected multilingual publishing. Plain language is a responsibility for each promised audience, not merely the original English writer.

Back to chapter index · Continue to chapter 16

16. Protect source policy and legal review through the rewrite

A simplified document can accidentally grant, remove or broaden a right. Policy owners, subject experts and qualified legal reviewers must confirm consequential statements. The content designer should not choose between precision and comprehension as though only one can survive.

Track which source clauses or operational rules support each proposed plain-language statement. A reviewer should see the current rule, the draft explanation and any material difference. If the provider’s refund policy conflicts with its actual booking software, correct the system or the policy before publishing an elegant explanation of the wrong workflow. A polished public notice is not a substitute for a functioning service.

Back to chapter index · Continue to chapter 17

17. Use accessibility principles rather than typography alone

Large fonts and short paragraphs can improve reading, but accessible content also requires meaningful heading structure, sufficient contrast, working links and suitable navigation. A user may resize text, use a screen reader, switch language or need an alternate format. Plain language and technical accessibility overlap but are not interchangeable.

W3C’s cognitive accessibility overview explains how clear information, predictable controls and different presentation options support people with cognitive and learning disabilities. The content-design service should coordinate with appropriate accessibility professionals and test the actual public page. It should not claim that meeting ISO plain-language principles automatically meets every WCAG requirement.

Back to chapter index · Continue to chapter 18

18. Test understanding by asking people what they would do

Readability scores and word counts measure textual features, not whether a reader can identify the right decision or action. Useful testing asks representative people to find an answer, explain the relevant condition and carry out a task without coaching. The objective is evidence about practical understanding.

Give a parent the fictional workshop booking page and ask what happens if the class provider cancels. Ask where they would request a change and which proof is needed, then observe what they find. If people consistently assume ‘credit only’ despite a real refund right, revise the content and presentation. A small test is directional evidence, not proof that every possible reader understands the material. Record limitations and retest important changes.

Back to chapter index · Continue to chapter 19

19. Measure support demand and avoid wrong incentives

A clearer page may reduce repeated customer questions, but low support volume does not necessarily mean people understand or receive their rights. Some confused users give up silently, while others submit incorrect bookings. Measure successful task completion, mistakes and feedback alongside contact demand.

For Brooklane, track whether readers can predict the correct cancellation outcome and complete the approved process. Do not reward staff for discouraging inquiries merely to make an information page appear successful. A good service uses complaints and misunderstood terms to improve the material and underlying process. Content metrics should illuminate genuine outcomes rather than favour the shortest possible text.

Back to chapter index · Continue to chapter 20

20. Build a revision process that keeps public words truthful

Policies, prices, class dates and contacts change. Plain-language content needs an owner, authoritative source, review date, dependent channels and a process for corrections. An old confirmation email or booking PDF may continue distributing a condition long after the website has been updated.

Maintain a change-impact list across webpages, forms, reminders, invoices and translations. When Brooklane changes a deadline, verify the operational system and public pages together. A consumer should not see one rule at checkout and another on the receipt. Document material corrections and decide whether affected customers need a direct explanation. Clear writing is a maintained service, not a one-off copywriting exercise.

Back to chapter index · Continue to chapter 21

21. The gold standard is a reader who can make the right decision

After its revision, Brooklane Workshops states the class fee and booking conditions clearly, presents cancellation scenarios in useful language and directs parents to an accessible contact route. The staff, webpage and booking software follow the same approved policy. A parent can identify what happens in their situation without being forced to decode a ceremonial legal sentence.

Plain language content design earns its gold standard when readers can find, understand and use accurate information. The achievement is not a lower reading-grade score or shorter paragraph alone. It is honest, navigable communication that respects people’s time and ability to make an informed choice.

Back to chapter index

Worked example: a refund notice the parent can actually use

All policy terms in this comparison are illustrative, not statements of an actual business’s rights. A real provider must validate its own legal and operational terms.

Decision-focused content acceptance matrix

Use these questions in a review or commissioning brief rather than treating a reading-grade score as a complete quality measure.

Plain language editorial checklist

• Start with the reader’s actual decision and verified source policy.
• Use ISO 24495-1 principles without claiming automatic certification.
• Put material conditions before the commitment or transaction.
• Replace unnecessary jargon while explaining required technical terms.
• Write clear actions, responsible parties, dates, money and exceptions.
• Give pages meaningful headings, links, tables and accessible structure.
• Review with subject owners and test realistic reader tasks.
• Preserve the same approved meaning across forms, emails and languages.
• Maintain content ownership and correct consequential mistakes.

Frequently asked questions

These answers clarify what plain language does and does not promise for legal, commercial, educational and digital communication.

1. Does plain language mean removing legal precision?

No. Plain language seeks to preserve the real rule while making its significance easier to understand. Some technical or legal terms should remain where they have necessary meaning, accompanied by a clear explanation and relevant example. A policy owner or qualified reviewer should confirm the rewritten conditions. A short sentence that incorrectly grants a refund is not an improvement over a longer accurate provision.

2. What are ISO 24495-1:2023’s core principles?

Readers should receive information relevant to their needs, find it readily, understand it and be able to use it. The standard applies primarily to textual printed or digital material and offers guidance across written languages, although examples are in English. These principles support a practical evaluation of whether people can complete a decision, not merely a preference for shorter words.

3. Is plain language the same as WCAG accessibility?

No. Plain language supports understandability and cognitive access, while WCAG contains broader technical and content success criteria. A very clear paragraph can sit inside a page whose controls are keyboard-inoperable. Conversely, a technically accessible website may use impenetrable jargon. The right approach combines readable content, semantic structure, operable controls and appropriate user testing.

4. Can readability formulas prove a document is easy to use?

Not by themselves. Formulas can estimate features such as sentence length or word complexity, but they cannot assess factual completeness, task sequence, cultural assumptions or whether an action is really possible. Test readers’ ability to find an answer and predict the correct outcome. A policy could receive a favourable readability score while hiding its key exception in an unrelated section.

5. Should every sentence be short and active?

No universal sentence length is suitable for every audience and subject. Shorter, direct sentences often help, but awkward fragmentation can hide relationships or create a mechanical reading experience. Passive voice can be reasonable when the actor is unknown or unimportant. Write for comprehension and truthful meaning, then test the result rather than impose one mathematical limit on every sentence.

6. How should difficult terms be handled?

Use ordinary language where accurate, explain necessary specialist terms and apply them consistently. A financial, scientific or regulatory phrase may remain because it identifies a real concept. Give the reader a practical explanation of what it means for their decision, with an appropriate example. Do not replace several different obligations with one vague term merely because that seems simpler.

7. What is the best structure for a cancellation policy?

Start with the decision readers need: when a refund, credit or rescheduling may apply. Separate customer cancellations from provider cancellations and identify timing, fees and required requests. Use a short summary, a clear scenario table when helpful and a link to the full approved terms. Test common edge cases before publication. Ensure the actual booking system follows the same policy.

8. Can a plain-language summary replace the full contract?

That depends on the specific legal and contractual context. A summary can explain essential conditions but should not silently contradict or erase legally necessary text. Tell readers which part governs if there is a distinction and obtain qualified review. When the summary communicates a different deal from the contract, the organisation has a problem to resolve rather than an excuse to blame the reader.

9. Does plain language need to be written again for each language?

The authoritative policy meaning should be consistent, but natural phrasing and examples may differ across languages. Qualified translators or reviewers need the source rule, glossary and audience context. A literal copy of an English idiom may not be clear in another language. Test critical conditions and the full user journey for each promised edition, rather than label all translations plain language solely because the English source was revised.

10. How can a company measure plain-language improvements?

Ask readers to find specified answers, explain conditions and complete a realistic action without guidance. Monitor avoidable errors, repeated enquiries, drop-off and corrections along with participant feedback. Make the task and success condition explicit. Do not claim a reduction in phone calls proves clarity if people are abandoning the process or losing entitlement through confusion.

11. How does plain language help cognitive accessibility?

W3C’s cognitive accessibility guidance recommends understandable words, manageable information chunks, familiar navigation and clear controls. People differ in memory, attention and language needs, so plain language benefits a wide audience rather than one medical category. It is supplemental guidance in addition to applicable WCAG criteria. An organisation should not require people to disclose a diagnosis before receiving clear instructions.

12. What should a content design agency hand over?

The brief should specify intended readers and decisions, verified source rules, approved content hierarchy, headings and links, rewritten public copy, meaningful examples, form labels as contracted, qualified review, testing findings and correction ownership. Include a list of dependent channels such as receipts and emails. A polished document without a way to maintain it is not a complete service.

Primary references and adjacent eduKate guidance

• ISO 24495-1:2023 Plain Language Governing Principles
• W3C WAI Cognitive Accessibility Overview
• W3C Supplemental Guidance: Clear Content
• W3C Supplemental Guidance: Understandable Controls
• W3C Supplemental Guidance: User Focus
• W3C Tables Tutorial
• W3C WCAG 2.2
• eduKate — Public Sector Plain Language Communication
• eduKate — Digital Accessibility Testing Services
• eduKate — Media Localisation Services
• Gold Standard Sectors & Services Directory

Standards note, October 2026: ISO 24495-1:2023 is a published standard about plain-language documents primarily in text form. Its scope does not replace WCAG, consumer law, legal review or the duties of a business to honour its actual policies. W3C cognitive-accessibility patterns cited here include supplemental guidance beyond normative WCAG success criteria. This page is service-design education, not a legal review of any specific booking contract.