Practical guides · Practical guide

How to write an RFP for computer system validation services

Two proposals for the same computer system validation can cover very different work. Give each supplier the same system description and specify which tasks your team will carry out. This guide provides a sample request, a pricing sheet and a worked comparison for external validation work in EU GMP manufacture of human medicinal products.

Table of contents

At a glance

What should a CSV request for proposal include?

Give each bidder the same system scope, process and data flows, current configuration and available evidence. Specify deliverables, the client's responsibilities, review cycles and acceptance criteria. Ask bidders to itemise testing, retesting, expenses and assumptions on the same pricing sheet. Before award, confirm who will do the work, how you will oversee it and how you can access the records.

  • Fill in the sample request with your system details and the evidence you already have.
  • Show drafting, execution, review and handling findings separately on the pricing sheet.
  • When commissioning external validation work, establish the agreement and the qualifications of the people assigned.
  • Resolve open rows on the same basis for every bidder.

What does a supplier need in a request for quotation?

Use the following outline for the request. Mark unknown information as open and assign someone to resolve it. For a critical system, an existing system description may already provide key details. Annex 11 section 4.3 addresses its content. The outline is our planning aid.

You could write, “Please quote for the deliverables described in the brief. Identify missing information, assumptions and what you need from our team. Price preparation, execution, review and handling findings separately. Set out what still needs to be resolved before work starts.” Adapt the wording to your project.

Worked outline for a CSV request for quotation
FieldInclude in the requestExample of a usable entry
Project Purpose and relevant decision Make the effective SOP available after documented review
System Product, version, deployment model and environment Name the service and tenant. Identify the test and target versions.
Scope Processes, sites and user groups Drafting, review, approval and read-only access at site A
Data flows Interfaces, exports and migration Historical documents initially remain accessible under controlled legacy access
Existing evidence Documents with version and status Requirements draft available. Role configuration under discussion.
Deliverables Conclusions the evidence needs to support Demonstrate the approval route, effective version and appropriate access
Working arrangements Templates, repository, tools and language Company SOPs and controlled project repository. Evidence required in German.
Assessment Person doing the work, reviewer and approval route Process team explains the intended rules. Designated roles assess results.
Internal contributions Data, access, contacts and dates Document owner supplies test data. IT provides test accounts.
Pricing sheet Services included and supporting assumptions Fixed work-package prices or estimated effort, including retests, review rounds and expenses
Quotation process Questions, submission and desired start date Enter calendar dates and the responsible contact

Sources: [1]

Provide documents with their actual version and status

Create an index of documents, versions, environments and the claim each document supports. A test draft has a different status from an approved result. Supplier testing can provide evidence when it maps to your intended use. Annex 11 section 3.3 addresses checking the documentation supplied with off-the-shelf software against user requirements.

A contents list, redacted examples and identified gaps may suffice for an initial quote. Agree access, working environment and confidentiality before sharing sensitive information. A supplier requesting another document should be able to explain what question it would answer. Keep unexamined evidence as an assumption in the estimate.

Sources: [1] [2]

Further reading:

Assess the provider and agree responsibilities before award

Annex 11 section 3.1 expressly includes third parties that validate computerised systems. It calls for formal agreements with clear responsibilities. Under section 3.2, competence and reliability are key selection criteria. The need for an audit depends on risk.

For outsourced GMP activities, Chapter 7 addresses the contract giver’s prior assessment of the contract acceptor (7.5), provision of required information (7.6), monitoring performance (7.7) and assessing the results (7.8). Subcontracting requires the contract giver’s prior assessment and approval of the arrangements (7.11). The contract sets responsibilities and communication (7.14–7.15), makes records available to the contract giver (7.16) and permits audits (7.17).

Chapter 2 section 2.23 addresses consultants’ education, training and experience in relation to the assigned work. It calls for records of name, address, qualifications and type of service. Ask who will actually work on the assignment. A company logo and corporate CV do not establish the qualifications of the individuals.

Sources: [1] [3] [4]

Further reading:

A pricing sheet for comparable services

Ask each bidder to fill in the same rows with a price or effort estimate and its assumptions. Record why any package is excluded and assign a person to resolve work that is still open.

Add travel, on-site work and other expenses where relevant. Ask whether technical implementation is included or priced separately. Labels such as “OQ” and “validation package” do not define that division of work.

What to include in the pricing sheet
Work packageAsk what work is includedClarify on the pricing sheet
Initial assessment Examine existing evidence and remaining gaps Inputs, effort limit and deliverable
Requirements and risks Clarification, drafting and agreement Customer inputs and review rounds
Test preparation Cases, expected results and suitable data Who provides the data and environment
Test execution Run the tests and record traceable results Number of test runs included and who is responsible
Findings Assessment, coordination of corrections and retests Boundary between assessment and technical remediation
Final assessment Bring results and open issues together Review, revisions and approval route
Handover Explain evidence, decisions and operational tasks Repository, access and practical instruction
Additional services Work arising from changes in scope Agreed terms and decision route

Plan your team’s contribution for each work package

Record a person, deliverable and date for each internal contribution. In the SOP example, the process team could define what makes a document version effective, IT provide test access and the designated reviewer assess draft results. Assign the roles that fit your organisation.

The table is a planning aid. Chapter 7 section 7.6 provides the basis for supplying the necessary information and sets no universal review deadline.

Internal contributions by work package
ContributionResolve before work startsEffect of missing input
Process rule Who decides the status and permitted use? Requirements and tests remain provisional
Test basis Who provides suitable example data and reference results? Testing cannot start on a reliable basis
Environment Which version is ready and who grants access? The schedule must be revised
Review Who assesses which deliverable, and by when? Completed drafts are still awaiting a decision.

Sources: [3]

Distinguish acceptance of the service from authorisation to use the system

A supplier can prepare and verify evidence for a later decision. Accepting its contracted deliverables and authorising use of the system are separate decisions. Specify what the supplier delivers and what your organisation is responsible for assessing afterwards.

Under Chapter 7 section 7.8, the contract giver reviews and assesses the results of outsourced activities. Agree acceptance criteria and a way to resolve review comments. Receiving every file does not establish that the agreed scope, outstanding findings and their significance have been assessed.

Sources: [3]

Comparing two proposals with different scopes

In this example, proposal A covers draft tests. Proposal B also covers execution and handling findings. The remaining tasks are unclear in both. Leave days and prices open until those gaps are resolved.

Assign an owner and an effort estimate to every open row before comparing totals. Investigate gaps in B as well as A. The larger initial quote may still leave work for your team.

Worked comparison of two proposals
DeliverableProposal AProposal B
Draft tests Included Included
Test data and environment Unspecified. Clarify. Unspecified. Clarify.
Test execution Internal work or additional commission Included
Handling findings Excluded Included
Final assessment Unspecified. Clarify. Unspecified. Clarify.
Input from process specialists Required Required

Questions to resolve before awarding the work

Log each question, the response, the affected pricing row and the decision. Treat a new requirement, a finding during testing and late test data as different events. The guide to fixed-price and time-and-materials work covers their commercial treatment.

At award, the brief, pricing sheet and internal contribution plan should describe the same scope. If data quality is still unknown, commission a limited analysis with a defined deliverable first. Both parties can then estimate the remaining work on a sounder basis.

Further reading:

Project experience and collaboration

Give suppliers a brief they can answer

Before you request a proposal, we review the available documents with your team and assign each open question to a work package. You can then put the same brief to several suppliers. If essential system information is missing, we start with a limited assessment. If your project is already well documented, we can move directly to pricing, the contribution needed from your team and the acceptance criteria.

Frequently asked questions about CSV requests for quotation

What if we do not yet know the system boundary?

Identify the open boundary and request a limited scoping assignment. Its deliverable can be a shared system brief and a defined follow-on package. A fixed-price request with an unknown scope gives little basis for comparing bids.

Do we need an approved URS before requesting a quote?

You do not necessarily need this for the initial request. State what already exists and whether defining the requirements should be part of the engagement. Share existing drafts and identify subject matter contacts so the supplier can scope that work.

What information do we need about the consultants assigned?

Chapter 2 section 2.23 addresses suitability for the task and records of the consultant’s name, address, qualifications and type of service. Assess the people assigned to your project. General company references cannot establish their individual suitability.

Sources: [4]

How should the quote handle subcontractors?

Identify each subcontractor’s intended tasks. Chapter 7 section 7.11 calls for the contract giver’s prior assessment and approval of the arrangements. Agree information access, deliverables and responsibilities across all parties.

Sources: [3]

Which iterations should be included on the pricing sheet?

Ask how many review rounds, corrections and retests are included and where the limits lie. Another partner may be responsible for the technical fix. Before award, agree who carries out each task and who can authorise extra work.

How do we know the quotation has been clarified sufficiently?

The provider can explain deliverables, assumptions, contributions, review and handling of findings. Each open question has an agreed next step. Compare the final offers row by row on the same basis.

Sources and review date

Primary sources checked on 17 October 2026. The regulatory scope is EU GMP for human medicinal products. The article cites specific provisions for contracts and staff. We developed the request, pricing sheet and comparison for project planning. The figures serve the worked example and establish neither market rates nor a general pricing model.

  1. European Commission: EU GMP Annex 11, Computerised Systems, January 2011 revisionGMP for human medicinal products, particularly sections 1–4, 7, 10–13 and 16–17, applied as cited in the relevant sections.
  2. European Commission: EU GMP Chapter 4, Documentation, January 2011 revisionControlled documentation and records. The official EudraLex entry links to the original chapter.
  3. European Commission: EU GMP Chapter 7, Outsourced ActivitiesOutsourced GMP activities, suitability, responsibilities, agreements and performance monitoring.
  4. European Commission · EU GMP Chapter 2, Personnel, effective from 16 February 2014Personnel, role-specific training and assessment of practical effectiveness. The official EudraLex entry links to the original chapter.

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

How does the quote match your brief?

Bring your system description, desired start of use and any proposal you have received. We can review the deliverables with you, identify which assumptions are supported and agree what to clarify before award.

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