Change control exists for one reason: a validated, registered, inspected process is only valid, registered and inspected as it was on the day the evidence was produced. Every change after that day either keeps that evidence relevant or quietly invalidates it. The change control system is how a site knows which one just happened. When inspectors cite change control, it is almost never because the procedure is missing. It is because something changed and the system did not see it.
What the regulations require
EU GMP Chapter 1, paragraph 1.4(xi), lists among the requirements of the pharmaceutical quality system that 'arrangements are in place for the prospective evaluation of planned changes and their approval prior to implementation taking into account regulatory notification and approval where required'. Three words carry the weight: prospective, prior and regulatory. The evaluation happens before the change, the approval happens before the implementation, and the regulatory status of what is changing is part of the evaluation.
Annex 15 section 11 goes further for anything with a validated state. Paragraph 11.1 requires that 'the control of change is an important part of knowledge management and should be handled within the pharmaceutical quality system'. 11.2 requires written procedures describing the actions to be taken if a planned change is proposed to a starting material, product component, process, equipment, premises, product range, method of production or testing, batch size, design space or any other change during the lifecycle that may affect product quality or reproducibility. 11.3 requires quality risk management to evaluate planned changes, and 11.5 requires that after implementation an evaluation of effectiveness is carried out.
ICH Q10 section 3.2.3 describes the change management system as one of four PQS elements and expects it to provide 'a high degree of assurance there are no unintended consequences of the change'. Chapter 1 paragraph 1.4(xi) requires that arrangements are in place for the prospective evaluation of planned changes and their approval prior to implementation, and Chapter 4 requires that documents, including any changes to them, are approved, signed and dated by authorised persons before use. For active substances, EU GMP Part II section 13, which is ICH Q7 as adopted in the EU, requires a formal change control system to evaluate all changes that could affect production and control. For devices, ISO 13485 7.3.9 covers design and development changes and 4.1.4 changes to the quality management system, and the MDR requires that substantial changes to the design, the intended purpose or the quality management system are notified to the notified body under Annex IX.
What falls inside the system
The Annex 15 list is deliberately open ended. In practice, a change control is needed for any intended alteration to something that has an approved, validated or registered state. The following are the categories sites most often get wrong, either by not raising a change or by raising it after the event.
- Equipment and utilities: replacements that are not demonstrably equivalent, relocation, new components in the product path, control system changes, changes to critical alarms and set points.
- Process and product: parameters, batch size, hold times, order of operations, starting materials, suppliers of starting materials and primary packaging, specifications, shelf life.
- Facilities: room classification, HVAC balancing, layout, flows of people and material, new activities in an existing room.
- Analytical: method changes, instrument changes that affect the method, reference standards, acceptance criteria, laboratory software.
- Documents and systems: SOP changes that alter what people do, batch record changes, computerised system configuration, patches and upgrades, user role changes in a validated system.
- Organisational and outsourced: contract manufacturer or laboratory changes, quality agreement changes, transfer of an activity between sites, changes at a supplier that the quality agreement obliges them to notify.
Like-for-like: the exemption that is usually not one
Most procedures exempt like-for-like replacements from formal change control, and inspectors accept the exemption when it is defined and evidenced. A like-for-like replacement is one where the new item is identical in form, fit, function, material of construction and manufacturer part number to the item it replaces, so that every piece of qualification evidence for the old item applies without argument to the new one.
The exemption fails at the word identical. A pump of the same duty from another manufacturer is not like-for-like. A gasket in a different elastomer is not like-for-like. A software version that fixes a bug is not like-for-like. Sites that let the requester decide whether a replacement is like-for-like, without a documented equivalence check by someone competent to make it, end up with a maintenance log full of changes that the change control system never saw.
Changes hiding in other systems
Inspectors find uncontrolled changes by reading other records, not the change log. The places to look are the ones your own internal audit should look at first.
- Maintenance work orders: replacements described as 'fitted new', 'upgraded' or 'modified'.
- Deviation records: CAPAs that say 'parameter adjusted' or 'procedure revised' with no change control number.
- Document control: SOP revisions whose change history says 'updated to reflect current practice'. Current practice changed first; the document caught up.
- IT service desk tickets: patches, configuration changes, new user roles, database maintenance on validated systems.
- Supplier correspondence: notifications of changes to a material or component that were filed rather than assessed.
- Batch records: parameters recorded consistently outside the registered range, which means the process changed and the record did not.
Planned deviations and temporary changes
A 'planned deviation' is a deliberate, one-off, time-limited departure from an approved instruction. Many inspectors dislike the term because it is routinely used to make a change without change control: the same 'temporary' departure is approved every month for a year. If your procedure permits planned deviations, it must require a risk assessment and a hard end date, and it should oblige the reviewer to ask whether the third repeat is a change. A temporary change with a defined reversal, approved through the change system, is the cleaner instrument.
How the validated state is lost
No site loses its validated state in one step. It loses it through a series of individually reasonable decisions: a like-for-like replacement that was nearly like-for-like, a parameter widened slightly to reduce alarms, a supplier substitution during a shortage, a patch applied by IT, a method tweak in the lab. Each was small. Together, the process running today is not the one in the validation report, and nobody can say when it stopped being. Module 1 of the course starts from inspection findings of exactly this kind and works back to the system that would have caught each one.