Define the population, package, conditions, timepoints, sample quantities and exception rules. Retain the version executed by each study.
All blueprints
See the change before the limit is crossed.
Connect the protocol, physical pull and original result across the life of a stability study. Use neil to investigate the evidence and prepare the work behind the next timepoint.
Keep the missing result in the work.
Four impurity results are below the assigned limit. All four are rising. Month nine has no reportable result linked. The study needs both the missing evidence and review of the values already recorded.
The study-wide queue gives that work an owner and a source: recover the nine-month evidence, review month twelve, confirm laboratory capacity, allocate the next pull and review the protocol amendment. A missing result is not silently counted as a pass.
Follow the six units, not just the due date.
The twelve-month pull allows removal from 4–10 September. On 7 September, six units leave chamber CH-02 at 08:30 UTC and reach the QC laboratory at 09:05. Removal and receipt are different events; neither means testing or review is complete.
Keep each handoff with its quantity, time and source. Reserve stock, repeats and destructive tests need their own allocation. A chamber event is assessed against the material present at the time, using historical placements and movements—not today's inventory.
Removed from CH-02
08:30Alex MorganShelf 3 / position B6 units · 35 minutes
Received by QC laboratory
09:05Receipt recordedTesting and review are separateRecorded pull window: 4–10 September. This handoff does not establish test completion or sample suitability.
Inspect the original pull record
Ask neil to configure the next study workflow.
Bring a protocol, a recurring study problem or a question about the data. neil can investigate permitted records and author linked work, capture fields and review paths in Seal. Start with the work you want your team to inspect.
Investigate the missing timepoint
“Trace month nine from its planned pull to the laboratory evidence. Explain what is missing and create the follow-up work.”
Ask neil to distinguish a missed pull, delayed test, invalid result and absent source. It can prepare a linked evidence request and an assessment of candidate explanations, with the records needed to distinguish them. Missing data stays missing until evidence resolves it.
Prepare the next pull across the study
“Prepare the next pull package. Check sample quantities, laboratory capacity and dependencies before proposing the schedule.”
neil can assemble proposed pull records and preparation tasks from the protocol and permitted inventory and planning records. Ask it to identify shortages, conflicts and stale availability, and compare scheduling options. A proposed slot is not a confirmed reservation.
Turn the protocol into testable configuration
“Configure reusable study, pull and result templates from this protocol. Include the exception paths and verification cases.”
Ask neil to author linked templates, required measurements, protocol-version references and review states. It can stage a change set and tests for missing readings, a late pull, insufficient units and a changed method. Your team reviews the configuration and runs the verification before publication.
Illustrative requests, not executed neil work. People review the evidence, verify configuration and approve changes.
Inspect the study these requests refer to
Keep the evidence behind the conclusion.
The 0.42% result identifies its method, acquisition and physical pull. Retain that source context when methods, specifications or processing change. A descriptive chart is not a fitted model; this one-batch example does not establish shelf life.
Define the population and data cutoff for each analysis. Keep exclusions, assumptions, uncertainty and open questions with the report. Protocol amendments preserve the version already executed; ongoing placements and report commitments keep their owners and original due dates. Scientific conclusions and publication remain authorised decisions.
Inspect the twelve-month result and its sources
Capabilities
Track the nominal timepoint, allowed window, actual removal, receipt and test completion separately. Preserve late and missing events.
Inspect measured values and missing evidence by batch, package and attribute. Keep descriptive trends separate from approved statistical analyses.
Keep missing evidence, result review, resource checks and protocol amendments in a shared work queue, with responsible roles and source records.
Follow a result into its method, acquisition and pull. Agree and verify interfaces for external laboratories and instrument systems.
Actual Seal interface, fictional study. Published identifies a saved version, not scientific approval.
Open full-size image in a new tabConnected records
Entity hierarchy
What it records
Kind
Stability Study
A complete stability study for a specific batch and protocol.
entity
ST-2024-001
24-month stability study for Drug Product A.
record
Stability Protocol
Defines storage conditions, timepoints, and testing requirements.
entity
ICH Accelerated
General-case accelerated protocol starting point; confirm product, package, purpose and applicable conditions.
template
ICH Long-Term
General-case long-term protocol starting point; confirm applicability and the approved storage conditions.
template
ICH Intermediate
Intermediate protocol starting point with justified conditions, triggers and testing.
template
Photostability Study
Light-exposure and protected-control design with product, package, exposure, sampling, tests, results, assessment, and conclusion.
template
Stability Chamber
Controlled environment for sample storage with temperature monitoring.
entity
Stability Sample
Sample placed on stability with defined pull schedule.
entity
Timepoint
Scheduled testing point (e.g., 3 month, 6 month, 12 month).
entity
Excursion
Chamber condition outside acceptable limits.
entity
Trend Analysis
Statistical analysis of stability data over time.
entity
Stability Batch & Package
Product, formulation, strength, process, site, batch, container closure, orientation, market, label, and design role.
entity
Stability Inventory Plan
Required units by condition, timepoint and test, reserves, repeats, destructive use, pulls, remaining quantity, shortages, and disposition.
entity
Stability Pull
Nominal and allowed window, actual removal, conditioning, transport, receipt, login, test start, return, destruction, people, and exceptions.
entity
PULL-ST001-18M
18-month pull completed within window with exact units, chain of custody, sample login, testing start, and remaining inventory.
record
Stability Result
Raw and reportable value, method, specification, unit, calculation, repeat status, OOS or OOT, instrument, standard, approval, and source.
entity
Stability Statistical Analysis
Population, transformations, model, pooling, criteria, estimates, confidence, diagnostics, exclusions, software, review, and conclusion.
entity
ST-ANALYSIS-001
Approved batch-specific and pooled models with confidence bounds, diagnostics, sensitivity, assumptions, and shelf-life support.
record
Shelf-Life or Retest Decision
Proposed period and storage with evidence, statistics, variability, extrapolation, commitments, approvals, filing, and authority outcome.
entity
Questions and answers
Yes. Keep each study's batch, package, conditions, timepoints and protocol version explicit. Compare populations only with the scientific and statistical justification required for the intended use.
Connect the source event to historical occupancy, movements and pulls. Prepare the candidate sample population, exposure evidence and unresolved gaps for review. Monitoring interfaces, alarms and recovery need source-specific configuration and verification.
Templates can be configured around applicable guidance. Conditions, design and evaluation depend on the product, package, purpose and governing protocol; a general-case template is not a universal requirement or a compliance certificate.
Prepare reports from a defined population and data cutoff, with linked results, charts, analysis versions and open issues. Review the generated package and its required submission format before approval and export.
Preserve the study structure, planned and actual events, amendments and source evidence throughout the program. Define retention, archive, retrieval and original-data readability requirements before the study closes.
Record whether the problem is a missed pull, delayed test, invalid result or absent evidence. Preserve the gap and its assessment. Do not substitute zero, interpolate silently or let a new result erase the earlier event.
No. The chart on this page is descriptive and contains no fitted model. Formal evaluations need justified populations, assumptions, diagnostics and uncertainty; qualified stability, statistics, quality and regulatory reviewers own the conclusion.
Use the event window and mapped condition together with actual placement, movement and pull history. Retain inclusion and exclusion reasons. An uncertain movement or missing sensor interval remains an explicit gap.
Yes. Retain the version used by each result and assess the effect of changes on interpretation and comparability. Segment or otherwise evaluate data under the approved analysis plan without overwriting original evidence.
neil can draft study assessments, linked evidence requests, pull packages and changes to templates, fields, rules and review states. It can prepare requirement links and verification cases. People verify and publish the change; neil does not approve shelf life.
Related blueprints
Pharmaceutical Cold Chain & Temperature Excursion Management Software
Qualify routes and shipping systems, assemble logger evidence, calculate exact exposure, identify the affected physical population, and make stability-backed disposition decisions without reconstructing a journey from emails.
CMC Data & Module 3 Content Management Software
Connect CMC content to protocols, results and process records. Prepare source-linked tables and drafts, review changes and preserve the data behind each submitted version.
Biologics Cell Bank, Seed Lot & Strain Management Software
Control master and working cell banks, viral and microbial seed lots, strains, characterization, cryogenic locations, vial withdrawal, passage, suitability, and downstream manufacturing impact.
Container Closure Integrity Testing (CCIT) Software
Govern container-closure configurations, critical quality attributes, CCIT methods, positive controls and standards, validation, routine and stability studies, transport challenges, results, investigations, trending, and lifecycle decisions.
Pharmaceutical Extractables & Leachables (E&L) Management Software
Map product-contact systems, characterize materials, plan extractables and leachables studies, calculate exposure and analytical evaluation thresholds, identify compounds, govern toxicological assessments, justify bracketing, and manage lifecycle change.
Pharmaceutical Nitrosamine Risk Assessment & Control Software
Govern product and API nitrosamine risk assessments, amine and nitrosating-agent knowledge, formation pathways, acceptable-intake limits, confirmatory methods and testing, mitigation, stability, supplier dependencies, regulatory reporting, and lifecycle review.
See your process in Seal.
Tell us about your workflow. We’ll show you how neil and Seal can help your team.
Book a demo