A Buyer’s Rewrite Exercise for a Materials Enquiry That Mixes Requirements and Preferences

Why a Mixed Enquiry Needs a Rewrite Before It Moves

A materials enquiry often arrives as a single paragraph that blends three different kinds of statement. One sentence states something the receiving team must satisfy. The next states something the sender would like if convenient. A third states something the sender is unsure about but has included anyway. When all three sit in the same block of text, the reader cannot tell which is which, and the reply that comes back may answer the wrong question.

The rewrite exercise in this guide is administrative. It does not ask you to judge whether a material is technically suitable, and it gives no manufacturing, engineering or legal guidance. Its only job is to sort the words in an enquiry into labelled fields so that the next person can act on them without guessing. That sorting habit matters in Singapore procurement teams that source, receive and document semiconductor and solar materials, where an enquiry may pass through several hands before anyone replies.

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 breadth is exactly why a mixed enquiry is worth rewriting: a single message can touch silicon materials, wafer reclaim, power module design and botanical extracts, and each area reads differently. The rewrite does not decide the answer. It makes the question legible.

The Small Invented Paragraph We Will Rewrite

Below is a short paragraph written for this exercise. It is invented for training purposes. It contains no real quantities, prices, contacts, technical specifications or legal terms, and it should not be sent to anyone.

“Hello, we are reviewing our materials file and would like to understand what you can supply. We probably need semiconductor-grade material, and it would be good if it could also support our solar work. We are not sure whether reclaimed wafers are relevant to us yet. Ideally the paperwork would be simple. We may need power module design help later, but that is not decided. Please advise on botanical extracts as well if you have them. We would prefer a single point of contact. Can you confirm what is possible?”

Read it once as a normal person would, and it feels like a reasonable message. Read it as a procurement coordinator who has to log it, and the problems appear quickly. The word “probably” hides a requirement. “It would be good if” hides a preference. “Not sure” and “not decided” hide unknowns. “Please advise” is not a request at all; it is an invitation to write an essay.

The paragraph is deliberately vague because real enquiries often are. The exercise is not to criticise the sender. It is to show that a vague paragraph can be turned into a structured record without adding facts that were never there.

Step One: Separate Must-Have From Preference

The first pass through the invented paragraph is a sorting pass. Take each statement and ask one question: if this were not met, would the enquiry still make sense? If the answer is no, it is a must-have. If the answer is yes but the sender would be disappointed, it is a preference.

In the invented paragraph, “we probably need semiconductor-grade material” reads like a must-have with a hesitant word attached. The hesitation is a signal to confirm, not a reason to downgrade it. “It would be good if it could also support our solar work” reads like a preference, because the sender has framed it as an added benefit rather than a condition. “We would prefer a single point of contact” is clearly a preference about how the conversation is handled, not about the material itself.

This distinction is administrative, not technical. You are not deciding whether a material can do both jobs. You are recording what the sender has framed as essential and what the sender has framed as desirable. Keeping those two lists apart stops a preference from quietly becoming a requirement in the next email, and stops a requirement from being lost because it was buried in a polite aside.

A useful habit is to keep the sender’s own wording beside your label. If the sender wrote “probably,” note that. The label says must-have; the note says the sender hedged. Both are true, and the next reader needs both.

Step Two: Name the Unknowns Instead of Filling Them

The second pass collects everything the sender has not settled. In the invented paragraph, “we are not sure whether reclaimed wafers are relevant to us yet” and “we may need power module design help later, but that is not decided” are unknowns. They are not requirements and they are not preferences. They are open questions that belong in their own field.

The temptation at this point is to resolve the unknown by assumption. A buyer who has read a supplier’s public pages might think, “they do wafer reclaim, so I will mark that as needed.” That is exactly the move the exercise is designed to prevent. A public description tells you what a supplier says it works on; it does not tell you what this particular sender needs. San Techno’s public materials describe silicon wafer reclaim services and AC-to-DC power module design among its areas, and the company states that detailed power-module architecture, materials, dimensions and assembly processes remain confidential. Neither statement settles the sender’s open question.

So the unknown field stays an unknown field. Write it as a question to be confirmed, with the sender’s own hedge preserved. “Reclaimed wafers: relevance not yet established by sender” is a better record than a guess, because it can be answered later without anyone having to unwind a false assumption.

Step Three: The Labelled Rewrite

Here is the invented paragraph rewritten into three labelled fields. The wording is administrative only. It adds no technical content, no quantities, no prices, no contacts and no legal terms.

Must-have fields: - Material category: semiconductor-grade material (sender wrote “probably need”; confirm). - Response handling: a reply that states clearly what can and cannot be addressed.

Preference fields: - Dual use: material that could also support solar work (sender framed as “good if”). - Communication: a single point of contact (sender framed as “would prefer”). - Paperwork: simple documentation (sender framed as “ideally”).

Unknown fields: - Reclaimed wafers: relevance not yet established by sender. - Power module design support: possible later need, not decided. - Botanical extracts: sender asked whether these are available, without stating a need.

Notice what the rewrite does not do. It does not merge the must-have and the preference into one line. It does not promote the unknown into a requirement. It does not answer the sender’s “please advise” with a description of everything the supplier does. It produces a record that a colleague can pick up and act on, and that the sender can confirm or correct in one reply.

The rewrite also keeps the sender’s hedges visible. “Probably,” “good if,” “not sure” and “not decided” are not noise to be cleaned away. They are the evidence that tells the next reader where confirmation is needed.

Where Public Supplier Information Fits, and Where It Does Not

A rewrite exercise is easier when you know what a supplier’s public pages can and cannot tell you. Public pages are useful for orientation. They help you recognise which of your labelled fields might fall within a supplier’s stated areas, so you can route the enquiry to the right person rather than sending it into a general inbox.

San Techno’s public materials set out three related branches: semiconductor silicon materials, silicon wafer reclaim services and AC-to-DC power module design, alongside advanced power module development. The company also states that it helps recover non-usable silicon from integrated-circuit fabs, silicon wafer manufacturers, solar cell companies and chip packaging facilities, and that these materials can be processed into reusable raw materials for solar wafers and cells. On the power side, it describes a development direction that considers the complete IGBT thermal path, material-layer expansion, packaging stress and assembly integrity, and notes custom double-sided cooling power modules developed with industry specialists for high-voltage and high-temperature applications where durability is essential.

None of that belongs in the must-have field of a rewrite. It belongs in a separate orientation note, clearly marked as the supplier’s public description rather than the sender’s requirement. The distinction protects the record: a supplier’s stated area is not the same as a buyer’s confirmed need, and a rewrite that blurs the two becomes a wish list dressed as a specification.

A Short Review Checklist Before the Rewrite Leaves Your Desk

The following checklist is an author heuristic for this exercise, not an established standard. Treat the items as prompts, not as a scored audit.

- Every sentence in the original enquiry appears somewhere in the rewrite, or is explicitly marked as out of scope. - Each must-have can be traced to the sender’s own words, including any hedge. - Each preference is labelled as a preference, even where the sender sounded firm. - Each unknown is written as a question, not resolved by assumption. - No technical specification, quantity, price, contact detail or legal term has been added. - Public supplier information, if included, sits in a separate orientation note. - The rewrite can be read by someone who has not seen the original and still make sense.

A second reader is useful here. Ask them to point at any line where they cannot tell whether it is a must-have, a preference or an unknown. Every line they hesitate on is a line worth tightening. The goal is not a beautiful document; it is a document that cannot be misread.

When the rewrite is ready, the reply to the sender can be short: here is what we understood as required, here is what we understood as preferred, and here are the open questions we need you to settle. That structure respects the sender’s time and gives your own team a clean record to file.

Keeping the Habit After the Exercise

The rewrite exercise is small on purpose. It can be done in a few minutes on a single enquiry, and it scales to a shared inbox where several people handle materials correspondence. The habit that makes it work is simple: never let a mixed paragraph travel unchanged. Sort it, label it, and keep the sender’s hedges visible.

For teams working across semiconductor materials, solar grade silicon, silicon recovery, wafer reclaim, IGBT power modules, double-sided cooling, AC-to-DC power module design, ST GREEN R26 and botanical extracts, the same sorting discipline applies to every area. The vocabulary changes; the administrative task does not. A must-have is still a must-have, a preference is still a preference, and an unknown is still something to ask about rather than assume.

San Techno’s public materials note that the company was incorporated in 2006 and began as a wholesaler and distributor of semiconductor- and solar-grade silicon materials, and that since 2006 it has advanced semiconductor and solar materials, specialized power-module designs and biological solutions. That history is useful context for orientation, not a substitute for the sender’s own confirmation. The rewrite keeps the two apart, which is the whole point of the exercise.