Questions worth asking about any material

By now, you may have noticed something about Snow.

Snow rarely starts with:

Is this good?

That question is too large.

Instead:

What is it?

Which lot?

Which document?

Who issued it?

What was measured?

Which unit?

What happened to it?

What does the evidence actually support?

Those smaller questions are how a complicated material becomes understandable.

This final Foundation lesson brings them together.

Question 1: What is this represented to be?

Start with identity.

Read:

• product or material name
• presentation
• identifying code
• issuer or supplier
• label description

Do not start with the laboratory result.

Do not start with the biggest percentage.

Do not start with the marketing language.

First establish what the object is represented to be.

Everything else attaches to that identity.

Question 2: Which lot or sample does the evidence describe?

Find the lot.

Find the sample identifier.

Find the report identifier.

Compare them exactly.

GS1’s traceability framework treats batch or lot identity as a distinct level of identification precisely because it allows one production group to be distinguished from another.

Do not treat identifiers as decoration.

They are the joins that hold the evidence together.

Question 3: What kind of document am I reading?

An SDS has one job.

A Certificate of Analysis has another.

A laboratory report may have another.

A specification sheet has another.

OSHA’s SDS structure, for example, is explicitly centered on hazard communication, including identification, hazards, composition, handling, storage, and related information.

Ask:

What was this document created to communicate?

Then judge it by that scope.

Question 4: Who is making the claim?

A laboratory result is a laboratory claim.

A manufacturer’s specification is a manufacturer claim.

A supplier statement is a supplier claim.

A NIST certificate is a NIST claim.

The source matters.

Authority does not transfer automatically from one organization to another simply because a logo or reference appears on a page.

NIST is explicit, for example, that organizations are responsible for supporting the traceability claims of their own measurement results.

Follow the claim back to its issuer.

Question 5: What was actually measured?

Look past the result.

Read the row name.

Read the method.

Read the reporting basis.

Read the unit.

If the table says:

98.7%

ask:

98.7% what, measured how?

A result cannot carry more meaning than the measurement behind it.

That was the heart of Foundation 02.

It remains one of the most useful questions in the entire Academy.

Question 6: Are the units telling the story I think they are?

A number without a unit is incomplete.

Mass is not volume.

Volume is not concentration.

Concentration is not count.

Percentages need a defined basis.

NIST’s SI guidance emphasizes that a quantity is expressed using a numerical value together with its unit, and that prefixes change scale by defined powers of ten.

Never compare numbers until you have checked what quantities they represent.

Question 7: What is the result being compared against?

A specification is not the result.

A result is not the specification.

If the report says:

PASS

ask:

Against what criterion?

Then:

Who established that criterion?

Then:

Does it apply to the question I care about?

A passing line in one row does not make every characteristic of a material pass.

Question 8: What happened between the material and the record?

This is the traceability question.

When was the sample collected?

Who submitted it?

Which lot did it represent?

Did an identifier change?

Can you connect the physical material to the analytical record?

Can you connect it to shipping or storage records?

GS1 frames traceability around identified objects and events described by who, what, where, when, and why.

Those questions turn isolated documents into a history.

Question 9: What happened after the test?

A result is tied to a point in time.

The material may continue to move afterward.

It may be stored.

Transferred.

Shipped.

Repacked.

A valid test result does not automatically document everything that happened later.

The question is not meant to create suspicion.

It is meant to preserve chronology.

Testing is an event in the history.

It is not the end of history.

Question 10: What do the storage records actually show?

If temperature matters, look for evidence of temperature.

Not just cold packaging.

Not just a storage statement.

Not just the fact that something arrived cool.

Look at the applicable condition, monitoring interval, timestamps, and excursions.

CDC and WHO temperature-control guidance provide concrete examples of why storage history is based on monitored conditions and documented events rather than appearance alone.

Again:

the exact requirements depend on the material.

The reading skill remains the same.

Question 11: Is something missing—or merely unstated?

These are different.

A document may not contain storage information because storage is outside its scope.

A report may not list a particular test because that test was not performed.

That does not automatically make the document defective.

But it means you should not invent the missing information.

Question 12: Is the evidence independent?

Sometimes independence matters.

A supplier can provide useful information about its own material.

A third-party laboratory can provide useful analytical information.

A standards body can define a measurement system.

These roles are different.

Do not assume:

third party = automatically correct

or:

supplier = automatically unreliable

Instead ask:

Who generated this evidence, and what role did they have?

Independence is context.

Not magic.

Question 13: Is the document current?

Look for:

• revision
• issue date
• superseded version
• corrected report
• current certificate
• updated method

NIST, for example, specifically advises users of its reference materials to ensure they have the current certificate or report associated with the material.

Old evidence may still be historically valid.

But you should know that it is old.

Question 14: What conclusion am I trying to reach?

This is one of Snow’s favorite questions.

Sometimes the evidence is fine.

The problem is the conclusion.

If the document reports identity, but you are trying to conclude purity, the gap is yours.

If the record proves a lot match, but you are trying to conclude perfect storage history, the gap is yours.

If the temperature log covers three days and you are trying to conclude what happened during the week before it began, the gap is yours.

Before criticizing the evidence, inspect the inference.

Question 15: What would change my conclusion?

Good evidence evaluation is not about defending your first impression.

Ask:

What additional record would resolve this uncertainty?

A matching lot?

A method reference?

A missing date?

A continuous temperature record?

A corrected certificate?

An original laboratory report?

This makes your uncertainty actionable.

Instead of:

I don’t trust this.

you can say:

This specific connection is missing.

That is much more useful.

Question 16: What remains unknown?

Every evidence set has a boundary.

Even excellent records leave some things unanswered.

That is normal.

The goal is not infinite certainty.

The goal is to know where the certainty ends.

Good questions are a quality system of their own

You do not need to memorize every analytical method.

You do not need to become an expert in every document format.

You do not need to distrust everything.

You need a repeatable way to read.

Start with identity.

Connect the lot.

Identify the document.

Find the issuer.

Read the measurement.

Respect the unit.

Follow the history.

Notice the boundary.

Then stop where the evidence stops.

That is the discipline behind all eight Foundation lessons.

The goal is not to know everything.

It is to know exactly what the evidence gives you—and exactly what it does not.