A Certificate of Analysis (COA) is the analytical record that accompanies a specific lot of research material. It documents which tests were performed, how they were performed, and what the results were for the sample that was examined. For laboratories that depend on consistent, traceable inputs, the COA is a primary point of reference — but it is most useful when read precisely, for exactly what it states and no more.

This guide outlines the fields a COA commonly includes, how laboratories typically interpret them, and where the boundaries of the document lie. The aim is documentation literacy: reading a COA as evidence about a tested sample within a wider quality framework, rather than as a guarantee.

The Purpose and Function of a COA

A COA exists to communicate the outcome of defined analytical testing for an identified lot. It links a physical material to a record, and a record to the methods that produced it. In doing so, it supports review, comparison, and traceability across the supply and handling chain.

Importantly, a COA is a snapshot. It describes the sample drawn and tested at a point in time, under the methods named on the document. It is one component of a quality system, alongside internal records, storage history, and — where applicable — independent analytical documentation.

Product and Lot Identification

The first function of a COA is unambiguous identification. Laboratories commonly review these fields before anything else, because every downstream record depends on them:

  • Material name and catalog identifier — the specific item, not a general category or abbreviation.
  • Lot or batch number — the unique identifier that ties this document to a defined production and testing record. It should match the label on the container.
  • Issue or release date — when the lot was documented as released for distribution.
  • Retest or re-evaluation reference, where applicable — a date or condition after which the material is reviewed again rather than relied upon by default.

Consistent identification is what allows a lot number on a vial to be connected to its COA, its order record, and its place in inventory. The relationship between these identifiers is covered in our guide to batch traceability and lot documentation.

Analytical Categories

The analytical body of a COA reports results for a defined set of tests. The specific categories vary by material and by the testing performed, but documentation may include the following.

Identity

Identity testing addresses the question of what the material is. Methods commonly used for identity confirmation are recorded alongside the result, so that the basis for the identification is transparent rather than asserted.

Purity

Purity testing describes the proportion of the tested sample attributable to the target material under a stated method. A purity value is meaningful only in the context of the method, the conditions, and the reporting limit used to generate it.

Appearance

Appearance is a descriptive observation — for example, the physical form and color of the material as examined. It is qualitative, and laboratories typically record it on receipt for comparison against the COA description.

Mass and Quantity Verification

Where applicable, a COA may document mass or fill verification for the lot. As with other fields, this reflects the measurement performed and its associated tolerance, not a property guaranteed for every unit independent of measurement.

Analytical Methods and Reporting Limits

Each result on a credible COA should be traceable to the method that produced it. A numeric value without a method is difficult to interpret; the same nominal result can mean different things under different techniques and conditions.

Reporting limits matter for the same reason. A reporting or detection limit defines the smallest quantity a method can reliably report. When a field reads "not detected," that statement is bounded by the method's limit — it indicates the substance was not detected at or above that limit, which is not the same as proof of total absence. Laboratories commonly review methods and limits together before relying on any individual value.

Interpreting Common Fields Without Overstating

Sound interpretation stays close to what the document says. A few habits help:

  • Read each result as a property of the tested sample under the stated method, not as a universal claim.
  • Treat "not detected" as bounded by the reporting limit, not as absolute absence.
  • Compare COA fields against the physical material and label on receipt, and record any discrepancy before the material enters a workflow.
  • Avoid inferring suitability for a particular use from a COA alone — suitability is determined by the laboratory against its own requirements and SOPs.

Supplier Documentation, Internal Records, and Third-Party Reports

Three distinct kinds of documentation often coexist, and conflating them weakens a quality picture:

  • Supplier documentation is generated by or on behalf of the organization releasing the material.
  • Internal records are created by the receiving laboratory — receipt logs, storage history, inventory status, and observations.
  • Independent third-party analytical reports, where applicable, are produced by a separate laboratory and provide an additional, independent line of documentation.

Each serves a different purpose, and they are strongest when retained together rather than treated as interchangeable.

What a COA Does Not Guarantee

A COA is evidence about a tested sample under stated methods. It does not, on its own, establish any of the following:

  • That the material is appropriate for a specific research workflow — suitability is a laboratory determination made against institutional SOPs.
  • That every unit in a shipment is identical to the tested sample; testing is performed on a sample, not on each container.
  • That stability has been preserved after the test date, particularly where storage and handling fall outside documented conditions.
  • Any property the document does not actually test for. A COA is silent on tests it does not list.
  • Regulatory approval, fitness for human or veterinary use, or any therapeutic, diagnostic, or consumption-related conclusion.

Recognizing these limits is what lets a COA do its real job: serve as one reliable, well-understood record within a broader, documentation-focused quality framework.

Key Takeaways

  • A COA documents defined tests on a specific lot — read it for what it states, not as a guarantee.
  • Identification fields (material, catalog ID, lot number, dates) anchor every downstream record.
  • Results are only interpretable alongside their methods and reporting limits.
  • Supplier documentation, internal records, and third-party reports are distinct and complementary.
  • Suitability and stability are determined by the laboratory and its SOPs — not by the COA alone.