All blueprints

Clinical supply. Blinded, available, accountable.

Clinical supply management software that keeps one record of each kit, from protocol demand, labels and packaging to depots, sites, temperature, returns and reconciliation, with treatment meaning restricted to authorised roles.

Illustration of a seal beside a sample transport case and study records.
KIT-004812 / one physical chain
Blinded to most. Fully traceable to the authorised few.
01
Packaging
coded unit · status · custody
02
Central depot
coded unit · status · custody
03
Site 014
coded unit · status · custody
04
Patient visit
coded unit · status · custody
05
Return
coded unit · status · custody
Visible identity
KIT-004812
Authorised mapping
Treatment code · product lot · assignment · subject
Blind intact
Packaged → released → shipped → received → assigned → returned → destroyed

Figure 1. Kit KIT-004812 moving from packaging through the central depot, site 014 and the patient visit to return. The visible identity stays coded; the mapping to treatment code, product lot, assignment and subject is restricted to authorised roles.

Summary

The problem
Clinical supply has to keep treatment identity blinded where required while every physical unit stays traceable, correctly labelled, within condition and accountable. Spreadsheets between packaging, depots, sites and the IRT make both harder.
Seal’s approach
Protocol and product versions resolve into kit patterns, packaging batches, labels and coded identifiers. Shipments, excursions, expiry updates, returns and destruction act on exact kits, and treatment meaning is visible only to authorised roles.
What changes
An excursion or label change identifies the exact affected units wherever they are, sites see which kits are blocked without seeing allocation, and study reconciliation shows each difference as an actionable record.
Where to start
One representative kit traced from protocol and product version to destruction, including an IRT retry, a temperature excursion and an emergency unblinding. Book a demo.

1Supply must be blinded and accountable at once.

Clinical trial supply has to satisfy two conditions that pull in opposite directions. Treatment identity must stay controlled and blinded where required, while every physical unit stays traceable, available, correctly labelled, within condition and accountable from packaging to destruction.

Seal connects the protocol and approved product state to kit design, packaging, labels, coded identifiers, depots, sites, shipments, excursions, returns and reconciliation. Supply teams act on the physical chain, and treatment meaning is visible only to the roles that need it.

1.1Why teams choose Seal for clinical supply

When forecasting, packaging, labels, depot stock and the IRT live in separate tools, the connections between them are kept in spreadsheets, and a label change or excursion becomes a hunt for the affected units. Seal keeps those steps on one record of each kit, from protocol version to destruction, and each kit carries the kit-pattern and label versions it was packed with. The affected units are found from the record, wherever they are.

The Clinical Operations blueprint exchanges site activation, enrolment and visit signals with it without collapsing responsibilities: activation can gate shipment, forecasts can update demand, and stockout risk can inform trial operations, without giving every user access to treatment detail.

2The protocol and product state define what to make.

Enrolment assumptions alone do not tell the supply team what to make. Demand also depends on arms, visit schedule, titration, cohorts, countries, site activation, lead times, shelf life and resupply strategy. Seal holds protocol versions and supply assumptions as controlled inputs, and keeps scenario outputs distinct from approved production and distribution instructions. An amendment identifies the visits, kits, labels, forecasts and active inventory it may affect.

The product changes too. An investigational medicinal product can change formulation, strength, manufacturer, packaging, label or shelf life while the study continues, and a comparator or placebo has its own lineage. Seal maintains product and packaging versions with effective scope by study, arm, country and time, and physical inventory keeps the exact version and source lot used. A new approval does not by itself make existing packs equivalent.

The EMA quality-documentation guideline for investigational medicinal products describes the manufacturing, control, packaging and stability information that supports clinical use. Operationally, those approved states have to resolve into the correct physical kit and label without informal interpretation.

3Kit design and packaging account for every component.

Blinded supply may require matching presentation, over-encapsulation, visit or titration kits, comparators and ancillaries. The visible kit identifier supports assignment and accountability without exposing treatment identity. Seal defines the kit pattern (components, quantities, label positions, allowable product versions, country scope and storage) separately from the kits produced from it, and each kit records the actual component lots and pack identifiers used.

Clinical packaging is manufacturing work. Seal creates an executable packaging batch from the approved kit and label definitions, with controlled issue, line clearance, scanning of source lot, version, status and expiry, and reconciliation of printed and coded items through issued, used, rejected, destroyed and returned states. Packaging operators verify the correct coded component without receiving unnecessary treatment meaning.

Every finished kit retains its product or comparator lot, packaging batch, component genealogy, visible identifier, hidden treatment code where applicable, expiry basis and release state.

4Labels resolve from the kit’s context.

Clinical labels vary by protocol, product, visit, country, language, storage, regulatory text and expiry.¹ Copying a master document for each combination turns consistency into a manual review problem. Seal stores approved label content as governed data and resolves the applicable text from the kit context; variable data such as kit number, batch and expiry renders from the source record, and template and printer versions stay controlled.

A reprint requires a reason and preserves the prior output. A label amendment identifies stock not yet packaged, packaged but unreleased stock, depot and site stock, shipments in transit and dispensed or returned units that need assessment.

5The randomisation boundary stays controlled.

An IRT may remain authoritative for subject assignment and treatment allocation, while clinical supply still needs kit numbers, availability, site, shipment, quarantine and dispensing acknowledgement. Seal defines that boundary explicitly. It can create or receive coded kit identifiers and send eligible inventory state without importing unblinded treatment meaning. Requests and acknowledgements are idempotent, so a retry does not allocate or ship the same kit twice, and failed or delayed messages remain visible for reconciliation.

Unblinding is a controlled exception. Emergency or planned unblinding should reveal only what the situation requires, to the authorised person, with a reason and a complete audit history.² The event records the subject or kit, requester, authorisation, time, information revealed and any safety workflow triggered, while supply users who do not need treatment identity continue to see coded inventory. A compromised blind can open a deviation with the affected users, kits and subjects already linked.

6Depots and sites see one physical chain.

Released kits move through depots, couriers, customs, sites, pharmacies and sometimes direct-to-patient channels. Each shipment records its pack-out, units, logger, route, carrier, dispatch, receipt and discrepancies. Site inventory derives from received and acknowledged units, not from a shipment marked delivered in a courier portal. Resupply uses enrolment and consumption signals within lead time, shelf life, country approval and buffer policy, so planners can see why a site is projected to stock out and which action is feasible.

A temperature excursion creates an assessment with the lots, kits, stability basis, exposure and locations attached. Quarantine propagates to the exact units wherever they are, and the decision to release, restrict, relabel, return or destroy updates their usable state. Sites see which kits are blocked and which remain eligible, without seeing allocation.

An expiry extension is an inventory transformation, not a global edit. The approved extension has scope: product and lot, packaging configuration, storage history, markets and protocol. Seal identifies the eligible units and creates controlled relabelling work, and old and new label states remain traceable. The Stability Management blueprint supports the shelf-life decision; clinical supply executes it against real inventory.

7Returns and destruction close accountability.

At the site, kits can be dispensed, partially used, unused, damaged, lost, quarantined, returned or destroyed, and accountability has to distinguish those states without revealing treatment beyond authorised roles. Returned units keep their storage and custody history, and destruction records its method, population, approval, vendor and certificate.

Study reconciliation compares what was packaged, released, shipped, received, dispensed, returned, lost and destroyed. Each difference remains an actionable record rather than an unexplained adjustment made to close a spreadsheet.

8Prove one kit through final reconciliation.

Trace one representative kit from protocol and product version through pack design, packaging batch, label, release, coded identifier, depot shipment, site receipt, assignment acknowledgement, return and destruction.

Exercise a protocol amendment, a label correction, an IRT retry, a damaged shipment, a temperature excursion, a lost kit, an expiry extension, an emergency unblinding and a reconciliation difference. The system is ready when blinded users can control the physical chain and authorised users can reconstruct the kit’s complete identity and history.

References

  1. 1Regulation (EU) No 536/2014, on Clinical Trials (Clinical Trials Regulation). EUR-Lex
  2. 2ICH E6(R3), Guideline for Good Clinical Practice (2025). ICH

AOperating model

Included in this blueprint

  • Study supply model
  • Clinical packaging
  • Controlled clinical labels
  • Blinded kit inventory
  • Depot and site distribution
  • Stability and expiry
  • Excursions and product quality
  • Release and reconciliation

Connected across Seal

BCapabilities

Table B.1. What the Clinical Supply Management blueprint covers. Linked capabilities are blueprints of their own.
CapabilityWhat it covers
Study supply modelTurn protocol versions, arms, visits, countries, sites and supply assumptions into controlled planning inputs and demand scenarios.
Clinical packagingRun kit and pack definitions as packaging batches with material verification, line clearance, labelling, inspection, yields and reconciliation.
Controlled clinical labelsRender approved labels from study, product, country, language, visit, storage and expiry data, with print and reprint history.
Blinded kit inventoryShow coded kits by depot, site and pharmacy, with reservation, quarantine, expiry and availability, without disclosing treatment identity to those who do not need it.
Depot and site distributionRecord pack-out, loggers, routes, carriers, dispatch, receipt and discrepancies for depot, site and direct-to-patient shipments.
Stability and expiryApply approved shelf-life conclusions to the eligible inventory through controlled relabelling and release work, rather than editing dates.
Excursions and product qualityExcursions, damage, loss, complaints and blind compromise start with the affected kits, lots, sites and subjects linked.
Release and reconciliationReconcile each unit from manufacture and packaging through release, shipment, dispensing, return, loss and destruction.

CConnected records

Entity hierarchy
What it records
Kind
Clinical Study
Protocol, treatment arms, visits, countries, cohorts, sites, supply assumptions and approved versions.
entity
Investigational Product
Drug, biologic, comparator, placebo or ancillary product with versions, lots, stability and regulatory scope.
entity
Kit Design
Approved components, quantities, appearance, label positions, country scope, storage and inspection pattern.
entity
Visit Kit Pattern
Reusable blinded kit configuration for a defined protocol visit, country group and treatment presentation.
template
Packaging Batch
Executed packaging and labelling work with issued components, line clearance, inspection, yield and reconciliation.
entity
Blinded Kit
Physical kit with coded identifier, component genealogy, hidden treatment meaning, expiry, location and state.
entity
KIT-004812
Released coded kit with product genealogy, label, shipment, site, assignment, return and final accountability.
record
Clinical Label
Controlled study, country, language, product, visit, storage and variable content rendered for a kit.
entity
Supply Shipment
Depot or site movement with kits, pack-out, logger, route, custody, receipt, discrepancies and condition.
entity
Site Inventory
Acknowledged physical kits at a depot, site, pharmacy or direct-to-patient location with usable state.
entity
Kit Accountability
Assignment, dispense, return, loss, damage, quarantine, reconciliation and destruction history.
entity
IRT Assignment Boundary
Controlled exchange of coded kit availability, reservation, assignment and acknowledgement.
entity
Figure C.1. Record types, templates and the relationships between them in this blueprint.

DQuestions and answers

What is clinical trial supply management software?

Clinical trial supply software controls investigational product versions, packaging and labelling, blinded kit identifiers, depots and sites, shipments, temperature, expiry, assignment boundaries, returns, destruction and final accountability. It connects protocol demand to the physical product chain without exposing treatment identity unnecessarily.

How is clinical trial supply different from CTMS or IRT?

CTMS governs trial operations such as sites, enrolment, visits and oversight. IRT commonly governs randomisation and treatment assignment. Clinical supply governs the manufactured and packaged product, coded kits, labels, inventory, shipments, condition, expiry, returns and reconciliation. Seal defines controlled boundaries among those responsibilities.

Can Seal preserve the treatment blind?

Yes. Visible kit identifiers and physical supply state are separated from hidden treatment meaning through role-based access and controlled integrations. Packaging and supply users can verify and move the correct coded unit without receiving information they do not need.

How are country-specific clinical labels generated?

Approved content is governed by study, product, country, language, visit, cohort, storage and regulatory scope. Variable data comes from the kit record. Template and printer versions, approvals, print events, scans, corrections and reprints remain traceable.

Can Seal integrate with an IRT or randomisation system?

Yes. The boundary can exchange coded kit availability, reservation, assignment, replacement and acknowledgement while the IRT remains authoritative for randomisation. Requests are designed to be reviewable and idempotent so retries do not create duplicate allocation or movement.

How are clinical supply temperature excursions handled?

The shipment or storage event identifies the exact kits, product lots, exposure window, route, packaging configuration, destination and stability basis. Affected units can be quarantined while an assessment decides whether to release, restrict, relabel, return or destroy them.

How does expiry extension and relabelling work?

The approved stability conclusion defines eligible product lots, packaging configurations, storage histories, countries and inventory population. Seal creates controlled relabelling work for eligible units, preserves old and new label states, and requires inspection and release before availability changes.

How are returned and destroyed kits reconciled?

Each unit’s packaged, shipped, dispensed, returned, lost, quarantined and destroyed states contribute to accountability. Differences remain visible events with investigation and disposition, rather than adjustments made only to close a total.

Can Seal support direct-to-patient clinical supply?

Yes. The configured model can represent authorised destination, protected information, pharmacy or depot handoff, pack-out, courier, receipt, condition and accountability while applying the study’s country, privacy, blinding and distribution rules.

What should a clinical supply implementation prove first?

Trace one representative kit from protocol and product version through design, packaging, label, release, coded identifier, depot and site shipment, assignment acknowledgement, return and destruction. Include an amendment, excursion, IRT retry, loss, expiry update, unblinding and reconciliation difference.

See your process in Seal.

Bring a procedure or a recurring problem. See how your team can use Neil to build the workflow, investigate the results and improve the next version.

Book a demo