Practical guides · Practical guide

Defining validation responsibilities for QA, IT and process owners

IT configures, the supplier tests and QA reviews, but who decides whether a result is acceptable or a deviation can close? Build the responsibility matrix around deliverables, decision authority, handovers and deputies. An interface example shows why a technical completion notice does not authorise GxP use.

Table of contents

At a glance

How should QA, IT and process owners share validation responsibilities?

A typical split is for process owners to define workflows, requirements and business acceptance criteria, and IT to prepare the technical environment and operations. The system owner maintains the version and evidence record. QA provides the oversight and release input assigned by the quality system. Suppliers perform agreed tasks. For each deliverable, identify who performs, decides, contributes and provides cover. An example RACI matrix does not replace formally assigned authority.

  • Start with verifiable results rather than a list of departments.
  • Separate the execution of a task from the decision regarding its outcome.
  • Assign responsibility only together with appropriate authorisations and capabilities.
  • Explicitly govern transfers, coverage, and transition into operation.

1. Assign task results instead of general duties

"IT is responsible for the system" sounds clear but leaves many decisions open. Who determines the technically correct material status? Who assesses whether a test covers the intended procedure? Who decides on further use in the case of a deviation? These questions relate to different outcomes, even when the same application is at the center.

Therefore, first of all, formulate the expected work results: coordinated requirements, suitable test environment, performed test, evaluated findings and documented usage decision. Each result includes comprehensible criteria. "Test done" can otherwise mean that someone has performed steps while another already assumes a positive professional evaluation.

A meaningful result description links subject and state: "Interface requirements with approved status values and error behavior aligned" is more precise than "clarify the interface." From this, the required knowledge, stakeholders involved, and decision authorities can be derived.

This approach is a practical guidance tool. It is intended to facilitate the clear implementation of existing organizational and quality rules, without creating an additional parallel structure.

Sources: [2] [4] [5]

Further reading:

2. Separate the regulatory framework from the RACI method

The example framework is Human Medicinal Product-GMP. Annex 11 outlines the collaboration between relevant functions, appropriate qualifications, access rights, and defined responsibilities. Chapter 2 links responsibility with authority and addresses the designation of duly authorized representatives. These foundations explain why a task delegation must function practically.

RACI is the format used in this example. None of the cited sources prescribes this table as a universal CSV template. Another clear method may achieve the same purpose. Assigning an identifiable decision role for each outcome is also a design recommendation.

A letter in the matrix does not confer any legally defined function nor expands an existing authority. Legal responsibilities, required independence, and internal release procedures remain decisive. Where multiple decisions interact, they are described separately, rather than consolidating authorities under a single "A".

Annex 15 provides for appropriate quality oversight throughout the validation lifecycle. This does not imply a general obligation to have QA alone approve each document or to prohibit QA from participating in any operational activities.

Sources: [1] [2] [4] [3]

3. The four RACI assignments are clearly defined

In this worksheet, R performs the agreed work or produces the contribution. A is accountable for the named result and has authority to decide within the defined scope. C provides the expertise needed before that decision. I is informed of the outcome and its consequences.

Explain these terms at the beginning of the team meeting. The English concepts "Responsible" and "Accountable" are easily translated twice as "verantwortlich" in German. Without a common definition, even when the table is fully completed, different expectations may arise. Use German descriptions directly in the columns as needed.

Information provided to an individual does not replace the necessity of formal involvement. If a department must assess the significance of a status value, a follow-up email regarding a previously conducted technical test is too late. Similarly, a C-assignment should address a specific question; providing a list of all possible point of contact delays decision-making.

A result may require multiple execution contributions. Then, who consolidates these contributions into a complete package? The matrix remains readable, without making professional input invisible.

Sources: [4] [2]

4. Build a matrix of results with comments

The following example matrix relates to a system project involving a relevant interface. The role designations are proposals and must be aligned with your quality system, your contracts, and actual authorities. No table row assigns a general legal responsibility.

For each row, specify the named individual or organizational role, representation, and location of evidence. I-Recipients should be conveniently summarized in a brief communication rule, for example: operation following completion of the test environment or affected users after usage decision.

When a decision combines technical evaluation and operational authorization, split the line. This makes it visible whether a test result, although accepted, cannot yet be utilized due to another prerequisite.

Own RACI work aid based on work results
ResultR: ImplementationA: Release decisionC: required contributionTransfer criterion
Requirements version Responsible process specialist Process owner IT, QA, affected interface partners Clear expected behavior and relevant failure cases.
Test environment IT Responsible System owner Test Lead, Supplier Status, data, and access rights are appropriate and documented.
Test execution Assigned Tester Named test lead Department and IT for inquiries Execution, results, and findings fully documented.
Professional assessment of results Technical Reviewer Authorised process owner QA and IT in accordance with the question posed Acceptance criteria and deviations evaluated in a traceable manner.
Usage decision Assignee Coordinator Internally authorised approval role Process, IT, and Quality Function by Responsibility Bring together the evidence, limitations and assessment of operational readiness.

Sources: [2] [4] [3]

5. Check authorities, competence, and delegation of responsibility together

A role is only effective if it can also make the assigned decision. Assess access to information, professional competence, available time, and the required organizational authority. A person may be responsible for the completeness of a protocol without being authorized to decide on remaining process risks.

Name representatives prior to the critical deadline. Document which responsibilities are delegated, the required qualifications, and where authorities are formally documented. Automatic forwarding of a mailbox does not transfer decision-making authority. The representative must also have access to the relevant documentation and up-to-date information.

In an SME, one person may hold several roles. Examine workload, conflicts of interest and the segregation requirements that apply. There is no general second-person review rule for every document. Where an independent assessment is required or forms part of risk control, preserve its effectiveness.

Therefore, assess role bundling specifically. A name change in the table does not resolve a conflict if both roles factually represent the same decision without independent verification.

Sources: [4] [2] [7]

6. Transfer procedures with inputs and closure criteria are described

Many accountability issues arise between two tasks. The supplier waits for test data, IT awaits target values, and QA receives a protocol whose deviations have not been evaluated. A matrix only reveals this gap when both the recipient and the required input are specified.

Describe for a test assignment, for example, the approved requirements, representative data, system status, and expected results. The handover to the technical reviewer includes execution evidence, deviations, and open questions. A simple status "completed" cannot replace this package.

Define how incomplete results shall be returned. The recipient should be able to clearly identify which information is missing and why it is required for the decision-making process. This establishes a professional accountability obligation instead of an endless cycle of comments.

Delivery deadlines also need alignment with the workflow. A decision on Friday is not realistic if critical raw information only arrives shortly before. Plan required involvement as work and identify bottlenecks early.

Sources: [5] [4] [2]

7. Integrate supplier contributions contractually and technically

Annex 11 Section 3.1 addresses clear agreements regarding the responsibilities of external parties for system performance. Therefore, describe whether a partner performs configuration, conducts tests, evaluates results, or assumes operational responsibilities. The general phrasing "validation included" leaves open the specific deliverables that are actually provided.

When actual GMP outsourcing activities are involved, Chapter 7 is relevant in addition. It addresses, among other things, agreed responsibilities, communication, and the recipient's evaluation of associated results. Therefore, every software purchase is not automatically equivalent to a comparable GMP outsourcing; assign the specific scope of services accordingly.

The company's matrix must align with the agreed performance obligations. If the contract covers only the test execution, the table should not implicitly assign the supplier broader usage rights. Conversely, an appropriately qualified external contribution may be utilized if its scope and authority are appropriately defined and agreed.

Also regulate inquiries, deviations, and changes during processing. Specify who is authorized to assign additional work and who assesses the technical significance of an unexpected result. A supplier's signature does not replace this reconciliation.

Sources: [2] [6]

8. Example: A status is technically correct but professionally inaccurate when transmitted

A pharmaceutical SME connects laboratory and commodity management system. A laboratory status should prevent the use of unreleased material in the target system. The supplier implements the transfer. For the test of this transfer, the following course is assumed.

The department defines the intended state: When a laboratory result is blocked, the affected material usage remains blocked within the planned workflow. IT provides an appropriate test environment and assigns the test objects. The supplier conducts the agreed test and documents the transfer.

In the example, a technically successful feedback is returned, yet the material appears available. The test supervisor verifies the completeness of the records; the technical reviewer assesses the unmet intended effect. No one explains the test solely due to the successful notification of pass. QA is included in the deviation evaluation according to the agreed responsibilities.

IT and supplier assess the status assignment. After controlled correction, the affected cases are re-evaluated, including a rollback to a locked state. The authorized role then reviews the technical outcome. The subsequent user decision takes into account additional requirements of the process.

If the process owner is unavailable, the authorised deputy appointed in advance decides on the same evidence. Escalate if no suitable deputy is available. The supplier does not acquire decision authority simply by being available.

Example: refined handovers in the interface scenario
StepLead contributionVerifiable result
Define the expected effect Process team with an authorised process owner Locked laboratory status prevents intended material usage.
Tests enable IT with System Owner Appropriate location, identified test objects, and effective access rights.
Document execution Supplier responsible Transfer record plus actual final business state.
Evaluate deviation Technical Expert and Authorized Decision Role Technical success at an incorrect target state remains a finding.
Provide justification for correction IT/Supplier, followed by professional assessment Affected status cases following a controlled change are to be re-evaluated.
Determine usage. Intern authorized role with required contributions Decision on defined scope; completion of testing alone is insufficient.

Sources: [2] [4] [5] [6]

9. Conflict, changes, and operational handover procedures

A clear matrix does not eliminate all disagreements. It, however, identifies who formulates the open technical question, which information is missing, and at which decision level action can be taken. A project deadline should not replace substantive discussion with a majority vote.

Establish an escalation procedure for resource shortages, conflicting requirements, and decisions outside approved authorities. Document the rationale. If new insights require a different role assignment, the matrix is updated and the change is communicated to affected parties.

With the completion of the project, responsibilities do not vanish. Assign change evaluation, incident management, access control, and regular system assessments to operations. Project leaders and implementation partners do not automatically remain permanently accountable.

During handover, verify that the new responsible party possesses the necessary access rights, knowledge, and documentation. A formal name assignment without actual assumption creates only a documented gap. Any existing actions must continue to have a clearly designated responsible individual and a duly authorized closing decision.

Sources: [2] [4] [7]

10. Introduce and maintain the matrix promptly and up to date

Start with a critical workflow and a few clear outcomes. Have the involved functions simulate their responsibilities in a specific case: who provides what, who makes decisions, who represents the function, and what happens in the event of a negative result? Only then is it worthwhile to expand the model to include additional project components.

For SMEs, preparation and binding involvement are more important than a large table. What is needed are organizational and release guidelines, process and system owners, performance agreements, and a realistic assessment of competence and capacity. Effort increases with unclear interfaces and conflicting contracts, not simply with the number of employees.

Review the assignment during personnel changes, new service provider, modified scope, or operational transition. Document the current valid version and avoid maintaining multiple conflicting copies. The following checklist assists in the final review.

  • Each row identifies a verifiable work outcome.
  • Execution and decision-making are linguistically clearly separated.
  • Decision responsibilities are assigned appropriate authorities and subject-matter expertise.
  • Required contributions are obtained in a timely manner; information alone does not substitute for them.
  • Representation, access, and available capacity have been clarified.
  • Agreement, quality system, and matrix do not contradict each other.
  • Transfers include inputs, results, and handling of open findings.
  • Escalation and responsibilities after project completion are defined.

Sources: [4] [5] [2]

Project experience and collaboration

Clarify responsibilities at an actual handover

QA, IT and process owners select an upcoming deliverable, such as a requirement or an assessed test deviation. Each role explains its contribution, decision authority and information needs. We resolve differences at that handover before creating multiple sign-off lists. In a small team, tasks may be combined where authority and required controls are preserved. For several sites or external partners, we also identify deputies and escalation paths.

Frequently asked questions about Responsibilities in validation

Is a RACI matrix required for validation?

The GMP sources referenced here require clear, appropriate responsibilities, but do not mandate a universal RACI template. Use the matrix when it enhances clarity of your processes. An equally well-structured alternative presentation can achieve the same objective. What is essential is that individuals understand their responsibilities, possess appropriate authorities, and that handovers actually function effectively. The mere existence of a completed table does not constitute evidence of this.

Sources: [2] [4]

What is the difference between R and A?

In the proposed work assistance, R performs the agreed work. A is responsible for the named result and has the decision-making authority. A supplier can, for example, carry out tests, while an authorized internal role evaluates their technical significance. Define these terms together, because both are easily translated only with "responsible". The definition does not extend any power of attorney.

Sources: [4] [2]

Can there be more than one 'A' in a line?

A clearly defined decision responsibility per outcome is generally easier to manage. However, this is a design recommendation, not a general legal rule. When actual multiple independent decisions or predefined shared authorities are required, these should be clearly separated. It is often helpful to split the line into a technical assessment and a subsequent usage decision, rather than consolidating distinct responsibilities into a vague outcome.

Sources: [4] [3]

Must QA approve each validation document?

A general assignment of this type cannot be derived from the aforementioned sources. The applicable requirements, your quality system, and the authorities established within it are decisive. Effective quality assurance oversight remains essential. Define the specific contribution of QA such that technical review, methodological validation, and decision-making are not merely substituted by a volume of signatures.

Sources: [3] [4]

Can the department simultaneously serve as process owner and tester?

This may occur organizationally, but must be evaluated on a specific basis. Assess competence, workload, potential conflicts of interest, and the applicable segregation requirements for the specific procedure. Not every document necessarily requires two different individuals. Where an independent review is mandated or intended as a necessary control, such a review must remain effective even in the presence of role bundling. Document the actual solution selected.

Sources: [4] [2] [7]

Are the System Owner and Process Owner always IT and domain expertise respectively?

Annex 11 defines the Process Owner as the individual responsible for the business process. The System Owner is responsible for the availability and maintenance of the computerised system, as well as for the security of data stored within it. This does not necessarily establish the same organisational assignment across all companies. Assign responsibilities to actual roles and consider shared services or external contributions. A suitable job title alone does not constitute sufficient authority or capacity.

Sources: [2] [4]

Who evaluates a test conducted by the supplier?

This must be agreed upon prior to execution. Separate the completeness of the supplied protocol from the technical evaluation of the results and any subsequent decision on usage. Depending on the scope of the task, appropriate external expert input may form part of the evaluation. However, the regulated entity must ensure that the required evaluation and decision actually take place and that its own requirements are adequately addressed.

Sources: [2] [6] [3]

How do we manage delegation for a release?

Name an appropriate representative with documented authority and access to the complete decision record. Clarify which tasks may be delegated and which boundaries remain. A mere absence note or spontaneous handover is insufficient. If no one can effectively represent, the process requires escalation or rescheduling; authority does not automatically transfer to the available project team member.

Sources: [4]

What do we do when the contract and RACI assign different responsibilities?

Resolve the discrepancy before the work or decision concerned. An internal table cannot silently extend an external contract. Compare the agreed scope, required outcome and actual authority. Update the relevant documents through change control and confirm the change with the parties involved. Until then, record the responsibility as open.

Sources: [2] [6]

How remains the matrix useful after go-live?

Transfer relevant responsibilities into routine operations: changes, incidents, authorities, evaluation of evidence, and open actions. Identify the responsible roles and verify their actual capability to act. Update assignments upon significant organizational or technical changes. A large project table does not need to remain unchanged; what is essential is a clear, up-to-date responsibility matrix for remaining tasks.

Sources: [2] [4] [5]

Sources and review date

Source: 6 October 2026. Reference: Human Medicines GMP. RACI legend, tables and interface case are own work aids; they do not replace valid organisational, contractual or legal rules of authority. Targeted supplementary reconciliation on 18.10.2026: Annex 11 No. 2 on cooperation and defined tasks as well as Annex 15 No. 1.3 on quality control. Annex 15 does not prescribe a general reporting line for all validation staff to QA; the division of roles in the contribution is an organizational example.

  1. European Commission: EudraLex Volume 4 – Current Human Medicinal Product GMP Framework
  2. European Commission: EU GMP Annex 11 – Computerised Systems
  3. European Commission: EU GMP Annex 15 – Qualification and Validation
  4. European Commission: EU GMP Chapter 2 – Personnel
  5. European Commission: EU GMP Chapter 4 – Documentation
  6. European Commission: EU GMP Chapter 7 – Outsourced Activities
  7. EMA/ICH: Q9(R1) – Quality Risk Management

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Clarify responsibilities and handovers in the validation project

We support you in clearly assigning work outputs, decision authorities, and supplier contributions. This results in a task delegation that aligns with your organisation and your specific system project.

  • 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 →