# GMP Deviation Report Template for Pharma Manufacturing > Source: https://netray.co/tools/gmp-deviation-report-template > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Write a structured pharmaceutical deviation report: event, immediate action, classification, impact, root cause, CAPA and QA approval. ## Category quality ## Industry Pharma and Life Sciences ## Audience - Quality assurance - Production manager - Quality control analyst ## Tool **Kind:** template **Output:** document **Fields:** #### Site **Key:** company **Type:** text **Default:** Meridian Pharma Ltd, Plant 2 #### Deviation number **Key:** dev_no **Type:** text **Default:** DEV-26-0187 #### Date of occurrence **Key:** date **Type:** date **Default:** 2026-10-12 #### Date detected **Key:** detected **Type:** date **Default:** 2026-10-12 #### Reported by **Key:** reporter **Type:** text **Default:** Compression operator, Shift B #### Area / equipment **Key:** area **Type:** text **Default:** Compression Suite C1, Press CP-03 #### Product and batches affected **Key:** batches **Type:** text **Default:** Metformin HCl Tablets 500 mg, batch B26-1042 #### Deviation type **Key:** type **Type:** select **Options:** - Unplanned - Planned **Default:** Unplanned #### Initial classification **Key:** class **Type:** select **Options:** - Minor - Major - Critical **Default:** Major #### Description of event **Key:** desc **Type:** textarea **Default:** During compression, the in-process average weight check at 10:40 showed 618 mg against a limit of 617 to 683 mg after a feeder speed change. Compression was stopped after the third failing sample. #### Immediate action taken **Key:** immediate **Type:** textarea **Default:** Press stopped, feeder speed reset, material from 10:15 to 10:40 segregated and tagged on hold. QA informed at 10:50. #### Impact assessment **Key:** impact **Type:** textarea **Default:** Product quality: segregated tablets may be underweight. Other batches: no shared equipment in use. Validation status: no impact. Regulatory filing: no impact. #### Root cause **Key:** root **Type:** textarea **Default:** Feeder speed was changed manually without updating the weight check frequency. Human error, with a contributing gap in the operator instruction. #### Corrective and preventive actions **Key:** capa **Type:** textarea **Default:** Corrective: reject held tablets after 100 percent weight sort. Preventive: lock feeder parameters to the recipe, revise SOP step 6.4, retrain operators. **Blocks:** #### Deviation Report **Body:** Site: {{company}} Deviation number: {{dev_no}} Type: {{type}} Initial classification: {{class}} Date of occurrence: {{date}} Date detected: {{detected}} Reported by: {{reporter}} Area / equipment: {{area}} Product and batches: {{batches}} #### 1. Description of the event **Body:** {{desc}} #### 2. Immediate action / containment **Body:** {{immediate}} #### 3. Impact assessment **Body:** {{impact}} #### Impact checklist **Table:** **Columns:** - Area - Impact (Yes / No) - Justification **Rows:** **0:** Product quality, identity, strength, purity **0:** Other batches or products **0:** Validated state / qualification **0:** Stability or retained samples **0:** Regulatory filing or marketing authorisation **0:** Data integrity **0:** Patient safety / recall potential #### 4. Root cause analysis **Body:** {{root}} #### 5. Corrective and preventive actions **Body:** {{capa}} #### CAPA tracking **Table:** **Columns:** - Action - Owner - Due date - CAPA / change control no. - Status **Rows:** #### 6. Batch disposition recommendation **Body:** Release / Reject / Rework / Hold pending investigation: ________________ #### Approvals **Signatures:** - Initiator - Department head - QA reviewer - QA head (closure) **Notes:** A generic starting layout. Your own deviation SOP defines classification criteria, timelines (many sites require initiation within 24 hours) and approval levels. Not legal or regulatory advice. ## Content **Intro:** A deviation is any departure from an approved instruction, procedure, specification or established standard. This template gives you the sections a QA reviewer and an auditor expect to see: facts, containment, impact, root cause, CAPA and a disposition decision. **Sections:** #### How to use it **Body:** Complete the fields with the facts as known at the time, not conclusions. Describe what happened, when, where, which batches and equipment, and who noticed. Keep the immediate action separate from the root cause, because containment happens within hours and the investigation takes days. Export to PDF or Word and attach supporting data such as chromatograms, alarm logs and the executed batch record pages. **Bullets:** - State facts and evidence, not blame - Record the time QA was informed - List every batch and equipment ID potentially affected - Link to CAPA or change control numbers #### Classification: minor, major, critical **Body:** Most sites classify by potential effect on product quality and patient safety. A critical deviation could affect patient safety or product quality in a way that makes the batch unsafe or non-compliant, such as sterility failure or mix-up. A major one could affect quality but has a lower likelihood. A minor one has no effect on quality, such as a missed signature caught the same day. The initial class can be revised after impact assessment. #### Root cause that withstands an audit **Body:** Avoid closing with operator error as the sole cause. Use a structured method such as 5 Whys or a fishbone covering man, method, machine, material, measurement and environment. If human error is real, ask why the system allowed it: unclear instruction, poor interface, workload, missing training. Preventive action should change the system, not just retrain. Trend deviations monthly to see repeating causes. #### Common mistakes and ERP linkage **Body:** Frequent findings are late initiation, vague descriptions, impact assessed only on the affected batch, CAPA with no due date and closure without effectiveness check. If your ERP holds the batch status, place the batch on quality hold in the ERP (for example a blocked or restricted stock status) when the deviation is opened, so it cannot be shipped before closure. **Cta:** Netray can help connect deviation data to ERP batch status so open deviations are visible at the point of release. This template is free to use without any contact. **Faq:** #### What is a planned deviation? **Answer:** A planned deviation is a temporary, pre-approved departure from a procedure, such as using an alternate equipment train for one batch. It needs QA approval before it happens, an impact assessment and a defined scope, unlike an unplanned event found after the fact. #### How soon should a deviation be reported? **Answer:** Immediately on detection, and most quality systems require formal initiation within 24 hours or one working day. Late reporting is a common inspection observation, so record the detection time and the time QA was notified. #### Is a deviation the same as an OOS result? **Answer:** No. An out of specification result is a failed test result handled through an OOS investigation, which may lead to a deviation. A deviation covers any departure from procedure, including events with no failing result. #### Does every deviation need a CAPA? **Answer:** Not always. Minor, isolated events may close with correction and a documented rationale. Major and critical deviations, and repeating minor ones, should have corrective and preventive actions with owners, dates and effectiveness checks. ## Search terms deviation report template, GMP deviation form, pharmaceutical deviation report format, deviation investigation report, planned and unplanned deviation, critical major minor deviation classification, deviation report example, deviation management SOP template --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json