How to verify an LC216 label against a batch report

A batch report tells you something about the container in front of you only if both documents describe the same material. This worksheet shows how to compare an LC216 label with a certificate of analysis or batch report, field by field. It also shows how to record what the report establishes and what it leaves untested.

What the LC216 label identifies

LC216 is an identifier printed on products. A label with that code is the supplier's claim about that container. It is not a universal identity specification. Two suppliers can print the same code without describing the same material.

This worksheet does not describe what LC216 contains. Its goal is narrower: to decide whether this report belongs to this label, and what the testing behind it actually assessed.

The comparison checklist

Work from the label outward. Transcribe each field exactly as printed. Don't normalize spacing, hyphens, suffixes, or capitalization. "LC216" and "LC-216" go into the record as two separate strings, with the difference noted.

CheckWhere to lookWhat to record
Identifier textLabel vs. report's product or sample nameBoth strings, character for character
Lot or batch numberLabel vs. report headerBoth values; match or mismatch
Sample descriptionReportWording as written
Testing laboratory and report dateReportAs written, or "not stated"
Each test performedReport results sectionTest name as written
Method for each testReportMethod name or reference, or "not stated"
Reference standard for each testReportAs written, or "not stated"
Result and acceptance criterionReportAs written
Claims on the label with no matching testLabel vs. reportList each one

Separating what was assessed from what wasn't

Identity, amount, and purity are three different questions:

A test answers only the question it was designed for, and only within the method and reference standard it names. A purity result does not confirm identity. An identity result says nothing about amount.

When a report omits the method or reference standard, write "not stated." Don't infer it from the test name. When the label makes a claim the report never addresses, list that claim as untested.

For general background on how quality control laboratories document methods, reference materials, and results, see the WHO's good practices for pharmaceutical quality control laboratories. It is cited here only as context on quality documentation. It is not a requirement that applies to any LC216-labeled product.

Illustrative example: LOT-A001 and LOT-A002

The following is fictional. The lot numbers, methods, and reference names are invented, and no ingredient information is implied.

The label reads "LC216 / Lot: LOT-A002." The batch report on hand names the sample "LC216" and lists "Lot: LOT-A001." It reports two tests:

There is no amount test.

FieldLabelReportStatus
IdentifierLC216LC216Match
LotLOT-A002LOT-A001Mismatch
Identity—Method M-1, Ref-Std-XAssessed (for LOT-A001)
Purity—Method stated; reference not statedAssessed, reference not stated
Amount—No testUntested

The lot mismatch decides the outcome. However the results read, this report cannot be attributed to the LOT-A002 container. Record the comparison as unresolved. Then contact the testing laboratory or the supplier and request the report that matches LOT-A002.

Don't treat the LOT-A001 report as "close enough." Don't annotate it to fit the label. Keep the record open until a matching report arrives, then repeat the checklist on that document.

To look up reports by lot, see Amplified Labs' certificate of analysis finder.

References