Purpose and scope of reconciliation records

Injection-order reconciliation records document the relationship between planned injection sequences and the instrument-acquired sequence exports, while preserving a clear record of any excluded or re-run injections. For research-use-only peptide LC-MS work, these records support reproducibility and auditability by linking sequence evidence to reviewer decisions and exclusion rationale. A robust reconciliation captures the planned plate/well map or sequence file, the acquired sequence export from the chromatography data system (CDS), pointers to the raw data folder, and a changelog of attributable edits applied prior to data review.

Required elements and attribution

A complete reconciliation should include the original run plan identifier, timestamps for sequence creation and execution, the raw sequence export (CSV or XML), and a detailed changelog. The changelog must record who made each change, when, and why, and reference specific injection-level metadata (injection number, sample identifier, retention-time windows) so an auditor can trace each decision. Ensure CDS audit-trail entries for any manual edits are mirrored in the reconciliation document to enable cross-system comparison of timestamps and user IDs. For guidance on audit-trail expectations and attributable changes in sequence records, see the Chromatography Data System Audit Trails technical guidance.

Linking planned, acquired, and excluded runs

Reconcile planned injections to acquired runs using consistent identifiers: injection number, unique sample ID, and retention-time windows. When an injection is excluded from final analysis, include the exported chromatogram or scan evidence and a reviewer note or flag detailing the analytical rationale for exclusion. Maintain both the original and any re-run sequence entries, with explicit pointers to which entry contributed to the final dataset. This evidence-based approach helps demonstrate that exclusion decisions are traceable and based on documented analytical observations. For discussion of injection-order effects and batch-sequence considerations in targeted LC-MS/MS, see Injection-order effects in targeted LC-MS/MS.

Practical workflow and templates

Implement a standard worksheet or digital template that pairs the planned sequence file with the acquired sequence export, a link to the raw data folder, and fields for exclusion rationale, reviewer decision (accept, exclude, request re-run), and signatures or electronic user IDs. When re-runs occur, record both the original and re-run entries and indicate which run was used for downstream processing. Ensure the template captures file hashes or immutable copies of exported sequence files so reviewers can validate that the exported evidence matches the saved reconciliation record.

Reviewer decisions and preserving evidence

Reviewers should record explicit decisions in the reconciliation record and reference the supporting exported chromatographic evidence and any integration or calculation notes. Linking reviewer comments to the exact exported sequence event and storing an immutable copy of the raw export reduces ambiguity during later quality checks or audits. Maintain links to authoritative guidance on CDS audit trails so team members understand expectations for attributable edits and sequence integrity. For more on maintaining complete injection sequences and attributable changes, consult the Chromatography Data System Audit Trails resource.

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.