Scope and pre-review system suitability

This checklist provides a structured workflow for reviewing chromatographic peaks generated during research-peptide analyses, emphasizing documented reviewer decisions and an auditable record trail. Before inspecting individual peaks, confirm system suitability results and capture run context: instrument ID, column lot or serial, method version, mobile-phase lot identifiers, and calibration/qualification status. Compare system suitability metrics to method acceptance ranges and document whether the run is acceptable. Link the system suitability report to the chromatogram file and note any deviations or corrective actions taken prior to peak review. For foundational reference material on chromatographic practice, see USP general chapter guidance and related resources https://www.usp.org/…/harmonization-november-2021-m99380.pdf.

Peak identity evidence and documentation

For each detected peak, document the evidence used to assign identity. Typical records include retention time comparison to authenticated reference standards, spectral matching where available, and co-injection observations. Record the reference material identifier, preparation details, and whether identity is confirmed, tentative, or not assigned. When identity assessment is influenced by integration choices (for example, unresolved shoulders or closely eluting components), include a rationale linking identity conclusions to the integration parameters applied. Preserve chromatogram snapshots and audit-trail identifiers that substantiate the identity decision.

Peak shape assessment and integration decisions

Evaluate peak shape characteristics (tailing factor, symmetry, resolution) and note anomalies such as shoulders, fronting, or split peaks. Record the integration algorithm and specific parameters used: smoothing, baseline definition, valley settings, and threshold values. If manual integration or re-integration is applied, log who performed the change, when it occurred, and why. Attach before-and-after chromatogram images or reference audit-trail entries. Maintain a concise decision log that states whether the reported result is the original integration, a corrected integration, or excluded from reporting because of unresolved artifacts. Ensure integration choices are reproducible by another reviewer using the recorded parameters.

Reviewer traceability, retention, and conditional actions

All reviewer decisions must be signed, dated, and linked to the exact chromatogram and data-file identifiers. Use electronic audit trails or signed worksheets to show the sequence of review actions and any escalations. Retain records according to laboratory policy, ensuring file naming conventions, version histories, and reviewer notes are searchable and linked in the laboratory information management system where available. If system suitability fails or peak identity/integration remains ambiguous, document conditional actions such as re-analysis with adjusted conditions, re-preparation of reference, or escalation for secondary review. Record each decision, the justification criteria, and the follow-up action; link original and subsequent records to preserve the full decision path. For expectations on record integrity and documentation, consult regulatory technical guidance such as the FDA data integrity Q&A https://www.fda.gov/media/119267/download.

Record assembly and review handoff

A useful record package can identify the source file, the method or sequence context, the operator or reviewer role, the date-time relationship, and the controlled location of the supporting evidence. The reviewer can then compare the documented plan with the evidence actually retained, note any exception using a defined classification, and link the decision to a dated review entry. This keeps a later reader from having to infer why a particular record was retained, excluded, or routed for further laboratory review.

Before the record is closed, laboratories can confirm that file names, sample identifiers, method identifiers, and archive locations use the same controlled references across the package. Where the evidence changes, the record can preserve the reason, the person making the change, and the relationship to the prior version. This is a documentation practice rather than a claim about an analytical outcome.

Source context

For related technical context, review the first referenced technical source and the second referenced technical source. Their role here is to inform a traceable laboratory-record structure; each laboratory should apply its own documented procedures and review controls.

Not for human consumption. For laboratory research use only.