Before You Translate a Community Notice, Decide What People Must Be Able to Do

Build the action, language, channel, reviewer, and response route together so a translated message can actually be used.

By Arbab Naseebullah Kasi, Chief Executive Officer - CEO, Feel Worldwide Foundation Inc.

Illustration of community organizers planning a multilingual notice and its response route.

A translated notice can be accurate sentence by sentence and still leave a reader unable to act. The date may be clear, but the registration form may exist only in English. A phone number may be listed, but nobody answering it may be able to continue the conversation in the reader's language. A flyer may reach the right neighborhood after the deadline has passed. These are not simply translation problems. They are design problems in the full route from information to action.

For community groups, schools, small nonprofits, and volunteer teams, the useful question is not only, “Have we translated this?” It is, “Can a person understand the decision, complete the next step, ask a question, and receive a usable response?” Translation is one part of that route. The rest includes choosing languages with the community, identifying the main action, selecting the right channels, checking quality, and preparing the response behind the notice.

Start with the action, not the document

Before sending text to a translator, write one sentence that describes what the reader should be able to do. For example: “A parent can reserve a place at Saturday's learning session and request an access accommodation.” That sentence gives the communication team a test. Every important element of the notice should help the reader complete that action.

The CDC Clear Communication Index treats a clearly stated main message and call to action as central features of understandable public information. Although the Index was developed for public health communication, its questions are useful beyond health settings: Is the main message easy to find? Is the requested behavior specific? Does the material explain how to do it? A community notice becomes stronger when the answer to each question is visible without searching through dense text.

Separate essential information from helpful background. Essential information often includes the purpose, who the activity is for, the date and time, location, cost if any, what to bring, how to respond, the response deadline, and how to request language or disability support. Background can explain why the activity matters, but it should not bury the action.

Choose languages from evidence and conversation

Do not assume that the most widely spoken language in a city is automatically the right language for every neighborhood or activity. Look at who already participates, who has asked for assistance, which schools or community partners serve the intended audience, and which languages people say they prefer for important information. Ask trusted local partners what they know, while avoiding the idea that one person represents an entire language community.

The HHS National CLAS Standards, designed for health and health care, offer a useful planning example: assess community needs, involve community partners, and review how well communication works. Those principles can inform a voluntary community notice without treating health-sector standards as a universal rulebook. Separately, check the current rules that actually apply to your organization and location. U.S. federal language policy changed in 2025, as documented in the Justice Department's July 14, 2025 guidance announcement; an older federal plan should not be used as current compliance advice.

Language choice is also about form. Some people may prefer spoken information, audio, a phone conversation, or a short video rather than a long written translation. Literacy, visual access, internet cost, device access, and privacy all affect whether a channel works. Ask about preferred language and preferred way to receive important information as separate questions.

Design the response route before distribution

A notice creates work after it is received. Someone must answer calls, read messages, record registrations, respond to accommodation requests, protect personal information, and explain changes. If the translated notice invites a reply in a language that the team cannot handle, the organization has created a visible doorway without preparing the room behind it.

Map the response route in advance. Name the person or service that will receive each type of reply. Decide what happens if an urgent question arrives, if a language is not currently supported, or if the activity is full. Prepare short approved responses for common questions. If a qualified interpreter or translator is needed, arrange that support before publishing the contact details. Do not ask children, family members, or untrained volunteers to interpret sensitive or consequential conversations simply because they are available.

The HHS National CLAS Standards apply to health and health care organizations, so they should not be presented as universal requirements. Their emphasis on understandable services, informing people about language assistance, and ensuring the competence of language assistance is nevertheless a useful quality benchmark for community planners. The larger lesson is practical: language access depends on people and processes, not only on translated files.

Review meaning, usability, and the digital details

A bilingual colleague can help, but knowing two languages is not the same as being qualified to translate every subject. Give the reviewer the purpose, audience, reading context, key terms, and space limits. Ask them to check whether the meaning, tone, dates, names, numbers, and instructions remain correct. For safety, eligibility, money, legal rights, or health information, use appropriately qualified professional support and a stronger review process.

Then test the complete route with an intended user or trusted reviewer who was not part of drafting it. Do not ask only, “Does this sound good?” Give the person a task: find the deadline, explain the next step, use the link or phone route, and identify where to ask for help. Observe where the route becomes uncertain. A confusing button, a long web address, an English-only form, or an unanswered number can defeat an otherwise excellent translation.

For web content, the W3C Internationalization Quick Tips recommends declaring the language of content, using Unicode, and allowing flexible layout because translated text may expand or flow differently. A practical team should also check text direction, mobile display, keyboard entry, captions, downloadable files, and whether a language selector is named in a way the intended reader can recognize.

A fictional teaching example: the notice works, but the route fails

Fictional example: A neighborhood group plans a free Saturday learning event. Volunteers translate the flyer into two locally requested languages and share it through community partners. The translation is accurate, but the registration link opens an English-only form. The phone line goes to voicemail with an English greeting, and the confirmation message does not explain how to request wheelchair access. Interest exists, yet the next step is difficult to complete.

The group redesigns the notice around one action: reserve a place and request needed support. It creates a short language-access brief with seven fields: intended reader, required action, chosen languages and evidence, distribution channels, qualified reviewer, response owner, and test result. The form uses plain labels in each supported language. The phone message offers a callback route. One volunteer owns registration, another monitors accommodation requests, and the team tests every link from a low-cost phone before distribution.

The group also adds a version date and owner to the source notice. When the venue changes, the owner updates the source first, sends the change through the same review process, and replaces each language version. This reduces the risk that several different notices remain in circulation.

Use a one-page action-to-response brief

For your next community notice, place these prompts on one page: What must the reader be able to do? Who is the intended reader? Which languages and formats were chosen, and what evidence supports the choice? Where will people receive the notice? Who checks meaning and usability? Who answers each response channel? What happens when the team cannot answer immediately? How will one intended user test the complete route? Who owns updates, and when will the notice expire?

A small team may not be able to support every language at once. Be honest about current capacity, prioritize the most consequential information, budget for qualified help, and tell people how to request assistance. Partial capacity should lead to a clear improvement plan, not a false promise. Record unmet requests because they provide evidence for the next language, channel, or partnership decision.

Language access is ultimately about participation. A person should not have to solve the organization's internal communication gaps before joining a local activity or asking a simple question. The Foundation's Community Engagement, Volunteerism & Local Action pathway emphasizes participation, trust, and shared action. Organizations interested in connecting around inclusive community practice can use the Foundation's Connect With Us page.

Your next action: Choose one notice that people must act on this month. Complete the seven-field language-access brief, then ask one intended user to attempt the full route from first reading to confirmed response. Fix the first barrier they find before distributing the notice more widely.

Reviewed October 9, 2026. This article offers general educational guidance. Organizations should assess any legal, contractual, health, safety, disability-access, or funding-specific duties that apply to their own work and location.