Regulations and compliance · Practical guide

ICH Q10: which IT findings belong in management review?

A long list of closed tickets can coexist with an unresolved quality problem. During management review, examine how effectively IT supports the pharmaceutical quality system. Identify data and IT findings that warrant a management decision, allocate resources and verify whether the resulting measures work.

Table of contents

At a glance

Which decisions should management be able to make from IT and data findings?

Management should be able to identify cross-system risks or recurring weaknesses affecting the pharmaceutical quality system, the actions required and any resource gaps. Turn substantiated findings into questions that require a decision. ICH Q10 describes management review and improvement. That review does not replace ongoing incident handling or periodic assessment of individual relevant computerised systems.

  • Significance arises from impact, repetition, and necessary decision.
  • Key figures require a reference point and professional context.
  • A corrective action is not solely substantiated by ticket closure.

1. Link IT findings to the pharmaceutical quality system

Consideration is given to the application within the human medicinal product GMP environment. ICH Q10 describes a model for the pharmaceutical quality system and its continuous development. It complements regional GMP requirements; the text explicitly states that the additional content beyond this does not constitute new binding requirements.

Not every technical activity falls within the scope of management review. Decisions are relevant, for example, when repeated impacts on reliable data, controlled processes, or available evidence are observed. Even a single significant gap may necessitate a leadership decision.

Therefore, for each proposed reporting point, ask: What decision should management make? If only an operational ticket requires further processing, the existing operating process is often the more appropriate location. Urgent risks must not be deferred until the next regular review.

Sources: [1] [2]

2. Distinguish system assessment from management review

The periodic system assessment according to Annex 11 looks at the state and further suitability of a specific system. The management review according to ICH Q10 can draw overarching conclusions from this: lack of technical capacities, are responsibilities unclear or does a company-wide implemented measure not work?

Both tasks can leverage existing data and documents. There is no general requirement to establish separate document systems or duplicate reports. It is important that the distinct questions and decisions are clearly addressed.

Example: Three systems report repeated delays in user account deactivation. Individual system assessments address the respective control gaps. Management may additionally need to decide whether the shared personnel changeover process and its resources should be adjusted.

Sources: [2] [1]

3. Prepare test results as specific decision questions

ICH Q10 identifies performance indicators, feedback on outsourced activities, internal and external evaluations, and changes in the environment as potential contributors. For IT, these informations should be linked to their impact on quality, not merely to availability or cost.

The following internal reference guide separates raw test results, significance, and decision-making. It does not prescribe a universal management framework. Select only the points that are actually relevant to your quality system.

Labour assistance: From IT findings to management decisions
FindingQuality inquiryPossible control decision
Recurrent export gaps Are the required records available in the intended use context? Responsibility and resources for a common export standard
Outstanding critical supplier actions Which process controls remain inadequate? Escalation, alternative planning, or additional internal capacity
Similar data entry errors in multiple systems Does a common organizational interface fail? Process and responsibilities for personnel changes are being revised.
Recovery of important data has not been demonstrated Has the emergency readiness been actually demonstrated? Priority, test capacity, and permitted interim measures determine
Effectiveness assessment without reliable data Can the improvement actually be assessed? Define appropriate reference values and analyte detection methods

Sources: [1] [2]

4. Example: Closed is not necessarily effective

A facility is managing 12 IT-related quality findings. Nine tickets are closed, three remain open. The administrative closure rate is 9 ÷ 12 = 75 percent. For five of the nine closed actions, valid effectiveness verification is available; for four, such verification is still pending.

This does not mean that these four measures are ineffective. There is no proof of this. Likewise, "75 percent would be effective" a false statement. In relation to all 12 measures, five, i.e. about 41.67 percent, have been proven to be effective; for the remaining seven, this is not yet the case in this example.

For a management decision, it is additionally assumed that two of the four missing efficacy substantiations require the same heavily loaded department. This rationale applies only to this example and does not represent a statement about real-world companies.

Tracking actions from a management review
GroupCountStatement / Decision
Closed, efficacy demonstrated 5 Maintain evidence of documentation and remaining limitations traceable
Closed, effectiveness testing missing 4 Not counted as effective; clarify data collection and accountability
Still open 3 Assess risk and priority for each action item
Total 12 9 closed = 75 %; 5 with efficacy documentation ≈ 41.67 %
Resource bottleneck 2 of 4 missing justifications Assign targeted specialist capacity and decide on a verifiable follow-up step

Sources: [1] [2]

5. Ensure misleading metrics do not occur

A key performance indicator requires a clearly defined population and a comparable time period. If the action portfolio significantly expands or older cases are removed from the list, the rate may change, even if the processing quality has not improved. Clearly disclose such changes.

Separate risk from quantity. An open critical recovery justification may be more significant than numerous completed minor improvements. An average rate must not obscure these differences.

Repeat is warranting explanation. Identical ticket categories may arise from different root causes; different categories may reflect the same process weakness. Allow subject matter experts to explain the patterns before deriving resource or supplier decisions.

Sources: [1] [2]

6. Specify actions with verifiable outcomes

„IT shall improve“ is not sufficient justification for a decision. Identify the subject, responsible party, required support, and expected outcome. The meeting date shall be determined operationally; this article does not prescribe a general review or completion deadline.

In the example, the capacity to manage the two blocked effectiveness tests could be provided by the lead. The expected outcome is not only a closed schedule but also a robust demonstration that the implemented actions either prevent or detect the relevant errors. If this objective is not achieved, the next step requires a renewed assessment.

ICH Q10 identifies potential outcomes including improvements, resource allocation, training and changes to quality objectives. Record the decision and how it was communicated so that implementation and subsequent evaluation can be traced.

Sources: [1]

7. Preparation without additional report stack

If possible, use existing system evaluations, deviations, supplier reports and policy registers. QA and IT should jointly prepare the statements; process managers explain the technical consequences. The management decides on questions that concern their responsibility or resources.

  • Define the reporting period, data sources, and reference populations.
  • Critical individual out-of-specification findings and recurring patterns are distinguished.
  • Actions for missing efficacy documentation are to be separated.
  • Review approved actions regarding outcomes and limits.
  • For each point, formulate a specific decision question.
  • Identify resources, responsible parties, and expected evidence.
  • Communicate results and ensure their traceability within the existing system.

Sources: [1] [2]

8. Close the loop for the next evaluation

A sound management evaluation concludes with a traceable feedback loop: Which finding led to which decision, and what was the subsequent observed outcome? If the intended effect fails to materialise, this constitutes a new basis for decision-making and does not justify merely rephrasing the original objective.

Consider also new external conditions, such as changes in supplier performance or relevant regulatory developments. Not every publication necessitates immediate technical modifications; however, it may trigger a targeted evaluation if the organization's own process is affected.

The benefit arises from a small number of robust decisions. Extensive documentation lacking accountability and traceability provides leadership with less than a clear picture of risk, action options, and required support.

Sources: [1]

Further reading:

Project experience and collaboration

Prepare recurring IT findings for management review

Many closed tickets can conceal one unresolved cause. With IT and Quality, we examine selected recurrences and their effects on processes and data. An isolated operational fault may need a targeted measure. Cross-system weaknesses or capacity shortages may need a management decision supported by evidence. We identify who owns the action, what effect is expected and how to verify it later.

Frequently asked questions about IT in management review

Must every IT ticket appear in the management review?

No. Condense the relevant findings and decisions pertinent to the quality system. A single critical incident may be significant; routine processes may remain operational. The selection should demonstrate its professional relevance.

Sources: [1] [2]

Does the Management Review replace the periodic system evaluation?

No. The system assessment considers the current system status. The management review may derive broader questions regarding effectiveness, accountability, or resource allocation from this information. Both tasks may share existing information, without duplicating the same statement in documentation.

Sources: [2] [1]

Does ICH Q10 require a specific IT key performance indicator list?

The text identifies potential evaluation criteria and performance indicators, but does not specify a single IT list applicable to every operation. Select key performance indicators based on relevant processes and decisions. Reference baseline, time period, and statement limits should be clearly defined.

Sources: [1]

Why are nine closed actions not nine effective actions?

An administrative closure may be in place despite the absence of efficacy substantiation. In the example of this article, only five effects have been demonstrated. The four remaining effects are not automatically invalid; their efficacy status remains open and must be appropriately addressed.

Sources: [1]

Are 75 percent in the example of this article an adequate proportion?

This cannot be assessed solely from the ratio. The ratio reflects only nine out of twelve completed actions. Whether open items are acceptable depends on their impact and the existing controls. A volume-based ratio does not replace this evaluation.

Sources: [1] [2]

Must urgent risks wait until the next review?

No. A Management Review does not replace the need for timely escalation or operational action. ICH Q10 addresses appropriate communication and escalation. The specific response depends on the significance of the finding.

Sources: [1] [2]

Do we need a separate report solely for IT?

Not mandatory. IT-related questions may be incorporated into the existing Management Review. What is essential are clear contributions, understandable decisions, and their subsequent follow-up. An additional document is only justified if it supports this function.

Sources: [1]

What helps a small company the most?

A concise list of specific decision questions supported by verifiable evidence. Leverage existing registers, identify a small number of accountable personnel, and distinguish completed tasks from those with documented impact. The effort should align with the scope and complexity of your quality system.

Sources: [1]

Sources and review date

Sources checked on 7 October 2026 include ICH Q10, Step 5, effective June 2008, and the January 2011 revision of Annex 11. The context is GMP for human medicines. The numbers of actions and decision models are our examples and do not prescribe performance indicators.

  1. EMA/ICH: Q10 – Pharmaceutical Quality SystemEMA/CHMP/ICH/214732/2007, Step 5; assumed and effective June 2008, PDF edition September 2015. Sections 1.1–1.3, 2.4–2.6, 3.2.4 and 4.1–4.3.
  2. European Commission: EU GMP Annex 11 – Computerised SystemsRevision January 2011, applicable since 30.06.2011; §§ 1, 4, 6–7, 9–13, 16–17. Human Medicines GMP Guideline; no draft version.

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

From IT findings, clear decision-making at the leadership level is achieved.

We support you in consolidating relevant examples and gaps in evidence, defining appropriate key performance indicators, and embedding actionable measures with verifiable impact within your existing quality system.

  • Computer system validation →

    Bring your GxP systems into validated operation, from laboratory software, MES and eQMS to ERP. We define the scope, plan risk-based tests using GAMP 5 and hand the evidence to QA for release.

Send a project enquiry Customer testimonials →