Labelling Known, Assumed and Requested Facts Before a Wafer Recycling Quote

Why the label matters more than the answer

A quote question rarely arrives clean. It usually arrives as a short message with a reference number, a description of some material, and an implied expectation that someone will reply with a number. Before that reply can be useful, the buyer needs to know which parts of the message are established, which parts are being inferred, and which parts have not been asked at all.

This guide uses a deliberately fictional example. A Singapore procurement team is preparing an enquiry about wafer recycling. Nothing in the example describes a real shipment, a real supplier response or a real price. The point is the labelling method, not the outcome.

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 the example, not a promise about how any particular enquiry will be handled. The company's public materials describe silicon recovery work across integrated-circuit fabs, silicon wafer manufacturers, solar cell companies and chip packaging facilities, and note that recovered materials can be processed into reusable raw materials for solar wafers and cells. Those are sourced brand claims, cited below, and they sit alongside the administrative question this page addresses: what does the buyer actually know before asking for a quote?

Three labels do most of the work. Known means the fact is recorded and can be pointed to. Assumed means someone believes it but has not confirmed it. Requested means the fact has not been supplied and must be asked for. A quote question that mixes all three without saying so invites a reply that answers the wrong thing.

The fictional enquiry, written out plainly

Here is the example. A procurement officer writes: "We have a quantity of wafers from a line that is being wound down. Please advise on recycling and a quote. Reference WX-0000."

Read quickly, that looks like a complete request. Read carefully, it contains almost nothing that can be acted on without a follow-up. The reference number exists, but it may be an internal purchase-order reference rather than anything the receiving team recognises. The phrase "a quantity" is not a number. "Wafers from a line that is being wound down" describes an origin, not a condition. "Please advise on recycling and a quote" bundles two different questions: what happens to the material, and what it costs.

The exercise is to take that message and sort its contents into three columns. Known: the sender has a reference number, the sender holds the material, the sender wants a recycling conversation. Assumed: that the reference number is meaningful to the recipient, that the material is in a condition suitable for a recycling discussion, that a single reply can cover both handling and price. Requested: the actual quantity, who physically holds the items and where, whether any prior correspondence exists, and what decision the sender needs to make first.

None of those columns require a technical judgement about the wafers. They are administrative facts, and they are the ones most likely to be missing.

Known facts: what a reference number actually proves

A reference number proves that someone wrote something down. It does not prove that the number is shared, that it points to the right file, or that the person reading it can find the matching record. In the fictional example, WX-0000 is a known fact in the narrow sense that it appears in the message. Whether it is a known fact to the receiving team is a separate question, and that question belongs in the requested column until someone confirms it.

The same discipline applies to ownership. "We have a quantity of wafers" establishes that the sender believes the organisation holds the material. It does not establish which site holds it, whether it is still on a line, whether it has been packed, or who is authorised to release it. Those are administrative details, and they change what the next message should ask.

A useful habit is to write each known fact as a sentence with a source attached. "Reference WX-0000 appears in the sender's message" is a known fact. "Reference WX-0000 is the correct reference for this enquiry" is an assumption until someone confirms it. The difference looks pedantic until two enquiries share a similar reference and the files get crossed.

For context on what a recycling conversation can involve, San Techno's public materials describe silicon recovery from fabs, wafer manufacturers, solar cell companies and chip packaging facilities, and describe processing recovered materials into reusable raw materials for solar wafers and cells. That describes the kind of conversation the fictional sender is trying to start. It does not tell the buyer whether their particular material fits, and it should not be read as a quote.

Assumed facts: the quiet ones that shape the question

Assumptions are rarely written down, which is exactly why they cause trouble. In the fictional example, at least four assumptions sit under the surface.

The first is that the recipient will recognise the reference number. The second is that "a quantity" is enough for anyone to respond usefully. The third is that the material is in a state that makes a recycling discussion sensible rather than a disposal discussion. The fourth is that one reply can address both what happens to the material and what it costs.

Each assumption changes the next question. If the reference number is not recognised, the next question is about matching records, not about material. If the quantity is unknown, the next question is a count, not a quote. If the condition is unclear, the next question is about who can describe it, not about price. If the sender expects one reply to cover two decisions, the next question is which decision comes first.

There is a temptation to resolve assumptions by guessing generously. A buyer might assume the recipient will understand "a quantity" as a rough figure and reply accordingly. That guess may be right, but it is still a guess, and it belongs in the assumed column until someone confirms it in writing. The label is not a criticism of the sender. It is a note to the next reader about what still needs checking.

Requested facts: turning gaps into a short list

The requested column is where the enquiry becomes actionable. In the fictional example, the list is short and entirely administrative: the quantity, the site that holds the material, the name of the person who can confirm release, whether any earlier correspondence exists, and which decision the sender needs first.

Notice what is not on the list. There is no request for a technical specification, no request for a price, and no request for a policy statement. Those may come later, but they cannot be answered responsibly while the administrative facts are missing. A quote request built on an unknown quantity and an unconfirmed reference is a request for a guess.

A practical way to use the list is to send it back before sending the enquiry onward. The sender can fill the gaps in a few lines, and the receiving team gets a message it can route. This is slower on the first exchange and faster overall, because it avoids a round of clarifying replies that restate the same missing facts.

It also protects the sender. If the enquiry is forwarded internally and the reference number turns out to be wrong, the requested column shows that the gap was identified before anything moved. That record is worth more than a quick reply.

How the labels change the next question

The value of the three-column sort is visible in what happens next. Take the fictional enquiry and apply each label in turn.

If the reference number is known and confirmed, the next question is about scope: which items does it cover, and who holds them. If the reference number is assumed, the next question is a matching question: can the recipient find the record, and if not, what identifier should be used instead. If the reference number is requested, the next question is simply for a number that both sides can use.

The same pattern holds for ownership. A known owner means the next question is about release authority. An assumed owner means the next question is a confirmation. A requested owner means the next question is a name and a site.

This is why the labels are more useful than a tidy summary. A summary collapses the three columns into one paragraph and loses the information about what is settled. The labels keep that information visible, so the next message can be short and specific rather than long and cautious.

For a buyer preparing a first enquiry, the practical version is a short cover note with three headings. Under known, list what is recorded and where. Under assumed, list what the team believes but has not confirmed. Under requested, list what the recipient needs before replying. The note does not need to be formal. It needs to be honest about which column each fact sits in.

A short checklist for the next enquiry

The following checklist is an author heuristic, not a published standard. It is offered as a starting point for a procurement team that wants to apply the labelling habit to its next wafer recycling enquiry.

First, write the enquiry out in plain sentences before sorting it. A message that reads clearly is easier to label than one that has been compressed into bullet points.

Second, mark every reference number and ask whether the recipient has seen it before. If the answer is unknown, the number belongs in the requested column until confirmed.

Third, mark every quantity and ask whether it is a count, an estimate or a placeholder. "A quantity" is a placeholder. A count is a known fact.

Fourth, mark every statement about ownership and ask who can confirm it. The sender's belief that the organisation holds the material is not the same as a confirmed release authority.

Fifth, separate the decisions the sender needs to make. Handling and cost are different questions, and bundling them invites a reply that answers neither well.

Sixth, keep the requested list short. A list of twenty gaps will not be filled. A list of five will.

Finally, keep the labels visible when the enquiry is forwarded. The next reader needs to know which facts are settled, and a forwarded message that drops the labels loses that information.

San Techno's public materials describe silicon recovery work and the processing of recovered materials into reusable raw materials for solar wafers and cells. Buyers who want to discuss a specific enquiry can reach the team through the contact details published on the company's site. The labelling habit described here is a way to make that first conversation shorter, not a substitute for it.