Contract laboratory LIMS. One sample operation, many client boundaries.

A contract testing laboratory does not run one internal QC program. It runs many client quality agreements, methods, specifications, sample identities, priorities, reporting rules, confidentiality boundaries, and turnaround promises through shared people, instruments, rooms, and inventory.

Seal connects commercial intake to GMP execution. The quote, client request, shipment, accession, sample and aliquots, methods, specifications, capacity, raw data, results, OOS communication, QA approval, certificate, portal delivery, retains, destruction, and invoice evidence remain one service record.

The client and laboratory define authorized contacts, products, sites, services, methods, specifications, data exchange, change notification, deviations and OOS communication, subcontracting, retain policy, turnaround, reporting, record retention, and approval responsibilities.

Seal makes those terms executable. A sample inherits the effective quality and service rules instead of relying on account-manager memory.

Tests, panels, sample preparations, method transfers, stability pulls, rush service, storage, shipping, disposal, data packages, and project work have controlled scope and pricing logic. A quote records assumptions, volumes, turnaround basis, exclusions, client inputs, validity, and approval.

Accepted lines become service orders without rekeying scope. Commercial revision cannot silently change an active GMP requirement.

Each tenant has products, materials, batches, specifications, methods, contacts, report templates, billing terms, and portal access. Shared compendial methods and laboratory resources can remain centrally governed while client-specific applicability and reporting stay separate.

Access control applies to records, search, exports, dashboards, notifications, and attachments. Laboratory personnel see only what their role and assignment require; client users see only approved external views.

Clients create or transmit expected samples with product, batch, tests, specification, method, quantity, hazard, storage, stability timepoint, priority, purchase order, and instructions. The laboratory reviews readiness before physical receipt.

Missing method, expired agreement, unavailable capability, insufficient quantity, or unapproved specification becomes visible while the shipment can still be corrected.

Receipt records carrier, seal, package condition, temperature evidence, custody, date and time, containers, labels, quantity, storage, hazards, and discrepancies. Expected and received identities are reconciled before login.

Quarantine, rejection, conditional acceptance, and client clarification preserve the material state. An accession number does not imply that testing may begin.

The parent sample, containers, composites, preparations, dilutions, extracts, plates, and reserve aliquots form a physical genealogy. Each transformation records source, quantity or volume, units, operator, equipment, conditions, time, location, and remaining material.

The system predicts required quantity across panels and protects retain or repeat-test reserves. Insufficient sample prompts an accountable choice rather than silent overconsumption.

Client-supplied, compendial, laboratory, and transferred methods carry ownership, approved version, site applicability, instrument requirements, calculations, data-review rules, and change notification. Specifications retain product, stage, market where needed, tests, limits, units, rounding, and reporting.

The sample resolves the correct method and specification at receipt and at execution. Later revisions do not rewrite the basis of an in-progress or reported test.

Turnaround depends on analyst skills, instruments, rooms, incubations, preparations, standards, reagents, columns, sequence capacity, review, and dependencies—not only a due date.

Seal schedules work at the operational 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 verifies method authorization, training, instrument qualification and calibration, software configuration, environmental state, standards, reagents, columns, and sample status. A scheduler can see the specific missing prerequisite.

Work queues show ready, waiting, blocked, in progress, pending review, and client-hold states with reason and owner. Aging does not hide inside a broad “open” status.

Sequences can be created with governed sample, method, standard, and processing identifiers. Returned files and results reconcile against planned injections, actual acquisition, audit trail, calculations, and source status.

The interface prevents one client's sequence or attachment from being exposed through another client's portal or report.

The analyst completes execution and initial checks. Technical review assesses source data, calculations, system suitability, method adherence, audit trails, and result validity. QA or authorized report review evaluates specification, exceptions, OOS, change, and report completeness.

Role assignment follows the quality agreement. Electronic signatures identify meaning and record version; reassignment and delegation remain traceable.

An initial OOS or atypical signal can require client notification within a defined clock while the laboratory assessment continues. Seal records notification content, audience, time, acknowledgement, shared evidence, and authorization for additional work.

The laboratory investigation retains raw evidence and scientific control. Client decisions, manufacturing information, resampling, and product impact remain related but accountable to the correct organization.

Report templates control client identity, sample and batch fields, methods, specifications, results, units, qualifiers, dates, comments, approvals, and legal text. Only approved reportable results enter the certificate.

Reissued reports retain reason, superseded version, changed fields, recipients, and delivery history. Raw-data packages, chromatograms, audit trails, and method attachments can be assembled under client-specific rules.

Clients can see expected shipments, receipt discrepancies, status, questions, approved results, reports, invoices, and authorized downloads according to agreement. Internal hypotheses, personnel notes, or other clients' information never leak through broad status fields.

Portal actions—approval, clarification, sample instruction, additional work, download, and acknowledgement—become attributable records tied to the service order.

Remaining samples and retains have physical location, quantity, condition, storage rules, expiry or destruction date, freeze-thaw or excursion history, ownership, and disposal authorization. Client return or transfer preserves custody.

Stability programs create scheduled pulls and testing against the effective protocol while preserving chamber, interval, timepoint, and report lineage.

Invoice evidence reconciles quoted services, received samples, completed or cancelled tests, rush fees, storage, shipping, external work, repeats, client-requested additions, and approved non-billable failures.

GMP decisions remain independent of billing status. Commercial disputes cannot alter laboratory evidence or release a report outside the approved path.

The laboratory measures request-to-receipt, receipt-to-login, ready-to-start, execution, technical review, QA release, and delivery. Client hold, missing information, instrument downtime, OOS, subcontracting, and internal queue remain distinct.

On-time delivery includes the promised basis and approved revisions. Capacity and quality metrics can be segmented without exposing one client's information to another.

The first implementation should follow one multi-test client request through quote, expected shipment, temperature discrepancy, conditional accession, aliquoting, method and specification resolution, capacity scheduling, instrument execution, OOS notification, approved retest, QA review, COA, portal delivery, retain storage, and invoice.

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