Contract laboratory LIMS.

A contract testing laboratory does not run one internal QC programme. It runs many clients’ quality agreements, methods, specifications, priorities and turnaround promises through shared analysts, instruments, rooms and inventory.

Seal keeps each client order as one service record, from quote and expected shipment through testing, QA approval, certificate, retains and invoice. The laboratory works from complete GMP evidence; each client sees only what its agreement allows.

1The client agreement governs the work.

The quality agreement defines authorised contacts, products, services, methods, specifications, OOS communication, subcontracting, retain policy, turnaround, reporting, record retention and approval responsibilities.¹ In Seal those terms are configuration the work runs on. Each sample inherits the effective quality and service rules of its client’s agreement instead of relying on an account manager’s memory.

Each client can have its own System, holding its products, batches, specifications, methods, contacts, report templates and billing terms, and users are assigned roles per System. Laboratory staff see what their System roles require, and client users see only the configured portal page and the records shared with them. Verify the boundary for each implementation with test users before live client access.

Compendial methods and shared laboratory resources stay centrally governed, while client-specific applicability stays separate. Client-supplied, compendial and transferred methods carry ownership, approved version, site applicability, calculations and change-notification rules; specifications carry product, stage, market, limits, units and rounding. The sample resolves the correct versions at receipt and at execution, and a later revision does not rewrite the basis of an in-progress or reported test.

1.1Why teams choose Seal for contract testing laboratories

Contract laboratories usually run a LIMS for testing, a CRM or spreadsheet for quotes and client terms, a separate portal for status and a finance system for billing, joined by people who remember each client’s agreement. Seal makes the client’s agreed terms configuration that each sample inherits, and runs the order from quote to invoice on one service record with a deliberate boundary between internal evidence and what the client sees. When a client changes a method or specification, the change takes effect as a version for new samples, while completed work keeps the terms it was tested under.

2Settle the scope before the sample arrives.

Quotes are built from controlled service definitions: tests, panels, preparations, method transfers, stability pulls, rush service, storage and data packages. A quote records its assumptions, volumes, turnaround basis, exclusions and approval. Accepted lines become service orders without rekeying, and a commercial revision cannot silently change an active GMP requirement.

Clients then submit expected samples with product, batch, tests, specification, quantity, storage, hazard, timepoint, priority and purchase order. The laboratory reviews readiness before receipt. A missing method, an expired agreement, an unapproved specification or an insufficient quantity surfaces while the shipment can still be corrected.

3Accessioning reconciles expectation with what arrived.

Receipt records the carrier, seal, package condition, temperature evidence, custody, containers, labels, quantity and discrepancies, and reconciles expected against received identities before login. Quarantine, rejection, conditional acceptance and client clarification each preserve the material state. An accession number does not by itself permit testing.

From there, the parent sample, aliquots, composites, preparations and reserve portions form a physical genealogy. Each transformation records source, quantity, operator, equipment, time, location and what remains. The system can calculate the quantity a panel needs and protect retain and repeat-test reserves, so an insufficient sample prompts an accountable decision rather than silent overconsumption.

4Plan capacity at the level of the test operation.

Turnaround depends on analyst authorisation, instruments, rooms, incubations, standards, reagents, columns, sequence capacity and review, not only on a due date. Seal schedules at that level, grouping compatible preparations and sequences while preserving client priority and cross-contamination controls. Rush work records who approved the displacement and which commitments moved.

Dispatch checks method authorisation, training, instrument qualification and calibration, standards, reagents and sample status, and names the specific missing prerequisite. Work queues show ready, waiting, blocked, in-review and client-hold states with a reason and an owner, so ageing does not hide inside a broad “open” status.

Instrument sequences are created with governed sample, method and standard identifiers. Returned files reconcile against planned injections, the audit trail and calculations, and per-client Systems keep one client’s sequence or attachment out of another client’s report.

5Review, OOS communication and release follow the agreement.

The analyst completes execution and initial checks. Technical review assesses source data, calculations, system suitability, method adherence, audit trails and result validity. QA or the authorised report reviewer then evaluates the specification, exceptions, OOS and report completeness. Role assignment follows the quality agreement, and each electronic signature records its meaning and the version signed.²

An OOS or atypical result can require client notification within an agreed period while the laboratory assessment continues. Seal records the notification content, audience, time, acknowledgement, shared evidence and any authorisation for additional work. The laboratory investigation keeps its raw evidence and scientific control; client decisions on manufacturing information, resampling and product impact remain linked but accountable to the client.

6The client sees a deliberate external state.

Certificates are generated from approved evidence. Controlled templates set client identity, sample and batch fields, methods, specifications, results, units, qualifiers, approvals and legal text, and only approved reportable results enter the certificate. A reissue retains its reason, the superseded version, changed fields, recipients and delivery history. Raw-data packages can be assembled under client-specific rules.

Through a configured portal page, clients see expected shipments, receipt discrepancies, status, questions, approved results, reports and invoices as their agreement allows. Internal hypotheses, personnel notes and other clients’ information stay out of external status fields. Approvals, clarifications, sample instructions, requests for additional work and downloads become attributable records on the service order.

Work continues after reporting. Remaining samples and retains keep their location, quantity, storage conditions, excursion history, ownership and disposal authorisation, and a return or transfer preserves custody. Stability pulls are scheduled against the effective protocol with chamber, interval and timepoint lineage.

7Keep commercial state apart from GMP evidence.

Invoice evidence reconciles quoted services, received samples, completed or cancelled tests, rush fees, storage, shipping, subcontracted work and approved non-billable repeats. Billing status never alters laboratory evidence or releases a report outside the approved path.

Turnaround metrics keep the waiting reason. The laboratory measures request to receipt, receipt to login, ready to start, execution, technical review, QA release and delivery, with client hold, missing information, instrument downtime, OOS and internal queue kept distinct. On-time delivery is measured against the promised basis and approved revisions, and metrics can be segmented without exposing one client’s information to another.

8Prove one client order from quote to invoice.

Follow one multi-test request through quote, expected shipment, a temperature discrepancy, conditional accession, aliquoting, method and specification resolution, scheduling, instrument execution, OOS notification, an approved retest, QA review, certificate, portal delivery, retain storage and invoice.

Include a method-version conflict, insufficient quantity, a rush reprioritisation, a subcontracted test, a report correction, an unauthorised client access attempt and a sample-return request. The model is ready when the client sees a coherent service and the laboratory retains complete GMP control.