Research Notes

GLP Recordkeeping Principles for Peptide Research Labs

August 26, 2026 · Peak Labs Quality & Verification · COA, documentation, quality, reference

Educational information for a laboratory audience. Not medical advice, not a recommendation for human use. Peak Labs products are for laboratory research use only.

A certificate of analysis tells a researcher what was in a vial when it left the manufacturer. It says nothing about what happened afterward: how the vial was received, where it was stored, who handled it, and whether the sample tested six months later is the same material that arrived. That gap is closed not by better chemistry but by better recordkeeping. Good Laboratory Practice, or GLP, is the framework most laboratories borrow for this purpose, even when they are not operating under a formal regulatory GLP study.

What GLP Means Outside a Formal Regulatory Study

GLP originated as a regulatory standard for nonclinical safety studies, most notably under the OECD Principles of Good Laboratory Practice and, in the United States, 21 CFR Part 58. A small research group working with peptides for in-vitro study is unlikely to be operating under a full GLP-compliant study protocol, and does not need to claim that it is. What is worth borrowing is the underlying discipline: every result should be traceable back to a specific sample, a specific instrument state, and a specific person, on a specific date. That traceability is what makes a dataset defensible later, whether the audience is a supervisor, a journal reviewer, or the researcher's own future self trying to reproduce a result.

The ALCOA+ Framework for Data Integrity

Regulatory agencies and standards bodies commonly summarise data integrity expectations with the acronym ALCOA+, extended from the original ALCOA principles used in FDA guidance. Applied to a peptide research notebook or LIMS entry, it translates into a short checklist:

Attributable: every entry is tied to the person who made it, not left anonymous.
Legible: records can be read and understood by someone other than the author, months later.
Contemporaneous: data is recorded at the time the work is performed, not reconstructed afterward from memory.
Original: the first recorded value is preserved, rather than only a transcribed summary.
Accurate: values match the source instrument or observation, with corrections made transparently rather than overwritten.
Complete, Consistent, Enduring, and Available: the extended principles cover retaining the full dataset, using consistent units and formats, storing records durably, and being able to retrieve them when needed.

None of this requires expensive software. A bound notebook with dated, initialled entries and no torn-out pages satisfies most of ALCOA+ as well as a validated electronic system does, provided corrections are struck through rather than erased and the reason for the correction is noted alongside it.

Core Records Worth Maintaining for Every Lot

Receipt and Chain of Custody

The record trail should start the moment a shipment arrives, not when the sample is first used. That means logging the arrival date, the condition of the packaging, and the lot or batch identifier before the vial goes into storage. A structured approach to this step is covered in more detail in our guide to sample labelling and chain of custody, and it pairs naturally with the certificate of analysis for that same lot, which should be filed and cross-referenced rather than left in an email inbox. Our COA reference page and the companion article on reading a peptide COA are useful starting points for what that document should contain and how to file it against a lot number.

Equipment Calibration and Maintenance Logs

Any instrument that produces a number used in a decision, an analytical balance, a pH meter, a freezer thermometer, needs a calibration and maintenance history. The log should record the calibration date, the reference standard used, the acceptance criteria, and the result, along with routine maintenance events such as filter changes or recalibration after a service call. If a balance reading from March is later questioned, the calibration log is what confirms whether the instrument was in specification at the time.

Standard Operating Procedures with Version Control

An SOP that has been silently edited three times with no record of what changed is worse than no SOP at all, because it creates false confidence. Each SOP should carry a version number, an effective date, and a brief change log. When a procedure changes, for example a revised weighing technique or a new reconstitution solvent, results generated under the old and new versions should be distinguishable in the record.

Sample-Level Logs

For any sample that gets aliquoted or subjected to repeated freeze-thaw cycles, a simple running log, cycle count, date, and who accessed the vial, prevents ambiguity about how many times a sample has been through a stress event before a result is interpreted.

Audit Trails and Electronic Records

Where a lab uses electronic instruments or a laboratory information management system, the audit trail is the electronic equivalent of the struck-through notebook correction. A meaningful audit trail records who changed a value, what the previous value was, when the change occurred, and why. Systems that allow silent overwrites without a trail should be treated as a gap to fix, not a convenience. Where budget or scale does not justify a full LIMS, a shared spreadsheet with locked historical rows and a change-log tab is a reasonable interim approach, provided it is backed up on a schedule the lab actually follows.

Common Gaps in Small Research Labs

The most frequent failure is not fraud but drift: a notebook that starts rigorous and becomes sparse under deadline pressure, a calibration log that is current for the primary balance but forgotten for a secondary one, or a COA archive that is complete for recent lots but has gaps from a busy quarter. Periodic self-audits, even an informal one done quarterly, catch these gaps while they are still easy to close. Questions worth asking in such a review are addressed in general terms on our FAQ page, which covers how documentation, storage, and quality records relate to one another in practice.

Building a System That Survives Turnover

The real test of a recordkeeping system is whether it still functions when the person who built it leaves. That means documentation should not depend on tribal knowledge: where files live, how lots are numbered, and which log corresponds to which instrument should themselves be written down. A short onboarding document that maps out the recordkeeping system, updated whenever the system changes, is one of the highest-value documents a small lab can produce and one of the most commonly skipped.

Sources and further reading

Research use only. Peak Labs products are supplied strictly for in-vitro laboratory research. They are not medicines or supplements, are not for human or veterinary use, and are not intended to diagnose, treat, cure, or prevent any condition.