Define the records behind a content section and retain missing timepoints, selected versions and review state. A folder count is not evidence completeness.
All blueprints
Every claim needs its evidence.
Connect submission content to selected source records, review and follow-up work. Ask neil to draft, compare and configure the workflow behind the next filing.
Same evidence. Three very different claims.
Select a draft statement to inspect what the source can support.
Impurity A (%)
M00.10
M30.15
M60.24
M9Missing
M120.42
Four observations. One missing timepoint.
“The twelve-month impurity result was 0.42%.”
A recorded observation—not an approval.
The twelve-month record supplies this value and identifies the method, acquisition and pull. Its technical review is still open.
Inspect the source recordIllustrative claim review using fictional study records. These are example drafts, not submitted content, automated decisions or demonstrated neil output.
Choose the evidence before drafting the claim.
A submission source set needs a defined population and recorded versions. Keep the selected studies, batches, methods and results alongside the content they support, including missing evidence and exclusions.
The ST-026 example contains four measured impurity results and a missing nine-month result. The numerical observation, completeness statement and shelf-life conclusion above therefore need different review decisions.
New source data should create review work.
Retain the source versions behind an approved section. If a result is corrected or new evidence arrives, compare it with the selected source set and assess the affected claims, tables and summaries.
Prepare a revised draft or new data cut when needed. Do not silently regenerate previously approved content, overwrite what was sent or assume that all markets can reuse the same wording.
Ask neil for inspectable submission work.
neil can analyse supplied documents and permitted records, draft source-linked content and configure the workflow behind it. Ask for the selected evidence, missing work and review tasks together—not just a polished paragraph.
Draft from a bounded source set
“Prepare the stability summary from these selected records. Cite each value and flag any claim the evidence does not support.”
A draft summary, source index and unresolved-evidence list. Missing results and unreviewed analyses stay visible for the regulatory and scientific reviewers.
Assess a changed source
“Compare the new study record with the version used in the dossier. Identify the claims, tables and summaries that need review.”
A proposed impact assessment and revision tasks linked to both source versions. Previously approved content remains unchanged until the required review.
Configure the content-review workflow
“Turn our submission procedure into linked content, evidence-request and review templates. Include tests for a missing source and a changed data cut.”
Draft templates, required fields, workflow states and verification cases. Your team verifies the configuration and connects the approved publishing route.
Illustrative requests and proposed work. The native captures do not demonstrate neil execution. Authorised people verify configuration and approve the decisions.
Content approval is not authority receipt.
Define the publishing and dispatch route for the intended submission. Regional technical profiles, package validation and gateway handling require a configured, verified integration or a specialist publishing workflow; the examples on this page do not demonstrate those services.
Retain the exact content and package versions, validation output, dispatch evidence and returned acknowledgements separately. Link authority questions and commitments to the original sequence without treating transport, technical acceptance and regulatory approval as the same event.
Capabilities
Keep a reported value connected to its method, acquisition and physical sample. Review numerical observations separately from scientific conclusions.
Assign the missing source, analysis or review as linked work with an owner and requirement. Keep unresolved dependencies visible to the content team.
Assess revisions and their downstream content before updating a selected evidence set. Preserve prior versions and the basis of earlier decisions.
Related fictional study source. Not a submission-package screenshot.
Open full-size image in a new tabConnected records
Entity hierarchy
What it records
Kind
Submission
Package sent to health authority. eCTD, variation, annual report. Tracked from draft to approval.
entity
eCTD Submission
Electronic Common Technical Document. Modules 1-5, formatted for gateway submission.
template
SUB-026 / illustrative content plan
Illustrative submission work linking the selected source set, draft content and required review. No filing or authority receipt is represented.
record
Variation
Change to approved product. Type IA, IB, II classifications. Impact assessment included.
template
VAR-EU-2024-012
Illustrative proposed change-linked filing work. Classification and market requirements need accountable assessment.
record
Annual Report
Periodic content package with selected sources, review and the applicable publishing requirements.
template
Health Authority Response
Question interpretation, response strategy, new evidence, content, review, sequence, dispatch, outcome, and commitments.
template
Correspondence
Communication with health authority. Questions, responses, information requests.
entity
Commitment
Promise made to regulator. Due date, owner, fulfillment tracking.
entity
Dossier
Complete regulatory file for a product. Versioned dossier retaining each submission and the assessed approved state.
entity
Submission Strategy
Market, authority, procedure, legal basis, scope, sequence, dependencies, risks, target dates, and accountable roles.
entity
Submission Content Plan
Requirement-to-section map with topic, source, author, review, language, dependency, due date, reuse, and readiness.
entity
Regulatory Claim
Quantitative or interpretive statement with exact source evidence, data cut, assumptions, author, citations, and review.
entity
CLAIM-STAB-0082
Illustrative draft claim assessed against ST-026. Available source records do not establish a twenty-four-month shelf life.
record
Submission Data Cut
Frozen source population, versions, queries, exclusions, mappings, transformations, reconciliation, approval, and hash.
entity
Submission Content
Section or document version with claims, tables, figures, references, translations, review, approval, and reuse history.
entity
Quality Module Content
Controlled CMC section with source records, data cuts, claims, tables, figures, references, review, and lifecycle reuse.
template
Content Review
Role-specific challenge with comments, responses, dispositions, reopen history, acceptance, signature, and approved version.
entity
eCTD Sequence
Regional envelope, modules, leaves, metadata, lifecycle operations, technical validations, published output, and checksum.
entity
SEQ-0003
Illustrative planned sequence with publishing, technical validation and dispatch still to establish. No acknowledgement is represented.
record
Questions and answers
No. It demonstrates source evidence and an illustrative claim review. The intended technical profile, publisher, validation tooling, dispatch route and acknowledgement handling must be established and verified for the deployment.
neil can work with supplied documents and permitted records to draft source-linked sections, assemble evidence requests, compare revisions and author content-review templates and verification cases. Drafts and configuration are staged for human review, not represented as approved or dispatched work.
Keep each claim attached to the selected source set, its limitations and review state. Ask neil to flag missing evidence or conclusions beyond the source. Expert review remains necessary; source citations alone do not guarantee that a claim is correct.
Retain the version used in the content and assess the new evidence against it. Identify the affected claims and prepare a revision or new data cut when appropriate. Previously approved sections and sent packages should not silently change.
Link proposed operational changes to accountable regulatory assessments and the resulting content or filing work. Required actions depend on the confirmed product, market and change scope—not on an automatic global classification.
Link correspondence to the relevant submission, topic and source material. Record the interpretation, owner, deadline and response evidence. Sending a response does not by itself establish that an obligation has been accepted or closed.
Use RIMS for registrations and approved market state. Use the submission workflow for content planning, selected evidence, review and the controlled publishing handoff. Define ownership and reconciliation where the records cross systems.
Retain the exact approved content and technical package versions, validation output, dispatch evidence and returned acknowledgements through the configured publishing route. Distinguish transmission, receipt, technical acceptance and regulatory approval.
Related blueprints
Post-Approval CMC Change & PACMP Management Software
Assess post-approval CMC changes across products and markets, govern established conditions and PACMPs, assemble comparability evidence, track authority outcomes, and prevent premature implementation.
Regulatory Change Impact & Commitment Management Software
Connect QMS changes, health-authority commitments, market assessments, submission dependencies, implementation controls, and closure evidence without turning the QMS into a second RIMS.
GxP Automated Reporting & Quality Intelligence Software
Prepare recurring reports from defined populations and source versions in Seal. Reconcile the inputs, reproduce the calculations and keep review actions with the signed output.
Pharmaceutical Stability Study Management Software
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.
Pharmaceutical Technology Transfer Management Software
Carry process instructions, parameters, calculations and method references into a receiving-site draft. Ask neil to prepare local changes and evidence-linked follow-up work.
Pharmacovigilance & Drug Safety Management Software
Safety intake, minimum criteria, triage, duplicate search, follow-up, MedDRA and product coding, seriousness, expectedness, causality, case quality, jurisdiction-aware timelines, ICSR generation and acknowledgements, aggregate reporting, signals, benefit-risk, and safety-quality linkage.
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