Keep Names, Terms, and Tone Consistent in Localization

An onboarding screen calls a feature “Streak Shield.” A reminder calls it “Streak Protector.” The help article uses “Streak Insurance.” A reader now has to work out whether those labels refer to one feature or three.

These names and the UI copy throughout this guide are invented editorial examples. They illustrate decisions a localization team can record and review.

The useful starting point is the content already in front of the reader: identify conflicting names, choose an approved form, and check every affected context. A glossary records the name. A style guide records writing rules. An approval log shows which decisions are ready to use.

Audit the content before choosing names

Collect the source strings and their existing translations from the release or content batch you are reviewing. Include the places people use together: onboarding, menus, notifications, help articles, and campaign copy. Keep a location or string ID beside each occurrence so a reviewer can find it again.

Search for recurring feature names, navigation labels, branded phrases, technical concepts, and names of people or places. Then look for competing versions. Start with conflicts that could change a reader’s understanding of an action or object.

An audit record might look like this:

Do not choose the most frequent version automatically. Check the source meaning, current product naming, and any existing approval. An older published label may be common because it was copied, even after the feature changed.

Give each editorial asset a clear job

Keep the documents easy to consult. They can live in separate tabs or files; the distinction matters more than the storage format.

• Glossary: source term, approved target form, context, category, usage notes, and status. Add terms whose variation could confuse the reader. Ordinary vocabulary rarely needs a fixed entry.
• Style guide: spelling variety, capitalization, punctuation, dates, numbers, units, headings, button labels, and formatting conventions. Record rules specific to the target language and medium.
• Voice guide: how a brand, narrator, mascot, or character speaks. Include reviewed examples that show sentence length, formality, humor, and emotional range.

For a comparison of their roles, see glossary, style guide, and voice bible.

Include a short reason for naming decisions. Record whether a name is translated for meaning, kept as an established name, transliterated, or adapted under an approved policy. That reason helps the next reviewer distinguish a deliberate choice from an inconsistency.

Record whether a name is

translated for meaning

kept as an established name

transliterated

adapted under an approved policy

Include a short reason for naming decisions.

That reason helps the next reviewer distinguish a deliberate choice from an inconsistency.

Make approval status visible

“Someone suggested this in a message” and “this is approved for publication” are different states. Use a small set of statuses with clear meanings:

Assign an approver to each decision. A solo translator can record their own decision and review date. A team might need an editor, product owner, narrative lead, or another responsible reviewer, depending on the term.

When someone encounters a new recurring term, they add the source context and proposal. The reviewer checks the meaning and naming policy. The approver records the final form, reason, and date. A change to an approved term also needs a list of affected locations and a named person to check them.

Use your own spreadsheet, document, or translation management system to maintain this editorial record. Move decisions out of chat into that record before the next handoff. The terminology approval workflow develops this process further.

Keep fixed names and edit the grammar around them

A fixed feature name should remain recognizable when the sentence changes. That does not require repeating the same sentence everywhere.

Consider this invented UI example, with Focus Session as the approved name:

Awkward: “Proceed with the initiation of the Focus Session.”

Edited: “Start your Focus Session.”

The edit removes heavy phrasing while preserving the name. Calling the same feature “Focus Round” would create a separate terminology decision.

Record which entries require an exact form and which allow approved grammatical variants. If the target language requires an inflected form, have a qualified reviewer specify it and its context. An editor should be able to adjust articles, word order, and surrounding verbs without guessing whether a new spelling is allowed.

Check similar-looking concepts before merging their names. Two actions may share a source word but perform different tasks. Their context, definitions, and string IDs belong in the decision.

Match tone to the reader’s task

A consistent voice can change its emotional intensity. An encouraging lesson message and a clear account-error message serve different purposes.

In the invented learning app, the mascot might say “Nice work. One more round?” after a lesson. An error message might say “Your progress could not be saved. Try again.” Both can use short, direct language. The error does not need a joke to resemble the mascot.

An encouraging lesson message

a clear account-error message

“Nice work. One more round?”

“Your progress could not be saved. Try again.”

Both can use short, direct language.

A consistent voice can change its emotional intensity.

Write rules for content types rather than relying on adjectives such as “friendly.” Specify where humor is appropriate, how to state a problem, and how much explanation a reader needs. Compare examples from the same task when reviewing tone.

Where titles, ranks, or forms of address carry relationship information, document who uses each form and when. A change in intimacy or status should be checked against the source before it is treated as accidental drift.

In an invented game example, soldiers address a leader as “High Warden,” peers use “Warden,” and an old ally uses a nickname. Record the official title and who may use each alternative. If the leader is promoted, note when the new title becomes valid and which earlier scenes still use the previous rank.

forms of address

soldiers

peers

an old ally

High Warden

Warden

a nickname

Record the official title and who may use each alternative.

Review the translation in its actual context

A string list can hide a problem that becomes obvious on screen. Open the relevant interface, screenshot, player, page, or preview during manual review.

For app copy, check that a help instruction names the button the reader can actually see. Confirm which action a short label triggers and inspect text that expands, wraps, or is cut off. Read placeholders with representative values inserted; the surrounding sentence may need a different structure.

For subtitles, inspect line breaks, timing, and readability in a subtitle editor and playback. For text inside artwork, inspect the lettering and placement. Set the review criteria for the actual delivery format and its requirements.

For games, compare an item’s name in inventory, quest instructions, and dialogue. For ecommerce, check product names and size or category labels across listings, filters, and checkout. A shortened label needs an approved context, not a new term chosen because space is tight.

These are tasks for the reader’s editorial workflow. A spreadsheet or terminology search can locate possible conflicts; the reviewer still needs the source and the rendered context to decide what to change.

A string list can hide a problem that becomes obvious on screen.

For app copy inspect text that expands, wraps, or is cut off

For subtitles inspect line breaks, timing, and readability

For games compare an item’s name in inventory, quest instructions, and dialogue

For ecommerce check product names and size or category labels

A spreadsheet or terminology search can locate possible conflicts

the reviewer still needs the source and the rendered context to decide what to change.

Check the release and record what changed

Before handing over the localized content, run a focused consistency review:

• Terms and names: compare occurrences with approved entries, including spelling and capitalization.
• UI references: check menus, buttons, screenshots, and help instructions against the current interface.
• Formatting: inspect punctuation, dates, units, placeholders, and the medium’s layout rules.
• Voice: read representative passages together and check them against reviewed examples for that task or speaker.
• Relationships: verify titles and forms of address against the scene or source context.
• Open decisions: resolve proposed terms or clearly flag the content waiting on a decision.
• Changed terms: search for deprecated forms in affected files and inspect each match before replacing it.

A global replacement can alter unrelated uses of the same word. Review the matches, then check the edited sentences in context.

Keep the final record compact: content version, glossary version, reviewer, review date, and unresolved decisions. After the next update, add new recurring terms and retire obsolete instructions. The record should make the next person’s task clear without asking them to reconstruct the discussion.

Changed terms

1. search for deprecated forms in affected files
2. inspect each match before replacing it
3. check the edited sentences in context

A global replacement can alter unrelated uses of the same word.

Keep the final record compact

content version, glossary version, reviewer, review date, and unresolved decisions

Keep the references usable between releases

Review entries when a feature changes or a new recurring concept appears. Check duplicate entries, obsolete instructions, and unfinished proposals. Keep previous decisions searchable and the current version obvious.

Give new collaborators the current references and a reviewed example. Add glossary terms when repeated variation would confuse the reader; leave one-off wording in the content review notes.

Review entries when a feature changes or a new recurring concept appears.

Add glossary terms

leave one-off wording

when repeated variation would confuse the reader

in the content review notes

Give new collaborators the current references and a reviewed example.