Aliquot tracking and chain of custody are related but distinct LIMS capabilities. Aliquot tracking records how a specimen is split into derivatives and which tests or storage events apply to each child record. Chain of custody records who held a specimen or aliquot, when, where, and for what purpose. A system can document parent-child lineage without a defensible custody log, and a custody form can exist without automated aliquot hierarchy. The practical question for a laboratory is therefore not whether a LIMS "has" these features, but which events it captures, how it links them, and whether the resulting record can be reviewed as a continuous sequence. Source documentation shows that the required depth varies by setting: a public health laboratory procurement specification, a federal fitness-for-duty rule, a forensic resource guide, and a biobank best-practices document each emphasize different controls. Vendor material describes one commercial implementation, but those claims should be read as product documentation rather than independent validation.

What the source documents actually require

The NCI Best Practices for Biospecimen Resources frames tracking as an informatics requirement tied to accreditation. It states that a well-defined tracking system is a requirement by accrediting agencies and that a global unique identifier may, where appropriate, support linking analytical datasets to a research participant or specific samples [1]. The same document specifies that biospecimen identifiers should be firmly affixed, legible to humans and machines, and durable under planned storage [1]. It also directs that retrieval date, time, temperature deviations, and freezer damage should ideally be recorded as part of an automated LIMS [1]. These are biobank-oriented controls: they prioritize durable physical labeling, identifier privacy, and storage-event capture over courtroom-style custody narratives.

The Alaska State Public Health Laboratories specification is more prescriptive about custody as a workflow object. It requires the LIMS to track and document custody of the clinical specimen from receipt to disposal, storage, or return to submitter, and to track the clinical specimen and its associated aliquots, their locations, and all lifecycle steps [2]. A separate requirement states that the LIMS must track aliquot creation and hierarchy, including what tests were performed on which aliquot [2]. The specification also requires digital signatures of all staff who handled the specimen or its aliquots [2]. This document treats aliquot hierarchy and custody as parallel requirements within a single preanalytical workflow, not as interchangeable terms.

Custody as a legal record versus an operational log

10 CFR 26.159 shows a stricter, rule-based version of custody for HHS-certified laboratories in fitness-for-duty programs. The rule requires laboratory personnel to use aliquots and laboratory internal chain of custody forms when conducting initial and confirmatory tests, while the original specimen and original Federal CCF remain in secure storage [4]. Each time a specimen is handled or transferred within the laboratory, personnel must document the date and purpose on the chain of custody form, and every individual in the chain must be identified [4]. Authorized technicians are responsible for each urine specimen or aliquot in their possession and must sign and complete chain of custody forms as they are received [4]. Here the aliquot is not merely a derivative record; it is an object whose possession creates a documented responsibility.

The forensic LIMS resource guide from the National Institute of Justice describes custody transfer as a system capability rather than a paper form. It states that the LIMS should be able to transfer custody of one or more items at one time, manually as a list or using scanning equipment with printed barcodes or RFID [6]. The guide also describes records of chain of custody associated with submitted items, with the ability to transfer or store evidence within and between agencies [6]. This framing emphasizes batch transfers and inter-agency movement, which differs from the single-donor, form-centric sequence in 10 CFR. A laboratory evaluating systems should ask whether custody events are modeled as individual sign-offs, batch transfers, or both.

A suggested validation scenario for aliquot custody

A laboratory could validate the combined workflow with a single accession split into three aliquots. In the scenario, aliquot A proceeds to testing, aliquot B is stored, and aliquot C is transferred to a second analyst. The validation would check that the LIMS records the parent accession, creates three child records with distinct identifiers, logs the storage location and timestamp for aliquot B, and captures the handler identity and purpose for the transfer of aliquot C. It would then amend a result on aliquot A and confirm that the original value and reviewer identity remain visible in the audit history. This scenario is a suggestion for internal testing, not a claim that any named product has passed such a test.

The scenario should also test failure paths. A custody transfer attempted without a required recipient identity should be rejected or flagged. An aliquot moved to a location without a recorded position should generate a warning. A report generated for the accession should list custody events in chronological order without manual transcription. These checks map to documented requirements: the Alaska specification's digital signature and location tracking [2], the NCI guidance on retrieval date and time [1], and the vendor's append-only audit description [3]. The value of the scenario is that it forces a laboratory to define which events are mandatory before evaluating any system.

How one vendor documents aliquot lineage and audit history

LIMS IQ's chain of custody and audit trail module documentation describes custody transfers with handler, timestamp, and location details, and states that edits, approvals, and aliquot lineage are kept in one reviewable audit history [3]. The vendor says the audit trail is append-only: events are written, never edited or deleted in place, and corrections are stored as new entries that reference the original [3]. It also describes parent-child lineage tracking for aliquots, slides, and downstream derivatives back to the originating specimen [3]. These are vendor claims about the product's design, not independently verified behavior. They are useful as a checklist of what a commercial system may offer, but they do not establish that the implementation satisfies any specific accreditation or regulatory requirement.

The vendor documentation also names intended workflows: forensic toxicology, employer drug testing programs, court-ordered testing, and chain-of-custody-required clinical work [3]. It states that custody events such as collection, sealing, transfer, receipt, and storage are captured with collector and recipient identity at each step [3]. A case-level report can list each custody event, personnel, timestamps, and notes [3]. This is a product-level description of event granularity. A buyer comparing this to the Alaska specification would still need to verify whether the system can link demographic data to custody, integrity, handling, and storage parameters as that specification requires [2]. Vendor documentation answers the "what is captured" question but not the "does it meet our procurement terms" question.

Aliquot workflow mechanics in a research LIMS

Illumina's Clarity LIMS documentation for version 6.2 describes aliquot creation as a step-level action. A user can create multiple aliquots of each sample, move one aliquot to the next step, and store the others for later use [5]. The interface allows creating the same number of derivatives for all samples or a different number for each individual sample [5]. Stored aliquots can later be resumed by searching for the sample, selecting an aliquot, and confirming the step [5]. This is a workflow-oriented model: the aliquot exists to support parallel processing and deferred use, not primarily to document custody. The documentation is marked for research use only and not for diagnostic procedures [5].

The contrast between Clarity LIMS and the Alaska specification is instructive. Clarity LIMS documents aliquot creation and storage as a lab-view operation, while the Alaska specification requires aliquot hierarchy to be linked to tests performed and to custody records [2]. A research laboratory may need only the former; a public health clinical laboratory may need both. The source documents do not state that Clarity LIMS lacks custody features, only that the cited aliquot documentation does not describe them. This is an unresolved question for any comparison: absence from a help page is not evidence of absence from the product.