Once candidate terms have been gathered from multiple sources, the real work begins: reconciling them into one coherent vocabulary. This means collecting every candidate into a single list, resolving inconsistencies in spelling, punctuation, and case, and, where several sources offer different words for the same underlying concept, deciding which one becomes the preferred term, with the others recorded as variants that authors and indexers should avoid using going forward.
This process should also surface gaps: does the resulting vocabulary actually cover every important concept the content needs, or are there topics with no proper term at all yet? At the same time, restraint matters, adding a term for every edge case bloats the system and causes the whole vocabulary to lose focus. Terminology isn't static either; as usage evolves, categories that go unused should be reconsidered, either folded into something more relevant or relabeled to match how people are talking about the topic now.
The hardest part of this work usually isn't finding candidate terms: it's what to do when the term your own organization prefers and the term your actual users search for turn out to be two different things.
"IRA" is the strongest choice for preferred term. It's recognized broadly across the industry, matches what competitors already use, and aligns with how people commonly search, giving it the widest real-world support across independent sources. "Future Fund Vehicle," however well-intentioned internally, reflects the company's own branding rather than language any customer would recognize or search for, which is exactly the conflict between organizational vocabulary and user vocabulary this kind of work most often runs into, and user vocabulary should generally win that conflict when the goal is findability.
"Individual retirement account" and "retirement savings account" should both become variant terms mapped to the preferred term "IRA," since they refer to the same underlying concept using fuller or slightly different phrasing that some users will still search with, keeping them as variants ensures those searches still succeed. "Retirment account," the misspelling, should also be captured as a variant rather than excluded outright: search-log analytics revealing a common misspelling is exactly the kind of finding a controlled vocabulary can quietly absorb, mapping the misspelled query to the correct preferred term so the user still gets a useful result despite the typo.The internal name "Future Fund Vehicle" doesn't disappear entirely from the organization's internal usage, but it should not become the label surfaced to customers navigating this content: that's the practical outcome of letting user and organizational vocabulary conflict get resolved in the user's favor.