Clinical supply depot agreements, tracked end to end

The depot contract is signed by procurement, performed by a logistics provider and audited against GxP expectations. Three groups, one document, and usually no shared obligation list.

What obligations sit inside a clinical supply depot agreement?

A clinical supply depot agreement typically carries storage and temperature control duties, excursion notification windows measured in hours, retention sample handling, import and export licence conditions, batch release and quarantine handling, destruction and reconciliation duties, and audit access rights. Most are time-bound and evidence-generating, which makes them obligation management problems rather than clauses to file and forget.

Last updated: September 23, 2026 · Reviewed by the Aavenir Life Sciences & Pharma practice

Key takeaways

  • ✓Excursion notification windows are the most commonly breached term in depot agreements.
  • ✓Depot qualification status expires, and an expired qualification invalidates downstream releases.
  • ✓Import licence conditions belong in the obligation register, not only in the logistics file.
  • ✓Reconciliation and destruction duties generate the evidence a regulatory inspection asks for.

A clinical supply depot agreement is a short document that carries a disproportionate amount of regulatory weight. It governs where investigational medicinal product sits between manufacture and the trial site, under what conditions, with what documentation, and what happens when something goes wrong at two in the morning in a warehouse eight time zones away.

The contract itself is usually handled competently. Procurement negotiates rates and liability, quality reviews the accompanying quality agreement, legal checks the indemnities. What tends to be handled poorly is everything after signature. The commitments inside the agreement are time-bound, evidence-generating and split across three internal functions, and they are usually tracked in a combination of a logistics spreadsheet, a quality system and somebody’s memory.

This datasheet sets out what a depot agreement typically obliges, which of those obligations fail most often, and how to structure a register that clinical supply, quality and procurement can all work from. It assumes the underlying quality agreement exists and is sound, and focuses on making the commitments in both documents visible and owned.

What the agreement actually obliges

Depot agreements vary by region and provider, but the obligation categories are consistent. Each of these generates dated, evidenced duties rather than a one-time acceptance at signature.

  • Storage and environmental control, defined temperature ranges by product, continuous monitoring, calibration of monitoring equipment, and documented mapping of the storage area.
  • Excursion detection and notification, a defined trigger and a notification window to the sponsor, usually measured in hours, followed by investigation and disposition within a longer window.
  • Regulatory authorisations, import and export licences, controlled substance registrations where applicable, and depot qualification status, each with its own expiry and renewal cycle.
  • Product accountability, receipt reconciliation, quarantine handling, release to sites against authorised requests, returns processing and periodic inventory reconciliation.
  • Destruction and record retention, destruction only on documented sponsor authorisation, certificates returned within a defined period, and record retention for a term that usually outlives the agreement.

Read as a list, none of these are surprising. Read as a set of dated obligations with named owners and evidence requirements, they are a substantial tracking burden that most sponsors carry informally. The same structural point applies to CRO and CMO relationships and is why obligation registers have become standard practice in life sciences obligation management rather than a nice-to-have.

Retention obligations outlive the contract

Record retention and, in some jurisdictions, retention sample duties typically survive termination by a number of years defined in the agreement. An obligation register that closes out every commitment when the contract ends will quietly drop exactly the duties an inspection is most likely to test years later.

Where depot obligations fail

Failures cluster in predictable places, and in almost every case the underlying cause is that the duty had a deadline but no owner watching it.

  • Excursion clocks nobody is holding. The depot detects and reports, but the sponsor-side acknowledgement, investigation and disposition each have their own windows that run unmonitored until a quality review finds them missed.
  • Lapsed qualification used anyway. Requalification slips past its due date while shipments continue. The remediation is not a renewal, it is a retrospective assessment of every movement since the lapse.
  • Licence conditions held only in logistics. Import licence quantity limits, expiry dates and product scope sit in a freight file rather than the obligation register, so a licence constraint is discovered at the border.
  • Reconciliation performed but not evidenced. Counts are done and never documented in a form that links back to the contractual requirement, which converts a completed obligation into an audit finding.
  • Destruction without documented authorisation. Product destroyed on a verbal or email approval that does not match the authorisation process the agreement specifies, leaving a gap in the accountability chain.

Standing up a depot obligation register

Step 1, Extract from both documents

Run extraction across the depot agreement and its companion quality agreement together, because the commercial and the regulated duties are deliberately split between them. Extracting one alone produces a register with visible holes, and the holes are usually on the quality side where the audit exposure is highest.

Step 2, Classify by clock type

Separate recurring duties such as periodic reconciliation and monitoring calibration from event-triggered ones such as excursion notification, and from expiry-driven ones such as licence and qualification renewal. Each type needs a different monitoring pattern, and lumping them together produces alerts nobody trusts.

Step 3, Assign a named owner per obligation

Not a function, a person, with a documented deputy. Clinical supply, quality and procurement will each own a slice. The register should make the split explicit so that an unowned obligation is visible as a gap rather than assumed to belong to someone else.

Step 4, Wire evidence to the obligation

Each completed obligation links to the artefact that proves completion: the investigation record, the reconciliation report, the destruction certificate, the renewed licence. An obligation marked complete without an evidence link is an assertion, and inspections test assertions.

Step 5, Set escalation before the deadline

Escalation timing should reflect how long remediation actually takes. A licence renewal needs warning in months, an excursion disposition in hours. Alerts that fire at the deadline itself are notifications of failure rather than controls.

One register for depot and quality commitments

See how depot obligations, owners and evidence links come together for a live trial portfolio.

Book a demo

Multi-depot and multi-country complications

A single-depot trial is a manageable tracking problem. A global trial running through regional depots under different local agreements, with different import regimes and different local qualification requirements, is not, and this is where informal tracking reliably fails. The obligations are structurally similar but the dates, thresholds and authorities all differ, and the sponsor needs a consolidated view of which depots are currently qualified and licensed for which products. Building that view by hand for each monitoring cycle is slow enough that it tends to be done quarterly, which is exactly the interval over which a licence lapse goes unnoticed. The same consolidation problem shows up across sponsor relationships generally, which is why teams increasingly treat depot, CRO and CMO obligations as one register rather than three.

Obligation types and monitoring patterns

The table below maps the recurring depot obligation types to the monitoring pattern each needs and the evidence that closes it. It is intended as a starting structure for a register rather than a complete clause inventory, since specific terms vary by provider and region.

Obligation typeClockTypical ownerClosing evidenceEscalate before
Temperature excursion notificationEvent-triggered, hoursQualityInvestigation and disposition recordHalf the notification window
Depot qualification or requalificationExpiry-driven, annual cycleQualityQualification report and approvalOne quarter
Import or export licence validityExpiry-driven, variableClinical supplyCurrent licence with scope and limitsTwo months
Inventory reconciliationRecurring, periodicClinical supplySigned reconciliation reportOne cycle
Destruction and certificate returnEvent-triggered, daysClinical supply with quality sign-offAuthorisation plus destruction certificateHalf the return window

The depot agreement is not a document that rewards being filed. Its value is entirely in whether the commitments inside it are performed on time and evidenced, and that is a monitoring problem rather than a contracting one. Sponsors that pull depot and quality agreement obligations into one owned register generally find the same thing: the contracts were fine, the performance was mostly fine, and the evidence was the part that had quietly gone missing. The work to close that gap is modest, a structured extraction pass across the agreement set, a clear ownership split between clinical supply and quality, and a discipline of linking artefacts to obligations as they complete. What it buys is the ability to answer a depot question in minutes rather than assembling the answer across three systems while an inspector waits.

For related guidance, see Cold chain excursion clauses: notify, quarantine, dispose, Clinical trial site payment terms: a tracking datasheet and Comparator drug sourcing agreements: control datasheet.

FAQ

Depot agreement questions

What is a clinical supply depot agreement? +
It is the contract between a sponsor or its clinical supply organisation and a depot operator that stores and distributes investigational medicinal product for a trial. It covers storage conditions, handling, local import and export duties, distribution to sites, returns, reconciliation and destruction. It usually sits alongside a quality agreement that carries the GxP-specific expectations, and the two need to be read together.
How is a depot agreement different from a quality agreement? +
The depot agreement is the commercial contract: scope, rates, term, liability, termination. The quality agreement defines the regulated responsibilities between the parties, including who releases, who investigates deviations and who owns documentation. Obligations arise from both, and tracking only one of them leaves a predictable gap at audit. The practical answer is a single obligation register fed by both documents.
Why are temperature excursion terms so often breached? +
Because the notification window is short, often measured in hours rather than days, and the trigger event happens at a warehouse at night or in transit across a time zone. The contractual duty exists but no system is watching the clock. Putting the window into an obligation register with an owner and an escalation path is what turns a clause into a process that actually runs.
What depot obligations expire and need monitoring? +
Depot qualification and requalification status, local import and export licences, controlled substance registrations where applicable, insurance certificates, and personnel training records where the agreement requires them. Each has a date, and an expired one can invalidate the compliance basis of shipments that happened after it lapsed. These are exactly the dates that belong on a monitored calendar.
Who owns depot obligations inside the sponsor organisation? +
In practice ownership is split, with clinical supply owning distribution performance, quality owning deviations and qualification, and procurement owning the commercial relationship. That split is workable as long as each obligation has one named owner rather than a department. Obligations assigned to a function rather than a person are the ones that go unactioned.
What evidence does an inspection expect on depot performance? +
Typically the qualification record, temperature monitoring data with excursion investigations and their outcomes, shipment and receipt documentation, accountability and reconciliation records, and destruction certificates. An inspector is checking that the contracted responsibilities were performed and documented. Obligation records that link to the underlying evidence shorten that conversation considerably.

Depot obligations, visible to clinical supply and quality

Aavenir Obligationflow extracts depot and quality agreement commitments into one monitored register with owners, dates and evidence links.

  • ✓Excursion and notification windows tracked with escalation
  • ✓Qualification and licence expiry monitored before it lapses
  • ✓Standalone or native on ServiceNow