Change Control
A practical guide to assessing, approving, implementing and reviewing manufacturing changes while keeping site decisions, document revisions and regulatory submissions distinct.

On this page · 11 sections
- 1What change control means, and how it differs from document control
- 2Regulatory basis by jurisdiction, product type and source authority
- 3Change management across the lifecycle
- 4Which changes to screen: materials, recipes, equipment, systems and methods
- 5Classify impact and uncertainty before choosing the evidence and approvers
- 6The operational lifecycle: from request to effectiveness-based closure
- 7Connecting decisions, versions and review evidence
- 8Connect validation, CAPA and training, then define exception recovery
- 9Three worked cases: scale-up, supplier uncertainty and recipe-display rounding
- 10Failure modes that survive paperwork, and the controls that expose them
- 11Implementation checklist and evidence walk-through
How does Change Control apply to your shop floor?
Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.
01What change control means, and how it differs from document control
Change control is a documented process for evaluating, authorising, implementing and reviewing changes that may affect product quality, controlled operations or the validated state. This is an operational definition; pharmaceutical guidance in ICH Q10, section 5 describes the corresponding change-management lifecycle.
A change request records the proposal; submitting it does not authorise implementation. Its practical purpose is to expose affected operations and evidence gaps before the proposed condition becomes routine.
A useful request and its assessment answer four questions:
- What will change? Identify current and proposed conditions and the reason for changing.
- What could be affected? Assess consequences for product quality, process performance, equipment, systems and people.
- What justifies implementation? Identify supporting evidence, unresolved questions, required checks and who must authorise the change.
- How will effectiveness be reviewed? Define evidence of the intended result and checks for unintended adverse effects.
These neighbouring records have different operational purposes:
| Record | Main question | Typical output | Connection to change control |
|---|---|---|---|
| Document control | Which revision is authorised for use? | Revision history and controlled issue | Implements approved instruction changes |
| Deviation | What departed from an expected condition, and why? | Report and investigation | May identify a need for change |
| CAPA | Which causes need corrective or preventive action? | Action plan and effectiveness review | May propose a change as an action |
For example, changing a mixing-time instruction may call for process-performance evidence and risk-based validation; a new document revision alone does not demonstrate assessment of the operational change.
Conversely, an editorial correction may leave the operation unchanged. Screen the meaning, not the number of edited characters: correcting a spelling error differs from moving a decimal point in an operating limit. The site procedure should explain how to document that screening decision and route changes with operational consequences.
Within the quality assurance process, connect the change decision to affected instructions, investigations and actions without treating these records as interchangeable. This makes the reason for each revision traceable to the operational decision behind it.
02Regulatory basis by jurisdiction, product type and source authority
Use the affected product and market to select the legal basis. In the change record, distinguish binding requirements from official guidance and from the site's chosen operating practice. A familiar change-control template is not an applicability assessment.
Requirements and guidance have different roles
For US finished pharmaceuticals, 21 CFR 211.100(a) requires written production and process-control procedures, including changes, to be drafted, reviewed and approved by the appropriate organisational units, and reviewed and approved by the quality control unit. This is a specific procedure-change duty, not a standalone mandate for the complete request-to-effectiveness workflow described in this article. The site procedure should identify which affected units perform those roles rather than treating quality approval as the only review.
Related references for legal review include 21 CFR 211.186, covering master production and control records, and 21 CFR 211.68, covering automatic, mechanical and electronic equipment. Check the particular provision before mapping a duty to a change-control step.
| Scope and authority | Connection to change control |
|---|---|
| EU medicinal products — binding GMP requirements | Annex 15, Principle says planned changes to facilities, equipment, utilities and processes that may affect product quality should be formally documented, with their impact on validated status or control strategy assessed. |
| EU medicinal products — GMP quality risk management | Chapter 1, paragraph 1.12 describes quality risk management as assessment, control, communication and review of risks to medicinal-product quality. |
| EU GMP computerised systems — official guidance | Annex 11, section 10 says system changes, including configurations, should be controlled under a defined procedure. Section 1 bases the extent of validation and data-integrity controls on a justified, documented risk assessment. |
| US medical devices — FDA explanatory guidance | The FDA QMSR overview, Incorporation By Reference, identifies ISO 13485:2016 as incorporated by reference. Use the overview for orientation, then review the applicable regulatory and incorporated-standard clauses. The regulatory reference is 21 CFR 820.10. |
Site authorisation and regulatory filings
As operating practice, keep the site's implementation decision separate from the regulatory-affairs assessment of variations or post-approval change filings. The first concerns controlled implementation at the site; the second considers the affected product authorisation and market-specific regulatory route. Site approval does not replace that assessment. Connect the two workstreams through recorded conclusions and any resulting implementation prerequisites.
One specific example is the Annex 15 glossary definition of Design Space: movement outside the design space would normally initiate a regulatory post-approval change process. Identify the relevant process design space during assessment rather than relying only on an equipment's technical operating limits.
A practical applicability entry identifies the affected market, product or authorisation, cited provision, assessment owner, conclusion and implementation condition. Treat labels such as minor or major as site classifications unless explicitly tied to a particular regulatory filing scheme.
For food, supplements and chemicals, build the applicability check from sector-specific sources rather than borrowing the pharmaceutical examples above. For related scope checks, see pharmaceutical cGMP and the device quality-system framework. Assign an owner to resolve uncertain applicability before the affected implementation decision.
03Change management across the lifecycle
In operational practice, change control governs a defined change; change management also considers knowledge and interactions across related changes. These terms can overlap: this is a working distinction, not a legal definition.
ICH Q10, section 1.6.1 is pharmaceutical quality-system guidance: it recommends managing product and process knowledge from development through commercial life to discontinuation. It identifies technology transfer, validation, manufacturing experience and change-management activities as knowledge sources. The wider ICH Q10 framework places this knowledge within the pharmaceutical quality system.
In practice, connect completed requests to their supporting evidence. Record the conditions tested, acceptance criteria, results, unexpected effects and remaining uncertainties. Use management review to examine related changes together and direct supported opportunities into continuous improvement. Include unsuccessful trials where they explain a rejected option or a limitation of the chosen approach.
For example, assume a mixing-speed adjustment was assessed only at one batch size. A later transfer to a larger vessel should not treat that result as proof for the new scale. Carry forward the test conditions and limitations, then assess what additional evidence is needed.
When related requests overlap, identify their shared assumptions. A conclusion reached before another change took effect may need reconsideration against the combined operating condition.
04Which changes to screen: materials, recipes, equipment, systems and methods
Screen the object being changed, not just the document awaiting revision. These categories are industry practice, not universal legal triggers; apply them within the site's products, processes and quality system.
- Material or supplier: a food supplier's changed manufacturing site prompts review of supplier risk, qualification and material suitability.
- Formula or recipe: a supplement potency-adjustment rule changes how ingredient quantities are calculated.
- Batch size or operating range: a larger batch or wider temperature range.
- Equipment, facility or utility: a replacement mixer, altered room layout or changed water supply.
- Test method or specification: a different analytical technique, sampling approach or acceptance limit.
- Computerised-system configuration or interface: revised permissions, calculation settings or data mappings.
- Packaging, label or controlled instruction: a new closure, device drawing revision or chemical production cleaning-sequence change.
Trace an impact chain. A component substitution may alter formula quantities, leading to review of relevant master instructions—for supplements, the master manufacturing record—then purchasing specifications in material master data, incoming checks, operator training and existing stock. The component is the changed object; those records and operations are potentially affected, not automatically changed.
Record permanence and reach before assigning risk: temporary or permanent; one product or a family; one line or multiple sites. Check shared dependencies beyond the originating department. A shared cleaning system or calculation library can connect products that otherwise have separate manufacturing records.
For temporary changes, specify the end condition and who checks it. Record whether the intended endpoint is restoration, extension after review or replacement by a permanent change. Duration describes the proposal; it does not establish its quality risk.
05Classify impact and uncertainty before choosing the evidence and approvers
For EU medicinal-product manufacture, Annex 15, section 11.4 calls for evaluating planned changes across product quality, pharmaceutical quality systems, documentation, validation and regulatory status. The framework below is suggested site practice, not a prescribed scoring system.
Start the quality-risk assessment with affected product attributes and process capability. Check contamination or mix-up pathways, data-integrity effects and movement beyond validated boundaries. Assess detectability before product release, reversibility and evidence uncertainty. Record assumptions, evidence of equivalence and unanswered questions.
Separate demonstrated facts from assumptions. For each important uncertainty, state what information would resolve it and whether that information is needed before a trial, before operational use or during follow-up. This turns a general concern into a decision dependency with an owner.
| Site-defined class | Decision basis | Evidence approach | Review depth |
|---|---|---|---|
| Minor | Bounded impact with supported equivalence | Verify equivalence and affected records | Focused affected-function review |
| Moderate | Plausible process or cross-functional effects | Targeted trials, checks or qualification | Coordinated cross-functional review |
| Major | Potential effects on critical attributes, validated boundaries or broad product scope | Expanded studies with justified acceptance criteria | Multidisciplinary review |
Example assumption: a supplier changes a product-contact gasket's elastomer formulation but retains its part number. Neither low cost nor urgency establishes low quality risk. Investigate compatibility and cleaning performance; unresolved equivalence is not a basis for a minor classification.
Check whether proposed detection controls actually address the failure mode. A finished-product test may not reveal every contamination pathway or intermittent system error. Explain the control's coverage and limitations instead of assuming that existing testing makes the change low risk.
Define who evaluates each impact, accepts the proposed evidence and decides whether remaining risk is acceptable. Assign reviewers by affected expertise and process ownership; retain applicable approval requirements for every class.
Translate residual risk into actions: resolve missing information, narrow scope, strengthen testing or monitoring, or decline implementation. Record action owners, acceptance criteria and the rationale for accepting remaining risk. A numerical score must not replace an accountable approval decision.
06The operational lifecycle: from request to effectiveness-based closure
The seven stages below are suggested site practice, not a universally mandated sequence. Separately, for EU medicinal-product manufacture, Annex 15, section 11.7 calls for post-implementation effectiveness evaluation where appropriate.
- Request. Record current and proposed states, reason, owner, intended benefit and affected objects. Specify material codes, equipment IDs, system versions or instruction revisions to establish the change boundary. Include justified exclusions where similar equipment or products are outside the proposal.
- Assess. Identify dependencies and assign a site-defined risk class with a rationale. Consider effects on product quality, validation, documentation and connected systems. Define implementation acceptance criteria, effectiveness measures, evidence owners and an observation window. Assign the applicability assessment described above to a named owner.
- Approve the plan. The first decision authorises execution within the defined scope. Record the plan version, approvers and prerequisites. For recipe changes, coordinate with the recipe review and approval process. Make clear which activities may begin and which remain dependent on unresolved conditions.
- Implement. Perform authorised work and link each action to evidence: completed tasks, installed versions, test results and revised records. Capture discrepancies and their disposition alongside successful test results. Obtain review and approval for changes to scope or acceptance criteria before proceeding outside the authorised plan.
- Verify readiness. The second decision authorises controlled operational use. Confirm the effective date or batch boundary, treatment of work in progress, revised instructions and relevant training. Check the prerequisites identified during assessment. Link each applicable training record to the instruction revision concerned. Record who authorised use and any operating restrictions.
- Review effectiveness. Compare representative operational results from the planned window with predefined measures and criteria. Check coverage of affected products, equipment and operating conditions. Task completion or elapsed time alone does not demonstrate effectiveness. An effectiveness check can inform the method without making every change a CAPA.
- Close or take further action. The third decision records an evidence-based closure conclusion. If evidence is insufficient, justify extended monitoring, assign an owner, define interim controls and set a revised review date. If results are unacceptable, assess affected product and operations, decide whether to restrict use, and authorise corrective work or a controlled reversal.
For a staged rollout, identify the products, lines or sites covered by each readiness decision. Keep the observation window tied to actual use, including the conditions needed for evaluation, rather than only to the installation date.
Retain withdrawn and rejected requests with the decision-maker, date and rationale. Distinguish requester withdrawal from reviewer rejection, preserving the original proposal and assessment so that a later resubmission can address the earlier decision.
- RequestDefine current state, proposed state, rationale, owner and affected scope.
- AssessEvaluate impacts, uncertainty, evidence needs and implementation dependencies.
- Approve the planAuthorise scope, acceptance criteria, responsibilities and execution conditions.
- ImplementExecute approved tasks and capture actual results and exceptions.
- Verify readinessCheck evidence, training and the intended operational cutover.
- Review effectivenessEvaluate predefined measures and investigate unintended operational effects.
- Close or extendApprove the conclusion or assign justified additional work.
07Connecting decisions, versions and review evidence
A practical change-control record structure uses a stable change ID to connect the proposal with its supporting records. One request may have several assessments, decisions and implementation actions. Keep those relationships explicit so that reviewers can follow the evidence without reconstructing it from correspondence.
- Request: reason, assessed baseline, proposed version, risk classification and its rationale.
- Assessment: affected products, processes and records, assessor, evidence references and conclusions.
- Decision: assessment reference, authorised scope, approver, outcome, decision time and effective date.
- Implementation: action owner, planned completion, verified completion, verifier and version-specific result references.
- Effectiveness: predefined acceptance criteria, review owner, review timing, results, conclusion and follow-up actions.
A recipe supersession log helps trace version succession. Reference the version actually assessed, rather than a link that displays only the latest revision. Preserve the relationship between that version and its decision when linked content changes. The decision points are those described in the workflow above.
Record decision time separately from the effective date, and planned completion separately from evidence-verified completion. These dates answer different questions: when permission was given, when the new condition applied, and when the work was demonstrated complete.
Change Request
Defines the intended transition.
- change_id
- change_owner
- current_state
- proposed_state
Impact Assessment
Connects affected objects to reasoning.
- change_id
- affected_object_id
- risk_class
- risk_rationale
Approval Decision
Preserves the authorised decision.
- change_id
- approved_scope
- approved_by
- approved_at
Action Evidence
Connects execution to acceptance.
- change_id
- action_id
- acceptance_criterion
- evidence_ref
Effectiveness Review
Records the evaluated outcome.
- change_id
- observation_window
- review_result
- reviewed_by
08Connect validation, CAPA and training, then define exception recovery
As a practical coordination approach, use the change record to link investigations or CAPA, qualification or validation evidence, applicable document versions and completed training for affected roles. Not every change starts with CAPA, and not every CAPA requires an operational change. Where linked, distinguish change acceptance from the CAPA effectiveness check: whether the corrective action worked.
Select evidence by asking what the proposed change could invalidate, not by assigning every change a fixed number of validation batches. A risk-based validation assessment should identify the relevant baseline—such as qualified equipment configuration or a validated operating range—and specify challenge conditions, acceptance criteria and protocol or report references. Justify the evidence selected and any reliance on existing results, while meeting applicable validation requirements. Record which results must be accepted before implementation.
For EU medicinal-product manufacturing, EU GMP Annex 15, paragraph 5.32 addresses incremental changes over time within ongoing process verification. Consider their combined effect and assess whether additional actions, such as enhanced sampling, are needed.
If an acceptance criterion fails, stop or contain affected work and preserve the actual execution record. Assess affected material, equipment state and data before responsible personnel authorise a revised plan or justified rollback. Treat rollback as an assessed recovery action, not an assumed return to a valid state. Document the reason, recovery evidence and conditions for resuming work; do not backdate approval or silently expand the accepted scope. Urgent containment addresses immediate exposure, not the assessment needed for a permanent solution.
09Three worked cases: scale-up, supplier uncertainty and recipe-display rounding
These hypothetical cases illustrate industry-practice reasoning, not regulatory classifications or reported outcomes. Each decision remains conditional on evidence.
Case 1: Pharmaceutical blend scale-up
Assumptions: A pharmaceutical blend increases from 500 kg to 750 kg in the same mixer; one component remains at a 20% mass fraction. Its mass increases from 500 kg × 0.20 = 100 kg to 750 kg × 0.20 = 150 kg. Batch size increases by (750 − 500) ÷ 500 × 100 = 50%.
Impact and evidence: Unchanged proportions do not establish equivalent mixer performance at the larger fill. Material movement, blend uniformity and discharge segregation may differ. Compare fill with the equipment operating range; evaluate mixing time, speed, representative sampling locations, analytical results, and downstream transfer and filling effects. Define acceptance criteria before trials.
Decision: Designated reviewers should assess evidence against those criteria before authorising routine use. Plan an effectiveness review of routine-batch uniformity and segregation results.
Case 2: Food powder supplier facility change
Assumptions: A food powder supplier changes manufacturing facility without changing the nominal incoming specification. Shared-line allergen exposure at the new facility is unknown.
Impact and evidence: An unchanged specification cannot resolve an unknown exposure pathway. Compare facility allergen profiles, shared equipment, production sequencing, cleaning evidence, segregation arrangements, material characteristics and lot traceability. Review cross-contamination controls rather than relying solely on a matching certificate of analysis.
Decision: Defer an equivalence conclusion until the information gap is resolved. Depending on findings, consider revised receiving or handling controls, segregation of affected lots, and label assessment for intended products and markets. Trace existing stock to its originating facility before deciding disposition; uncertainty at the new facility does not necessarily apply to every lot.
Case 3: Recipe-display rounding
Assumptions: A generic recipe application changes from displaying masses in 0.1 g increments to rounding them to the nearest 1 g; stored precision is unchanged. The nominal target is 100.0 g; the hypothetical acceptance interval is 99.8–100.2 g, inclusive.
Impact and evidence: A stored value of 100.4 g displays as 100 g but exceeds the upper limit by 0.2 g. Test endpoints (99.8 g and 100.2 g), interior values (99.9 g and 100.1 g), and failures (99.7 g and 100.3 g). Check whether operator decisions, automated comparisons, exports and retained records use stored or displayed values. Distinguish display precision from balance capability relative to tolerance.
Decision: Do not classify the change as cosmetic until testing establishes unambiguous decisions and records. If rounding masks failures, revise presentation or decision logic and repeat affected tests.
10Failure modes that survive paperwork, and the controls that expose them
Use these illustrative practice checks at the lifecycle gates covered above. Inspect evidence of what changed, not merely whether the request has signatures.
| Failure mode | Observable warning | Preventive or detective control | Review evidence |
|---|---|---|---|
| Fragmented requests hide cumulative impact | Several requests affect the same process | Link requests affecting shared equipment, materials or processes; assess combined impact | Object-linked request list and combined assessment |
| Approved scope differs from deployed change | Installed settings differ from approved settings | Reconcile approved and executed configurations | Configuration comparison, discrepancies and dispositions |
| In-process stock crosses cutover unidentified | Old and new routes share unmarked stock | Identify the batch or inventory transition boundary | Lot list, status labels and routing records |
| Effectiveness criteria selected after results are known | Criteria first appear in the closure report | Record the measure, criteria and review timing before execution | Dated plan, acceptance criteria and results |
| Wrong procedure revision at point of use | Retrieved revision does not match the batch's authorised instructions | Test instruction retrieval against the cutover plan | Location, retrieved revision and test timestamp |
Use audit trail review to investigate unexplained configuration differences where those changes are logged.
For monthly trends, use two fractions. Overdue-action fraction: open high-risk actions past their due date divided by all open high-risk actions, both at month-end. Effectiveness-failure reopening fraction: distinct changes receiving effectiveness review that month and reopened that month because effectiveness failed divided by all distinct changes receiving effectiveness review that month. Report zero denominators as not applicable. Examine causes and ageing rather than treating closure volume as change quality.
11Implementation checklist and evidence walk-through
Use this practice-based review aid alongside the assessment and workflow above; it is not a standalone regulatory checklist. Record exceptions against the relevant decision rather than treating every unanswered item as an administrative follow-up.
- Scope: identify previous versions, affected products, equipment and records, and justified exclusions.
- Ownership: name the change owner, functional reviewers and closure decision-maker.
- Risk: confirm that the classification rationale addresses the implemented scope.
- Readiness: verify completion of the prerequisites identified during assessment.
- Evidence: link results to acceptance criteria established before execution; explain failures and unresolved actions.
- Cutover: identify the approved revision, first applicable batch or date, and disposition of superseded material.
- Follow-up: locate the effectiveness measures, observation window and conditions for closure.
Trace one changed object into use
As a suggested review method—not a prescribed audit sample size—choose an implemented change and trace one affected object. For a recipe, compare the approved revision with the version actually used in a batch record. Check that supporting evidence covers the authorised scope and operating conditions. Locate the effectiveness conclusion or a justified, authorised open review with an owner and due date, using the workflow above.
Then reverse the trace: start with an affected production record and find its authorising change decision. Investigate missing or inconsistent references, including whether other batches used the same version, and assign responsibility for resolving the gap.
Frequently asked questions
Q.Can a typographical correction stay within document control, or does it need a change request?+
Yes, where the site's procedure permits it after assessment; use the distinction explained in the definition section. In the document control record, retain the original wording, replacement text and rationale, and complete the site's applicable review and approval steps. Check for the same wording in translated instructions, labels and training materials. If operators may already have relied on the error, identify affected versions and work performed, and assign a historical-impact assessment alongside the correction.
Q.Does replacing equipment with the same model or part number establish that it is like-for-like?+
Not by itself; apply the approach in the risk-assessment section. Compare the replacement with the approved configuration specification, including firmware, product-contact materials, operating range, utilities, calibration requirements and interfaces. Ask engineering to identify differences that the catalogue number does not reveal. Record the comparison evidence, unresolved questions and installation or performance checks selected for the intended use. Where equivalence remains uncertain, assign an owner to resolve that uncertainty before accepting the replacement as like-for-like.
Q.What should happen when a temporary change reaches its expiry date but is still needed?+
Use the exception-recovery section to plan the decision before expiry: seek an approved extension, initiate a permanent change or arrange controlled reversion. For an extension, assess operating experience, cumulative exposure, outstanding actions and whether safeguards remain adequate. Retain the original expiry date alongside the approved new date and accountable owner. If expiry has already passed, record the lapse through the site's deviation process, identify affected operations and assess what occurred during the gap.
Q.Can one change request cover several products or sites with different implementation dates?+
Yes, where participating sites' procedures permit a shared record. Use a product-and-site matrix showing applicable versions, local assessments, prerequisites, approvers, implementation dates and effectiveness evidence. Identify which activities are shared and which remain local. Define each cutover by batch, campaign or another unambiguous boundary so that batch execution history remains traceable. Keep unresolved scopes open when another site finishes. If ownership or dependencies become difficult to follow, use linked child records with explicit criteria for closing the parent request.
Q.How should two open changes affecting the same process or system be assessed together?+
Use the risk-assessment section's method on the combined configuration, not just each request separately. For example, assess a faster transfer rate together with a shorter mixing time. Link the requests, identify shared assumptions and decide whether implementation order matters. Include any intermediate configuration that production will use in the testing plan. Assign one owner for interaction risks in the quality risk register. If either request changes, revisit whether the other request's assessment and evidence still apply.
Q.How should an urgent equipment replacement be documented if normal review could not happen first?+
Follow the exception-recovery section and preserve the actual sequence of events. Record the failure, immediate safety actions, replacement identity, installed configuration, times, personnel and authorization actually obtained. Use the site's emergency-change or deviation route to identify affected product, establish operating restrictions and assign checks before further use. Use maintenance logs and contemporaneous records to reconstruct the event, identifying later additions as such. Give the reviewer a clear list of completed actions, missing evidence and decisions still needed.
Q.How should a pending regulatory-affairs assessment affect an otherwise approved site change?+
Following the regulatory-framework section, keep the unresolved assessment as an implementation gate for the affected scope. Assign a regulatory-affairs owner, a target decision date and the evidence needed to clear the gate. In the quality assurance process, identify affected products and markets and specify which preparatory activities may proceed. Record who can authorize removal of the gate and how scheduling teams will be notified. Recheck the assessment if the proposed scope or implementation sequence changes.
Q.How can a low-volume manufacturer set an effectiveness-review window when batches are infrequent?+
Adapt the effectiveness-based closure approach in the operational-lifecycle section to actual production opportunities. For illustration, a site might plan to review the next two affected batches with a six-month calendar checkpoint; these are planning choices, not prescribed minima. Define the measurements, baseline and interim monitoring before implementation. At the checkpoint, record available evidence and any production opportunities still outstanding, then reassess safeguards and timing. Use a CAPA effectiveness check as a practical comparison when designing the review.
Primary sources
- 21 CFR 211.100 — Written procedures; deviations
- EudraLex Vol 4 Annex 11 — Computerised Systems
- FDA: Quality Management System Regulation (QMSR) overview
- ICH Q10 Pharmaceutical Quality System
- EudraLex Vol 4 Part I Chapter 1 — Pharmaceutical Quality System
- EudraLex Vol 4 Annex 15 — Qualification and Validation
Explore this topic
Change Control sits inside 4 overlapping topic clusters in our glossary. Every neighbour is one click away.
Electronic records, signatures, audit trail and ALCOA+ data-integrity principles.
ICH Q8/Q11/Q12 toolkit — Quality by Design, design space, control strategy, CPV and lifecycle management.
URS-through-PQ lifecycle, GAMP 5 categorisation and CSA's modern alternative.
HCT/Ps, blood cGMP, donor eligibility, ISBT 128 labeling and forward-tracing lookback.
Want to see how Change Control could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.
