Lab Result Deviation Evidence Packet

The problem

Laboratory deviation records are often scattered across disparate instrument logs, worksheets, and audit trails. Manually organizing this evidence into a traceable investigation packet is time-consuming and prone to overlooking critical data integrity gaps.

What it does

• Builds a structured source register from specifications, raw instrument data, and analyst notes.
• Maps sample identities across chain-of-custody, receipt, and preparation records to identify discrepancies.
• Separates original observations from recalculated results, retests, and resamples to preserve data integrity.
• Chronologically links analytical controls, system-suitability results, and equipment alarms to specific results.
• Flags gaps such as unsupported hypotheses, missing audit trails, and unauthorized retests for technical review.

Why this beats prompting it yourself

This skill enforces strict regulatory-style boundaries, ensuring that hypotheses are never conflated with confirmed causes. It maintains a neutral stance that prevents the agent from making unauthorized validity decisions or disposition claims that could compromise a quality investigation.

Use cases

• Preparing a source-indexed packet for internal quality assurance or technical review.
• Reconstructing a data trail when audit logs show reintegration or reprocessing.
• Organizing evidence when a laboratory hypothesis is presented as a confirmed root cause.
• Mapping batch impact across shared instruments, materials, and analysts.

Known limitations

Requires all records to be supplied via file or Read tool. Cannot determine result validity, assign root cause, or assess public health risks.