Table of contents
At a glance
When does a fixed-price validation proposal make sense?
A fixed price is meaningful when the system boundary, deliverables, client inputs and acceptance criteria are sufficiently clear. If evidence or configuration is still missing, commission a bounded scoping exercise or agree how time and materials will be controlled. Compare proposals on the same assumptions, including deviations, retesting and change requests. We estimate the work after scoping.
Scope of this guide
This guide helps buyers compare proposals. It offers neither individual contract advice nor market-average prices. Define the scope and terms of your project. For third-party services affecting computerised systems, EU GMP Annex 11 section 3.1 calls for formal agreements and clear responsibilities. The pricing models, person-days and budget controls discussed here are our own commercial planning recommendations.
Sources: [1]
Define deliverables you can assess at acceptance
Start with intended use. Which processes and data should the system cover? Which extensions, interfaces and migrations are included? Define the results needed for the next decision on use. A package might include assessed requirements, a risk assessment, agreed tests, evaluated findings and handover. Choose a format that fits your quality system.
Distinguish routine work from genuine unknowns. The quote should explain how normal test findings are assessed. Adding another application clearly changes scope. Between these cases lie changes that need explicit rules, such as new interface fields, a revised business process, unavailable test data or another site.
| Proposal item | Question to resolve | Example of a clear boundary |
|---|---|---|
| Systems | Which application and version? | Named tenant and specified release |
| Processes | Which end-to-end workflows? | From goods receipt to a defined use of the material |
| Interfaces | Which messages and recipients? | Specified result transfer and the error-handling route |
| Migration | Which historical records? | Defined objects, period and transformation rules |
| Retests | Which work on findings is included? | Agreed assessment and repeat tests |
| Handover | Which documents and capabilities? | Accessible evidence and a practical exercise for the operating team |
When can we estimate the effort?
We establish the estimate after scoping, once the intended outcome and boundaries of your project are clear.
In our project experience, addressing audit findings has taken between 2 and 200 consulting days, depending on the scope.
This range concerns remediation of audit findings. We estimate your own project against its specific scope.
What do the three pricing models tell you about project cost?
A day rate tells you the price of one day of work. An effort budget estimates or caps the time needed. A fixed price covers agreed deliverables under stated assumptions. The pricing model alone tells you little about the outcome. Compare the system boundaries, deliverables, work your team will provide and acceptance criteria.
A fixed price can fit when the processes, interfaces, system version and handling of test deviations are clear. If the starting point is largely unknown, a limited assessment before committing to delivery may be more economical. A fixed price with many open assumptions often moves uncertainty into later change requests.
Time and materials can suit an investigation or changing priorities. Agree the priority of tasks, how spend and remaining work will be reported and who decides on budget changes. A weekly timesheet shows time spent. Connect that time to completed work and the decisions it enables.
Worked example comparing equivalent scopes
Suppose a time-and-materials proposal estimates 30 external days. Migration and handover are expressly excluded and add six days in this example, bringing the comparable estimate to 36 days. Check the fixed-price proposal against the same deliverables, customer input and assumptions about change before comparing its total.
If the test environment is late, a time-and-materials project may incur waiting time. Whether it is charged depends on the agreement. In a fixed-price project, the delay may affect schedule or contribution assumptions. Agree how reserved staff time, postponement and restarting will be handled.
List the outstanding information, plausible assumptions and decisions that would resolve them. A limited first analysis might establish the number of critical interfaces or the condition of historical data. Its deliverables should be usable even if a different supplier carries out implementation.
| Item | Example value | Meaning |
|---|---|---|
| Initial estimate | 30 person-days | Check which deliverables are included |
| Migration and handover excluded from the example quote | 6 person-days | Identify the missing work |
| Effort for the comparable scope | 30 + 6 = 36 person-days | Only then apply the rate quoted in the offer |
| Fixed-price proposal | Check the same deliverables and assumptions | The pricing model alone does not establish completeness |
Decide on changes before implementation
A practical change process records the trigger, technical impact, work added or removed and effect on timing. The customer then decides whether to authorise the change. An invoice for undocumented additional work is hard to assess. Unrecorded scope growth under a fixed price creates the same problem.
Distinguish a customer request from correction of deficient work. An incorrectly prepared test already in scope differs from a request for another interface. The applicable treatment depends on the contract. Discuss both cases using examples before awarding the work.
A short change record can cover five fields. Record the original scope, requested change, process impact, cost and timing effects, and the decision. Link it to the current project baseline so an approved change to the test basis also reaches the release plan.
Clarify the working arrangements before award
Even with external delivery, someone must arrange decisions, access, tests and approvals. Internal tasks omitted from the quote can make the schedule unrealistic. Show these dependencies against the milestones.
Agree how new findings and change requests will be handled. A fixed price need not include every new requirement, and hourly billing still needs a view of deliverables. Define the outcomes and review open decisions regularly.
Measure progress through decisions and evidence
A project may need many documents, but file counts alone cannot show quality. Which requirements are agreed, risks assessed and critical workflows tested? What findings and customer decisions remain open? A project can have 95% of its files complete and still lack a central quality decision.
Agree milestones with verifiable outcomes. “Testing complete” should mean that the agreed scope was executed, findings were assessed and the next decision is ready. A collection of screenshots cannot establish that by itself. Payment milestones can be linked to these deliverables as agreed in the quote.
For time-and-materials work, report completed outcomes, remaining activities, actual spend, expected remaining effort and dated decisions. The same technical information helps on a fixed-price project. The customer still needs to manage internal contributions, changes and decisions on use.
Which pricing model fits the next step?
When the need is still unclear, we recommend a limited assessment first. A known system project may support a defined implementation package. If your team will deliver the work, targeted coaching may fit better. Derive the price from the agreed working model and its boundaries.
At Daniel Herrmann Consulting, the IT GxP Audit establishes the starting point and priorities. The IT GxP Compliance Programme develops common procedures, IT GxP Coaching supports your team’s own work and IT GxP Consulting can carry out implementation. Fixed prices are possible once the scope is clear. We agree the assumptions, contributions, included work, milestones and handover in the quote. Other services follow their own agreed pricing terms.
Consider what your team will be able to do after handover. Can staff reconstruct decisions, access the evidence and carry out operational tasks? A lower initial price may prove costly if routine work always requires external support. Assess the tasks and access your team will actually have.
Worksheet for testing proposal assumptions before award
Give each bidder the same three changes to discuss, such as an extra interface, late test data and a systematic test finding. Ask which work the agreed scope covers and where a new decision would be needed.
Use the answers to tighten the scope. A supplier need not cover every event at no charge. It should explain how the commercial boundary relates to the work. Agree priority and budget impact before substantial additional work on a time-and-materials project as well.
Account for your team's time. An unavailable test environment or an absent decision-maker can affect the schedule more than the supplier's day rate. Identify the internal tasks needed for each milestone. You can then compare bids against the capacity your team actually has.
Record changes through the agreed project process. Keep a short current scope summary that distinguishes the original deliverables from approved additions. It gives the team a working reference alongside the contract.
| Situation | Rule to clarify in the proposal | Why it matters |
|---|---|---|
| Additional interface | Who decides the added scope, timing and price? | New data paths and failure modes can change the tests needed. |
| Late customer contribution | Which input or decision is missing, and how will the work be rescheduled? | The test environment and the people needed must be available together. |
| Test finding | Which investigation, coordination of corrections and retests are included? | Recording a defect does not complete the decision on use. |
| Unsuitable legacy data | Which assumptions apply and when is analysis needed? | Preserving historical meaning can require additional work. |
| Project close | What documentation, access and practical exercises will be handed over? | Acceptance should confirm that the deliverable can be used. |
What counts as a correction or a change in scope?
Distinguish a failure to deliver an agreed result, an assumption that proves false and a new request. The specific contract governs their treatment. It is as unhelpful to charge for every extra step automatically as it is to expect unlimited changes.
Suppose an agreed test of a batch hold reveals an implementation defect. Assessing the finding belongs to the agreed evidence process. The service model should identify who makes and pays for the technical fix. A new warehouse with a different process raises a separate scope question. Defining both cases helps the parties decide promptly.
| Trigger | Compare against | Resolve before implementation |
|---|---|---|
| An agreed deliverable is missing | Scope of services and acceptance criterion | Responsibility for correction |
| An assumption proves false | Documented proposal assumption | Impact and suitable adjustment |
| A new feature is requested | Existing scope | Additional work and who approves it |
| Regulatory inspection finding | The actual finding and risks | Immediate action and the scope of longer-term work |
| The customer’s input changes | Agreed customer contribution | Rework and new dependencies |
What to include in a budget progress report
Agree a short recurring update showing completed deliverables, the outstanding decision, the next step and the budget impact. For time and materials, show actual spend and forecast remaining work. For fixed-price work, show package status, prerequisites and approved changes. Attendance and document counts alone do not establish readiness for release.
Include your team’s work. A lower quote may require more internal preparation, review, data provision or operating training. Compare equivalent packages. Regulatory suitability must be assessed independently of pricing. Neither a fixed price nor an hourly budget guarantees an authority’s decision or a defect-free project.
Next steps
- Define the systems, processes and expected deliverables.
- Identify existing evidence and outstanding uncertainties.
- Tie the pricing model to customer responsibilities, acceptance and change control.
- Track completed deliverables and open decisions.
Project experience and collaboration
Choose a pricing model that fits the scope
Before suggesting a fixed price or time and materials, we review the open assumptions with you. Which system boundaries are agreed? Which records are available? Who still needs to decide what? A defined package is easier to price than an unfamiliar system with several dependencies. If needed, we start with a short assessment and use the findings to plan the rest. With either model, we agree what your team contributes, how you accept the work and how to handle changes.
Frequently asked questions about Fixed-price and time-and-materials CSV
Does a fixed price guarantee regulatory approval?
No. A fixed price sets the payment for an agreed scope. It cannot establish regulatory suitability or determine an authority’s assessment.
What should the proposal state explicitly?
State the scope, deliverables, assumptions, responsibilities, customer contributions, acceptance criteria and treatment of changes. The details depend on the project.
Can a fixed-price project still incur extra costs?
Yes, if agreed assumptions or scope change and the contract provides for additional work. Define the boundaries and how changes are authorised before implementation. Ask specifically about interfaces, migration, retests, delays and customer contributions.
How can we control a time-and-materials project?
Agree priority outcomes, a budget, regular progress reporting and a decision point before the budget is exceeded. Report completed work and expected remaining effort together. An hourly limit can stop a project before a useful decision is reached, so define a usable outcome for the agreed budget.
Is a paid initial assessment worthwhile?
It can be when system boundaries, data or documents are unclear. Specify an output such as assessed boundaries, open risks and an actionable plan. The value lies in the uncertainty it resolves and the evidence your team can continue to use.
Which customer contributions should the proposal list?
Name the required data, test access, process decisions and people, with realistic dates. “The customer will provide reasonable assistance” leaves too much undefined. Check internal capacity before agreeing milestones.
How can we compare quotes with different document counts?
Compare the conclusions and evidence required. One file or several may work if requirements, risks, tests, findings and handover are traceably connected. Document count describes the format rather than the quality achieved.
Is every test finding chargeable as additional work?
No. There is no universal answer. Check the agreed scope, assumptions and allocation of responsibilities. Assessing a finding, fixing a technical defect and requesting a new feature can represent different work. Resolve the contract terms and authorise any additional delivery explicitly.
What should a useful budget update include?
Show completed deliverables, pending decisions, remaining tasks, dependencies and forecast cost. For time and materials, include a reasoned estimate to complete. For fixed-price work, show the package status and approved changes. Hours consumed alone do not establish progress towards the deliverable.
Does Daniel Herrmann Consulting offer fixed prices?
Yes, once the scope is clear. We agree scope, timing, milestones and handover. The proposal specifies which services are included.
Sources and review date
The sources set the technical context. We developed the tables, checklists and examples. On 18 October 2026, Annex 11 section 3.1 was checked specifically for formal agreements and responsibilities. The pricing models and calculations are our own planning examples.
- European Commission: EU GMP Annex 11, Computerised Systems (2011)EudraLex listed this version as current on 14 October 2026. It addresses computerised system use, risk, operation and the data lifecycle. The proposed tests are our own practical interpretation.
Sources checked: .
Agree scope and pricing before commissioning work
We help you assess the starting point, assign responsibilities and put the required evidence into operation. The appropriate support depends on your system, your team and the decision you need to make.
- 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.

