Tracing a Fictional Quantity Back to Its Source Before You File It

Why a Number in an Email Is Not Yet a Record

A procurement file often begins with a sentence someone typed quickly. In this guide the example is deliberately fictional: an internal email says that a colleague counted a number of sample vials and passed the figure along. Nobody disputes the sentence. The problem is that the sentence is not a record of a count. It is a record of someone writing down a count.

That distinction matters more than it first appears. When a figure enters a procurement file, later readers tend to treat it as settled. A planner may use it to size a follow-up request. A colleague preparing a comparison may carry it forward. An auditor may read it as evidence that a physical count took place. If the only origin is an email line, none of those readers can see the difference between a figure that was observed and a figure that was mentioned.

Your job before filing is not to decide whether the number is right. It is to record where the number came from, in language that makes its status clear. That is a source-of-quantity decision, and it is a writing decision as much as a counting one.

This page sits within the San Techno resources collection, which covers practical documentation questions for teams handling semiconductor materials, solar grade silicon and related sourcing work. The guidance below is general record-keeping advice. It does not describe any real shipment, stock level or count.

Separate the Figure From the Claim Behind It

A quantity in an email usually arrives attached to an implied claim. The writer may mean "I counted these," or "someone told me this," or "this is roughly what we expect." The words in the email rarely say which. Before you file, make that implied claim explicit, at least to yourself.

A useful habit is to ask three short questions of the line you are about to file. First, who wrote the figure, and were they describing something they saw or something they were told? Second, does the email name a moment or a place where the count happened, or does it only state the result? Third, is there any other document in the file that touches the same figure?

If the answer to the second question is no, you are working with an unconfirmed figure. That is not a failure. Many early-stage notes are unconfirmed by nature. The failure would be filing it as though it were confirmed.

Keep the original wording. Do not tidy the email into a cleaner sentence, because the tidying is where the uncertainty disappears. If the email says "about a dozen vials," the word "about" is part of the source and belongs in your note.

Write a Source Note That Names the Origin

A source note is a short line, placed next to the figure in your record, that says where the figure came from and what kind of figure it is. It should be readable by someone who never saw the email.

Here is a fictional example. The email from a colleague reads: "Counted the sample vials on the bench this morning, looks like twelve." A source note for the procurement file might read:

"Quantity of twelve sample vials. Origin: internal email from [colleague], dated [date], describing a bench count made that morning. Figure not independently verified. No separate count sheet attached at time of filing."

Notice what the note does. It names the origin, it quotes the kind of statement the email made, and it states plainly that the figure is unverified. It does not repeat the number as a fact about the world. It records the number as a fact about the email.

A weaker note would read "twelve vials confirmed." That sentence borrows authority the email never had. A stronger note keeps the figure and the doubt together, so a later reader can act on both.

Decide What Status the Figure Carries

Not every unconfirmed figure needs the same treatment. A short status label helps the next reader know how much weight to give it. These labels are a suggested convention, not an industry standard, and your organisation may prefer its own wording.

Reported: the figure comes from a person's message and has not been checked against another record. This is the default for a count mentioned in an email.

Observed: the figure comes from a count that someone recorded at the time, with a date and a place, and that record is in the file.

Reconciled: the figure has been compared with at least one other document and the two agree, or the difference is explained.

Using a label does not change the underlying evidence. It only makes the evidence legible. A figure labelled reported can later be upgraded if a count sheet arrives, and the upgrade itself is worth noting, because it shows the file was maintained rather than assembled once.

Where a figure will feed into a commercial decision, such as a sourcing enquiry for semiconductor materials or a discussion about wafer reclaim volumes, the label matters most. A reported figure can start a conversation. It should not close one.

Keep the Trail Short and Attached

The most common way a source note fails is by drifting away from the figure it describes. A note kept in a separate message, or in someone's memory of the email, is not a source note. It is a rumour with good intentions.

Keep the note in the same place as the figure. If your record is a spreadsheet row, put the note in an adjacent column. If it is a document, put the note directly beneath the figure. If it is a shared folder, name the file so the link is obvious.

Attach the original email where policy allows, or record its date, sender and subject line so it can be found again. Do not paraphrase the email into the note and discard the email. The paraphrase is your reading; the email is the source.

A short trail is better than a long one. Three elements are usually enough: the origin, the date, and the status. Anything more tends to become a second narrative that competes with the first.

Where This Fits in a Materials Sourcing File

Procurement teams working with semiconductor and solar materials often handle documents that arrive in stages: an enquiry, a reply, a sample note, a specification sheet. Each stage can introduce a figure, and each figure needs its own origin. A quantity mentioned in a sample email is not the same kind of figure as a quantity on a packing list, and the two should not be merged into one line without a note explaining the merge.

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. For context on the kinds of sourcing conversations these files support, the company describes helping recover non-usable silicon from integrated-circuit fabs, silicon wafer manufacturers, solar cell companies and chip packaging facilities. That description explains why a sourcing file may contain several kinds of material reference at once, and why a clear source note helps a reader tell them apart. It does not tell you anything about a specific quantity, and it should not be read as one.

A Short Checklist Before You File

Run through these questions before the figure leaves your hands. They are a writing checklist, not a compliance test, and the order is a suggestion rather than a rule.

Does the note name who wrote the figure and when? Does it say whether the figure was observed, reported or reconciled? Does it keep the original wording, including any hedge words? Is the note stored next to the figure rather than somewhere else? Can a reader who never saw the email understand what the figure is and is not?

If any answer is no, the note is not finished. That is a normal stage to reach, and it is better to reach it before filing than after.

One further habit helps. When a figure is later confirmed, add a line rather than replacing the original note. The history of a figure is often more useful than its final value, because it shows how the file was built and where the uncertainty sat.

For teams that want to discuss a sourcing requirement or a materials question, use the contact details on the San Techno website. Those contact details are for general enquiries and do not replace your own record-keeping.