WorkflowAPI & Drug Substance

Drug Master File (DMF) & CEP Authoring

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 ↓
Watch with transcript →
The problem

The change control said no filing impact; the file still says fresh solvent

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 Problem Today

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

  • Sections
  • Changes
  • Letters
  • Batches
  • Filing impact set at approvalOne field decides, and nobody checks it later
  • Open and closed parts driftRestricted detail leaks while the client's needs drop out

The Solution

  1. The file read as statementsBoth parts split into statements, each with its page
  2. Checked against the plantInstructions, batch records, specifications and the solvent log
  3. Routed by each file's rulesAmendment, annual report, ASMF update, notice and the client's variation
  4. Two people sign before it goesThe regulatory lead signs; the plant QA head co-signs the plant facts

Built-in controls

  • Agents never file, send or pick a filing class
  • Restricted detail stays out of client letters
  • Client answers move the case only through fields

What You Get

The holder finds its own gap and tells the client first, so each client's filing rests on a file that matches the plant.

  • A file clients can rely onBatch records and the file read against each other
  • Clients see their own actionEach change routed to what the client must file, and when
  • One filing, with dataThe client's variation goes in once instead of twice
Features

Drug master file checked against one plant's batch records, change by change

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.

  1. 01Two-part file

    Drug master file drawn as its open and closed parts, section by section

    • Each CTD section with its state. Current, changed since the last filing, owes an update or differs from the plant, shown once the agents have read it.
    • A change ledger down the spine. Each change control since the last annual report shows its DMF, annual report, ASMF, notice and client lanes in one column.
    • Report clock and leak meter on top. The writer sees the annual report's due date and how many open-part sentences carry restricted detail.
  2. 02Plant versus file

    The file's own page beside the batch record page that contradicts it

    • Both pages as they look. The restricted-part wording and the batch record entries sit side by side, highlighted where they disagree.
    • Batch by batch since the change. Each batch since the change is listed with its wash solvent and where it is now, so the extent is known before anyone writes.
    • Statements that agree are shown too. Each statement in the file lists its source, including the ones that still match the plant.
  3. 03Lanes

    DMF amendment, annual report, ASMF update and notice routed for one change

    • Each lane with the rule behind it. The amendment cites 21 CFR 314.420(c), the notice the quality agreement and the ASMF update EMA's procedure, and each lane names its owner.
    • A ruling that sends no-impact to a person. An earlier ruling on changed sources sends this change and one other to the regulatory CMC lead, though both were marked no filing impact.
    • The client's variation stays the client's. The lane says the client decides its own filing, and the quality record goes to the plant QA head.
  4. 04Open part

    Restricted detail moved out of the ASMF applicant's part, and a gap filled

    • Restricted detail moved by a person. Wash volumes, temperatures and an in-process limit were flagged, and each moved to the closed part on the writer's click.
    • The reverse gap found. The open part no longer told the client where an impurity forms and how it is purged, so a paragraph is drafted for the MSAT lead to confirm.
  5. 05Challenger

    Drafts read as the agency assessor and as the client before anyone signs

    • Two readers, one list. The assessor reads the closed part, the client reads the open part, and each point is settled by a drafter, rewritten or handed to a named person.
    • An overclaim in its own draft. The draft agency answer called a new supplier equivalent while the plant's trend showed an unknown impurity rising, so it was rewritten with the data.
  6. 06Filing plan

    Three filing paths played forward before the regulatory lead approves one

    • Amend now, hold and amend once, or revert. Each path shows its amendment date, how often the client files and its risk, with assumptions the writer can edit.
    • Proposed by the writer, signed by the lead. The writer's choice is logged as a proposal, and the regulatory lead's approval waits until that lead has opened the restricted page.
  7. 07Plant facts

    Plant facts co-signed by a QA head who first read the batch record and log

    • Two records opened first. The QA head must open the first recovered batch's record and the solvent log; the agents' summary table counts for nothing.
    • The signature says what was read. Its meaning states only what those two records show, and the deviation for batches made outside the file is raised alongside it.
  8. 08Notice

    Written notice to the client, signed by two people and frozen as sent

    • What changed, where, which batches, what next. The notice names the sections of each file, the batches made since the change, the filing plan, the related testing and the prior approval that was never asked.
    • Frozen when sent. A later change to the plan opens a follow-up notice with its own two signatures, and the one the client holds stays as it was.
  9. 09Client portal

    The client's regulatory lead answers the notice in fields on a portal

    • Received, variation planned, type and date. The client's answer moves its own lane on the change ledger, and nobody retypes an email.
    • Questions go to a named person. Anything typed is set aside for the regulatory CMC lead to read and changes nothing by itself.

The writer drafts, the regulatory lead signs, QA owns the plant facts

The person who drafts the file never signs it, and plant facts carry a QA signature.

Regulatory CMC leads

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
Regulatory writers

Draft sections, amendments, notices, letters and the annual report

  • What changed, read from the plant
  • Drafts challenged before review
  • The annual report built from sent amendments
Plant QA heads

Confirm the plant facts a filing states and own the quality record

  • The two records to open, named
  • A co-signature limited to what was read
  • The deviation raised in the same step
MSAT leads

Confirm the process text and what moves between the two parts

  • Each moved sentence to confirm
  • A drafted paragraph on impurity fate
  • The open part kept descriptive

The annual-report compiler refuses to report a new change in the annual report

Eight agents read, compare, route, guard and draft; the regulatory CMC lead and the QA head sign.

File reader

Splits both master files into statements, each with its page.

  • Never edits the file
Consistency checker

Compares each statement with the instructions, batch records, specification, approved suppliers and the solvent log.

  • Never decides whether a gap is a deviation or a filing
Change router

Lays out what each change control owes under each file's rules and applies approved rulings.

  • Never clears a no-impact a rule sends to a person
  • Never files
Leak guard

Reads each open-part sentence for restricted detail, and the open part for what the client needs.

  • Moves a sentence only on a person's click
Annual-report compiler

Builds the report's two lists from sent amendments and letters of authorization.

  • Never lists a new change as reported
Letter drafter

Drafts notices and letters of authorization from the routed lanes.

  • Never sends
  • Never puts restricted detail in a client letter
Answer drafter

Drafts agency answers from the file and the plant's own data, with citations.

  • Never calls material equivalent without the data behind it
Challenger

Reads the closed part as the agency assessor and the open part as the client.

  • Leaves each of its points for a drafter or a person to settle
More screens

The solvent change's amendment lands a day after the annual report is due

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.

An agency answer rewritten with the trendThe answer to an FDA information request lists the eight batches since the second supplier, the unknown at RRT 1.18 rising from 0.03% to 0.07%, below 0.10%.
The annual report's two listsAmendments since the last report and the authorized parties under their letters; the solvent change is left out, since a new change goes in an amendment as it occurs.
The client's lane after its answerOn the change ledger, the solvent change shows the notice sent and the client's variation planned with its target date, beside the sections it touches.
Each file the plant holds or suppliesMaster files by product and client, 37 change controls touching a filed process with the agents' reading, and no CEP until an active gains a monograph.
Who signed what, after opening whatEach signature with its reason and meaning, from the QA head's co-signature to the notice sent and the client's answer; the whole record downloads for an inspector.
A ruling becomes a rule only once approvedA changed source or grade is never no filing impact without the lead's signature: approved. A proposed rule on recovered solvent in a filed step waits.

demoSample data, from the working solution.

The QA head's co-signature covers only what two opened records show

Regulatory writer
Sees
The gap, the lanes and the three filing paths
Signs
Nothing: proposes the filing plan and prepares the drafts
Regulatory CMC lead
Sees
The restricted page the change touches and the proposed plan
Signs
The filing plan, the notice, agency answers, the annual report and learned rules
Plant QA head
Sees
The first recovered batch's record and the recovered-solvent log
Signs
The plant facts in the notice, and the deviation for batches made outside the file
MSAT lead
Sees
Each sentence moved between the parts and the drafted paragraph
Signs
The process text of the open part
Client's regulatory lead
Sees
The frozen notice on the portal
Signs
Its answer in fields, and its own variation

No agent files, sends a notice or decides a filing class

Filing or sendingAmendments, notices and agency answers go out only once the regulatory CMC lead has signed.
Deciding a filing classWhether a change owes an amendment is decided by the regulatory lead; the router only lays out the lanes.
Calling a gap a deviationThe plant QA head decides the quality record and raises the deviation.
Moving restricted text aloneThe leak guard flags a sentence; a person moves it and the MSAT lead confirms.
Deciding the client's variationThe client chooses its own filing and answers in fields.

What regulatory CMC leads ask about a drug master file

What is a drug master file?

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.

When does a DMF need an amendment instead of the annual report?

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.

What separates the open and closed parts of an ASMF?

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.

Who signs a notice to clients about a change?

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.

Does it cover certificates of suitability?

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.

What happens when the file and the batch records disagree?

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.

Bring one master file
and its last batch records.

Send 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.