Two Procurement Examples of a Missing Reference and a Reference Marked Not Applicable

Why two small form answers deserve a second look

A materials service enquiry often travels as a short cover note plus a form. The form asks for a reference: a document number, a prior enquiry reference, a purchase order line, or an internal tracking code. Two answers to that single field cause most of the confusion at the receiving desk. One is blank. The other says not applicable.

At first glance both look like the same thing: no reference supplied. They are not. A blank field is an unanswered question. A field marked not applicable is an answered question, but only if someone explains why the question does not apply. Treating them as identical is how a tidy-looking pack arrives with an open thread that nobody owns.

This guide compares two fictional administrative examples. It does not describe disposal instructions, material classification, legal requirements, technical acceptance criteria, personal data, contacts or pricing. It is about the paperwork habit of distinguishing an omission from a deliberate exclusion. San Techno Pte Ltd, a Singapore-based company working across semiconductor and solar materials, silicon recovery, specialized power module development and botanical extracts under the ST GREEN brand, is used only as identity context for the enquiry setting.

Example one: the missing reference

Consider a fictional enquiry from a Singapore purchase desk about a wafer reclaim discussion. The form has a field labelled prior reference. It is empty. The cover note says only see attached.

The receiving desk now has a question it cannot answer from the pack: was there a prior reference that the sender forgot to copy, or is this genuinely a first contact? Those are different situations. A forgotten reference means a thread already exists somewhere and the new enquiry may duplicate it. A first contact means the desk should open a fresh record. The blank field does not tell the reader which.

The practical fix is not to guess. The sender should either fill the field or write a short author note beside it, for example first enquiry, no prior reference. That single sentence converts an omission into a statement. The receiver can then file the enquiry without chasing.

A useful habit for the sending side is to scan the form once for empty fields before sending and ask, for each one, whether the reader could answer it from the rest of the pack. If not, the field needs a note. This is an author heuristic, not a rule drawn from any standard.

Example two: the reference marked not applicable

Now consider a second fictional enquiry, this time about silicon recovery. The same prior reference field is filled with the words not applicable. The pack looks complete because no field is empty.

But not applicable is a conclusion, not an explanation. The reader still does not know whether the sender has no prior reference, whether the reference sits with a different team, or whether the sender believes the field does not apply to this type of enquiry at all. Each reading leads to a different next step.

The fix is the same shape as before: an author note. Not applicable, first contact with this supplier is a complete answer. Not applicable, reference held by our logistics team is also complete, because it tells the reader where the thread lives. Not applicable on its own is a placeholder that shifts the work back to the receiver.

This is where the two examples diverge. A blank field signals that the sender did not address the question. A not applicable entry signals that the sender addressed it but did not finish the thought. Both create an unanswered question; only the second one looks answered.

What the receiving desk should do with each

The receiving desk can apply a simple triage. For a blank field, the default assumption should be that the question is open, and the enquiry should be logged with a note that the reference is pending. For a not applicable entry, the desk should read the surrounding text to see whether an author note explains it. If none does, the entry is treated as open as well, but the follow-up question is narrower: not what is your reference, but why does the field not apply.

Keeping these two states separate in the log matters more than it first appears. A pack with three blank fields and a pack with three not applicable entries may need the same number of follow-ups, but they are different follow-ups. Mixing them into one category called incomplete hides which question is actually outstanding.

A short log column with three values, supplied, blank and not applicable without note, is enough for most desks. The third value is the one that catches people out, because it looks finished.

Writing the author note so it survives forwarding

An author note only helps if it travels with the form. A note typed into an email body is often lost when the form is forwarded to a colleague. A note placed directly beside the field, in the same document, is far more likely to survive.

Three habits keep the note useful. First, keep it short enough to read at a glance. Second, make it a statement rather than a question, so the reader is not left wondering whether the sender is asking for help. Third, avoid abbreviations that only the sending team understands.

Where the enquiry touches a service area, the note can name the context plainly. A wafer reclaim discussion and a silicon recovery enquiry may both use the same form, but the reason a reference is absent can differ. Naming the context in the note helps the receiving desk route the enquiry correctly without needing to interpret a bare not applicable.

None of this requires new systems. It requires the sender to treat the reference field as a sentence to be finished rather than a box to be cleared.

Where this fits in a San Techno enquiry

San Techno works across semiconductor silicon materials, silicon wafer reclaim services and AC-to-DC power module design, alongside its ST GREEN botanical extracts brand. An enquiry that reaches the company through a form may concern any of these areas, and the administrative habits above apply regardless of which one is involved.

For readers preparing a wafer-related enquiry, the silicon wafer disposal page is the natural place to start, because it sets out the context for that conversation. The reference field on any accompanying form is where the two examples in this guide tend to appear.

It is worth being clear about what this guide does not do. It does not tell anyone how to classify, handle or dispose of any material, and it does not set out legal or technical requirements. Those belong to the specific service conversation and to the applicable rules, not to a general note about form fields. The guide is limited to the paperwork question of how a blank field and a not applicable entry should each be documented so that the reader is not left guessing.

A short checklist before sending

Before an enquiry leaves the desk, a quick pass over the reference field and its neighbours catches most of these cases. The following is an author heuristic, offered as an example rather than a standard.

One: is any field empty that the reader could not answer from the rest of the pack? Two: does any field say not applicable without a reason beside it? Three: would the note still be visible if the form were forwarded without the covering email? Four: does the note name the context, such as a wafer reclaim or silicon recovery discussion, so the receiver can route it?

A pack that passes these four questions is not necessarily complete, but it no longer contains the two specific ambiguities this guide describes. The blank field has become a statement, and the not applicable entry has become an explanation. The receiving desk can then spend its time on the substance of the enquiry rather than on reconstructing what the sender meant.