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
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 ↓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
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.
Kept in separate copies
Built-in controls
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.
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.
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.
Sign the CDMO's manufacturing content and recommendation for each client registration
Keep the core files and market layers, and prepare each package
Accept client answers into the change control and keep the supply gates
Run the validation batches on the new line and confirm the report date
Six more screens from the same change, from the core file nobody has traced yet to the market rules only the client can change.
demoSample data, from the working solution.
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.
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.
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.
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.
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.
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.
A shortage is named weeks ahead, with a plan the client sees instead of a missed date.
1-min demoMaterial Expiry & Retest ManagementEvery date that would stop a batch is seen while there is still time to retest, swap or move it.
1-min demoExport Documentation CheckA wrong paper is found at the plant's export desk, before the goods wait at a border.
1-min demoSend the manufacturing sections a client filed in each market and one open change control, and we will trace it paragraph by paragraph.