GMP Change Control Training: Plan, Assess and Close Changes Safely

Opens with a question about the smallest change at your site that could harm a patient, and a quick check on a change made this year. Covers three FDA cases: the October 2023 letter to Global Pharma Healthcare, where an artificial tears cap plug changed to one with a prehole without its impact being evaluated; the September 2026 letter to Bentley Laboratories over a rephased formulation made without revalidation; and Jubilant Generics, where a condition set in a 2017 change control was not followed after a batch failed assay. Draws out the common pattern, clears two myths, and introduces J-K-L Pharma's plan to replace the fifteen-year-old tablet press 3 in Mumbai, followed through the ten modules. It ends with a recap and three practice questions.

What you will be able to do

• Explain what change control exists to do at a GMP site
• Recognise the common failures behind recent FDA findings
• Describe the change followed through the course and how it is assessed

Why it matters

Knowing how small changes led to FDA findings helps you spot changes at your own site that bypass the system.

Practice: Practice: Why change control matters · 3 questions

Returns to the 2023 Global Pharma Healthcare letter, where FDA also asked the firm to review changes made outside its change management system. Defines change control as a formal system in which qualified people review proposed or actual changes that might affect the validated state, across materials, processes, equipment, premises and more. Covers the US and EU requirements in brief: changes evaluated before they are made, approved by the right people including quality, and checked afterwards. Shows where changes hide, in suppliers, software, settings and temporary fixes, a Tokyo tablet maker with editable recipe values, and when true like-for-like work, such as an identical feeder paddle, goes by a simpler route. Applies this to J-K-L's tablet press 3. It ends with a recap and three practice questions.

What you will be able to do

• Decide whether an activity is a change that needs change control
• Identify changes hidden in suppliers, software and settings
• Tell true like-for-like work from a change

Why it matters

Recognising every change, including those that start outside your site, is the first defence against unassessed risk.

Practice: Practice: What counts as a change · 3 questions

Starts with the 2026 Bentley Laboratories letter, where FDA asked for procedures that ensure changes are justified, reviewed and approved by the quality unit. Covers what a change request must state: what changes, why, where, when, who owns it and how big it is, with a technical justification giving the reason and expected benefit. Compares J-K-L Pharma's first draft with its second draft of change CC-0231, which keeps the new press and its weight control software in one record. Explains the single named owner, quality screening, registration and classification, assigning reviewers, and success criteria agreed before approval, such as tablet weight variation and rejects per batch. Shows a London packaging site's request form built around six questions. It ends with a recap and three practice questions.

What you will be able to do

• Write a change request that states scope and technical justification
• Set measurable success criteria before a change is approved
• Explain the roles of change owner, experts and quality

Why it matters

A clear request lets reviewers judge a change quickly and stops a vague description hiding a risk.

Practice: Practice: The change request · 3 questions

Returns to the artificial tears cap plug and the questions an impact assessment would have asked about sealing, sterility, the approved application and testing. Covers what an assessment looks at, as Annex 15 sets out: product, process, validation, cleaning, documents and people, systems and regulatory filings. Explains using quality risk management with effort and formality matched to the risk, as ICH Q9 revised in 2023 describes, and recording the reasoning, not just a score. Shows part of J-K-L Pharma's impact assessment for CC-0231, including a redesigned feeder housing with new internal corners found in the maker's documents. Ends the method with unintended consequences: default settings, shared equipment, downstream steps and data, and counting deviations caused by recent changes. It ends with a recap and three practice questions.

What you will be able to do

• Assess the impact of a change across product, process and systems
• Match the depth of assessment to the risk, as ICH Q9 describes
• Look for unintended consequences such as default settings

Why it matters

Finding all the effects of a change before it is made prevents the deviations that a weak assessment would miss.

Practice: Practice: Impact assessment · 3 questions

Opens with the question J-K-L's quality reviewer asked: does any approved application, in any market, describe the equipment, process or controls being changed? Explains that change control makes sure the filing question is asked and recorded for every change, while regulatory affairs answers it for each market and prepares any filing. Covers the US route with major, moderate and minor categories under 314.70, and the EU route with variations of Type IA, IB and II and extensions under the revised framework. Shows J-K-L's conclusion for the new press: minor for the US annual reports citing FDA's 2004 guidance, no EU variation, no Gulf filing, agreed with J-K-L Pharma Europe. Covers common filing mistakes and making a required filing a gate before first use. It ends with a recap and three practice questions.

What you will be able to do

• Make sure the filing question is asked and recorded for every change
• Outline the US and EU filing categories for changes
• Set a filing as a gate before first use where needed

Why it matters

Checking filing needs before first use stops a safe, validated change from being made before it is allowed.

Practice: Practice: Regulatory filings · 3 questions

Starts with FDA's December 2019 letter to Health Pharma USA, whose quality unit lacked procedures for change control and shipped products before review. Covers who approves a change: the responsible functions, with quality assurance at the start and at the end, and how formality matches the stage, with ICH Q10 Table III calling for a formal system in commercial manufacturing. Explains approving the plan before work starts and reviewing supporting data before final approval. Shows J-K-L Pharma's implementation plan for the new press, built from its impact assessment, turning findings into tasks, owners, dates and gates, with a way back if the change fails. Ends with checking that approval, first use, qualification and training dates run in the right order. It ends with a recap and three practice questions.

What you will be able to do

• Identify who must approve a change and at which stages
• Turn an impact assessment into a plan with tasks, owners and gates
• Check that approval, first use and training dates are in order

Why it matters

A plan approved first and evidence approved last makes each signature on a change record mean something.

Practice: Practice: Approval and the plan · 3 questions

Opens with FDA's finding that Bentley Laboratories did not revalidate after major process changes, did not follow its own validation master plan and retained no stability samples. Covers completing the qualification and validation set in the plan before first use, including software configuration. Shows what J-K-L's validation engineer found while testing the new weight control software: a lower alarm limit still at the maker's wider default, recorded as a failure, corrected, retested and protected by access controls and an audit trail. Explains drafting every affected document, training before the effective date, one clear effective date when the old way stops, and recording problems during implementation as deviations while the gate stays closed. It ends with a recap and three practice questions.

What you will be able to do

• Complete qualification and validation before first use
• Set one effective date with documents and training ready
• Handle a problem found during implementation as a deviation

Why it matters

Having everything ready before the effective date stops old and new documents or settings being used side by side.

Practice: Practice: Making the change · 3 questions

Returns to the Jubilant case, where a change condition was never followed, and to FDA's 2019 and 2026 requests for provisions to determine change effectiveness. Covers closing a change only when every task's evidence is in place, commitments are tracked and quality gives final approval on the data. Explains the effectiveness review against agreed criteria, and shows J-K-L's six-month review of the new press: weight variation met, rejects not met at first until a feeder speed setting was corrected through a small change, and no new deviations. Shows how the result went into the MET500 product quality review, feeds management review and trends, and led J-K-L to add a standing question on alarm limits to its impact assessment form. It ends with a recap and three practice questions.

What you will be able to do

• Close a change only when evidence and commitments are complete
• Run an effectiveness review against agreed criteria
• Feed change results into the product quality review

Why it matters

Checking months later that a change did what it promised catches problems that a closed record would hide.

Practice: Practice: After the change · 3 questions

Starts with the artificial tears cap plug as a supplied component changed without anyone at the site deciding it. Covers temporary changes with an end date and an assessment, as J-K-L used while the new press was installed, and emergency changes agreed with quality and assessed straight after. Works through a letter to J-K-L's purchasing team: the MET500 film coating supplier moving to a new factory in two weeks, and the steps to open a change control, request data, check the quality agreement's notice period and hold new lots. Explains contract manufacturer changes entering your own system, and equipment, premises, utilities and software changes, including configuration settings, limits, recipes, user roles and report templates. It ends with a recap and three practice questions.

What you will be able to do

• Control temporary and emergency changes with end dates and assessments
• Bring supplier and contract manufacturer changes into your own system
• Treat software settings and updates as changes to the validated state

Why it matters

Handling the special cases properly closes the routes by which changes most often slip around the system.

Practice: Practice: Special cases · 3 questions

Opens by setting the three FDA letters side by side, each asking for an independent assessment of the whole change management system. Covers measuring the system with indicators such as overdue, emergency and temporary changes and deviations caused by changes, and a Tokyo tablet maker that cleared a backlog of minor changes and improved its form. Works through a moment on a J-K-L line: an operator finds a setting that differs from the procedure after overnight maintenance, and must hold and report, not change it back alone. Explains each person's role, from noticing and reporting to owning, assessing, approving and deciding filings, what is changing, and J-K-L's press 3 change from start to end, then the final exam.

What you will be able to do

• Explain each person's role in noticing and reporting changes
• Measure a change control system with practical indicators
• Apply the whole change control method from request to review

Why it matters

Knowing your own part means changes are noticed and reported early, whatever your job on site.

Practice: Practice: Your role, the whole method · 3 questions