Establishing a comprehensive identity-evidence packet for peptide reference materials centers on documenting ion-adduct and charge-state assignments, and linking those annotations to calibration, raw-file provenance, processing parameters, and reviewer decisions. This article outlines practical record types and a workflow to produce auditable evidence that supports identity assertions for high-resolution mass spectrometry (HRMS) datasets.

Why an identity-evidence packet matters

An identity-evidence packet bundles all records that justify an annotation of a peptide observed by HRMS. The packet makes explicit which ion-adducts were considered, how charge states were assigned, the calibration used for mass accuracy, which raw files underpin the calls, and which processing or integration choices influenced the reported m/z and isotopic pattern interpretations. Referencing established terminology improves clarity; see the IUPAC guidance for consistent term usage at IUPAC Gold Book: term. Consolidation of these records supports reproducibility and auditability across laboratory teams.

Key annotation records to capture

Every packet should include structured records for:

• Observed m/z and proposed formula or composition, with precise mass error (ppm) and the tolerances used for assignment.
• Ion-adduct hypothesis list (e.g., [M+H]+, [M+Na]+, multiply charged forms) with rationale for inclusion or exclusion based on observed isotopic patterns and adduct-specific fragmentation, when available.
• Charge-state assignment evidence: annotated spectra showing charge-specific isotope spacing, deconvolution summaries, and any software settings used to infer z.
• Calibration and external references: calibration file identifiers, date/time, and a short note on calibration stability or deviation during the acquisition window.
• Raw-file provenance: instrument identifier, acquisition file name, operator initials, and a checksum or hash to prevent silent file edits.

Guidance on standardized reference materials and databases, including reference spectra and curated entries, can augment these records; see the NIST standard reference resources for database context at NIST SRD-1A and peer-reviewed method discussion in the literature such as the HRMS peptide characterization review at PMC article on HRMS peptide characterization.

Recommended workflow and conditional procedures

Adopt a stepwise workflow that records conditional decisions as discrete entries rather than burying them in narrative notes. A practical sequence:

1. Acquire raw data with a run sheet noting instrument status and calibration files applied.
2. Perform mass calibration and save both pre- and post-calibration metadata; if re-calibration is performed, record triggers and parameters for the conditional action.
3. Generate initial peak lists and propose plausible ion-adducts; flag ambiguous peaks for targeted re-acquisition or MS/MS evidence collection.
4. Assign charge states using isotope spacing and, where available, deconvolution outputs; capture software version, parameter file, and date stamped results.
5. Document all processing steps (filters, smoothing, centroiding, baseline subtraction) as a parameterized log so results are reproducible.

Conditional procedures (for example, when isotopic envelopes are poorly resolved) should reference decision rules: what thresholds trigger re-acquisition, what alternative adduct lists are considered, and which secondary experiments are acceptable to resolve ambiguity.

Reviewer records and traceability

Reviewer records complete the packet. Each review entry should state the reviewer identity, date/time, checklist items verified (ion-adduct logic, charge-state consistency, calibration acceptability), and a concise rationale for acceptance or further action. If a reviewer overrides an automated assignment, the packet must include the evidence that supported the override (annotated spectra, comparative reference matches, or orthogonal measurements). Retain immutable snapshots of the accepted dataset (read-only copies of raw files, exported annotated spectra, and a signed processing report) to preserve traceability.

Assembling these components into a searchable, versioned archive helps laboratories demonstrate that peptide annotations rest on documented analytical evidence rather than undocumented interpretation. Structured packets also streamline peer review and inter-lab comparisons.

Not for human consumption. For laboratory research use only.