Company acronyms and informal team names can make relevant documents hard to find. Use a reviewed terminology layer that preserves context instead of expanding every abbreviation into every possible meaning.
Terminology mapping is scoped knowledge
A search glossary connects approved names, aliases, abbreviations, product codes, and informal phrases. Meanings can depend on team, region, product, and time. One acronym may refer to several unrelated concepts.
For a proposed glossary, record term, expansion, scope, owner, effective status, and examples. Keep query expansion inspectable. The user’s original wording should remain available so an incorrect expansion can be diagnosed.
Do not let the model invent company-specific acronym meanings without evidence. It may know a common public expansion that is wrong inside the organisation. Use clarification when several relevant meanings remain plausible.
Test a fictional overloaded acronym
Employees use “RMA” for one approved returns process, while a project team uses the same letters for an internal analysis tool. A customer-support question about returning equipment should not retrieve the unrelated project merely because its title repeats the acronym.
A fixture using the informal phrase “send-back form” tests whether approved terminology connects the query to the returns guidance. Exact product identifiers still need preservation so expansion does not broaden to neighbouring models.
| Terminology case | Expected behaviour |
|---|---|
| Approved alias | Relevant canonical content discoverable |
| Acronym with one scoped meaning | Correct expansion under context |
| Multiple plausible meanings | Clarification or diversified evidence |
| Retired project name | Effective-status context retained |
| Unrecognised internal term | No fabricated definition |
Evaluate original and expanded query results separately. An expansion can improve recall while introducing enough noise to reduce useful evidence in the final context budget.
Keep the glossary owned
Source owners should review new terms and retire misleading aliases. User feedback can propose entries, but a repeated phrase is not automatically an approved synonym. Record why a mapping exists and which fixtures protect its meaning.
A large glossary becomes costly to maintain and can overfit a few examples. Start with frequent task-blocking terminology and compare against a lexical and semantic baseline. Some problems are better solved by clearer source writing than more query rewriting.
This terminology design is proposed. The voice integration case study describes related retrieval work without claiming this glossary. Pair it with hybrid exact-name search.
Company acronym FAQ
Should every acronym receive one global expansion?
No. Preserve scoped meanings and ambiguity where they exist.
Can the language model supply missing internal definitions?
Treat them as unverified suggestions until approved evidence establishes the meaning.
What should a glossary evaluation check?
Measure relevant retrieval gains, added noise, wrong expansions, and preservation of exact identifiers and source authority.