Plan for the service in every supported language.
Choose language support using the community’s needs and the agency’s applicable language-access requirements. Ask which tasks matter most, what channels people use and what happens when someone needs assistance. A page translated into another language does little good if its required form, acknowledgement and support route remain unusable to that audience.
Map the full journey: find the service, understand eligibility, prepare information, complete the next step and receive an update. Identify where translation, interpretation or another assisted route is needed. Record a real owner and provider for each arrangement rather than promising help that staff cannot deliver.
The historical Digital.gov multilingual-content Q&A (opens in a new tab) discusses competent translation review and publication timing. Use it as practice guidance, with current obligations confirmed by agency reviewers; it is not a determination of requirements for your municipality.
Track source and translation revisions separately.
| Field | What it establishes | Fictional example |
|---|---|---|
| Content ID and source revision | Which approved facts the page reflects | Workshop registration, source R4. |
| Language and public destination | Where that audience reaches the task | Spanish equivalent service page. |
| Translation state | Whether work is requested, reviewed or live | R4 translation under review; R3 still live. |
| Language reviewer and decision | Who checked the exact revision | Authorized reviewer, decision and timestamp recorded. |
| Changed facts | What requires special checking | Registration deadline and location changed. |
| Dependent versions | What else must be updated | Form instructions, confirmation and scheduled posts. |
| Publication check | Which revision is actually live | R4 published and links checked on mobile. |
On a small screen, scroll the table sideways to see every column.
These fields are a proposed planning model. Do not mark a version current because a translation job completed successfully. Someone must verify that the intended revision reached the intended page and that all consequential facts survived the change.
Follow one changed fact through the workflow.
Fictional Cedar Bay example. An approved workshop deadline changes from one Thursday to the following Monday. The source owner records the new full date, closing time and local time zone in source revision R4. The translation request identifies those fields and all places where they appear, including form instructions and scheduled reminders.
A competent reviewer checks the translated revision against R4, including the meaning of the deadline, eligibility and next action. The publisher checks the live language page and connected form. The record then shows which versions are live and which remain pending. A pending version is not described as equivalent to R4.
This example demonstrates revision control rather than supplying a translation ready for official publication. Arrange an approved temporary communication and assistance plan for a delayed essential update. Do not silently leave an earlier deadline in another language, and do not invent language-specific instructions without authorized review.
For changes already published incorrectly, use the correction workflow across all affected languages and channels.

Maintain terminology, with context.
Record service names, recurring terms and approved equivalents with a short definition and context. Include the intended audience and who approved the term. A word-for-word list can mislead when the same English term names different services.
Digital.gov’s translation-glossary guidance (opens in a new tab) explains how a shared glossary supports consistency across translators. Use a glossary as a review aid, and revise it when service meaning changes. It does not replace review of a full sentence, form instruction or legal notice.
Machine translation may assist an authorized process, but a tool’s output should not be treated as evidence that a consequential instruction is correct. Define which content needs competent human review and who can approve publication.

Check language switching and the actual next step.
- A language switch should lead to the equivalent content when available, with a clear explanation of gaps.
- Set the document language correctly and identify passages in other languages where needed.
- Test long labels, different date conventions and right-to-left layouts when they apply.
- Keep numbers, units, locations, links and downloadable editions consistent with the approved source.
- Check the linked form, confirmation and support instructions, not only the page body.
- Use appropriate speakers of the supported language to test understanding of the task.
Include multilingual editing and preview in the CMS evaluation. A product’s list of supported languages does not establish the agency’s capacity to maintain its content.
Budget for every later revision.
Define translation requests, normal and urgent review, backup reviewers, access and handover in the operating scope. Track changes that create new work, such as a form redesign, a new service or a vendor portal change. Preserve the revision map when switching providers.
The content owner should be able to answer which source revision a language page reflects and what remains outstanding. Connect those responsibilities to content governance and website ownership and maintenance. That makes multilingual access an ongoing service responsibility instead of a launch-day checkbox.

