Track outsourced samples through report acceptance

A contract laboratory emails a report on Friday afternoon. Procurement marks the service complete, the laboratory coordinator closes the tracker and production asks whether the batch can move forward. QC then notices that the report refers to a different method revision from the test request. The analytical work may be complete, but the organisation has not established whether it answers the authorised question.

Contract laboratory sample tracking should preserve that distinction. It connects the physical sample journey to a specific analytical request and an accountable review decision. A courier delivery, an invoice and a signed report are useful evidence of different events. None alone establishes that the requested work has been accepted by the commissioning QC team.

This guide describes an operating and software design for outsourced chemical and physicochemical testing. Sampling quantities, test methods and scientific acceptance criteria come from the approved procedures and qualified laboratory personnel.

Give the sample and the test request separate identities

One sample can support several tests. One test can involve several preparations or documented repeat activities. A batch number alone cannot reliably represent these relationships.

Create a sample record linked to its source material or product batch. Create a separate request for each agreed analytical scope. When a sample is divided, retain the parent identity and assign each dispatched portion its own identifier. Record the contract laboratory's accession number when it becomes available; preserve both organisations' references.

The following fields form a useful starting point for a joint QC and IT workshop:

Do not turn every field into mandatory free text. Use controlled identifiers where a master record exists and reserve narrative fields for context that cannot be represented safely by a code. Agree who can correct a mistaken identifier and retain the original value and reason for correction.

Agree the analytical scope before dispatch

The test request should distinguish the intended method from a document attachment that happens to be in an email. Establish how the current approved method and specification are supplied, how the laboratory acknowledges them and who handles a proposed change.

WHO's 2024 laboratory guidance addresses test requests, capability review, sample identification and the resolution of request issues before testing. Its stated scope excludes biological-product and microbiological laboratories; those operations need their relevant guidance. Treat this as an applicable reference for the analytical scope here, not a substitute for Indian requirements or the site's approved procedures. WHO pharmaceutical quality-control laboratory guidance, sections 1 and 6.2.

For the proposed workflow, capture the request version that the laboratory accepted. If the method changes after dispatch, keep the earlier version visible and route the change through the agreed review process. The system should not silently replace the attachment and make it appear that the laboratory always had the new instruction.

Also agree the handling of insufficient sample, damaged packaging, unexpected results, additional work and residual material. A purchase order can reference this arrangement, but the coordinator needs operational access to it while managing an exception.

Use states that expose the next decision

A single “pending” status combines several unrelated problems. Replace it with a sequence that identifies the next responsible party:

1. Request prepared: the proposed scope exists and awaits the required internal review.
2. Ready to dispatch: the authorised request and physical portion are linked.
3. Dispatched: custody has transferred to the recorded transport party.
4. Receipt acknowledged: the laboratory has recorded arrival and any condition issues.
5. Scope accepted: the laboratory has confirmed the agreed work or raised a discrepancy.
6. Report received: a report is available for the relevant internal review.
7. QC review complete: the review outcome and any follow-up are recorded.

These are suggested application states. Map them to the actual procedure rather than adopting their names without discussion. Allow a request to enter an exception state from several points. A damaged sample should not have to progress through “scope accepted” just to reach an investigation queue.

Keep batch disposition separate. QC's acceptance of an outsourced report can contribute to a wider batch decision; it should not automatically trigger release unless the authorised process explicitly supports that transition and its conditions are met.

Follow one split sample across two laboratories

Consider an illustrative sample, S-240, from batch B-610. The approved sampling process supplies 60 g for the outsourced activities in this example. QC allocates 20 g to Laboratory A, 25 g to Laboratory B and records 15 g remaining internally. These quantities illustrate reconciliation only; they are not sampling recommendations.

Laboratory A receives portion S-240-A against request R-401 for an assay. Laboratory B receives S-240-B against request R-402 for a specified impurity test. Each laboratory returns its own accession reference. Both requests retain the parent sample and batch links.

Laboratory A's report passes the internal review. Laboratory B's first report contains an incorrect request reference. The coordinator records the discrepancy and obtains an amended report through the agreed process. The first report remains retrievable and linked to the amendment. QC then reviews the corrected record and the underlying discrepancy before recording its outcome.

At that point, the tracker shows two reviewed reports, not merely two received attachments. Residual-material handling remains a separate task: obtain or record the agreed retention, return or disposal information for each dispatched portion. The internal 15 g balance is independent of whatever remains at the external laboratories.

This structure prevents a common error: closing the parent sample as soon as the first laboratory finishes. Completion is evaluated against the authorised set of requests and required closure tasks.

Design three useful exception queues

Start with queues that someone can actually work through during the day.

Receipt discrepancies include a missing acknowledgement, identity mismatch or reported transport damage. The coordinator establishes the facts; the responsible technical owner decides the effect on the work. A reminder cannot resolve uncertainty about what arrived.

Analytical-scope questions include a method-version mismatch, a request for additional sample or proposed additional testing. Route these to the designated QC contact and record the agreed decision. Avoid letting a commercial approver authorise a technical change merely because they can approve an invoice.

Report-review exceptions include missing references, incomplete commissioned scope, amendments and unresolved analytical questions. Distinguish an administrative correction from an issue that requires scientific investigation. The applicable investigation procedure determines the latter pathway.

For each queue, show age, owner, the precise missing decision and the affected request. “Email sent” is an activity; “method discrepancy resolved by the authorised reviewer” is an outcome.

Choose integration after the records are stable

A controlled register can establish the process at modest volume if access, change history, attachments and review responsibilities are adequately managed. A laboratory information management system becomes more useful when many requests, instruments or sites need reliable shared identities. The LIMS sample workflow guide explores that broader queue design.

An external portal or application interface can reduce rekeying, but first agree the meaning of identifiers and events. Receiving the same report twice should update neither the completion count nor the review outcome twice. A changed report should create a visible amendment, not overwrite the reviewed version.

For document extraction, let software propose report identifiers and references with a link to their source location. Uncertain matches should reach a person. Keep the uploaded original and its relationship to the reviewed record. For upstream data capture, see laboratory instrument integration; for changes in analytical capability, see analytical method transfer.

Prove closure with difficult cases

Test the workflow with a split sample, a duplicate report, an amended report and a laboratory receipt that disagrees with the dispatch record. Confirm that each case reaches the correct owner and that a report awaiting review remains visibly open.

Measure dispatch-to-receipt time separately from accepted-scope-to-report time and report-to-review time. Otherwise, a delay in internal review can look like poor laboratory performance. Define how paused or disputed requests affect each measure and retain those exclusions in the report.

NextEdge Labs can help map these identities and handovers into a bounded integration project. Begin with a representative request and its exceptions so the scope reflects the work that QC and the coordinator must perform.

Summary and next actions

Outsourced sample tracking is complete when the organisation can reconstruct what was sent, what work was agreed, what returned and how the responsible reviewers accepted or challenged it.

• Map one recent request from sampling through report review and residual-material handling.
• Agree sample, portion, request and report identifiers with the external laboratory.
• Assign owners for receipt discrepancies, scope changes and report amendments.
• Pilot the workflow with a split sample and verify that receiving a PDF cannot prematurely close the work.