Report Numbers, Batch Numbers and Sample Identifiers
Give each number a job
A report number identifies a document or reporting event. A batch number identifies a defined production grouping under the producer’s system. A sample identifier tracks the item received or created by a laboratory. These numbers may appear together, but they are not interchangeable.
A purchase-order number adds another layer: it connects a transaction with your organisation. It usually cannot, on its own, establish which sample was analysed. Write the identifier’s owner and purpose beside the value rather than maintaining a single spreadsheet column called “reference”.
Draw the relationships
Imagine two vials from one supplier lot sent to different laboratories. They could share the supplier batch code while receiving separate laboratory sample numbers and separate report references. Conversely, one report might contain results for several samples. Read the document structure before assuming a one-to-one relationship.
For a useful pharmaceutical reference, ICH Q7 covers laboratory records and certificates. For ordinary research purchasing, design a small mapping table linking supplier code, physical stock identifier, submitted sample and report. Include the source of each connection.
Handle revisions explicitly
A revised report can retain its original number and gain a revision suffix, or receive a replacement number. Ask the issuing laboratory how its system works. Record which version supersedes which, the stated reason for amendment and whether any analytical result changed.
The wider records perspective in OECD’s GLP data-integrity publication is relevant when planning this audit trail. That does not make an internal spreadsheet GLP compliant; it helps identify the context that should remain understandable when staff or software change.
Use the mapping during research
At receipt, give each physical item a local stock reference without covering the original label. At testing, record which item supplied the sample and whether it was opened, divided or pooled. At reporting, attach the laboratory result to that submitted sample first. Any extension to other stock needs its own justification.
The COA library can help locate supporting files, while your local register supplies the delivery-specific relationships. Before an experiment is recorded, check that the notebook references both the material and the actual document reviewed.
If two codes disagree, retain both and investigate the difference. Changing one to make the table look consistent can destroy the very clue needed to resolve a mix-up. Clear relationships matter more than a visually tidy list of numbers.
Related research reading
- What Raw Analytical Data Adds to a Short Certificate
- What a Redacted Batch Field Means for Traceability
Explore the research blog and original batch-document library for further context.