WorkflowContract Manufacturing (CDMO)

Multi-Market Post-Approval Change Filing

Post-approval changes for contract manufacturers: one core manufacturing file, each market's registration as a layer over it, and a plant change traced into every paragraph it touches before any batch from it is supplied.

See one added press line traced into six registrations ↓
Watch with transcript →
The problem

Six registrations of one tablet, and nobody holds the six texts side by side

A contract manufacturer writes the manufacturing section of a client's dossier once. Then each market asks for its own version: the batch formula per tablet here, equipment by class only there, a different long-term stability condition somewhere else. Each request is a copy of the Word file, edited and sent, and after a few markets nobody can say which wording each market holds.

When a change control adds a second compression line, the CMC specialist opens each copy, hunts for the old line's name and writes a filing view per market. Planning is left a note to keep the new line's batches away from markets that have not approved it. A dossier still in preparation goes in without the planned change, and the same change comes back later as a separate filing with its own review clock.

Built forRegulatory CMC leadsCMC writersQA change control specialistsMSAT validation leads

The Problem Today

One product's manufacturing text drifts into a different copy per market, so a change is searched for by eye and supply depends on memory.

12 mo
most ICH Q1E lets a shelf life run past the long-term data published

Kept in separate copies

  • Dossiers
  • Formulas
  • Stability
  • Requests
  • A new line, an unready marketA batch from the added line can reach a market that never approved it
  • A hoped-for shelf life copiedA planning sheet's number lands in the dossier instead of the signed data

The Solution

  1. One core file, one layer per marketThe section drawn as the dossier prints it, each market's differences laid over it
  2. The change traced to paragraphsEvery registration searched, and what was searched listed when nothing is found
  3. A market's reviewer goes firstAn agent reads the draft as that market's reviewer would and catches the agents' own claim
  4. The client confirms each routeFixed-field answers open supply gates per line and market

Built-in controls

  • No batch to a market from a line it has not approved
  • The writer authors; the CMC lead approves
  • Agents propose filing routes; the client decides

What You Get

A client opens each new market from one core file, and a planned change goes into a dossier still in preparation instead of a later filing.

  • Two lines at approval, not oneThe added line is usable in the new market as soon as it is approved
  • Packages read as the reviewer willThe client receives a package already challenged, own errors fixed
  • Each market's wording on recordEvery difference from the core cites the rule behind it
Features

Post-approval changes features, from the paragraph trace to the supply gates

A change control adds a second compression line as an alternate for a client's film-coated tablet, registered in four markets and in preparation in two more. Here is that change, filed market by market.

demoThe CDMO, the client, its product, the markets and every figure are sample data.

  1. 01Trace run

    Change impact traced through each registration's manufacturing text

    • Agents show their reading. The core keeper, change tracer and route proposer each list the records they opened and how sure they are, so the CMC lead checks the reasoning.
    • Planned markets brought into the trace. Markets with no dossier yet sit beside the six registrations; a typed steer adds them as a step, and they inherit the core text with the new line once it is implemented.
  2. 02Registered text

    Module 3 CMC sections marked where the change touches them

    • The paragraph, not the license. The compression paragraph and the validation paragraph light up in each market's text, with the registered and the proposed wording one under the other.
    • Untouched sections checked too. In-process limits that apply to the press in use are checked and marked not touched, so the trace says what it left alone and why.
  3. 03Market layer

    Each market's dossier differences laid over one core CMC file

    • Insertions and deletions per market. Switching a market on shows its differences over the core text, so the writer sees exactly what that authority holds.
    • Each difference cites its rule. A market's restated batch formula or class-only equipment wording carries the client-signed rule behind it, so no difference is left unexplained.
  4. 04Change trace

    CMC post-approval changes classed per market for the client to confirm

    • Ten paragraphs in five registrations. One market states the press by class only, so its text holds no hit and the trace explains why instead of staying silent.
    • Routes proposed, never decided. Annual report, a variation in the annual update, prior approval or no filing is proposed per market from its rules, and the client confirms.
  5. 05Reviewer

    A market's reviewer played against the draft dossier, agents' errors included

    • A shelf life the data cannot carry. The layer agent had copied the client's planned shelf life; the reviewer held it to what the signed trend statement supports under ICH Q1E.
    • Validation for every line named. A market that names the new line needs its validation data at submission, so the report date goes to the validation lead to confirm.
    • A failed batch decided by a person. How the validation summary reports the new line's failed first batch is the regulatory CMC lead's call, with a reason code.
  6. 06Rehearsal

    Fold the change into the dossier in preparation, or file it later

    • Both options with their dates. Validation, report and content dates are computed against the market's late-update window, with the plant's shutdown skipped.
    • Assumptions anyone can change. Moving the validation restart shows the submission slipping, so the recommendation is made on dates the team can test.
  7. 07Package

    CMC dossier package signed by the writer and the CMC lead, then sent

    • Author and approver, two people. The CMC writer signs that the trace and recommendation were checked, and the regulatory CMC lead approves only after opening the same version.
    • Three questions with fixed answers. Which applications take the line, what shelf life to propose and whether the routes stand come back as choices the record can apply.
  8. 08Client portal

    Client portal with fixed-field answers, scoped to the client's own products

    • Only the client's own products. The client's CMC lead sees its products, registrations and packages, and nothing of another client's.
    • Disagreement blocks only that market. Rejecting one named route holds that market alone, so the rest of the filing plan keeps moving.
  9. 09Filing tracker

    A filing tracker per market, with supply gates that follow the accepted answer

    • QA accepts the answer into the change. The QA change control specialist opens the answer and signs it into the change control, and only then do the gates follow its fields.
    • A package per authority. Each authority's manufacturing sections download separately, marked unsigned if anything changed after the signatures.

The CDMO writes the manufacturing text; the client owns each registration

Regulatory CMC signs the content and the recommendation, the writer keeps the core and the layers, QA keeps the gates, and MSAT vouches for the validation dates.

Regulatory CMC leads

Sign the CDMO's manufacturing content and recommendation for each client registration

  • Each market's paragraph, side by side
  • A package already read as a reviewer would
  • Dates to recommend from, not hopes
CMC writers

Keep the core files and market layers, and prepare each package

  • One core file instead of many copies
  • Proposed wording beside registered wording
  • Minor changes traced in bulk on a sample
QA change control specialists

Accept client answers into the change control and keep the supply gates

  • Gates that follow the client's fixed fields
  • Blocked allocations refused with the reason
  • A trace due date on each change
MSAT validation leads

Run the validation batches on the new line and confirm the report date

  • The reviewer's question routed to them
  • The protocol opened before they confirm
  • A dossier date that matches the plan
More screens

The new line is open in no market today, and blocked outright in one

Six more screens from the same change, from the core file nobody has traced yet to the market rules only the client can change.

The core file before anything is tracedManufacturers, batch formula and process sections as the dossier prints them, the registrations across the top, and nothing marked until the agents have read.
The writer signs firstThe CMC writer signs that the trace and recommendation were checked; the approver's line waits, and the CDMO's recommendation still needs the client.
Gates by line and marketThe old line stays open where approved; the new line waits for its validation report, its stability start or approval, and one market blocks it outright.
Registrations across every client productEach product with its client, plant and registrations, approved, in preparation or planned, filtered by client or plant, each product kept as one core file with its layers.
The CMC change management queue, each change with its trace due dateOpen changes by product with class and trace due date; minor ones can be traced in bulk, with a sample opened and two people signing the batch.
Market rule sets the client signsEach market's rule is entered and signed by the client's regulatory team and read only here; the CDMO's own settings change only once the CMC lead approves.

demoSample data, from the working solution.

The validation lead signs the report date the dossier promises each authority

CMC writer
Sees
This version of the package, opened to the end
Signs
As author: the trace and the recommendation checked
Regulatory CMC lead
Sees
The same version, opened again after any change
Signs
The CDMO's manufacturing content and recommendation, and how a failed batch is reported
MSAT validation lead
Sees
The validation protocol for the new line
Signs
The report date the dossier will carry
QA change control specialist
Sees
The client's answer, and any note a person opened
Signs
The answer accepted into the change control

A client's own market rules can be read here but changed only by the client

Choosing a filing routeThe route proposer suggests one per market from the guidance and the client's signed rules; the marketing authorization holder confirms it.
Editing registered textAgents draft a layer change for a dossier in preparation; registered wording changes only through the client's filing.
Opening a supply gateBlocking takes effect at once; a gate opens only on an accepted client answer and the route's own evidence.
Stating an unsupported shelf lifeNo layer may carry a shelf life the signed stability data do not support, whatever a planning sheet says.
Reading the client's noteA note typed beside the answer waits for the regulatory CMC lead to open it before the answer can be accepted.
Changing a client's market ruleEach market rule set is entered and signed by the client's regulatory team; the CDMO reads it and cannot edit it.

Every core paragraph names the batch record or report it was written from

Core manufacturing filesEach product's manufacturing sections and supplied stability summary, by version.
Registered text and market rule setsEach market's wording and the rules the client signed for it.
Change controls and equipment comparisonsWhat changes, where, and whether it shares design and operating principle.
Master batch records and validation reportsThe sources every core paragraph is written from.
Signed stability trend statementsThe shelf life the data support, never the planned one.
Quality agreements and client answersThe impact clock per client, and its fixed-field replies.

What CMC regulatory affairs teams ask about post-approval changes

What are post-approval changes?

Post-approval changes are changes to how an approved medicine is made, tested or packed after its registration is granted. Each market classes them by its own rules, from FDA's prior approval supplements, changes being effected and annual reports to the EU's types of variation, and the holder of the registration files them.

Who decides the filing category, the CDMO or the client?

The client, as the marketing authorization holder. The CDMO proposes a route per market with its basis, the client confirms or disagrees in fixed fields, and a disagreement with one route holds only that market.

Why fold a change into a dossier still in preparation?

Because a dossier in preparation is the cheapest place to add a planned change. Filed after approval, the same change becomes its own application with its own review clock, and the market is supplied from one line meanwhile. The rehearsal shows both dates before anyone recommends.

What if a market states equipment by class only?

Then a line change within the same class is not a registered detail there. The trace still searches that registration, finds no paragraph, and says what it searched and which rule explains the result.

How is a batch kept out of a market that has not approved the new line?

Supply gates are kept per line and market. An allocation request for a batch from the new line to a market whose gate is blocked is refused with the reason and logged, and QA disposition and the client's qualified person still decide release.

What happens when a market's variation rules change?

The route proposer reads which rules apply on the date the change is filed. The EU's revised variations guidelines apply only to filings made from their start date, so a change whose validation report lands later is proposed under the new codes.

Bring one product
filed in several markets.

Send the manufacturing sections a client filed in each market and one open change control, and we will trace it paragraph by paragraph.