Peptide Batch Testing and Documentation

Define the batch before testing

A batch or lot is a defined quantity of material produced or handled under a specified set of conditions and assigned a unique identifier. The exact operational definition belongs in the organization’s quality system. For the COA reader, the essential point is that the identifier must remain consistent across labels, sampling records, analytical data, and the released certificate.

Catalog names are not batch identifiers. Two vials with the same compound name can belong to different lots with different production, test, or storage histories. Never use a certificate from one lot as evidence for another merely because the product name matches.

Sampling and chain of custody

The analytical instrument receives a small test portion. A documented sampling plan is what connects that portion to the larger batch. The plan should address who sampled, where and when sampling occurred, how containers were selected, how the sample was labeled, and how its integrity was maintained through transfer and preparation.

A customer-submitted sample may support conclusions about that submitted material, but broader batch representation depends on the sampling evidence. Reports should describe scope honestly so that a single-vial result is not automatically generalized beyond its traceable population.

Build the test panel from the specification and risk

A batch test panel may include identity, chromatographic purity, assay or content, water, residual solvents, appearance, or other attributes when justified. Not every attribute is measured by every method, and not every peptide has the same relevant risks. The approved specification should define which tests and criteria govern disposition.

FDA’s Q7 guidance states within its API scope that specifications should identify tests and acceptance criteria, and that laboratory-control records should include complete data derived from testing. The underlying principle—preserving the relationship among the sample, procedure, data, review, and decision—is useful for evaluating research documentation without implying that a research material has a particular regulatory status.

• Identity and the method used to support it
• Purity or related-substance procedure and reporting basis
• Quantitative content or assay when specified
• Material-specific residual or physical attributes
• Defined acceptance criteria and documented method references

Method control and run acceptance

Analytical procedures should have controlled identifiers and revisions. Analysts should be able to retrieve the exact version used for the batch. Equipment status, reference standards, reagents, calculations, and system-suitability checks form part of the context that makes a numerical result reviewable.

ICH Q2(R2) relates analytical validation to the intended purpose of the procedure. A method used for identity may have different performance questions from one used for a quantitative impurity result. A COA can summarize the outcome, but the laboratory should retain enough underlying information to reconstruct and review the analysis.

Separate specification, result, and disposition

The specification is the criterion; the result is the reported observation; disposition is the controlled decision based on the complete record. Keeping these fields separate prevents a target value from being mistaken for measured data. It also makes clear when a result is informational rather than part of release criteria.

A certificate that states “conforms” should retain or reference the applicable criterion. If a result is qualified, below a reporting limit, estimated, or outside the validated range, the qualifier belongs with the value. Removing it changes the meaning of the data.

Deviations, unexpected results, and retesting

Unexpected or out-of-specification results should be handled through a documented investigation process appropriate to the laboratory. Repeating injections until a preferred result appears is not a scientific decision rule. Any invalidation, retest, resample, or revised conclusion should have a documented rationale and preserve the original data relationship.

FDA laboratory-control materials emphasize validated procedures, complete data, and consistent injection nomenclature in their regulated context. For a certificate reader, unexplained replacement of results, missing versions, or selective traces are reasons to request clarification rather than average away uncertainty.

The certificate is part of a record lifecycle

After review and authorization, the COA should carry a unique report identity and remain linked to the batch. If an error is corrected, the amended version should identify its status and maintain an audit relationship to the previous version. Online records should avoid serving two conflicting certificates as though both are current.

At the receiving laboratory, verify the lot, save or reference the current report, and record the date of verification. If the certificate cannot be found, the lot does not match, or a later amendment changes a material result, follow the institution’s hold and review process.