This is a ready-to-use effectiveness review for an internal audit (self-inspection) program. It sits above any single audit report: instead of describing one audit, it rolls up a full annual cycle (or another defined review period) across every audit performed, and asks whether the program as a whole is doing its job, finding real problems, closing them with evidence, and getting better over time. It is written to feed directly into management review as a required input. Replace every <<FILL: ...>> placeholder with your own specifics, set your own document numbers and dates, and route it through your normal document control, review, and approval. A worked filled specimen follows the template. Verify each cited regulation against the current source before you rely on it. Using this template does not by itself create program effectiveness; the conclusion is only as honest as the underlying audit and CAPA data feeding it.
Document control header
| Field | Entry |
|---|---|
| Document title | Internal Audit Program Effectiveness Review |
| Document number | <<FILL: e.g. QA-AUD-RPT-EFF-001>> |
| Version | <<FILL: version, e.g. 1.0>> |
| Effective / issue date | <<FILL: date>> |
| Review period covered | <<FILL: from date>> to <<FILL: to date>> |
| Review cycle | <<FILL: e.g. annual, or per the defined program cycle>> |
| Document owner | <<FILL: role, e.g. Internal Audit Lead>> |
| Approver | <<FILL: role, e.g. Head of Quality>> |
| Related program document | <<FILL: internal audit program SOP / plan number>> |
| Feeds | <<FILL: management review meeting reference, e.g. management review REC-ID / date>> |
1. Purpose
This report answers a question that a single audit report cannot: taken as a whole, over a full cycle, is the internal audit program itself working? It rolls up every audit performed against <<FILL: SITE / ORGANIZATION>>’s internal audit program in the review period and evaluates schedule execution, finding volume and severity trends, repeat and systemic findings, CAPA closure and effectiveness performance tied to audit findings, and the health of the auditor pool. The report closes with a documented conclusion on program effectiveness and is a required input to management review under ICH Q10.
A single audit report tells you what one area looked like on one day. This report tells you whether the program, across every area and every audit, is catching real problems before someone else does, whether the same problems keep coming back, and whether the organization is actually spending its limited audit hours where the risk lives. Those are different questions, and conflating them is a common design gap: a site can run every scheduled audit on time and still have a program that is not effective, if the same finding reappears audit after audit and nothing structural changes.
2. Scope of this review
<<FILL: state the review period, which sites/business units are covered, and which audit types are in scope, e.g. "all scheduled, follow-up, and for-cause internal audits performed at Site X between 1 January and 31 December 2026, excluding supplier audits and regulatory inspections, which are covered separately.">>
3. Roles and responsibilities
| Role | Responsibility |
|---|---|
| Internal Audit Lead / Program Manager | Compiles the underlying data, drafts the review, identifies trends and systemic themes, proposes program changes. |
| Head of Quality | Reviews and approves the report, owns the effectiveness conclusion, escalates unresolved systemic risk to senior management. |
| Auditee area management | Provides input on whether audit findings reflected real operational risk and whether corrective actions held. |
| Senior management | Receives the report through management review, decides on resourcing or scope changes the review recommends. |
4. Schedule execution
Did the program do what it committed to doing? A program with a strong risk-based schedule that is not actually executed is not evidence of anything.
| Metric | This period | Prior period | Comment |
|---|---|---|---|
| Audits scheduled | <<FILL>> | <<FILL>> | |
| Audits completed | <<FILL>> | <<FILL>> | |
| Schedule adherence rate | <<FILL: %>> | <<FILL: %>> | |
| Audits slipped, with documented reason and reschedule | <<FILL>> | <<FILL>> | |
| Audits slipped with no documented reason | <<FILL>> | <<FILL>> | Any nonzero count here is itself a finding |
| For-cause audits triggered | <<FILL>> | <<FILL>> | List the triggering events |
| Follow-up audits triggered by prior significant findings | <<FILL>> | <<FILL>> | |
| High-risk areas audited at the required frequency | <<FILL: yes/no per area, or %>> | <<FILL>> |
5. Finding volume and severity trend
Trend findings across the whole program, not just within single audits. A declining count with a stable or expanding audit scope is a genuine signal; a declining count driven by a shrinking scope or softer classification is not.
| Metric | This period | Prior period | Two periods ago | Trend | Comment |
|---|---|---|---|---|---|
| Total findings | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | |
| Critical findings | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | |
| Major findings | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | |
| Minor findings | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | |
| Observations / OFI | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | |
| Findings per audit (average) | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | A program averaging near zero findings per audit for several cycles is a program not looking hard enough |
| Findings by area (top 3 by count) | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> |
6. Repeat and systemic findings
This is the section that most directly answers whether the program, and the CAPA system behind it, is actually effective. A repeat finding is the same underlying gap surfacing in more than one audit cycle for the same area; a systemic finding is a gap that shows up in similar form across multiple, otherwise unrelated areas.
| Finding theme | Area(s) affected | First identified | Number of cycles recurring | Root cause status | Escalation |
|---|---|---|---|---|---|
<<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL: closed / open / not yet reached>> | <<FILL: escalated to management review Y/N, date>> |
<<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> |
For every theme in this table, state explicitly whether the recurrence means the original CAPA was not effective, the CAPA addressed only a symptom rather than the root cause, or the finding is genuinely a new instance with a distinct root cause that happens to look similar on the surface. Treating every repeat as automatically systemic is as much a failure of rigor as ignoring a real pattern.
7. CAPA performance tied to audit findings
Findings that never close, or close without evidence, make the whole exercise theater. This section is the audit program’s view into the CAPA system’s performance on its own output.
| Metric | This period | Prior period | Target (set yours) | Comment |
|---|---|---|---|---|
| Audit-generated CAPAs opened | <<FILL>> | <<FILL>> | ||
| Closed on time | <<FILL: %>> | <<FILL: %>> | <<FILL>> | |
| Overdue, by severity | <<FILL>> | <<FILL>> | ||
| Closed at correction only, without a documented root cause | <<FILL>> | <<FILL>> | <<FILL: target 0>> | This is the pattern that produces next cycle’s repeat finding |
| Effectiveness checks performed for critical/major CAPAs | <<FILL: %>> | <<FILL: %>> | <<FILL: target 100%>> | |
| Effectiveness checks that failed (problem recurred despite a closed CAPA) | <<FILL>> | <<FILL>> | <<FILL: target 0>> | Each one gets reopened and reassessed for root cause, not just re-closed |
8. Auditor program health
The program is only as good as the people running it.
| Metric | This period | Comment |
|---|---|---|
| Auditors on the current qualified roster | <<FILL>> | |
| Auditors with qualification current (technique plus technical domain) | <<FILL: count / %>> | |
| Auditors overdue for refresher or requalification | <<FILL>> | |
| Independence exceptions logged (disclosed conflict, cross-site/contract auditor used) | <<FILL>> | Nonzero is not itself a problem if documented; undocumented independence gaps are |
| Auditor workload distribution | <<FILL: e.g. min/max audits led per auditor>> | Flags over-reliance on one or two auditors |
| Co-auditor / trainee slots used for auditor development | <<FILL>> | Shows the pipeline is being fed, not just the current roster used |
9. Comparison against external findings
Where available, compare internal audit results in scope areas against findings from supplier audits, regulatory inspections, or customer audits covering the same or adjacent scope in the period. A material gap, external parties catching things the internal program missed, is the hardest and most important honesty test available.
| External source | Area | Finding | Was it also raised internally, and when | Gap assessment |
|---|---|---|---|---|
<<FILL>> | <<FILL>> | <<FILL>> | <<FILL: yes/no, date if yes>> | <<FILL>> |
10. Program changes recommended
Based on the analysis above, state what the program should change for the next cycle: schedule reweighting, additional auditor qualification, a revised checklist for a recurring gap area, a scope addition, or a resourcing request.
| Recommendation | Basis (reference section above) | Owner | Target date |
|---|---|---|---|
<<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> |
11. Overall effectiveness conclusion
State a direct conclusion, not just a data summary. Address explicitly: is the program executing its schedule, is it turning up real and proportionate issues, are findings closing with evidence rather than promises, are repeat and systemic themes being escalated and addressed at the root, and is the program holding up against any external comparison available.
<<FILL: overall conclusion, e.g. "The internal audit program executed [X]% of its scheduled audits, produced findings at a rate consistent with a program that is genuinely looking rather than checking a box, and closed [X]% of audit-generated CAPAs on time with documented effectiveness evidence. One theme, [theme], recurred across two cycles and is escalated below as requiring a structural fix rather than a further round of local corrective action. No material gap was identified against available external audit results in the period.">>
12. Approvals
| Role | Name | Signature | Date |
|---|---|---|---|
| Prepared by (Internal Audit Lead) | <<FILL>> | ||
| Reviewed by (Quality Assurance) | <<FILL>> | ||
| Approved by (Head of Quality) | <<FILL>> |
13. Revision history
| Version | Date | Author | Summary of change |
|---|---|---|---|
<<FILL: 1.0>> | <<FILL: date>> | <<FILL: author>> | Initial issue. |
Filled specimen
The following shows the same report completed for a fictional annual review at “Acme Bio”, covering the 2026 internal audit cycle. The company, people, and numbers are illustrative; replace them with your own.
Header
| Field | Entry |
|---|---|
| Document number | QA-AUD-RPT-EFF-2026-01 |
| Review period covered | 01 January 2026 to 31 December 2026 |
| Review cycle | Annual |
| Document owner | R. Vance, Internal Audit Lead |
| Feeds | Q1 2027 management review, 14 February 2027 |
Schedule execution
12 audits scheduled, 11 completed, adherence 92%. One audit (warehouse, low-risk tier) slipped to Q1 2027 with a documented resourcing reason and a firm reschedule date. Two for-cause audits were triggered in the period: one after a confirmed aseptic process simulation failure, one after a complaint trend on a packaging line. One follow-up audit was completed, verifying the 2025 audit trail review corrective action (see below). All three high-risk-tier areas (sterile fill, QC chemistry, computerized systems and data integrity) were audited within their required annual frequency.
Finding volume and severity trend
| Metric | 2026 | 2025 | 2024 | Trend |
|---|---|---|---|---|
| Total findings | 31 | 39 | 44 | Declining |
| Critical | 0 | 1 | 0 | Flat, low |
| Major | 6 | 8 | 11 | Declining |
| Minor | 22 | 27 | 30 | Declining |
| Observations | 3 | 3 | 3 | Flat |
| Findings per audit (average) | 2.8 | 3.5 | 3.7 | Declining, but still turning up real issues, not near zero |
Top areas by finding count: QC chemistry laboratory (7), computerized systems and data integrity (6), sterile fill and aseptic (5).
Repeat and systemic findings
| Finding theme | Areas affected | First identified | Cycles recurring | Root cause status | Escalation |
|---|---|---|---|---|---|
| Audit trail review not documented for a subset of sampled sequences before release | QC chemistry, computerized systems | 2024 | 3 (2024, 2025, 2026) | Open, third instance | Escalated to this review’s recommendations, section 10 |
| OOS investigations closed without a supported root cause | QC chemistry | 2025 | 2 (2025, 2026) | Closed in 2026 with a revised investigation SOP; effectiveness check pending until Q2 2027 | Tracked, not yet escalated |
The audit trail review theme is assessed as genuinely systemic rather than three unrelated instances: each cycle’s corrective action addressed the specific system or team involved rather than the underlying gap, a disposition process that does not force the reviewer to attach evidence of the check before release. That structural fix is proposed in section 10.
CAPA performance tied to audit findings
28 audit-generated CAPAs opened in 2026 (one finding pair shared a CAPA). 86% closed on time (2025: 74%). Three overdue CAPAs at year end, all major, all more than 45 days overdue and escalated to the Head of Quality. Two CAPAs across the year were closed at correction only, without a documented root cause; both were minor findings involving a single missed signature, reopened and corrected to include root cause before final closure. Effectiveness checks were performed for 100% of critical and major CAPAs (6 of 6). One effectiveness check failed: the 2025 audit trail review corrective action for the QC chemistry lab was verified effective at 90 days but the gap reappeared in a different system 8 months later, which is the repeat theme recorded above.
Auditor program health
7 auditors on the roster, 7 with current qualification. 1 auditor is due for refresher training in Q1 2027, on schedule. No undocumented independence gaps; 1 disclosed independence exception (a cross-department auditor used for the packaging line for-cause audit because the qualified home-department auditor had recently transferred into that area), documented on the audit plan. Audit leadership was concentrated: 2 auditors led 8 of the 11 audits between them; broadening the lead-auditor pool is recommended in section 10.
Comparison against external findings
One supplier audit and no regulatory inspections occurred in scope areas during 2026. No material gap was identified: the packaging complaint trend that triggered the for-cause internal audit was also raised independently through the complaint system, and no external party identified an issue the internal program had missed.
Program changes recommended
| Recommendation | Basis | Owner | Target date |
|---|---|---|---|
| Add a mandatory attached-evidence field to the disposition step in all systems subject to audit trail review, closing the repeat theme structurally rather than per-system | Section 6 | IT Quality Lead | 30 Jun 2027 |
| Qualify 2 additional lead auditors to reduce concentration on 2 people | Section 8 | Internal Audit Lead | 31 Dec 2027 |
| Add a mid-year metrics checkpoint rather than waiting for the annual review, so a recurring theme is caught after 2 instances instead of 3 | Section 6 | Internal Audit Lead | Q2 2027 |
Overall effectiveness conclusion
The internal audit program executed 92% of its scheduled audits and both triggered for-cause audits when warranted, produced findings at a rate consistent with real scrutiny rather than a compliance exercise, and closed 86% of audit-generated CAPAs on time with effectiveness verification performed on all critical and major items. One theme, audit trail review evidence at disposition, recurred across three cycles because successive corrective actions treated it as a local fix rather than a structural one; this review escalates it as requiring the system-level change proposed in section 10, and recommends a mid-year checkpoint so a comparable pattern is caught sooner in future cycles. Overall, the program is judged effective with one identified structural gap now escalated for closure.
Approvals
Prepared by: R. Vance, Internal Audit Lead, signed 20 January 2027. Reviewed by: QA, signed 22 January 2027. Approved by: Head of Quality, signed 24 January 2027.
What this document catches that a single audit report misses
- A program with a clean schedule-adherence record that has never asked whether the same finding keeps coming back.
- Repeat findings tracked within each individual audit report but never rolled up and named as systemic across the program.
- CAPA on-time closure reported without ever checking whether closure meant genuine root-cause correction or just a correction that let the clock stop.
- No documented, defensible answer to “how do you know your internal audit program is actually effective,” beyond “we complete our schedule.”
- Auditor qualification and independence tracked per audit but never reviewed in aggregate, so a concentration or staleness problem across the whole roster goes unnoticed.
- No comparison against external audit or inspection results, so the program cannot say whether it is catching what a regulator or customer would catch.
How to adapt this document
- Set your document number, owner, and review period in the header, and point it at your real program governing document.
- Pull the underlying counts in sections 4 through 8 from your audit log, CAPA system, and auditor roster rather than re-deriving them by hand each cycle; if your systems cannot produce these numbers today, name that gap in section 10.
- Keep the repeat-and-systemic-findings table (section 6) honest: require an explicit root-cause-status call for every theme, not just a count of recurrences.
- Route the completed document into your management review agenda as a named standing input, referencing it by number rather than re-typing its content into the meeting record.
- Confirm every regulation cited below against the current published version before issue.
Regulations this supports
- ICH Q10, Pharmaceutical Quality System (internal audit / self-inspection as a management responsibility and input to management review, and continual improvement generally).
- EudraLex Volume 4, GMP Chapter 9, Self Inspection (self-inspections to monitor implementation of and compliance with GMP and to propose corrective measures).
- 21 CFR 211.22, Responsibilities of quality control unit (the quality unit framework a self-inspection program operationalizes for US drug GMP).
- ISO 13485:2016 clause 8.2.4, Internal audit, and clause 5.6, Management review, where the site or business unit is subject to the QMSR (21 CFR Part 820 incorporating ISO 13485:2016 by reference, effective 2 February 2026).
- ICH E6(R2)/E6(R3), for sponsor audit programs feeding an equivalent effectiveness review in a GCP context.