This article describes an approach to creating and maintaining LC-MS blank-response attribution records to distinguish carryover from sequence contamination in peptide analyses. The goal is clear recordkeeping that supports traceability, analytical evidence, reviewer decisions, and conditional procedures while avoiding ambiguous conclusions.

Purpose and scope

Blank-response attribution records document observed signals in blank injections that cannot be attributed to the current sample alone. Proper records enable laboratories to determine whether a detected blank signal arises from instrument carryover, sequence contamination from prior injections, or other sources such as solvent or reagent impurities. This article focuses on record content, decision criteria, and conditional follow-up actions.

Core record elements

• Instrument and method identifiers: instrument name, serial number, method version, and chromatographic conditions.
• Run metadata: date/time, sequence position of blank(s), preceding sample identification, and injection volumes.
• Analytical evidence: full chromatograms and mass spectra for the blank and relevant adjacent injections, integrals, signal-to-noise ratios, and retention time comparisons.
• Traceability links: file paths or repository IDs for raw data and processed results, and reference to method SOPs or vendor guidance such as the M10 guideline (ICH M10).
• Reviewer assessment: a documented decision rationale including whether carryover or sequence contamination is the most likely source, confidence level, and any dissenting notes.
• Conditional procedures: required follow-up actions when attribution is uncertain or confirmed, including additional blank injections, reruns, or instrument cleaning steps.

Attribution decision criteria

Decisions should be based on reproducible, objective criteria. Suggested factors to document and evaluate include:

• Retention time alignment between blank signal and analyte peaks in prior injections (allowing for defined tolerance windows).
• Relative signal intensity compared to preceding sample(s) and to historical blank baselines.
• Mass spectral matching (accurate mass, isotopic pattern) to distinguish unrelated background peaks from analyte-related carryover.
• Effect of sequential blank injections: carryover often decreases across successive blanks; persistence suggests other sources.

Conditional follow-up procedures

When records indicate likely carryover, document which mitigation steps were performed and their outcomes. Typical conditional procedures include:

• Injection of multiple solvent blanks and documentation of signal decay pattern.
• Targeted instrument cleaning (e.g., needle wash, sample loop purge) with pre- and post-cleaning blank results recorded.
• Reanalysis of samples in a different sequence or on a different instrument when practicable, with cross-reference to original records.
• Escalation steps for persistent unexplained signals, including method review and vendor guidance (see Waters Alliance IS system support documentation for instrument-specific procedures: Waters Alliance IS support).

Reviewer documentation and traceability

Each attribution decision should be signed off by a designated reviewer and include timestamped notes. Maintain an audit trail linking raw data files, processed results, and the attribution record so that independent reviewers can reproduce the assessment. Routine checks and periodic audits of blank-response records help ensure consistent application of criteria.

References and resources

Consult regulatory and vendor guidance when establishing laboratory-specific policies. See the ICH M10 guideline for principles relevant to bioanalytical method validation and documentation: ICH M10. Additional instrument-specific recommendations are available from vendors such as Waters: Waters Alliance IS support.

Reconciliation fields that keep the record reviewable

A compact record can preserve the event identifier, source file reference, method version, instrument or balance identifier where relevant, reviewer identity, timestamp, and disposition. It can also distinguish observed evidence from an interpretation so a later reviewer can retrace why a record advanced, paused, or required a follow-up check. The fields should remain linked rather than copied into disconnected notes.

When a review identifies an exception, the record can point to the original raw-data location, the applicable procedure revision, and any authorized follow-up action. A final review field can capture the decision date, the individual making the decision, and the controlled record that explains the rationale. This approach preserves traceability without presenting a result as a product claim.

For analytical-procedure reference context, consult the FDA analytical procedure guidance alongside the sequence record.

Not for human consumption. For laboratory research use only.