Skip to content

How We Build · 6 min read
Why we write every screen in everyday words

Picture a resident who opens an online form to ask for a permit. The first screen says "Authenticate to proceed with your transaction" and the error that follows says "Invalid input". She closes the page and takes a tricycle to the office instead. The system worked exactly as it was built, and it still failed her.

The words are part of the service

When an office buys software, most of the attention goes to features: what the system can record, compute and print. Much less goes to the labels, instructions and messages that people actually read. Yet for the person using it, those words are the service. If they cannot tell what a button does or why a form was refused, the feature behind it might as well not exist.

This matters more in the Bangsamoro than in most places. The Philippine Statistics Authority's 2024 literacy survey found that 93.1 percent of Filipinos aged 10 to 64 could read, write and compute, but only 70.8 percent were functionally literate, which adds the ability to understand what is read.12 In BARMM the functional literacy rate was 64.7 percent, below the national rate, and the region had the lowest basic literacy rate in the country.2

Put simply, about one in three people of that age in the region did not meet the standard for understanding what they read. Software for public use here has to be written for them, not for the person who wrote the terms of reference.

What plain language means

Plain language is not baby talk and it is not a matter of taste. It has an international standard, ISO 24495-1, published in June 2023, which sets out governing principles and guidelines for developing plain language documents. The standard says its widest use is for documents meant for the general public, and that it also applies to technical writing and legislative drafting.3

The definition used with that standard is practical. A text is in plain language when its wording, structure and design are so clear that the intended readers can easily find what they need, understand what they find, and use that information.4 The test is the reader's result, not the writer's intention.

Governments have made this a duty. In the United States, the Plain Writing Act of 2010 requires that content for the public be written for its specific audience, and the federal guide built on that law calls "write for your audience" the first rule of plain language.59 In the United Kingdom, plain English is mandatory for all of GOV.UK, the government's main website.6

What the research says about readers

A common worry is that simple words will insult educated readers or sound unofficial. The evidence points the other way. The United Kingdom's content guidance reports research showing that people with higher levels of literacy prefer plain English, and that the more specialist a person's knowledge, the stronger that preference. It also cites a study of legal language in which 80 percent of people preferred sentences written in clear English.6

A usability study with experts in science, technology and medicine found the same thing: highly educated online readers want short information that is easy to scan. The researchers advise writing for the general public at about a sixth to eighth grade reading level, and keeping sentences to 15 to 20 words.7

The reason is simple. A director reading a screen at five in the afternoon is as tired and hurried as anyone else. Plain words save that reader time, and they are the only words that reach the reader who finished Grade 6.

Philippine law already points this way

The Ease of Doing Business and Efficient Government Service Delivery Act of 2018, Republic Act No. 11032, requires every government office to publish a Citizen's Charter. It must be posted where people can see it and written in English, Filipino or the local dialect. It must list the requirements, the steps, the person responsible for each step, the maximum time, the fees and how to complain.8

That list is a good description of what any government screen owes its user. We treat it as the minimum for software as well: before a person starts a request, the screen should say what they need to prepare, how long it takes, what it costs and what happens next.

How we apply it

Our approach is to treat words as part of the design, written and reviewed with the same care as the code. A label names the thing in the words the user would say aloud. A button says what will happen when it is pressed, such as "Send request" and not "Submit" or "Proceed". An error message says what went wrong and what to do about it, in that order.

We keep technical and legal terms where the law or the profession needs them, and we explain each one the first time it appears. The United Kingdom's guidance makes the same distinction: specialist terms are allowed where needed, while buzzwords and vague jargon are not.6 Sentences stay short, and long instructions are broken into numbered steps.

We also think plain language has to work in the languages people use. Many office systems are written only in English, but an interface should be ready for Filipino and for local languages where an office decides it needs them. We think the right time to plan for that is at the start, because adding a second language to a finished system is slow and costly.

  • Use the word the user says, not the word in the database.
  • One idea in each sentence, and one action on each button.
  • Say what is needed before the form starts, not after it fails.
  • Explain every term of law or procedure the first time it appears.
  • Test the wording with a person who has never seen the system.

What to ask of any system you buy

If you are choosing software for an office, a cooperative or a school, you can check its language without any technical training. Ask to see the screens a first-time user will meet, and read them aloud. Ask to see three error messages. Ask a clerk or a client who was not in the planning meetings to complete one task while you watch, and note every place they stop to ask what a word means.

Each of those stops is a cost the office will pay again and again, in phone calls, repeated visits and requests filed wrongly. Words are the cheapest part of a system to get right, and we think they are one of the clearest signs of whether its builders had the user in mind.

Sources

  1. PSA: Only 70.8% of Filipinos aged 10-64 functionally literate. GMA News Online, 2025-07-31.
  2. For every 10 Filipinos, 9 have Basic Literacy, While 7 have Functional Literacy (Final Results). Philippine Statistics Authority (press release, Reference No. 2025-227, copy hosted by ABS-CBN News), 2025-06-30.
  3. ISO 24495-1:2023. Plain language - Part 1: Governing principles and guidelines. AccessibleEU Centre, European Commission (catalogue entry for the ISO standard), 2023-06-01.
  4. ISO Plain Language Standard. Plain Language Association International (PLAIN).
  5. Plain language guide series. Digital.gov, U.S. General Services Administration.
  6. Use clear language - GOV.UK content and publishing guidance. Government Digital Service, United Kingdom.
  7. Plain Language Is for Everyone, Even Experts. Nielsen Norman Group, 2017-10-08.
  8. Republic Act No. 11032, Ease of Doing Business and Efficient Government Service Delivery Act of 2018. The Lawphil Project, Arellano Law Foundation, 2018-05-28.
  9. Principles of plain language. Digital.gov, U.S. General Services Administration.
#HowWeBuild#BARMMTech#MoroTech
Share