12 July 2026 · 9 min read

Peptide Lot Traceability and Record-Keeping for Small Research Labs

If you run a small lab or R&D team, you probably do not have a full quality system or a dedicated LIMS. You still need to know which batch of peptide was used in which experiment, and you need to be able to find that information months later when results look odd or a reviewer asks questions.

This guide sets out a practical approach to lot traceability and record-keeping for peptide reference materials in small research settings, without over-engineering the process.

Why lot traceability matters

Lot (or batch) traceability is the ability to link:

A specific vial of peptide, identified by its batch or lot number,
To the COA and supplier documentation for that batch,
To the experiments, protocols and results that used it.

This matters because:

Batches can differ in purity, water content, or minor impurities, even from the same supplier.
Storage conditions or handling can vary between vials and over time.
When results change, you need to know whether the peptide batch changed at the same time.

Without batch-level records, you are left guessing. With them, you can test hypotheses instead of starting over.

What you should be tracking

For each peptide reference material, aim to capture a core set of fields. You can do this in a spreadsheet, a simple database, or a shared lab document.

At receipt

Peptide name and sequence (if applicable)
Supplier name and contact details
Batch / lot number (as printed on the vial and COA)
COA reference (file link or document ID)
Date received
Person who accepted the batch
Initial storage location (e.g. “Fridge A, shelf 2” or “Freezer B, drawer 3”)

During use

Date first removed from storage
Dates of subsequent removals and returns (optional but useful for critical batches)
Reconstitution details
Date of reconstitution
Solvent used
Final concentration
Who prepared it
Solution storage location (if different from powder)
Any observations
Appearance different from COA description
Solubility issues
Unexpected behaviour in assays

Linking to experiments

Experiment or project ID
Protocol or method reference
Date(s) the batch was used
Key outcomes or notes (e.g. “first run with this batch”, “results consistent with batch X”, “notable deviation from prior runs”)

You do not need to track every single use in minute detail. The goal is to have enough information to explain what you did and to spot patterns over time.

A simple record structure you can use today

If you are starting from scratch, a spreadsheet with one row per batch is enough. Column headings might include:

Peptide name
Sequence / molecular formula
Supplier
Batch number
COA file link
Purity (from COA)
Date received
Storage location (powder)
Reconstitution date
Solvent
Concentration
Prepared by
Storage location (solution)
Experiments used in (list of project IDs or links to another sheet)
Notes / observations

You can add a second sheet that logs individual experiments, with columns for:

Experiment ID
Date
Peptide batch number(s) used
Protocol reference
Person responsible
Brief outcome or notes

This two-sheet structure keeps the system simple but powerful. You can filter by batch to see every experiment that used it, or filter by experiment to see every batch involved.

How to link batches to your existing workflows

You already have some form of lab diary, project folder structure, or shared drive. The trick is to integrate batch information into what you already do, rather than building a parallel system that nobody uses.

Practical steps:

Reference batch numbers in protocols

Add a line in your standard protocol templates: “Peptide batch number(s) used: _”. This makes it easy for anyone running the method to record the batch without thinking too hard.

Include batch numbers in file names or headers

For key experiments, put the batch number in the file name or at the top of the analysis document. For example: “2026-07-08_AssayX_Batch12345”.

Use a shared folder for COAs

Create a folder structure like: Peptides > [Peptide Name] > [Batch Number] > COA.pdf. Then link to that folder or file from your tracking sheet.

Add batch info to order and delivery records

When you log an order from a supplier, include the batch numbers that arrive and the date they were logged into the lab system. This supports both traceability and inventory management.

The more you can make batch recording part of the normal flow, the less it feels like extra admin.

Minimum viable traceability for very small teams

If you are a one-person operation or a very small team, you can strip this down to the essentials:

One spreadsheet with one row per peptide batch.
A folder for COAs, organised by peptide and batch.
A rule that every experiment file name includes the batch number(s) used.
A note in your lab diary or method document whenever you start using a new batch.

That is enough to answer questions like:

“Which batch did I use for that run in March?”
“Have I changed batches since I saw that odd result?”
“Do I have COAs for everything I used in this project?”

You can add more detail later as your work grows in complexity.

How this supports quality and compliance

Good traceability practices support several goals at once:

Reproducibility

You can repeat experiments with the same batch or deliberately test a new batch, knowing exactly what changed.

Troubleshooting

When results drift, you can check whether batch changes, storage issues or reconstitution differences line up with the timing of the change.

Reporting and review

When writing up or responding to reviewers, you can describe your materials and batch usage precisely, rather than vaguely.

Regulatory alignment

Even if you are not running a formal quality system, documenting batch usage and storage aligns with the expectations for research-use-only materials in the UK.

Regulators and funders increasingly expect documentation that shows what materials were used and how they were controlled.

Common gaps and how to fix them

Some typical weaknesses in small labs:

No link between experiments and batch numbers

Fix: add a single “batch number” field to your main experiment log or protocol template.

COAs saved but not tied to batches in any system

Fix: adopt a simple folder structure and link each COA to the corresponding row in your batch spreadsheet.

Batch numbers noted in some places but not others

Fix: standardise one place where batch numbers must always be recorded (e.g. protocol header or experiment log), and train everyone to use that consistently.

No record of reconstitution details

Fix: add three columns to your batch sheet: reconstitution date, solvent, concentration. Fill them in whenever you make a solution.

You do not need to fix everything at once. Start with the gaps that cause the most confusion in your day-to-day work.

Research-use-only and regulatory context

This guide is written for researchers handling peptide materials as laboratory reagents, not as medicines or for personal administration.

In the UK, peptides supplied as research-use-only materials are distinct from medicinal products regulated by the MHRA. Traceability and record-keeping should reflect their role as research tools, supporting good practice and reproducibility, not clinical use.

Nothing in this article is medical advice, and none of it should be interpreted as guidance for human or veterinary use. Keeping that boundary clear in your documentation and communications is important both for compliance and for maintaining a credible research-materials operation.

Summary

Lot traceability for peptide reference materials does not require complex software or a full quality system. You need:

A simple, consistent way to record each batch and its key attributes.
A reliable link between batches and the experiments that use them.
Basic records of storage, reconstitution and handling.

Set up a minimal system now, use it consistently, and refine it as your work grows. Over time, those records will become one of your most valuable assets when you are trying to understand, reproduce or defend your results.