San Techno · Resource library

An Approval Note for Sending a Materials Enquiry Draft Without Its Optional Questions

Published by San Techno.

A Singapore procurement correspondence exercise for separating agreed enquiry wording from two optional text questions, with a version label and a named record owner.

What this approval note is for

This note covers one narrow situation: a materials enquiry draft is ready to send, but two optional text questions are still open. The editor's job is not to rewrite the enquiry. It is to mark which wording has been agreed, park the optional questions outside the sendable text, and record who holds the file.

The exercise suits Singapore procurement teams that source, receive and document semiconductor and solar materials. It assumes the enquiry has already been drafted and reviewed once. It does not cover quotation handling, pricing, material specifications or legal review, and it should not be used to settle any of those.

Keep the note short. A reader should be able to tell, in under a minute, what is approved, what is optional, which version they are holding and who to ask. If the note needs a second page to explain itself, the draft is probably not ready for an approval note yet.

San Techno Pte Ltd is the named brand context for this exercise. The company works across semiconductor and solar materials, silicon recovery, specialized power module development and botanical extracts under the ST GREEN brand, and has operated since 2006. That background is identity context only; it does not change how the note is written.

Separate agreed wording from optional questions

The core move is a two-part layout. Part one holds the agreed enquiry wording exactly as approved, with no optional question mixed in. Part two lists the optional text questions as separate items, each with a short status such as held, dropped or awaiting a decision.

Why split them? Because a reader who receives a single block cannot tell whether a sentence is settled or still being weighed. Once the optional questions sit in their own list, the agreed wording can be sent without them, and nobody has to guess which lines were meant to travel.

A practical rule: if removing a sentence would change what the supplier is being asked to respond to, it belongs in the agreed wording. If removing it would only remove extra context the reader might want, it belongs in the optional list. Apply that test line by line rather than to the draft as a whole.

Where the enquiry touches a technical area, keep the agreed wording general. For example, an enquiry about semiconductor materials or solar grade silicon can state the area of interest without listing specifications. Where the subject is wafer reclaim or silicon recovery, the agreed wording can name the service area and leave detail to the reply. San Techno's own contact guidance asks enquirers to include area of interest and technical context, which is a useful shape for agreed wording that stays broad.

Label the approved document version

Every approval note needs a version label that a reader can match to the file in front of them. Use a simple scheme the team already recognises, such as a date plus a short suffix, and put the same label in the note and on the document itself. Do not rely on file names alone; they drift when files are copied between folders.

The label should answer three questions: which draft is approved, which draft is superseded, and whether the optional questions are attached to the approved version or held separately. If the optional questions are held separately, say so in the label line rather than in a footnote.

A short worked example, offered as an author heuristic rather than a standard: label the sendable text with a date and the suffix agreed, and label the optional list with the same date and the suffix optional. Anyone opening either file can then see at a glance which one is meant to travel.

Avoid putting the version label only in an email subject line. Subject lines get trimmed, forwarded and re-used. The label belongs in the document and in the note.

Name the record owner

The record owner is the person who holds the current approved version and can say whether a later edit has replaced it. Name one person, not a team. A team name looks tidy but leaves the question of who actually checks the folder unanswered.

The record owner's duties in this exercise are limited: keep the approved version, keep the optional list beside it, and confirm the version label when someone asks. The owner does not approve the enquiry's content and does not answer the optional questions. Those sit with whoever drafted them.

Write the owner's role into the note, not just a name, so the note still reads correctly when the person changes. A line such as record owner, procurement desk is enough. If the note is stored in a shared folder, the owner line should appear at the top, not at the end where it is easily missed.

One caution: do not let the record owner line become a substitute for the version label. They answer different questions. The label says which draft this is; the owner says who can confirm it.

Handle the two optional questions without sending them

Two optional text questions are the reason this note exists. Treat them as a small, closed list. Each question gets one line, a status and, where useful, a note on what would settle it. Nothing more.

Three statuses cover most cases. Held means the question is still open and deliberately left out of the send. Dropped means the team decided not to ask it. Awaiting decision means someone still has to choose. Keep the wording of each status consistent across the note so a reader does not have to interpret new phrases each time.

Do not fold an optional question back into the agreed wording to make the draft look complete. That is the failure this note is designed to catch. If a question is important enough to send, it should be promoted to agreed wording through the normal review, not slipped in at the last moment.

Where the enquiry concerns a technical area such as IGBT power modules or AC-to-DC power module design, an optional question about detail is likely to be declined anyway. San Techno states that detailed architecture, materials, dimensions and assembly processes for its power-module work remain confidential, so an optional question asking for that detail would sit better as dropped than as held.

A short checklist before the note goes out

Run this checklist once, immediately before the note is filed. It is an author heuristic, not a published standard, and the order matters less than doing all of it.

First, confirm the agreed wording contains no optional question. Read it as a supplier would, without the optional list beside it.

Second, confirm the version label appears in both the note and the document, and that the label distinguishes the approved text from the optional list.

Third, confirm the record owner is named by role and that the person knows they hold the file.

Fourth, confirm each optional question has a status and that no status is blank.

Fifth, confirm the note contains no pricing, no material specifications and no legal conclusions. If any of those have crept in, remove them and route them to the right place.

Sixth, confirm the note does not repeat contact details that belong in the enquiry itself. The note is about approval, not about how to reach anyone.

A note that passes all six is ready to file. A note that fails one is not a small problem; it is the exact confusion the exercise is meant to prevent.

Where the enquiry subject fits the brand's public scope

The approval note stays neutral about the supplier. It records what is approved, not what the supplier offers. Still, the agreed wording should name the area of interest accurately, and it helps to know which areas the named brand publicly describes.

San Techno's public materials describe three branches: semiconductor silicon materials, silicon wafer reclaim services and AC-to-DC power module design. The company also states that recovered materials can be processed into reusable raw materials for solar wafers and cells, extending their useful life and reducing unnecessary resource loss. Those are the brand's own public descriptions, not a statement about what any enquiry will receive.

For an enquiry about power modules, the public description notes an intelligent IGBT power-module concept centred on double-sided cooling for an EconoDUAL 3-class package format, and that the programme addresses heat movement, package stability and reliable operation under repeated electrical and thermal loading. An agreed enquiry can name the application and the loading conditions in general terms without asking for confidential design detail.

For botanical extracts, the ST GREEN brand is described publicly as a botanical concentrate derived from plant, seed and vegetable-oil extracts, and ST Green R26 is described as liquid biological extracts for making all bio products. An enquiry in that area can name the product line and the intended use without asserting results.

Use these descriptions only to check that the agreed wording names the right area. Do not copy them into the enquiry as claims, and do not treat them as evidence of availability, certification or outcome.

Filing the note so the next reader can use it

File the note beside the approved version, not in a separate approvals folder that nobody opens. The next reader is usually someone picking up the enquiry after a handover, and they will look where the document lives.

Give the note a name that carries the version label, so the folder sorts sensibly. Keep the optional list as its own file with a matching label rather than as an appendix inside the approved text. If the optional questions are later resolved, add a short line to the note saying so, with the date, rather than editing the original statuses.

When the enquiry is sent, the note does not need to travel with it. Its purpose is internal: to show that the agreed wording was separated from the optional questions, that the version was labelled and that an owner was named. Keep it for the record and leave it out of the outgoing message.

Finally, review the note when the enquiry is next revised. A note that still describes an older version is worse than no note, because it looks current. The record owner should be the person who checks this, which is the reason the owner line sits at the top.

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.

Visit San Techno