What a certificate of analysis actually tells you
A certificate is a record of one specific batch, not a promise about the product line. Here is what has to be behind it before it is worth the paper it's printed on.
A certificate of analysis is often treated as a formality — a PDF that accompanies an order because someone expects one. Used properly, it is closer to an audit trail: a signed statement that a specific batch was measured, on a specific date, against a specific method, by a named person, and that the numbers on the page are what came out of the instrument.
It is a record, not a promise
A specification sheet describes what a product is designed to be. A certificate of analysis describes what one particular lot measured as, after it existed. The two documents look similar and are routinely confused, but only one of them is evidence. If the same PDF is emailed out for every order of a given product regardless of lot number, it is a specification sheet wearing the wrong name.
The four things that have to be on it
- A lot number that matches the vial in front of you — without it, nothing else on the page can be tied to your material.
- A named analyst and a release date, so the document has an author and a point in time rather than floating free of both.
- Results reported against a defined method, not just a percentage sitting on its own with no method reference.
- Identity confirmation alongside purity — a clean result on the wrong compound is still the wrong compound.
The release workflow behind the document
A sample is pulled at production, sent to the lab, and tested against a written method. The results go to quality control for review against our internal specification, which is set tighter than the minimum we would accept from a supplier. Only once that review passes does the certificate get generated — the document is the output of the process, not a formality attached afterwards.
Where ours live
Every certificate we issue is uploaded to a public batch lookup by lot number, and it stays there. If you are building an audit trail for a grant, a procurement file, or an internal QA record, that is the version to keep — searchable by lot number rather than by whichever email thread it originally arrived in.