Health, Education & Government Life Sciences & Pharma Cell & Gene Therapy

Sample Chain of Custody

Regulated development and commercialization journeys where clinical, quality, and market access align.

Example organizations in this space: World Courier PCI Pharma Services Almac Group BioMatik

This interactive experience is the shipped product itself — the same application code customers run in production, mounted read-only in your browser over a real sample journey. Not a video, not a mockup: because the demo and the product are one codebase, it can never drift from the real thing.

Inside this journey
  1. Outcome Discovery

    Align on sample volumes, site distribution, temperature profiles, prior failures, stakeholders, and measurable success signals.

    Discovery Questions

    Where success begins: defining a shipment you can trust

    • How do you currently define a successful sample shipment for a typical study? Options: Arrives at lab within target window, Maintains temperature within spec, Barcode and chain-of-custody complete, No regulatory findings on receipt, Other
    • In a typical month, how many clinical shipments does your team move that require temperature control? Options: 0-50, 51-200, 201-1,000, 1,001-5,000, 5,000+
    • Tell me about the mix of collection types you handle, for example frozen plasma, room-temperature swabs, or cryopreserved cells. Options: Frozen plasma/serum, Cold chain refrigerated (2-8°C), Frozen with dry ice, Ambient stabilized kits, Cryopreserved/ultra-low
    • Which single metric would make you call a pilot a clear success and accelerate contracting? Options: % shipments within temp spec, Time-in-transit target met, Complete chain-of-custody records, Zero sample rejections at lab, Other

    Where the current process trips you up

    • If one critical handoff failed tomorrow, how certain are you you could reconstruct chain of custody and recover the sample's value? Options: Completely certain, Mostly certain with effort, Uncertain, Not possible
    • Describe the last time a temperature excursion occurred in a study you run, what caused it, and what the downstream impact was.
    • Which parts of the transfer chain cause the most friction: site packing, local courier pickup, international transit, or receiving lab logging? Options: Site packing, Local courier pickup, International transit, Receiving lab logging, Multiple of the above
    • Who on your team currently becomes the escalation owner when a shipment is out of temperature, and how long does it take to get an initial response? Options: Clinical supply lead, QA/Compliance, Logistics coordinator, Lab operations, No single owner
    • Which single failure mode would make you stop a deployment immediately, for example repeated barcode mismatches or systemic temperature excursions? Options: Systemic barcode mismatches, Repeated temperature excursions, Missing chain-of-custody records, Regulatory nonconformance at receiving lab, Other

    Who needs to be in the room when problems surface

    • Who are the decision makers and approvers that must sign off on a change to your sample logistics process? Options: Clinical supply director, QA/Regulatory lead, Lab director, Procurement, IT/Integration owner, Other
    • When a sample-related regulatory question arises during a filing, who on your side typically responds to auditors and how much lead time do they need? Options: QA/Compliance within 24 hours, Lab director within 48 hours, Clinical operations within a week, Depends on case
    • Which reporting cadence helps your leadership feel confident, real time alerts, daily digest, or weekly summaries? Options: Real time alerts, Daily digest, Weekly summary, Custom dashboard with filters
    • If the pilot demonstrates the target metric, who can sign commercial terms and how fast could they approve a vendor? Options: Clinical supply director within 1 week, Procurement within 2-4 weeks, Requires executive review 4+ weeks, No clear authority

    The sample details that actually matter

    • Which site distribution best describes your upcoming program, number of sites and spread across regions? Options: Single country, <50 sites, Multi-country, 50-200 sites, Global, 200-1,000 sites, Highly distributed with remote locations
    • How many different temperature profiles do you routinely manage across your studies, for example 2-8°C, frozen, ambient stabilized? Options: One profile, Two profiles, Three profiles, More than three
    • Describe your kit provisioning model, who prepares kits, where they are stored, and how inventory is tracked.
    • Which barcode identity checks do you currently require at collection and at receipt, for example 1D barcode scan, 2D matrix, and human read confirmation? Options: 1D barcode scan, 2D matrix scan, Barcode plus human read, RFID, No standard today
    • Which of these constraints would kill a pilot for you: inability to monitor temperature in real time, lack of API for LIMS, or no named courier lanes? Options: No real-time temperature monitoring, No LIMS/CTMS API access, No dedicated courier lanes, None of these would kill it

    Stories that reveal how recovery really works

    • When a shipment has failed in the past, what sequence of steps did your team follow to contain the issue and what took the most time?
    • Who typically owns communications to study sites about sample issues, and how do sites prefer to receive those notifications? Options: Clinical operations email, Site portal notification, Phone/SMS to site coordinator, Local CRA
    • If an exception event required sample replacement, what is your acceptable replacement window before data quality is compromised? Options: 24 hours, 48 hours, 72 hours, Depends on sample type
    • Tell me about one recovery that worked well and one that did not, and what separated the two outcomes.

    What your current options look like and why they might stick

    • Which alternatives are you actively evaluating right now, including incumbent providers, internal build, or other vendors? Options: Incumbent logistics provider, Internal operations build, New third-party vendor, Regional courier partners, Other
    • What would have to be true about your current approach for you to keep it rather than change vendors, for example cost parity, fewer audits, or better coverage? Options: Cost parity, Improved audit readiness, Better geographic coverage, Faster delivery times, Existing contractual commitment
    • Has anyone on your team proposed solving this without an outside vendor, and if so what level of internal effort and timeline did they estimate? Options: Yes, small internal pilot 1-3 months, Yes, significant program 6-12 months, No internal proposal, Unsure
    • Which option would be a showstopper if it stayed true, for example incumbent refuses SLA changes or internal team lacks resources? Options: Incumbent refuses SLA changes, Internal team lacks resources, No single stakeholder owns decision, Regulatory constraints prevent change

    Practical readiness: systems, people, and approvals

    • Which core systems must integrate for success, and do those systems provide APIs or file-based exports we can use? Options: LIMS with API, LIMS with flat file, CTMS with API, ERP/procurement, No integration needed
    • Who owns the API or integration work on your side and how many dedicated FTEs can they commit during pilot integration? Options: IT integration team, 1-2 FTEs, LIMS team, 1 FTE, No internal owner assigned, External integrator
    • Is the sample metadata needed for chain-of-custody clean and accessible, for example patient IDs, visit numbers, collection timestamps, and site identifiers? Options: Yes, fully accessible, Partially available with cleanup, Not currently available, Unsure
    • Which regulatory approvals or legal reviews could gate a pilot start, such as IRB approvals, data transfer agreements, or import permits? Options: IRB/ethics approvals, Data transfer agreement, Import/export permits, No known gates, Other
    • If integrations or approvals add more than four weeks to the schedule, would that rule out a Q4 pilot for you? Options: Yes, unacceptable delay, Acceptable with mitigation, Depends on criticality

    Acceptance signals and the decision that follows

    • What measurable acceptance criteria must the pilot meet for you to move to enterprise rollout, for example 95% shipments within temperature spec and full LIMS field mapping? Options: % shipments within temp spec, Complete LIMS/CTMS integration, Zero sample rejections, Courier lane coverage verified, Other
    • If the pilot proves those acceptance criteria, what is the earliest your organization could complete contracting and begin phased rollout? Options: Immediately within 1 week, 2-4 weeks, 1-2 months, 3+ months
    • Which commercial or compliance concern would block you from moving forward even if pilot metrics are met, for example unresolved data residency or unacceptable SLA terms? Options: Data residency, SLA terms, Pricing, Insurance/liability, Other
    • Who needs to sign final acceptance and what single action would accelerate them to sign within a week? Options: Clinical supply director, Procurement, QA/Regulatory, Executive sponsor
    • Describe the next three practical steps from your perspective that would move this from conversation to an executed pilot.
  2. Solution Experience

    Walk through how operational processes, temperature monitoring, barcode identity checks, and exception handling will operate in the buyer's real workflows and failure scenarios.

    Solution Experience

    • Solution Experience Session
    • You confirm the demonstrated workflows remove the rework and lab rejections you described.
    • Confirm the current state and its cost to your team
    • Deliver a site-level operational runbook for the two reviewed scenarios showing handoffs, barcode checkpoints, temperature thresholds, and exception playbooks within five business days.
    • You confirm the recovery procedures produce the audit evidence needed for regulatory review.
    • End-to-end operational walkthrough using your workflow
    • Provide shipment logs, prior incident reports, and a sample of your LIMS field mappings for the two pilot sites before the pilot kickoff.
    • Confirm pilot sites and a two-week window for scheduled proof shipments so the seller can prepare monitoring and reporting.
    • Failure scenario 1, temperature excursion proof
    • You agree on pilot acceptance criteria and the remaining integration evidence required before decision.
    • Failure scenario 2, identity or mislabeling proof
    • Validate integrations, alerts, and acceptance criteria
    • Forced validation checkpoint
    • Agree next evidence steps and pilot criteria
    • Solution Experience Session
    • Solution Experience Deck
    • Solution Brief: Operational Runbook and Acceptance Criteria
    • meeting
    • slides
    • document
  3. Solution Scope

    Define global courier coverage, kit provisioning, temperature-control requirements, barcode verification steps, LIMS/CTMS integrations, responsibilities, and acceptance criteria.

    Scope Configuration

    • Provide pre-barcoded specimen collection kits
    • Deploy validated temperature-controlled packaging solutions
    • Execute global temperature-controlled sample shipments
    • Provision temperature loggers and deliver monitoring data
    • Continuous temperature monitoring with excursion alerting
    • Capture barcode identity verification at every handoff
    • Digital chain-of-custody records and audit package delivery
    • Central laboratory receiving, accessioning, and sample logging
    • Biorepository cold storage, inventory, and controlled retrieval
    • LIMS and CTMS integration and status synchronization
    • Customs-ready import/export documentation and clearance filings
    • Exception handling: recovery, quarantine, and rerouting services
    • Regulated sample disposition and certificate of destruction

    Scope Questions

    Provide pre-barcoded specimen collection kits

    • How many distinct kit SKUs and part numbers will you require for the program (e.g., PKG-001 blood tube kit, PKG-002 urine kit)?
    • Which barcode symbologies must the pre-barcoded labels use for downstream lab ingestion (e.g., GS1-128, Code 128, QR, UUID)? Options: GS1-128, Code 128, QR, UUID, Other
    • List the label data elements that must be pre-printed on each kit (for example: subject ID, visit number, collection date/time, kit lot, kit expiry).
    • Do you require pre-assembled consumables or cold packs inside the kit (for example: gel packs pre-conditioned to 2-8°C, desiccant, cryovials)? Options: Yes, No
    • Who in your team will approve final kit artwork and batch lot release (provide role/title that signs the kit lot release certificate)?
    • Specify expected monthly kit consumption and per-site buffer stock level (example: 200 kits/site/month with 50-kit safety stock).

    Deploy validated temperature-controlled packaging solutions

    • Which target temperature profile must the packaging validation cover for your samples (choose the profile used for validation testing, for example 2-8°C, -20°C, or -80°C)? Options: 2-8°C, -20°C, -80°C, Ambient, Custom
    • Indicate the maximum transit duration per shipping lane the packaging must maintain the target temperature for (for example: 48 hours, 72 hours, 120 hours). Options: <24 hours, 24-48 hours, 48-72 hours, 72-120 hours, >120 hours
    • Describe the validated test condition you require for packaging approval (for example: payload mass, ISTA-style profile, external ambient extremes, pre-conditioning steps).
    • Which insulation or refrigerant types are acceptable for your study kits (for example: phase-change material rated to hold 2-8°C, dry ice with validated sublimation profile)? Options: Phase-change material (PCM), Gel/ice packs, Dry ice, Vacuum insulated panel, Other
    • What acceptance criteria will confirm packaging validation for your temperature profile (for example: maintain 2-8°C for 72 hours with no excursions outside ±2°C and internal logger trace attached)?
    • Provide the expected payload configuration to validate (example: number of vials, total sample mass, packaging dimensions and weight).

    Execute global temperature-controlled sample shipments

    • Which origin and destination lanes must be covered in the global network (list country pairs or regions and typical transit time expectations per lane)?
    • Do the shipments require door-to-door service or door-to-airport handoff for specific lanes (select applicable delivery scope)? Options: Door-to-door, Door-to-airport, Airport-to-airport, Hybrid
    • Which airwaybill (AWB) and manifest data elements must accompany each shipment for customs and receiving (for example: consignee name, IOR number, Harmonized System code, sample description)?
    • Are there lanes that require pre-filed import permits or controlled substance paperwork for biological specimens (identify country and permit type required)? Options: Yes, No
    • Provide the required pickup windows and site-level collection cutoffs for scheduled courier pick-ups (example: 09:00-11:00 local for clinical sites).
    • Which transit-time SLAs do you require by lane (for example: next-business-day, 48-hour, 72-hour) and what is the maximum allowable deviation before escalation?

    Provision temperature loggers and deliver monitoring data

    • Which logger type do you require to be provisioned with shipments: real-time telematics (cellular/GPS), Bluetooth-enabled loggers, or passive data loggers that are downloaded at receipt? Options: Real-time telematics, Bluetooth-enabled, Passive data logger, Other
    • How must logger data be linked to specimens: by kit barcode, AWB number, or LIMS accession ID? Options: Kit barcode, AWB number, LIMS accession ID, Other
    • What data format and delivery method do you require for logger traces (for example: CSV or JSON via SFTP, portal download, or webhook payload)? Options: CSV via SFTP, JSON webhook, Portal download, Other
    • Are current calibration certificates required with each logger batch (for example: ISO/IEC 17025 or supplier calibration certificate)? Options: Yes, No
    • Describe the minimum logger battery life or operational window required to cover longest lane transit (for example: 7 days battery life with 1-minute sampling).
    • Which metadata must the logger deliver with the trace for audit (for example: logger serial number, start/stop timestamps, timezone, time-stamped temperature samples)?

    Continuous temperature monitoring with excursion alerting

    • Which temperature thresholds should generate an initial excursion alert for each profile (for example: breach of 2-8°C by ±2°C for more than 10 minutes)?
    • Through which channels do you want real-time alerts delivered (select all that apply: email, SMS, portal notification, webhook to your system)? Options: Email, SMS, Portal notification, Webhook
    • What escalation timeline do you require after an initial alert before automatic rerouting is initiated (for example: 30 minutes to contact site, 2 hours to activate contingency)?
    • Do you require automated heatmap or event summaries for each excursion for inclusion in the audit package (for example: summary PDF with trace and event annotations)? Options: Yes, No
    • Indicate the maximum allowable cumulative excursion time per shipment before the sample is flagged for quarantine (example: cumulative 15 minutes outside target range).
    • Who are the nominated escalation contacts and roles to be notified during a temperature event (provide role/title and 24/7 contact method)?

    Capture barcode identity verification at every handoff

    • At which handoff points must you capture a barcode scan (select from: site collection, courier pickup, airport handoff, customs, receiving laboratory, biorepository)? Options: Site collection, Courier pickup, Airport handoff, Customs, Receiving laboratory, Biorepository
    • Which verification checks are required at each scan event (example: barcode present and readable, subject ID matches LIMS subject ID, kit lot matches manifest)?
    • Do you require offline-capable handheld scanners with batch sync for remote sites with intermittent connectivity? Options: Yes, No
    • What tolerance or acceptance rules should trigger a manual reconciliation at scan time (for example: barcode mismatch, missing field, or duplicate scan within 5 minutes)?
    • Specify any barcode label durability requirements for your sample type (for example: cryogenic label resistant to -80°C, chemical exposure resistance).
    • Identify the mandatory fields that must be captured in the scan transaction for LIMS ingestion (for example: sample barcode, scan timestamp with timezone, operator ID, GPS/location).

    Digital chain-of-custody records and audit package delivery

    • Which artifacts must be included in the digital audit package for each shipment (for example: signed manifest, time-stamped scan trail, temperature trace, AWB, customs clearance records)?
    • What format and delivery cadence do you require for audit packages (for example: consolidated PDF per shipment delivered via SFTP within 24 hours of receipt)? Options: Consolidated PDF via SFTP, Zipped CSV/JSON via SFTP, Portal download, Webhook
    • Which regulatory evidentiary standards must the audit logs meet for your filing (for example: FDA 21 CFR part 11 electronic signatures, ICH GCP traceability)? Options: FDA 21 CFR part 11, ICH GCP, ISO 9001/13485, Other
    • What evidence will validate acceptance of the chain-of-custody audit package (for example: complete signed CSV manifest, time-stamped scan trail matching LIMS accession, and 21 CFR part 11 compliant audit log)?
    • Do you require retention of audit packages for a specified period for regulatory inspection (specify retention period in years)? Options: 1 year, 3 years, 5 years, Custom
    • Who in your organization will be the authorized recipient of audit packages and responsible for confirming package completeness (provide role/title)?

    Central laboratory receiving, accessioning, and sample logging

    • What are the receiving hours and cutoffs at your central lab for same-day accessioning (for example: 08:00-16:00 local, cutoff 14:00)?
    • Which accession fields must be captured on receipt and mapped into LIMS (for example: accession number, sample barcode, subject ID, visit, collection datetime, condition on receipt)?
    • Describe your quarantine and disposition workflow for samples that arrive with temperature excursions or missing documentation (example: isolate in quarantine freezer, notify sponsor, hold for disposition decision within 48 hours).
    • Which sample rejection reasons and corresponding QC codes should be recorded at accession (for example: temperature excursion, label unreadable, leak detected)?
    • Do you require automated creation of a receiving report and LIMS accession file after batch receiving (for example: daily CSV of all accessions sent to your study team)? Options: Yes, No
    • Which SLA defines timely accessioning for your study (for example: samples accessioned and logged into LIMS within 4 hours of lab receipt)?

    Biorepository cold storage, inventory, and controlled retrieval

    • Which storage temperature zones will you require across the biorepository (for example: -80°C, -20°C, 2-8°C, ambient) and approximate sample split by zone?
    • What inventory identifiers and barcodes should be used for frozen storage locations and racks (for example: freezer ID, shelf ID, box barcode)?
    • How fast must controlled retrieval operate once a pull request is raised (for example: same-day retrieval within 4 hours, next-business-day)? Options: Same-day (within 4 hours), Next-business-day, 48 hours, Custom
    • Do you require continuous environmental monitoring with backup power and alarm notifications for each storage zone (specify alarm recipients and thresholds)? Options: Yes, No
    • What chain-of-custody artifacts should accompany each retrieved sample (for example: retrieval form, signed transfer manifest, temperature during transfer)?
    • Provide any maximum storage duration rules or retention policies by sample type (for example: 5 years for serum aliquots, indefinite for DNA extracts).

    LIMS and CTMS integration and status synchronization

    • Which LIMS and CTMS records and fields must be synchronized with the integration endpoint (specify required fields such as sample_id, subject_id, visit, collection_time, accession_number, storage_location)?
    • Which integration methods are acceptable for your systems (for example: REST API with JSON payloads, SFTP CSV drops, HL7 messaging)? Options: REST API (JSON), SFTP CSV, HL7, Other
    • Provide a list of endpoint security requirements and authentication methods for the integration (for example: OAuth2 client credentials, SSH keys for SFTP, IP allowlisting).
    • How should delayed or failed syncs be handled and retried (for example: retry 3 times with exponential backoff, create an exception ticket in your issue tracker)?
    • What acceptance criteria will confirm integration success (for example: 99% successful status sync for accession events over a 7-day test, all mapped fields verified against sample test set)?
    • Who will be the technical point of contact for integration testing and API credentials on your side (provide role/title and preferred contact method)?
  4. Mutual Commit

    Finalize commercial terms, SLAs, compliance obligations, data-sharing agreements, and escalation governance.

    Agreement Modules

    • Master Services Agreement (MSA)
    • Statement of Work (SOW)
    • Service Level Agreement (SLA)
    • Commercial Terms & Order Form
    • Data Processing Agreement (DPA) with HIPAA BAA Trigger
    • Escalation & Governance Matrix
    • Acceptance Criteria & Change Order Procedure
  5. Deployment

    Lock readiness facts and configuration values before execution begins.

    1. Pre-Deployment Readiness

      Confirm owners, pilot sites and dates, courier lanes, regulatory documentation, access requirements, and training plans required before execution.

      Pre-Deployment Questions

      Environment and site access

      • List the pilot site(s) included in this deployment (one line per site: site name — city — country — site ID). This will populate the pilot schedule and site-specific tasks.
      • Are facility access requirements for each pilot site (badging, escorted access, biosafety approvals) already granted? If not, indicate whether approvals are pending and the target date per site. Options: Yes — all sites approved, Partially — some sites pending, No — approvals not started
      • Are the courier lanes (origin → destination pairs) and the expected first-pickup dates for those lanes confirmed for each pilot site? Options: Yes — lanes and first-pickup dates confirmed, Partially — some lanes or dates pending, No — lanes not yet agreed

      Data and configuration readiness

      • Will the buyer provide integration endpoints and credentials for LIMS/CTMS by what date? (We only need the ready-by date here so we can schedule integration testing; actual endpoints/credentials go in DeploymentConfig.)
      • Has the field-mapping approach for LIMS/CTMS been decided and who owns the source-of-truth mapping (buyer, seller, or joint)? Options: Mapping decided and buyer owns mapping, Mapping decided and seller owns mapping, Mapping undecided — buyer to decide, Mapping undecided — joint workshop required
      • Are barcode formats and acceptance/rejection rules for pilot shipments defined for each site (e.g., required fields, acceptable symbologies, reject conditions)? Options: Yes — fully defined, Partially — formats or rules pending, No — not defined yet

      People and ownership

      • Are named owners assigned for these workstreams: deployment lead, operations/fulfillment, IT/integration, QA/regulatory, and training? Options: Yes — all owners assigned, Partially — some owners missing, No — owners not assigned
      • If any owners are missing or not yet submitted, list named owners and contact info for each assigned workstream (one line per owner: full name — workstream — email).

      Timing, regulatory gates, and constraints

      • Confirm the target pilot start and end dates for each site (we will not schedule courier onboarding or training before the pilot start date). Provide site → start date → end date.
      • Which regulatory or documentation gates must be cleared before pilot execution and what are the target clearance dates? Select all that apply and include dates in the free-response field if selected. Options: Import/export permits, IRB/ethics approvals, GxP/GMP declarations or certifications, Customs/broker arrangements, No regulatory gates
      • Is a training plan for site staff and couriers defined (content, delivery method, and who signs completion)? If yes, when will training be delivered and by whom? Options: Yes — training plan defined with delivery date(s), Partially — outline exists but dates/owners pending, No — training plan not defined
    2. Configuration Details

      Capture integration endpoints and credentials, LIMS/CTMS field mappings, barcode formats, temperature thresholds and alert rules, reporting endpoints, and packaging specifications.

      Configuration Details

      Environments & Endpoint URLs

      • Enter the target environment name (Default: Production) — this is the exact environment the deployment will configure (e.g., Production, Staging, Sandbox).
      • Enter the Platform API base URL (format: https://api.example.com) that the seller will call for operational events.
      • Enter your LIMS API endpoint URL (format: https://{host}/api/v{n}/ — the integration will push/poll sample records here).
      • Enter your CTMS API endpoint URL (format: https://{host}/api/v{n}/) or leave blank if no CTMS integration is required.
      • Enter the courier tracking API endpoint URL (format: https://{host}/track) the platform will call to reconcile courier statuses.
      • Enter the temperature-device telemetry endpoint URL (format: https://{host}/telemetry) that supplies per-shipment temperature streams.
      • Select the integration API version to target (Default: v1). Options: v1, v2, v3

      Authentication & Credential Handoffs (non-secret identifiers only)

      • Select the authentication method your LIMS supports for this integration (do not paste secrets here). Options: OAuth2 client credentials, API key (identifier only), Basic auth (integration username only), SAML assertion (identifier only), Other
      • Enter the LIMS integration client ID or integration username (identifier only — the secret will be exchanged via your secrets manager at kickoff).
      • Who will hold and transmit the LIMS secret at deployment kickoff? (select where the secret will be stored/exchanged — secret itself is NOT pasted here). Options: Buyer's secrets manager, Seller's secrets manager, Customer provides via secure file transfer at kickoff, Other
      • Select the authentication method your CTMS supports for this integration (if no CTMS, choose 'None'). Options: OAuth2 client credentials, API key (identifier only), Basic auth (integration username only), SAML assertion (identifier only), None, Other
      • Enter the CTMS integration client ID or integration username (identifier only).
      • Who will own temperature-device credential exchange (the platform will not accept raw secrets in this sheet)? Options: Buyer's device management team, Seller's device onboarding team, Device vendor (customer-managed exchange), Other

      Field Mappings — LIMS / CTMS source fields (one concrete mapping per question)

      • Enter the exact LIMS field name that contains the site's sample identifier (e.g., 'sample_id').
      • Enter the exact LIMS field name used for the accession number (e.g., 'accession_no').
      • Enter the exact LIMS field name that stores the collection site code (e.g., 'site_code').
      • Enter the exact LIMS field name that contains the study or protocol ID (e.g., 'study_id').
      • Enter the exact LIMS field name used for visit code or visit number (e.g., 'visit_code').
      • Enter the LIMS field name for the sample collection timestamp (format: ISO 8601 expected — e.g., 2024-07-21T14:30:00Z).
      • Enter the LIMS field name that will store received barcode value (e.g., 'barcode_value').
      • Specify the timezone to apply to all timestamps if not provided by source records (IANA timezone, Default: UTC).

      Barcode & Identity Verification

      • Select the barcode symbology your sites will print and scan (choose the primary symbology used in production). Options: Code 128, GS1-128 (GS1-SSCC), QR code, DataMatrix, Other (specify in next field)
      • If 'Other' above, or if you have a custom pattern, enter the exact barcode regex or pattern to validate (e.g., ^[A-Z0-9]{12}$).
      • Enter the expected fixed barcode length in characters (enter 0 if barcode length is variable). Default: 0.
      • Enter the human-readable sample label format used on kits (examples: 'StudyID-SiteID-SampleType-Seq').
      • Select the check-digit algorithm applied to barcodes (if none, choose 'None'). Options: Modulo 10 (Luhn), Modulo 11, GS1 check digit, None, Other
      • Require an on-scan identity verification step against the LIMS record prior to pickup? (Default: Yes). Options: Yes, No

      Temperature Thresholds & Alert Rules

      • Select the temperature unit for thresholds (Default: Celsius). Options: Celsius (°C), Fahrenheit (°F)
      • Enter the default lower temperature threshold (in selected unit). Confirm or replace (Default: 2 °C).
      • Enter the default upper temperature threshold (in selected unit). Confirm or replace (Default: 8 °C).
      • Enter the allowed excursion duration before an alert is generated (minutes — Default: 30).
      • Enter the default alert severity level (1 = Emergency to 5 = Info — Default: 2).
      • Select the type(s) of alert escalation endpoints you will provide (the platform will request exact endpoint URLs via secure exchange). Options: Email webhook (URL), HTTP webhook (URL), PagerDuty integration (routing key owner), SMS gateway (phone owner), Platform incident page

      Packaging & Shipping Specifications

      • Select the primary package type used for shipments. Options: Passive (ice/PCM), Active (powered/controlled), Ambient, Custom
      • Enter the expected inner container usable volume in milliliters (numeric).
      • Enter the maximum number of samples per kit (numeric).
      • Select the primary insulation material for the packaging. Options: EPS foam, Polyurethane foam, Vacuum Insulated Panel (VIP), Other
      • Is dry ice allowed in this shipment profile? (If yes, specify maximum mass in the next field). Options: Yes, No
      • Enter the maximum dry ice allowed per package in grams (enter 0 if not allowed — Default: 2000 g).
      • Enter required courier labeling or UN number string to appear on packaging (free text exact label required).

      Reporting, Webhooks & File Exports

      • Select which webhook events the platform should send to your endpoint (you may select multiple). Options: ShipmentCreated, ShipmentPickedUp, TemperatureAlert, ChainOfCustodyUpdated, ShipmentDelivered, ExceptionLogged, InventoryAdjusted
      • Select the webhook retry policy to apply to outbound notifications (Default: Immediate with 3 retries). Options: Immediate with 3 retries (Default), Exponential backoff up to 5 retries, No retries (one attempt)
      • Enter the SFTP endpoint URL for batch reporting files (format: sftp://hostname/path) or leave blank if unused.
      • Select the cadence for batch reporting files (Default: Daily batch). Options: Real-time (webhook), Hourly batch, Daily batch (Default), Weekly batch
      • Select the reporting file format your systems ingest (choose one). Options: JSON, CSV, NDJSON, XML
      • Enter the reporting contact email address for delivery failures and feed issues.

      Operational Ownership & Access

      • Enter the full name and role of the buyer's owner for the LIMS integration (format: Name — Role).
      • Enter the full name and role of the owner responsible for courier lane onboarding (format: Name — Role).
      • Enter the full name and role of the owner responsible for temperature-device onboarding (format: Name — Role).
      • Does the buyer require single sign-on (SSO) for platform user access? Options: Yes — SAML-based IdP, Yes — OIDC-based IdP, No — local accounts
      • Enter the buyer role/title that should receive 'Platform admin' access (exact role text).
      • Enter the number of days audit logs must be retained (numeric — Default: 365).

      Validation, Pilot Test IDs & Acceptance

      • Enter the pilot test shipment ID prefix to use for all pilot shipments (exact string — e.g., PILOT-2024-).
      • Enter the number of pilot test shipments you plan to run (numeric — Default: 3).
      • Enter the planned pilot start date (format: YYYY-MM-DD).
      • Provide the URL to the acceptance criteria document the deployment will use (format: https://...).
      • Select the role that will perform final go-live signoff once acceptance criteria are met. Options: Quality Lead, Supply Chain Director, Laboratory Director, Operations Manager, Other

      Feature Flags & Optional Modules

      • Enable the temperature analytics dashboard for this deployment? (Default: Yes). Options: Yes, No
      • Enable automated chain-of-custody PDF generation for each receipt/transfer? (Default: Yes). Options: Yes, No
      • Enable biorepository inventory synchronization (push/pull inventory states to LIMS)? (Default: No). Options: Yes, No
    3. Deployment

      Execute pilots and phased rollouts with sequenced tasks, courier onboarding, training, and named owners for each operational checkpoint.

    4. Go-Live Validation

      Verify test shipments, integrated data flows, temperature-monitoring fidelity, complete chain-of-custody records, and formal acceptance before scaling.

      Checklist items

      • Execute test shipments for each active courier lane
      • Validate end-to-end integrated data flows
      • Verify temperature-monitoring fidelity under operational conditions
      • Verify complete chain-of-custody records for each test shipment
      • Obtain written go/no-go acceptance sign-off
      • Document and approve rollback and remediation plan
      • Activate and test SLA escalation paths
      • Validate integration security and access controls
      • Assemble and archive go-live audit package
  6. Success

    Track KPIs, maintain audit-ready records, manage issues and enhancement requests, and run recurring reviews to sustain compliance and quality.

    Success Reviews

    • Go-live Health Check
    • First Measurement Review
    • Acceptance Gate — Operational Acceptance
    • Quarterly Operational Review
    • Annual Compliance and Continuous Improvement Review

    Issues & Enhancements

    • Implement agreed reporting or dashboard updates to improve metric visibility.
    • If any criterion failed, record a concrete remediation and re-test plan with deadlines.
    • Confirm legacy system decommissioning or archival is scheduled and will not remain an active operational fallback.
    • Publish the acceptance decision document with recorded pass/fail results and the named signatory.
    • Execute remediation actions for any failed criteria and deliver re-test evidence by the agreed deadlines.
    • Complete the legacy system decommission or archive and provide confirmation of data retention and read-only access where applicable.
    • KPI trends and dashboard review
    • Confirm whether on-time delivery and temperature-excursion metrics remain within Solution Scope targets or require corrective action.
    • Ensure high-priority operational issues are assigned and scheduled for resolution before the next quarter.
    • Validate that audit-ready records are complete for the period under review.
    • Close or escalate high-priority tickets with agreed deadlines and publish progress updates.
    • Re-confirm success criteria and owners
    • Prepare and bundle audit documentation for the next internal or external audit window.
    • Year-to-date KPI summary vs Solution Scope targets
    • Validate annual compliance posture by reviewing cumulative temperature-excursion rate and chain-of-custody completion rate against Solution Scope targets.
    • Agree the top three continuous improvement initiatives and timelines to sustain quality and compliance.
    • Confirm training and escalation updates needed to support the next year's monitoring plan.
    • Approve and schedule the top continuous improvement initiatives with expected completion windows.
    • Deliver a consolidated audit packet summarizing the year and corrective actions for regulatory readiness.
    • Publish the agreed monitoring cadence and any revised KPI targets back into Solution Scope documentation.
    • Confirm the deployment components listed in Solution Scope are operational or documented with remediation plans.
    • Identify the top three operational blockers and agree remediation timelines.
    • Schedule the next data-driven checkpoint and assign owners for follow-up actions.
    • Document all open issues with remediation dates and publish the tracker for stakeholder review.
    • Execute targeted re-tests of affected courier lanes and test shipments within the agreed window.
    • Update or distribute required training materials to address observed user gaps.
    • Present first measurement data vs Solution Scope targets
    • Establish whether on-time sample delivery rate and temperature-excursion rate are moving toward the Solution Scope targets.
    • Identify root causes for the top performance gaps and record remedial actions with resolution dates.
    • Confirm the schedule and criteria for the acceptance gate meeting around day 90.
    • Implement agreed remedial tasks for the highest-impact delivery and temperature issues and report status before the acceptance gate.
    • Run a targeted verification batch of shipments for affected lanes and deliver results to the shared workspace.
    • Correct any LIMS/CTMS field-mapping or integration errors that contributed to chain-of-custody gaps.
    • Restate acceptance criteria and numeric targets
    • Produce a documented acceptance decision with pass/fail recorded for each Solution Scope criterion and a named signatory where required.
    • Chain-of-custody and sample identity review
    • Present outcome data against each criterion
    • Root cause diagnosis for gaps
    • Deployment and migration validation
    • Regulatory audit and findings review
    • Early operational signals and usage patterns
    • Continuous improvement proposals and prioritization
    • Document pass or fail per criterion and capture formal acceptance decision
    • Open issues and enhancement request backlog
    • Review chain-of-custody completeness and sample identity incidents
    • Agree corrective actions and timeline to acceptance gate
    • Training, ownership, and escalation governance for next year
    • Audit-readiness and regulatory compliance status
    • Agree remediation plan for any failed criteria
    • Open issues and blockers
    • Agree next-year monitoring cadence and KPI adjustments
    • Agree immediate remediation actions
    • Incumbent system wind-down confirmation
    • Agree actions for the next quarter
First-Party AI

1-2 minutes please — Your AI agent is working

First-Party AI™ can make mistakes. Always check important information.