A post-approval CMC change is one technical proposal with many regulatory clocks. The process, material, method, site, specification, equipment, or control may be scientifically coherent while each market has different approved text, established conditions, reporting category, protocol availability, submission route, approval state, commitment, and implementation date.
The system must keep technical truth and market authority connected without confusing them. One global change record is too blunt; one unrelated record per country fragments the scientific argument.
The approved product state is the baseline
Product, strength, dosage form, presentation, manufacturing and testing sites, process, materials, specifications, analytical methods, controls, container closure, shelf life, and commitments form the current approved state by market.
Effective authority comes from approved applications and lifecycle actions, not from the latest internal master document alone.
Established conditions identify regulated commitments
Process parameters, material attributes, facilities, specifications, methods, controls, and other elements can be identified as established conditions with associated reporting categories and supporting justification.
The model preserves where the condition is stated, its exact scope, market, application, approval date, effective version, and related supportive information.
One change has a precise technical delta
The proposal records current and future state, affected objects, rationale, intended benefits, implementation options, validation and comparability needs, supply implications, sites, products, and target timing.
Structured differences make impact computable. “Update manufacturing process” is not enough to determine reporting or evidence.
The affected-product surface is traversed, then reviewed
Where-used identifies products, strengths, sites, markets, submissions, specifications, methods, process versions, validation states, stability commitments, inventory, planned campaigns, and partner agreements that depend on the changed object.
Owners confirm inclusion and exclusion with rationale. Automated breadth does not replace scientific and regulatory judgment.
Market assessment preserves jurisdictional difference
For each authorization, the assessor evaluates approved state, established conditions, reporting category, eligibility for protocol or reliance pathway, required data, language, fees, sequence, approval or notification timing, and implementation constraint.
The result can be prior approval, notification, annual reporting, no filing, consultation, or another local route without forcing all markets into a US or EU taxonomy.
A PACMP is an executable protocol
The protocol defines proposed change or change family, conditions for use, studies and batches, methods, acceptance criteria, statistical approach, stability, commitments, reporting category after successful completion, documentation, and implementation rules.
The ICH Q12 guideline describes the Post-Approval Change Management Protocol as a regulatory tool for predictable and efficient management of post-approval CMC changes. Seal makes its approved obligations operational rather than treating the PACMP as a static submission attachment.
Protocol eligibility is checked before execution
Product, market, approved protocol version, change type, site, scale, process range, prerequisites, prior commitments, outstanding actions, and allowed deviations determine whether the PACMP may be used.
If the actual change exceeds the approved protocol, the system opens a new regulatory assessment instead of applying the expected lower reporting category automatically.
The evidence plan serves science and filings
Comparability, engineering, qualification, process validation, analytical bridging, specifications, stability, shipping, microbiology, extractables and leachables, human factors, or other evidence is planned once with market-specific obligations attached.
Batches and studies retain purpose, configuration, population, acceptance, source results, deviations, conclusion, and which regulatory claim they support.
Evidence cohorts prevent false equivalence
Pre-change, post-change, development, engineering, validation, stability, commercial, site, scale, method, and material populations remain explicit. Bracketing and matrixing decisions carry rationale and limits.
The comparison can be regenerated when a result changes or an additional market asks a different question.
Acceptance criteria are approved before results
Protocol criteria carry attribute, method, population, statistic, limit, direction, missing-data handling, exception rule, and market applicability. Amendments remain versioned and separately authorized.
Results do not redefine the threshold after the fact. Departures route through scientific assessment and may invalidate the intended regulatory pathway.
Health-authority interactions update obligations
Questions, requests for information, commitments, meeting agreements, deficiencies, clock stops, responses, approvals, rejections, withdrawals, and post-approval conditions link to the market assessment and technical evidence.
A request in one jurisdiction can create a global study or restrict only that market; both patterns remain representable.
Submission content is assembled from governed claims
Affected CTD sections, summaries, tables, protocols, reports, validation evidence, stability data, specifications, methods, commitments, forms, and regional administrative content resolve from the effective change and market route.
Document rendering remains traceable to structured source and approved versions while allowing regulatory authors to provide necessary narrative.
Implementation authority is market and product specific
Technical completion does not by itself authorize commercial implementation. The gate considers market approval or notification conditions, protocol acceptance, commitments, effective labeling where relevant, site readiness, partner readiness, inventory strategy, and supply decision.
Authorized dates and conditions can differ by market, site, strength, or presentation.
Inventory and campaigns need a transition strategy
Pre-change and post-change materials, intermediates, bulk, finished goods, labels, specifications, methods, and batch records require cutover rules. Segregation, depletion, dual state, rework, retest, relabel, or destruction may be required.
Orders and batch execution resolve which markets may receive each configuration. An approved change in one market cannot leak into an unauthorized one.
Commitments survive project closure
Ongoing stability, continued verification, report submission, method monitoring, supplier notice, annual report, post-implementation review, or authority condition remains assigned with due date, evidence, market, escalation, and closure criteria.
Closing the internal change does not close obligations whose evidence will mature later.
Deviations can change the regulatory route
Protocol deviation, failed criterion, changed study, missing batch, unexpected trend, implementation error, or out-of-scope configuration triggers reassessment of comparability and reporting.
Seal identifies affected markets, submissions, commitments, inventory, and campaigns while preserving the original plan and actual course.
The lifecycle view answers “what is approved where?”
For any product and market, the reviewer can see current approved state, pending submissions, accepted protocols, open commitments, future implementation, transitional inventory, and recent changes.
For any technical object, the reverse view shows where it is approved, referenced, planned to change, or still awaiting authority.
Where Seal is strongest
Seal is strongest between quality change control, CMC knowledge, regulatory lifecycle, and manufacturing execution. It preserves one scientific change while allowing jurisdiction-
That is the point where document-only regulatory systems and site-only quality systems most often lose synchronization.
Prove one difficult global change end to end
The first implementation should follow one manufacturing-site or process change through approved-state comparison, established-
Include one market eligible for an approved PACMP, one requiring prior approval, one notification, one no-filing decision, a criterion miss, an added stability commitment, pre-change inventory, parallel site production, and delayed approval. The first usable release must block the new configuration from any market that has not authorized it.
