The change was approved. The product still could not ship.

A manufacturing-site change passed technical review, validation, quality approval, and local implementation. The change record was green. Months later, supply planning learned that several markets required regulatory action before product made at the new site could be distributed there.

Nothing was wrong with the engineering package. The failure sat between systems: change control knew what changed; regulatory affairs knew the registrations; neither record governed when each market could use the changed state.

This is not a second RIMS and it is not an eCTD publisher. RIMS remains the authoritative portfolio of products, registrations, dossiers, submissions, correspondence, and approved market states. Submission management plans and dispatches filing packages. Change control governs the proposed operational change.

This blueprint joins them. It determines which registered products and markets may be affected, records the accountable regulatory assessment, creates the required regulatory actions, blocks implementation where approval is a prerequisite, and returns evidence to the quality record.

That boundary makes the workflow useful: one global change, many market decisions, explicit release conditions.

Regulatory assessment cannot recover from a vague source record. The change carries the before and proposed-after state for product, material, specification, process, method, equipment, software, site, supplier, packaging, labeling, storage, shelf life, or control strategy.

Reason, urgency, affected facilities, planned effective date, validation strategy, inventory exposure, and temporary-versus-permanent status are structured. Supporting documents remain linked to the claims they establish.

The system traverses governed relationships from the changed object to products, presentations, registrations, manufacturing and testing sites, dossiers, labels, and commitments. It produces a candidate impact set with the relationship that caused each market to appear.

Regulatory owners confirm, add, or exclude candidates with rationale. Automation proposes scope; an accountable person owns it. A market is never silently removed because a reference was incomplete.

For every affected registration, regulatory affairs records classification, legal or procedural basis, required data, submission type, authority interaction, approval-before-implementation rule, reporting window, grouping opportunity, local document need, fee, expected review path, and uncertainty.

Requirements are versioned by jurisdiction, product class, procedure, and effective date. A rule update creates a review task for open assessments; it does not rewrite the historical basis of a signed decision.

The system does not pretend that every classification is deterministic. Precedent, authority advice, product knowledge, regional interpretation, and risk can produce alternatives.

Each assessment retains the options considered, evidence, assumptions, dissent, consultation, chosen strategy, approver, and date. A later reviewer can understand why a market was classified—not merely see the final dropdown value.

Required actions become owned work: data generation, document authoring, translation, local affiliate review, publishing, dispatch, fee payment, authority response, approval, notification, label implementation, and commitment fulfillment.

Dependencies form a real network. A filing cannot be ready before its evidence; an implementation gate cannot open before the required approval; a market launch cannot precede the approved state. Forecast dates may move without changing statutory dates.

There is rarely one global effective date. Some markets may permit implementation before notification, others after a defined waiting period, and others only after approval. Existing inventory, product manufactured under the previous state, packaging, and release status can add further constraints.

Seal maintains a market implementation matrix: proposed, allowed, blocked, approved, implemented, and verified. MES, ERP, labeling, release, and distribution controls can consume the applicable decision rather than infer it from a closed change record.

During a transition, both old and new states may be legitimate. A batch can be suitable for one market and ineligible for another. The record therefore connects material and batch genealogy, manufacture date, packaging version, destination market, registration state, and implementation authorization.

Exceptions require a documented decision and approval. Teams can see where dual-state operation exists, how long it is planned to last, and what must happen before convergence.

Meeting minutes, questions, information requests, deficiency letters, advice, approvals, acknowledgements, and commitments link to the market assessment and topic they affect.

A question about comparability can change the evidence plan. An approval condition can become a new commitment. The correspondence is not an attachment graveyard; it is evidence that changes the executable regulatory position.

Commitments can originate in approval letters, inspection responses, meeting minutes, submissions, variations, safety measures, or formal correspondence. Each obligation records the exact source text, interpretation, jurisdiction, product, deliverable, milestone, dependency, owner, escalation, evidence requirement, submission link, and acceptance state.

Completion means the promised outcome and evidence exist. Dispatch may satisfy a filing milestone but does not automatically prove that an authority has accepted or closed the obligation.

Awareness date, statutory due date, internal target, forecast completion, filing date, authority receipt, validation acknowledgement, review clock start, clock stop, response due date, approval date, implementation date, and commitment closure are separate fields.

The plan can forecast risk without moving the legal deadline. Calendar calculations retain the rule and calendar used so that the result is explainable.

An approaching internal target and an approaching legal due date are not equivalent. Escalations consider remaining work, critical-path dependencies, approval prerequisites, market supply impact, owner response, and current forecast.

Leadership sees obligations at risk with causes and recovery actions. Notifications are an output of the controlled plan, not the plan itself.

AI may extract candidate obligations, dates, products, and deliverables from controlled correspondence. It may compare proposed wording with approved positions or identify registrations connected to a changed site. Every suggestion retains its source passage, confidence, model and prompt version, reviewer decision, and correction.

It cannot approve a classification, invent a requirement, close a commitment, or authorize implementation. Those actions remain signed decisions by designated roles.

One submission may address several changes, and one change may require many submissions. The many-to-many relationship remains explicit down to the affected dossier content and approved outcome.

Bundling decisions retain rationale and dependency. If one element is withdrawn or questioned, teams can determine which changes and markets are affected without reconstructing the package from filenames.

The global change closes only under an approved closure policy: all required assessments completed, actions dispositioned, prerequisite approvals received, permitted implementation executed, evidence linked, residual exceptions accepted, commitments created, and downstream master data synchronized.

Markets intentionally deferred remain visible with owners and conditions. “Closed” never means the remaining work disappeared into another department.

Which approved changes are waiting on regulatory action? Which markets block use of the new site? Which commitments are due this quarter? Which submissions contain evidence from Change CC-0148? Which registrations still use the previous specification? Which market assessments lack a current rule basis?

Every aggregate drills into the source change, assessment, requirement, action, submission, authority outcome, and signed decision.

For any change, Seal can show its original scope, affected-product derivation, market assessments, reviewers, requirement versions, planned actions, correspondence, submissions, approvals, implementation gates, exceptions, evidence, commitments, and final reconciliation.

That is the defensible record: not that two systems both said “complete,” but that every affected market moved from one controlled state to another under an accountable decision.