Practical guides · Practical guide

Introducing CSV in a mid-sized company: a procedure your team can use

In a small business, one person often holds several roles. A CSV framework needs to support that working arrangement and make decisions clear. Start with the systems already in use, available evidence and people who can answer outstanding questions. A limited pilot shows which procedures and templates the team actually needs.

Table of contents

At a glance

How does a mid-sized pharmaceutical company introduce CSV processes?

Start with an inventory of systems, their GxP relevance, owners and existing evidence. Assess outstanding risks and define usable procedures for implementation, changes, incidents and appropriate reviews. Test the approach on a limited pilot to see what the team can apply and what needs adjustment. Company size affects how available resources are organised, not the level of applicable requirements.

  • A system inventory requires purpose and ownership, not just technical names.
  • Few applicable methods can be more helpful than numerous underutilized templates.
  • New systems and incomplete stock records require different approaches.
  • A pilot must transition into ongoing responsibilities and receive appropriate training.

A system directory with technical alignment

Capture relevant applications including tables, interfaces, and external services. Describe the tasks they support and the records or decisions that depend on them. A server inventory can provide information, but it is insufficient on its own.

Assign responsibilities and known evidence. Flag unclear statements for visibility. A justified GxP classification is more helpful than a blanket assertion that all systems are critical or all are non-critical standard software. Annex 11, Section 4.3 requires a current inventory of relevant systems with their GMP functionalities; for critical systems, a current system description is required. This inventory should support further decision-making and be maintained and updated upon changes.

Sources: [1] [2]

Assign roles to existing staff appropriately.

In smaller organisations, a single individual may assume multiple responsibilities. Key factors include sufficient competence, available time, and clear authorisations. Necessary independence and professional oversight must not be replaced by a mere list of roles.

Clarify who defines requirements, provides technical information, evaluates results, and makes decisions regarding the intended use. Identify appropriate representatives and escalation pathways. An external consultant may provide support; however, operational responsibility and necessary expert decisions must still be established and organized.

Sources: [3] [1] [4]

A procedure from the new system to current operation

Assign the appropriate rules and owners to lifecycle tasks in the matrix. Multiple topics may be included in a procedure, as long as the workflow remains clear and understandable for your team.

The procedure should make these decisions transparent. A template may support documentation but must not replace the actual thinking process. If personnel cannot explain the purpose of a field, the use of that field should be reviewed.

A procedure from the new system to current operation
TriggerQuestion to be answeredUseful outcomeAnnex-11 Reference
New System What is required and how is suitability demonstrated? Limited requirements and appropriate substantiation 4
Change What influences the intended use? Rational assessment and appropriate follow-up actions 10
Disruption Which processes or records are affected? Traceable investigation and resolution 13
Review Are the condition and controls appropriate? Reasoned assessment of relevant information 11
Supplier Which contributions are appropriate and agreed? Understood Services and Responsibilities 3
System retirement How are required information records made available? Appropriate decision regarding data and dependencies No. 7, 17 for data availability and archiving

Sources: [1] [5]

Further reading:

Gaps in stock levels for newly introduced products differ.

An existing system without complete substantiation starts from a different baseline than a new project. Assess the current state of inventory and evaluate potential implications. Current investigations may provide relevant insights, but such findings must not be presented as evidence of past performance.

Prioritize based on significance and remaining uncertainty. A single comprehensive action—"retype all documents"—may overlook critical risks. For certain systems, targeted supplemental assessments should take precedence; for others, process boundaries, roles, or data flows must first be clarified. The approach should align with the actual problem at hand.

Sources: [1] [5] [6]

Select a pilot to validate the framework.

Consider a limited, relevant case with available stakeholders. A targeted update to a calculation template may be more appropriate than concurrently implementing an ERP system. The pilot should integrate requirements, risk assessment, validation evidence, and future operational responsibilities.

Observe where the procedure provides value and where it generates unclear or redundant work. Adjust it substantively before widespread implementation. A successful pilot does not automatically validate its applicability to all other system types. Differences in complexity and risk must still be considered.

Sources: [1] [2]

Example: Several application lists are consolidated into a system directory

Assuming a small operation has several application lists, but no common assignment of system and GMP function. Department, QA and IT first describe the actual use. A laboratory application carries out test results; in ERP certain functions can be relevant for material or batch processes. The test is directed to this concrete application and does not classify each module equally because of the product name alone.

In our example, each relevant entry is assigned a described purpose, a responsible role, and a link to existing validation evidence. Unclear functions are made visible by designating a responsible party and specifying the next clarification step. Based on this inventory, prioritized tasks for implementation, gap remediation, or operational use are derived. This example does not claim a prescribed classification into a fixed number of risk categories.

Sources: [1] [7]

Plan and operate training from the outset

Employees must be able to apply the relevant steps pertinent to their responsibilities. Train the procedure using actual case examples and assess remaining uncertainties. A single presentation with a signed attendance sheet provides only limited evidence of practical application.

Ensure ongoing maintenance is also addressed. Who identifies a new system? Who receives change notifications? Who takes over in the absence of a designated individual? A process reliant on a single unavailable employee may become disrupted in daily operations. Responsibilities and authorities must align with actual duties.

Sources: [3] [1]

Further reading:

Align the program scope with external support.

A suitable assignment can integrate analysis, pilot runs, process optimization, and supported implementation. Define clearly which tasks your team is responsible for and which are temporarily or permanently outsourced. Technical troubleshooting and resolution of inventory gaps should also be explicitly assigned.

The duration depends on the starting condition, system complexity, and level of stakeholder involvement. A fixed monthly figure alone neither reflects outcomes nor quality. A CSV program represents only a portion of your GxP compliance strategy: quality systems, training, supplier management, and internal audits must align with the system processes. For example, it does not replace independent evaluation of laboratory or manufacturing processes. Define clearly within the program scope which areas are addressed and which are linked to existing quality procedures. Establish verifiable intermediate milestones: clear inventory, defined responsibilities, completed pilot, and operational readiness. Value is derived from appropriate application, not from the volume of delivered files.

  • System purpose, responsibility, and evidence of traceability.
  • Assign roles according to skills and available time.
  • Decisions throughout the lifecycle supported by clear procedures.
  • Document gaps in existing evidence and address them according to significance.
  • Integrate pilot runs, training, and ongoing operation.

Sources: [4] [3] [1] [7] [8]

Further reading:

Project experience and collaboration

Build a CSV framework around the systems you already have

We develop the starting point with the staff who will carry out the work. We review the systems, existing evidence and decisions still to be made. A limited pilot shows which rules the team needs and where responsibilities can be organised more simply. If suitable procedures already exist, build on them. If the system inventory is unclear, first establish a reliable overview.

Frequent Questions on CSV Processes in SMEs

Do smaller companies face reduced GMP requirements?

Enterprise size alone does not elevate the actually applicable requirements. Chapter 1, Section 1.3 takes into account both scale and complexity when establishing or modifying the pharmaceutical quality management system. These factors influence the appropriate design of the organization; however, logical decision-making and adequate suitability remain essential.

Sources: [7] [3] [1]

Do we need a separate SOP for each lifecycle phase?

Describe the required tasks in such a way that personnel can apply them in daily practice. Multiple lifecycle phases can be combined into a single procedure or, if needed, managed separately. What is essential is that responsibilities and workflows remain clear; a fixed number of SOPs cannot be derived from this.

Sources: [5] [1]

Do we need to first complete all the old documentation?

First, assess and evaluate the current actual state and relevant risks, leading to an appropriate prioritization. Historical execution data must not be fabricated. Current, supplementary investigations must be documented with their actual timing and purpose.

Sources: [5] [6]

Can a person hold multiple roles?

This could be possible if suitability, resources, authorizations, and required controls are appropriately defined. A general release of any role combination would be inappropriate. Assess specific duties and necessary independence.

Sources: [3]

How large should the first pilot batch be?

It should include relevant decisions while remaining feasible for available personnel. A manageable case helps establish the framework. Particularly complex or acute crisis tasks may not be suitable for the first joint learning step.

How do we determine whether the new process is functioning?

Employees can explain an actual process, obtain required documentation, and edit changes with appropriate justification. Open questions are escalated to the responsible party. Verify this through specific case examples rather than solely by the number of approved procedures.

Sources and review date

Primary source date: 17 October 2026. The focus is on CSV processes within the human pharmaceutical GMP environment. Lifecycle matrix, pilot approach, and example directory serve as internal organizational tools. No universal template count, fixed project duration, or general exemptions based solely on company size are asserted. EU GMP statements relate to human medicinal products (EudraLex Volume 4). FDA sources pertain specifically to the designated US regulatory domain.

  1. European Commission: EU GMP Annex 11, Computerised Systems, January 2011 revisionHuman medicinal products – GMP; in particular, §§1–4, 7, 10–13, 16–17; specific application for each section.
  2. ICH Q9(R1): Quality Risk Management, official text from the European CommissionRisk-driven decisions, appropriate formalities, and handling of subjectivity; own matrices are implementation proposals.
  3. European Commission: EU GMP Chapter 2, Personnel, effective from 16.02.2014Personal, role-specific training and assessment of practical effectiveness; official EudraLex entry with original chapter.
  4. European Commission: EU GMP Chapter 7, Outsourced ActivitiesOutsourced GMP-related activities, suitability, responsibilities, agreements, and monitoring.
  5. European Commission: EU GMP Chapter 4, Documentation, January 2011 revisionControlled documentation and records; official EudraLex entry with original chapter.
  6. FDA: Data Integrity and Compliance With Drug CGMP – Questions and Answers, December 2018Data integrity in pharmaceuticals under CGMP; no reinterpretation of new tests into historical records.
  7. European Commission: EU GMP Chapter 1, Pharmaceutical Quality SystemQuality management, accountability, root cause analysis, CAPA and change control; no project budget allocation.
  8. European Commission: EU GMP Chapter 9, Self InspectionSelf-inspection, independence, evidence, findings and corrective actions; no official guarantee of existence.

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Combine the system inventory with an upcoming change request.

A brief system overview and a specific immediate trigger are sufficient for an initial boundary definition. This enables clarification of which decision should be addressed first and which scenario is suitable for a limited pilot.

  • GAMP 5 consulting →

    Understand how GAMP 5, EU GMP Annex 11 and 21 CFR Part 11 apply to your systems. We translate the relevant requirements into proportionate validation work and evidence your team can defend in an audit.

Send a project enquiry Customer testimonials →