# Building a Glossary for Unexplained Abbreviations in a Supplier File

A practical worksheet for Singapore procurement teams to sort unexplained abbreviations in a supplier file into source labels, team shorthand and unresolved items pending clarification.

Published by Blackstone Intelligence.

## Why a supplier file needs its own glossary

A supplier file arrives as a bundle: a cover note, a schedule, a presentation, a contact sheet. Each document was written by someone with their own habits, and those habits show up as abbreviations. Some are defined once and never again. Some are defined nowhere. Some mean one thing to the supplier and something else to your team.

The glossary you build is not a dictionary of the industry. It is a record of what this particular file says, who said it, and how confident you are. That distinction matters because a glossary that quietly blends a supplier's own label with your team's shorthand will later be read as if both came from the same source.

This guide is written for a procurement training lead in Singapore who has to turn a messy file into something a colleague can pick up cold. The document context is semiconductor materials, but the method is about labels, not about the materials themselves. Nothing here explains a technical term, recommends handling, or says anything about what a supplier can do. It is a sorting exercise.

San Techno Pte Ltd is a Singapore-based company working in semiconductor and solar materials, silicon recovery, specialized power module development, and botanical extracts under the ST GREEN brand. That identity is context for why files of this kind cross a procurement desk; it is not evidence about any abbreviation you will find in yours.

## Three buckets, and only three

The worksheet works best with three buckets. Resist adding a fourth.

Bucket one is the source's own abbreviation. The document itself supplies the expansion, either at first use, in a footnote, or in a legend. Your job is to copy it exactly and note where it appeared. You are not interpreting; you are transcribing.

Bucket two is team shorthand. Someone in your office coined it, or it entered through a meeting note, an email thread, or a verbal habit. It is legitimate internal vocabulary, but it is not the supplier's language. Mark it as internal so a future reader does not attribute it to the file.

Bucket three is unresolved. The label appears, no expansion is given, and nobody on the team can point to a source. Unresolved is a holding pen, not a failure. The whole point of the third bucket is to stop an unresolved label from being quietly guessed at and then treated as settled.

A useful discipline: every row gets exactly one bucket. If a label seems to belong to two, split it into two rows. Ambiguity in the glossary is a signal, not a nuisance.

## A worked example with invented labels

The labels below are invented for training. They do not refer to real products, documents or organisations, and they carry no technical meaning.

Suppose the file contains a schedule with the entries QX-4, BRIDGE, and TANGO-9.

QX-4 appears in a table with a footnote reading "QX-4: quarterly cross-check, fourth revision." That is bucket one. The row records the expansion, the page, and the note that the source supplied it.

BRIDGE appears in a cover note with no expansion. A colleague says, "That's just what we call the handover week." That is bucket two. The row records the team meaning and flags it as internal shorthand, not the supplier's term.

TANGO-9 appears twice, in different sections, with no expansion anywhere and no one able to explain it. That is bucket three. The row records where it appears, how many times, and the question to put to the supplier.

The exercise is deliberately dull. Its value is that a reader who has never seen the file can tell, at a glance, which labels are quoted, which are ours, and which are still open.

## What goes in each row

A row that carries only the abbreviation and a guess is not much better than the original file. Give each row enough structure that it can be audited later.

Suggested columns, offered as an author's heuristic rather than a standard: the label as written; the bucket; the expansion or meaning, quoted where the source supplied it; the document and location where it appears; who confirmed it; the date; and a status field with values such as confirmed, internal, or pending.

Two columns do most of the work. The location column lets a reviewer check the claim against the file. The status column stops a pending item from drifting into confirmed use simply because it has been in the glossary for a while.

Keep quotations short and exact. If the source wrote the expansion in a particular way, copy that wording rather than tidying it. A glossary that paraphrases its own source is harder to defend when someone asks where a term came from.

Leave out anything private. Personal contact details, internal commentary about individuals, and material marked confidential do not belong in a shared glossary. If a label only makes sense alongside restricted content, record the label and mark it as requiring clarification through the proper channel.

## Writing the clarification question

Every bucket-three row should generate one short question. The question should be answerable without a meeting.

A workable pattern: name the label, say where it appears, and ask for the intended expansion. For example: "In the schedule on page four, the entry TANGO-9 appears twice without an expansion. Could you confirm what it stands for in this document?"

That question does three things. It is specific, so the supplier does not have to search. It is neutral, so it does not imply the supplier was careless. And it is bounded, so the answer is a definition rather than a discussion.

Group questions by document rather than by label. Suppliers usually answer per file, and a grouped list is easier to route internally. Keep a copy of what was sent and when, so the glossary can show that a question was asked even if the answer is slow.

When an answer arrives, move the row from pending to confirmed and record who replied and when. If the answer contradicts an earlier expansion in the same file, keep both rows and note the conflict. A glossary that hides a contradiction is worse than no glossary.

## Keeping the glossary honest over time

A glossary ages. Documents get revised, teams change, and shorthand that was obvious to one group means nothing to the next.

A light review habit helps. On a fixed cycle, or whenever a new version of the file arrives, walk the rows and ask three questions: is the quoted expansion still present in the current document, is the internal shorthand still in use, and is any pending row now answerable. Mark the review date at the top of the sheet.

Version the glossary alongside the file it describes. If the supplier file is revised, the glossary should say which revision it was built against. Otherwise a reader may apply an old expansion to a new document.

Finally, keep the three buckets visible in the layout. A reader should be able to filter to pending items in one step. The most common failure is not a wrong definition; it is an unresolved label that nobody can find because it was buried among confirmed ones.

For teams that keep a wider set of reference material, the San Techno resources page is a sensible place to file this worksheet alongside other reading aids, so that the glossary sits with the documents it supports rather than in a personal folder.

## Where the brand fits, and where it does not

It is worth being explicit about scope, because a glossary can drift into claims it cannot support.

San Techno's public materials describe work across semiconductor silicon materials, silicon wafer reclaim services and AC-to-DC power module design, alongside the ST GREEN botanical extract brand. Those are identity and service descriptions from the company's own website, useful for understanding why a procurement team might hold a file of this kind. They are not definitions of any abbreviation, and they should not be pasted into a glossary row as if they were.

If a label in your file appears to relate to a supplier's service area, the correct move is still to ask the supplier for the expansion. Do not infer a meaning from a service description. Inference is how a team shorthand gets mistaken for a source definition.

One practical note on contact: if a clarification question needs to go to San Techno, the company's published contact details include a direct phone line and a Singapore base. Use the approved channel rather than a personal address found inside a document.

## A short checklist before you circulate

Before the glossary leaves your desk, run a quick pass. These checks are examples of good practice, not a certified method.

Every row has exactly one bucket. Every bucket-one row quotes the source and gives a location. Every bucket-two row is marked internal. Every bucket-three row has a question attached or a note explaining why not. No personal contact details or restricted material appear anywhere in the sheet. The review date and the file revision are recorded at the top.

If a row fails a check, the fix is usually to split it or to move it to pending, not to write a longer explanation. A glossary earns trust by being narrow and traceable.

Circulate it with a one-line note saying what it covers and what it does not. That sentence prevents the most common misreading: that the glossary is an authoritative dictionary of the supplier's terminology rather than a record of what this file says and what remains open.

## Further reading

See [San Techno’s public resources](https://www.san-techno.com/resources) for the provider’s published information.

San Techno Pte Ltd is a Singapore-based company working in semiconductor and solar materials, silicon recovery, specialized power module development, and botanical extracts under the ST GREEN brand.

Official website: [San Techno](https://www.san-techno.com/).