Revised peptide COAs: document control and data integrity

A revised certificate of analysis needs a visible relationship to the record it replaces. The buyer should be able to identify the changed information, the reason for the change and the effect on an earlier purchasing decision. A newly dated PDF with the same filename leaves those questions unanswered.

For research use only peptides, document control connects the accepted specification to the records supplied for the actual batch. It also helps a supplier communicate a correction without losing the history of what a customer originally received. This is particularly useful when procurement, quality review and receiving are handled by different people.

What published data-integrity guidance contributes

MHRA’s March 2018 guidance explains ALCOA as attributable, legible, contemporaneous, original and accurate, with complete, consistent, enduring and available describing further data-lifecycle expectations. These concepts help frame questions about a record’s history. See section 3.10 of the MHRA guidance.

The regulatory scope matters. MHRA’s guidance concerns pharmaceutical and regulated GLP settings. Its official landing page also explains the relevance of OECD’s later GLP guidance. These references do not certify this website, its catalog or a supplier’s document system.

OECD published GLP Data Integrity, Series No. 22, on 20 September 2021 for facilities or sites conducting GLP studies or phases. It describes risk-based management of data across its lifecycle. The purchasing checks below are our recommendations for research-material records, rather than a declaration that every RUO transaction is a GLP activity.

Identify the reason for the revision

A spelling correction and a changed material designation can have different consequences. The issuer should describe the change precisely enough for the recipient to assess it. Avoid treating every revision as either a harmless formatting update or proof that the material failed a test.

This classification is a review aid, not a finding about any particular report. A correction request should cite the exact document reference and relevant field so that both organizations discuss the same issue.

What a useful revision record contains

Ask the issuer how it links a replacement to the original. The explanation can be proportionate to the correction, but the recipient still needs an understandable history.

• A stable report identifier and an identifiable revision.
• The material designation and batch or lot to which the record applies.
• The issue date and the relationship to the earlier version.
• A description of the changed fields and the stated reason.
• The responsible issuer or authorized approval record.
• An explanation of whether the earlier version has been superseded.
• A notification route for recipients whose decisions may be affected.

The buyer should keep the received original with the correction correspondence and the accepted replacement. In the purchasing system, mark the current approved version clearly while retaining access to the history. Replacing the only stored copy makes it harder to explain which evidence was available when an order was accepted.

Separate the COA summary from supporting data

A formatted report is one part of the evidence

A COA summarizes information for a batch. It does not necessarily contain every supporting analytical record or the complete change history maintained by the issuer. Ask what records can be supplied for the particular question and whether a confidentiality arrangement is needed for deeper disclosure.

An unavailable record remains an evidence gap

Limited public access does not establish that a batch is authentic or inauthentic. It tells the buyer that the public record is insufficient to answer the question. Record the request, the issuer’s response and the institution’s decision about whether that gap is acceptable. Our COA assessment guide explains the initial batch match.

Retain electronic records in a usable form

A document link can expire or lead to a replacement file. Save an authorized copy in the institution’s agreed record system, together with the source and receipt context. Confirm who can retrieve it if the colleague who received the email leaves the project.

A file checksum can help detect whether a stored file has changed, but it does not verify the truth of its contents or the identity of its issuer. An official contact route, the document history and the material match still need review. Avoid uploading private reports to public verification services without the document owner’s authorization.

Agree the correction route before a problem occurs

For repeat supply or private-label projects, identify who receives revised reports, who reviews their impact and how a superseded copy is marked. These responsibilities can sit in the project’s quality agreement alongside the accepted specification and document-access arrangements.

Send Hytanbio-Tech the exact designation and report or batch reference through the documentation contact route. Include the field requiring clarification. Do not send personal health information or confidential experimental details in the initial message.

For research use only. Not for human, veterinary or diagnostic use. This resource provides no experimental or administration instructions.