Deviation Report Format & Template — Free Excel Download (with Example)

2026-06-17

Download a free deviation report format and Excel template for pharma — with a filled example, classification rules (minor/major/critical), and the deviation-to-CAPA workflow. Aligned to ICH Q10, US FDA 21 CFR 211, EU GMP and India's revised Schedule M.

Deviation Report Format and Template — Free Excel Download with Filled Example

A deviation is any departure from an approved instruction, procedure, specification or standard. How you record it decides whether it stays a controlled, closed event — or becomes an audit finding. This page gives you a deviation report format you can use today: a ready Excel template, the field-by-field guide, a fully worked example, and the classification rules inspectors expect, aligned to ICH Q10, US FDA 21 CFR 211, EU GMP and India's revised Schedule M.

⬇ Download the Deviation Report template (Excel) — free, no sign-up. Drop it into your QMS and adapt to your SOP.

What a deviation report format must contain

These are the fields a defensible deviation record needs. This is the template — each field is something QA or an inspector will ask about.

| Field | What goes in it |

|---|---|

| Deviation No. / Date | Unique ID + date logged |

| Reported by / Department | Who raised it, from where |

| Date & time of occurrence / detection | When it happened vs when it was found |

| Product / Batch / Equipment / Area | What's affected |

| Type | Planned (pre-approved) / Unplanned |

| Classification | Minor / Major / Critical |

| Description | What actually happened vs what should have, per the SOP/BMR |

| Immediate action / containment | What was done at once (quarantine, line stop) |

| Impact assessment | Effect on product quality, other batches, validation status |

| Root cause | If investigated (5 Whys / Fishbone) |

| CAPA reference | Linked CAPA number |

| QA evaluation / disposition | Batch decision + justification |

| Status / Closure | Open / Overdue / Closed · approver · date |

A filled deviation example

| Field | Example entry |

|---|---|

| Deviation No. / Date | DEV-2026-058 · 12 Jun 2026 |

| Reported by / Dept | QC Analyst · Quality Control |

| Occurrence / Detection | Occurred 11 Jun (compression); detected 12 Jun (QC moisture test) |

| Product / Batch / Area | Paracetamol 500 tablets · Batch B-4471 · Compression Line 2 |

| Type | Unplanned |

| Classification | Major |

| Description | Tablet moisture content 4.8% against specification ≤ 3.0% — out of specification (linked OOS-2026-031) |

| Immediate action | Batch B-4471 quarantined; Compression Line 2 held |

| Impact assessment | One batch affected; no other batches on Line 2 since last clearance; validation unaffected |

| Root cause | Line 2 dehumidifier failed; not on the preventive-maintenance schedule (see CAPA) |

| CAPA reference | CAPA-2026-014 |

| QA disposition | Batch rejected pending CAPA effectiveness; root cause + CAPA tracked to closure |

| Status | Open |

This is one connected thread: a deviation triggered an OOS investigation, which fed a CAPA. Inspectors follow exactly that chain — so your formats must reference each other by number.

How to classify a deviation

Classification drives the rigour of the response, so get it right and justify it:

Minor — no impact on product quality, safety, efficacy or data integrity (e.g. a minor documentation error caught and corrected). Logged and corrected; may not need full root-cause analysis.
Major — potential impact on quality or a GMP-system breach (e.g. an OOS result, a missed in-process check, a temperature excursion). Requires investigation, impact assessment and usually a CAPA.
Critical — actual or high-likelihood impact on patient safety or product quality, or a serious data-integrity breach. Immediate escalation, full investigation, CAPA, and management notification.

Planned vs unplanned deviation

Planned (pre-approved) deviation — a deliberate, temporary, pre-authorised departure from a procedure for a specific reason (e.g. a one-off documented change for a single batch), approved by QA before execution.
Unplanned deviation — anything unexpected, recorded after it occurs. The example above is unplanned.

How to fill it (the parts people get wrong)

Description — state what should have happened (per the SOP/BMR) and what did. "Process deviation observed" is not a description.
Impact assessment — the field QA leans on. Address the affected batch and whether other batches, equipment or validation status are touched. "No impact" needs a justification.
Root cause + CAPA — a major/critical deviation that closes with no root cause and no CAPA is a classic finding. Link the CAPA number.
Status — keep it live. If you can't show open and overdue deviations on demand, that is the finding.

The deviation workflow behind the template

  Deviation occurs / detected
     -> Log + immediate containment
     -> QA classify (minor / major / critical; planned / unplanned)
     -> Impact assessment
     -> Investigation + root cause (major/critical)
     -> Raise CAPA  -> link CAPA no.
     -> QA disposition (batch decision)
     -> Closure -> feeds APQR & trending

Deviation sits at the centre of the quality system — it connects to OOS investigations, CAPA, market complaints, the wider QMS, and rolls up into the Annual Product Quality Review.

Why deviation control is required

ICH Q10 — deviation management is part of the Pharmaceutical Quality System.
US FDA 21 CFR 211.100/211.192 — any unexplained discrepancy must be investigated and recorded.
EU GMP Chapter 1 — deviations must be recorded and investigated within the PQS.
India's revised Schedule M — requires a deviation procedure with classification, investigation and CAPA.

From template to live system

A spreadsheet template gets you a consistent format; it doesn't get you control. On paper, deviations go missing, classifications are inconsistent, and "open vs overdue" is impossible to see. A workflow-based quality system makes deviation a controlled flow — QA classification is an enforced step, the CAPA link is built in, a live dashboard shows open/overdue deviations and trends, and a built-in audit trail supports ALCOA+ data integrity by design.

Frequently asked questions

What is the deviation report format?

The standard record for a deviation: deviation number, reporter, occurrence/detection, product/batch/area, type (planned/unplanned), classification (minor/major/critical), description, immediate action, impact assessment, root cause, CAPA reference, QA disposition and closure. Download the Excel template above.

Is the deviation template free?

Yes — the Excel template above is free, no sign-up. Adapt the fields and numbering to your SOP.

What is the difference between a deviation and a CAPA?

A deviation is the event (a departure from procedure). CAPA is the action you take to fix its root cause and prevent recurrence. A major deviation should link to a CAPA.

What are the types of deviation?

By timing: planned (pre-approved) and unplanned. By severity: minor, major and critical.

Which regulations require deviation management?

ICH Q10, US FDA 21 CFR 211, EU GMP Chapter 1, and India's revised Schedule M.

Flobri runs deviation management as a connected digital workflow — QA classification, impact assessment, an enforced CAPA link, a live open/overdue deviation dashboard and a built-in audit trail — so a deviation is a controlled event you can prove, not a form that goes missing. See how Flobri turns a process description into a live workflow.