COA transparency means a reader can follow a posted result back to a specific sample and see who tested it, when it was tested, which method and limits were used, and how that sample connects to the batch offered for sale. A PDF containing a purity number provides very little context when those connections are missing. The useful evidence lies in the documentation trail around the result.
That trail should be readable without asking the seller to fill in every blank. The product page, vial label, batch record, and laboratory report should share enough identifiers that another person can follow the same path and reach the same document.
A COA needs a chain of evidence
A laboratory begins with the sample it receives. It assigns a sample or registration number, records identifying information supplied with the sample, performs the requested tests, and issues a report under its own report number. The report should identify the laboratory, the material and batch described by the requester, the methods and acceptance limits, the actual results, the completion date, and the person who authorized the record.
The batch or lot number carries that chain back to the material under review. The number on the vial should match the number used in the seller's COA library and on the report. Product names alone are too broad because the same material may be sold across many batches, each with its own production and testing history.
The sample boundary also deserves attention. WHO guidance for pharmaceutical quality-control laboratories states that results relate to the items tested and, when the laboratory did not control sampling, to the sample as received. A report tied to a batch therefore documents the submitted sample associated with that batch. The lot match provides traceability, while the result remains a measurement of the material the laboratory actually received.
| Visible detail | What it lets a reader verify |
|---|---|
| Laboratory name and report number | Identifies who issued the record and which report is under review. Without both, attribution and direct verification become difficult. |
| Product, sample ID, and batch or lot | Connects the tested sample to the listed material and helps prevent a valid result from being attached to the wrong product or batch. |
| Received, tested, and reported dates | Places the sample and analytical work within the batch history. |
| Method, limits, units, and numerical result | Shows what was measured and how the value was judged. A pass statement or percentage cannot supply this context by itself. |
| Authorization and page identification | Shows that the complete record was reviewed and issued as one unit rather than detached or incomplete pages. |
Source reports and separately commissioned tests
An upstream source-lab report and a test commissioned separately by PSC have different histories. The upstream document records testing supplied from the source side of the batch. A separately commissioned report records a sample sent from material available to PSC. Labelling those records by origin is more informative than placing both under a broad third-party-tested description.
When both reports cover the same lot, the reader can compare their sample identifiers, dates, methods, units, and results. Similar findings from separate submissions can provide useful corroboration, especially when the second report was generated later from sale inventory. The comparison still depends on the scope and quality of each method; two purity percentages produced under different chromatographic conditions are not exact duplicate measurements.
A meaningful discrepancy needs to remain visible long enough to be understood. The sensible response is to confirm the batch connection, ask whether the laboratories used comparable methods, review sample handling, and investigate whether retesting is warranted. Quietly displaying only the more favourable report would break the documentation trail that transparency is supposed to preserve.
This approach also keeps the test results in their proper roles. Readers who need help interpreting the analytical fields can use our separate guide to reading a COA. The transparency question is whether the records, samples, and batches connect; the analytical guides explain what each measurement contributes once that connection is established.
Redactions should leave the analytical record reviewable
Public copies sometimes omit commercial contact details, account information, or sensitive supply-chain relationships. A redaction becomes consequential when it removes the information needed to identify the analytical record. If the issuing laboratory, report number, sample identifier, batch, method, units, result, or authorization is hidden, a reader loses an important part of the verification path.
The public page should identify that a document has been redacted and describe the type of information withheld. Where a source relationship must remain confidential, a separately commissioned report can supply a more open analytical record, provided its own provenance and batch connection remain visible. A seller's typed summary is not an equivalent replacement for the laboratory's issued result.
Revisions need the same care. Laboratories may correct or supersede reports, and a seller may replace an old public copy after receiving an amended file. The page should show which version is current, when it replaced the earlier copy, and why. Keeping that short history prevents an ordinary correction from looking like a silently altered result.
The value of transparent documentation
Transparent documentation lets another reader reconstruct the evidence: the vial points to a batch, the batch points to a registered laboratory sample, and the sample points to an authorized report with methods, limits, units, dates, and results. It also shows whether the report came from the source or from testing commissioned later and whether any part of the public record has been withheld or replaced.
That visibility makes the limits easier to understand without turning them into a wall of disclaimers. The report covers the submitted sample and the tests listed on the page. Storage after sampling, properties that were never measured, and the condition of every individual container require their own evidence. A transparent COA package earns its value by showing exactly where the documented result came from and allowing the reader to verify that path.
Sources and context
- Health Canada's API GMP guidance describes an authentic COA as a batch-specific record containing the tests, acceptance limits, numerical results, release information, and relevant dates: GUI-0104.
- Health Canada's drug-product GMP guide requires actual numerical results, batch references, validated methods, and clear identification of subcontracted laboratories in the regulated contexts it covers: GUI-0001.
- WHO laboratory guidance lists the sample registration number, report number, laboratory, requester, sample and batch description, procedures and limits, results, dates, authorization, and external-provider identification expected in an analytical report. It also states that results relate to the items tested and, when the laboratory did not perform sampling, to the sample as received: WHO Technical Report Series 1052, Annex 4.
- The WHO model COA shows how those elements fit into one batch-linked certificate and identifies subcontracted results, sampling information, page numbering, acceptance criteria, and authorization: WHO Technical Report Series 1010, Annex 4.
These regulated examples provide a useful framework for reading analytical records. They are not presented as a claim that a public PSC research-material page is a regulated pharmaceutical batch-release certificate.
Research-use notice: Precision Synthetics Canada products and documentation are provided strictly for lawful, non-clinical laboratory research purposes only. COAs and testing records are not medical documents, safety guarantees, sterility guarantees, therapeutic endorsements, dosing guidance, or approval for human or veterinary use.