
Free change control templates
Structure and guidance for every section, free. These templates are reference tools and are not part of the paid course. Change Control Essentials teaches the method behind them; regulatory variation submissions are not taught in the course.
Change request form
The record that opens a change: what is proposed, why, what it is expected to touch and how it is classified, written before anything is altered so that the assessment can be an assessment rather than a justification.
1. Identification
Change number, date raised, site, area, system or equipment, products and processes initially in scope, change owner, QA contact.
2. Current state and proposed state
What exists now, by document number, version, model, parameter or configuration, and what it will be after the change. Written in the future tense. If the change has already been made, stop and raise a deviation.
3. Reason for the change
The problem the change solves or the benefit it brings, with the evidence: deviation reference, CAPA number, trend, obsolescence notice, regulatory commitment or business case.
4. Change type and classification
Like-for-like, minor or major, decided against defined criteria with the rationale written out. Like-for-like requires a documented equivalence assessment, not a tick.
5. Regulatory assessment
Whether the change touches a registered particular in any market, with the variation category under Regulation (EC) 1234/2008 and the classification guideline, or the notified body notification for devices, and whether prior approval is needed before implementation.
6. Preliminary impact and functions to consult
Which functions must assess: validation, QC, regulatory, supply, quality agreements and customers, documentation, training, IT. Each named function is a required signature on the impact assessment.
- Which validated systems, processes or methods reference the thing being changed?
- Which customers or contract givers have a quality agreement that mentions it?
- Which procedures, batch records or training will need to change?
7. Pre-approval
QA approval to proceed to assessment and planning. Not approval to implement. Dated, and earlier than any action on the change.
Cross-functional impact assessment
The assessment each consulted function completes for a change, with the evidence for every 'no impact' conclusion, so that the record shows the impact was assessed rather than asserted.
Validation and qualification
Which qualified equipment, validated processes, cleaning validations and computerised systems the change touches; whether requalification or revalidation is required; the protocol or the rationale for not needing one.
Analytical methods and stability
Whether any test method, specification or stability commitment is affected, and whether a stability study or method verification is needed before or after implementation.
Quality agreements, customers and suppliers
Every quality agreement that mentions the item, whether notification or prior approval is required, and the date the customer was told. 'Not applicable' requires the list of agreements checked.
- Which agreements were reviewed, by reference?
- Which clause requires notification, and what is the notice period?
Supply and materials
Effect on approved suppliers, material specifications, incoming testing, lead times and stock of the current item. Whether both states will be in use at once, and how they will be distinguished.
Documentation and training
Every procedure, batch record, specification, drawing and form that must change, and who must be trained before go-live. Listed by document number.
- Which documents reference the current state?
- Who performs the task and how will they be trained before the change is live?
Risk assessment
The risk the change introduces and the risk it removes, assessed with a documented tool proportionate to the classification, with the controls that bring residual risk to an acceptable level.
Functional sign-off
Each consulted function signs its own assessment. A 'no impact' with no name against it is an assertion, not an assessment.
Implementation and effectiveness plan
Defines, before approval, what must be done, in what order, what must be complete before the change goes live, how it will be verified, and how you will know it worked.
Action plan
Every action with its owner and due date, marked as pre-requisite (must be complete before go-live) or post-implementation. Documents, training, qualification, customer notification and regulatory submission are almost always pre-requisites.
Go-live gate
The list of pre-requisites QA checks as complete, with evidence, before implementation approval is given. The gate is the difference between a change control and a to-do list.
Implementation approval
A second, separate approval, dated after the pre-requisites are complete and before the change is made. Distinct from pre-approval.
Verification of implementation
Evidence that what was implemented is what was approved: the installed part number, the final parameter, the deployed version, the effective document. Checked by someone other than the implementer.
Effectiveness check design
What will be measured, over what period or number of batches, against what acceptance criterion, by whom and when. Defined when the change is raised, not at closure.
Closure
Closed on the effectiveness result, not on completion of the actions. If the check fails, the record stays open and the follow-up change or deviation is referenced.
Learn the method behind the templates.
Change Control Essentials: 5 lessons, one worked case, 4 printable job aids, check questions, a 20-question final assessment and a certificate. About 2 hours, self-paced.