# GMP Change Control Form Template for Pharmaceutical Sites

> Source: https://netray.co/tools/gmp-change-control-form-template
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Document a GMP change request with justification, impact on validation and filings, risk rating, implementation plan and QA closure.

## Category

compliance-legal

## Industry

Pharma and Life Sciences

## Audience

- Quality assurance
- Regulatory affairs
- Engineering
- Validation engineer

## Tool

**Kind:** template

**Output:** document

**Fields:**

#### Site

**Key:** company

**Type:** text

**Default:** Meridian Pharma Ltd, Plant 2

#### Change control number

**Key:** cc_no

**Type:** text

**Default:** CC-26-0042

#### Date raised

**Key:** date

**Type:** date

**Default:** 2026-10-19

#### Change owner

**Key:** owner

**Type:** text

**Default:** Manufacturing Engineering

#### Change type

**Key:** type

**Type:** select

**Options:**

- Permanent
- Temporary

**Default:** Permanent

#### Change category

**Key:** category

**Type:** select

**Options:**

- Process
- Equipment
- Facility / utility
- Material / supplier
- Specification / method
- Document / SOP
- Computerised system

**Default:** Equipment

#### Initial risk rating

**Key:** risk

**Type:** select

**Options:**

- Low
- Medium
- High

**Default:** Medium

#### Current state

**Key:** current

**Type:** textarea

**Default:** Tablet compression uses press CP-03 with a 36 station turret and manual feeder speed adjustment.

#### Proposed change

**Key:** proposed

**Type:** textarea

**Default:** Install a force-feeder with recipe-locked speed on CP-03 and update press operating SOP and batch record accordingly.

#### Reason / justification

**Key:** reason

**Type:** textarea

**Default:** Reduce weight variation events (three deviations in 12 months) caused by manual speed changes.

#### Impact summary

**Key:** impact

**Type:** textarea

**Default:** Equipment re-qualification (IQ/OQ/PQ), SOP and MBR revision, operator training. No change to formulation or registered process parameters.

#### Implementation plan

**Key:** plan

**Type:** textarea

**Default:** Install in planned shutdown week 46, execute qualification, run three confirmation batches, release for commercial use after QA approval.

**Blocks:**

#### Change Control Request

**Body:** Site: {{company}}
Change control number: {{cc_no}}
Date raised: {{date}}
Change owner: {{owner}}
Type: {{type}}
Category: {{category}}
Initial risk rating: {{risk}}

#### 1. Current state

**Body:** {{current}}

#### 2. Proposed change

**Body:** {{proposed}}

#### 3. Reason and justification

**Body:** {{reason}}

#### 4. Impact assessment

**Table:**

**Columns:**

- Area
- Impacted (Yes / No)
- Action / reference

**Rows:**

**0:** Product quality / specifications

**0:** Validated process or qualification status

**0:** Cleaning validation

**0:** Regulatory filings (variation / supplement)

**0:** Stability program

**0:** SOPs, master batch records, training

**0:** Computerised systems / data integrity

**0:** Suppliers / contract partners

**0:** EHS and utilities

#### Impact summary

**Body:** {{impact}}

#### 5. Implementation plan

**Body:** {{plan}}

#### Action tracker

**Table:**

**Columns:**

- Action
- Owner
- Due date
- Completed (date / initials)

**Rows:**

#### 6. Approval to implement

**Signatures:**

- Change owner
- Department head
- Regulatory affairs
- QA approver

#### 7. Closure and effectiveness check

**Body:** All actions complete: Yes / No
Effectiveness check date and outcome: ________________
Change closed by QA on: ________________

#### Closure approval

**Signatures:**

- Change owner
- QA head

**Notes:** A starting layout. Your approved change control SOP sets categories, approval levels and timelines. Do not implement a permanent change that affects the registered dossier before the required regulatory approval or notification. Not regulatory advice.

## Content

**Intro:** Change control is the system that stops a well-meant improvement from silently breaking a validated process. This form walks through the information a QA approver needs: what changes, why, what it touches, what must be validated or filed, and how the change is closed.

**Sections:**

#### How to use the form

**Body:** Describe the current state and the proposed state in plain words, then state the reason. Complete the impact table honestly, marking Yes where any validated process, filing, SOP or system is touched. Add the implementation plan with owners and dates. Export to PDF or Word, route it for approval before any physical or documentary change is made, and keep it together with the supporting risk assessment and test evidence.

**Bullets:**

- Raise the change before work starts
- Involve QA and regulatory affairs early
- List every document and system touched
- Define the effectiveness check before closure

#### What the guidelines say

**Body:** ICH Q10 treats change management as a core element of the pharmaceutical quality system, with evaluation by subject matter experts and assessment against the registered dossier. EU GMP Chapter 1 and Annex 15 expect formal change control for anything that can affect quality or validated status. FDA 21 CFR 211.100 requires written procedures to be drafted, reviewed and approved by the quality unit, with changes made the same way.

#### Risk and regulatory impact

**Body:** Rate the change with a documented method such as ICH Q9 risk assessment or FMEA. A like-for-like replacement is often low risk; a new supplier for an API or a change to a critical process parameter is high. Always decide whether the change needs a regulatory variation, supplement or notification before implementation. A change implemented first and filed later is a serious compliance finding in many markets.

#### Common mistakes and ERP notes

**Body:** Common failures are implementing before approval, closing without checking that actions finished, forgetting SOP and master data updates, and temporary changes that quietly become permanent. If the change affects bills of materials, routings, specifications or approved suppliers, the ERP master data must be updated under the same change number so planners and buyers use the new version.

**Cta:** Netray can help tie change control numbers to ERP master data revisions so nothing is released against an outdated BOM or routing. The form is free to use without any contact.

**Faq:**

#### What needs change control in a GMP site?

**Answer:** Anything that could affect product quality, the validated state, safety, data integrity or the regulatory filing: process parameters, equipment, utilities, suppliers, specifications, methods, SOPs, software and facilities. Like-for-like repairs are often exempt if defined in the SOP.

#### What is a temporary change?

**Answer:** A change with a defined end date or number of batches, for example using a substitute supplier of an excipient for one batch. It still needs assessment and approval, plus a defined return to the original state or conversion to permanent.

#### Who approves a change?

**Answer:** The change owner's department head, QA, and where relevant regulatory affairs, validation, EHS and engineering. QA always has final authority for GMP changes under the quality unit responsibilities.

#### How is an effectiveness check done?

**Answer:** Define the measure in advance: for example no weight deviations in the next ten batches, or trend of a critical parameter. Review it after enough batches and record whether the change achieved its goal before closing.

## Search terms

change control form template, GMP change control format, pharmaceutical change control procedure, change request form pharma, change control SOP template, change control impact assessment, ICH Q10 change management, change control checklist pharma

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json