Hold the master files and sign filings, letters, notices and agency answers
- Gaps found before an agency finds them
- Each change with its lanes and rules
- Earlier rulings applied to new changes
A drug master file solution for API makers and CDMOs that reads the DMF and ASMF against the batch records and finds where the file no longer says what the plant does. Each change is then routed to its amendment, the annual report, the client notice and the client's own variation.
See one master file checked screen by screen ↓A master file is written from the office, while the plant changes through change controls. Whether a change touches the file is decided once, at approval, usually by the change owner in a filing-impact field, and nobody reads the file against the batch records afterward.
One wrong answer leaves the file untrue for each batch made since, and the client's own filing with it. The two parts drift as well: restricted detail creeps into the part a client may forward, while that part loses what the client needs to justify its own specification. The annual report turns into a catch-all, and agency answers get written from memory.
Built forRegulatory CMC leadsRegulatory writersPlant QA headsMSAT leads
The file is written from the office, so a change the plant made can stay out of it until an agency finds it.
Kept in step by hand
Built-in controls
The holder finds its own gap and tells the client first, so each client's filing rests on a file that matches the plant.
The regulatory writer runs the file check, the QA head confirms the plant facts, the regulatory CMC lead approves the plan and signs the notice, and the client answers on its portal.
demoEach file, batch, solvent lot, person and date here is sample data, as are both companies.
The person who drafts the file never signs it, and plant facts carry a QA signature.
Hold the master files and sign filings, letters, notices and agency answers
Draft sections, amendments, notices, letters and the annual report
Confirm the plant facts a filing states and own the quality record
Confirm the process text and what moves between the two parts
Eight agents read, compare, route, guard and draft; the regulatory CMC lead and the QA head sign.
Splits both master files into statements, each with its page.
Compares each statement with the instructions, batch records, specification, approved suppliers and the solvent log.
Lays out what each change control owes under each file's rules and applies approved rulings.
Reads each open-part sentence for restricted detail, and the open part for what the client needs.
Builds the report's two lists from sent amendments and letters of authorization.
Drafts notices and letters of authorization from the routed lanes.
Drafts agency answers from the file and the plant's own data, with citations.
Reads the closed part as the agency assessor and the open part as the client.
Past the one change: the agency answer, the annual report, the client's lane, the files the plant holds, its audit record and its learned rules.
demoSample data, from the working solution.
A drug master file is a confidential submission to FDA in which an API maker describes how it makes its substance, so that clients can reference it in their own applications through a letter of authorization. Here agents read the DMF and its European counterpart, the ASMF, against the batch records and route each change to what it owes.
Each addition, change or deletion is filed as an amendment as it occurs, and each authorized party is told in writing. The annual report lists the period's amendments and authorized parties and does not report new changes, so the compiler refuses to add one.
The applicant's part may be read by the client; the restricted part is read only by the agency. The leak guard keeps route detail, process controls and critical-step limits out of the open part, and adds back what the client needs to justify its specification.
The regulatory CMC lead signs it, and the plant QA head co-signs the plant facts after opening the records they rest on. Once sent, the notice is frozen, and a later change opens a follow-up notice.
A certificate of suitability exists only for a substance with a monograph in the European pharmacopoeia. Where one exists, changes are filed under the certificate's own categories; where none does, as for the actives in this sample, the files view says so and watches for a monograph.
The change gets its lanes: an amendment, the annual report entry by date, the ASMF update, a written notice and the client's own variation. The plant QA head decides the quality record, and the client decides how and when to file.
The filing's impurity section is ready before validation starts, and every purge claim shows its sum.
1-min demoProcess Development Report AuthoringOne sourced set of claims carries the report, the impurity assessment and the PPQ protocol, and the client's reviewer can check each one.
1-min demoCompendial Change ManagementOnly the methods a new chapter truly binds are revised, each tested on the lab's own runs before the day it becomes official.
1-min demoSend one DMF or ASMF section with the batch records and change controls behind it; we will read it against the plant and route what it owes.