By Patricio Ledesma, Founder and CEO, Sofpromed
Table of Contents
I'm Patricio Ledesma.
Today I want to discuss something every biotech company faces.
Change orders.
At the beginning of a study.
The CRO budget looks reasonable.
Six months later.
The sponsor receives change order number ten.
Then number twenty.
Then number thirty.
Suddenly.
The study costs much more than expected.
Many sponsors believe CROs create change orders simply to increase revenue.
Sometimes that happens.
But often.
The real problem starts much earlier.
The root cause is usually:
- Poor protocol planning.
- Poor scope definition.
- Poor contracts.
- Poor governance.
Today I'll explain how CROs manage change orders.
How sponsors should negotiate them.
And how to avoid excessive change orders from the beginning.
What Is a Change Order?
A change order is a formal modification to the contract.
It typically changes:
- Scope.
- Timeline.
- Resources.
- Deliverables.
- Budget.
Not every change order is unreasonable.
Some are unavoidable.
Others should never happen.
Typical CRO Change Order Categories
Table 1. Most common CRO change order sources
|
Category |
Frequency |
Preventable? |
|
Protocol amendments |
Very High |
Partially |
|
Enrollment delays |
Very High |
Partially |
|
Additional sites |
Very High |
Yes |
|
Additional countries |
Medium |
Yes |
|
Additional monitoring visits |
High |
Yes |
|
Database changes |
High |
Yes |
|
Statistical outputs |
Medium |
Yes |
|
Safety reporting increases |
Medium |
Partially |
|
Vendor scope changes |
High |
Yes |
|
Regulatory authority requests |
Medium |
No |
Which Change Orders Are Fair?
Let's be fair.
Some change orders are legitimate.
Imagine:
The study starts with:
- 20 sites.
- 200 patients.
- 3 countries.
Six months later.
The sponsor decides to add:
- 15 more sites.
- 2 more countries.
- 100 additional patients.
The CRO's workload has increased substantially.
A change order is reasonable.
Most sponsors accept this.
Which Change Orders Are Concerning?
Now let's look at questionable situations.
Examples:
The CRO charges extra for:
- Standard project management meetings.
- Basic timeline updates.
- Minor database modifications.
- Clarification emails.
- Routine status reports.
Sponsors should challenge these items.
Especially if the original scope was broad enough to include them.
Why CROs Like Change Orders
Let's be honest.
Many CROs bid aggressively.
Especially during competitive proposals.
The initial budget may look attractive.
Then later:
Revenue is recovered through change orders.
This is common in the industry.
Particularly among very large CROs.
Table 2. Typical CRO commercial strategies
|
Strategy |
Sponsor Risk |
|
Low initial bid |
High |
|
Aggressive assumptions |
High |
|
Narrow scope language |
High |
|
Frequent change orders |
High |
|
Fixed-fee proposal with exclusions |
High |
|
Transparent assumptions |
Low |
|
Broad bundled scope |
Low |
The Biggest Sponsor Mistake
The biggest mistake happens before contract signature.
Sponsors focus on:
Total price.
Instead of:
Assumptions.
I always tell sponsors:
Don't negotiate the budget first.
Negotiate the assumptions first.
Most future change orders originate from assumptions.
Not rates.
Review Every Assumption
Before signing.
Ask the CRO:
How many monitoring visits are included?
How many protocol deviations?
How many database updates?
How many SAE reconciliations?
How many outputs?
How many meetings?
How many medical reviews?
Everything should be clear.
Table 3. Assumptions that frequently trigger change orders
|
Assumption |
Typical Risk |
|
Monitoring frequency |
Very High |
|
Enrollment duration |
Very High |
|
Number of sites |
High |
|
Number of countries |
High |
|
Queries per patient |
Medium |
|
Protocol amendments |
Very High |
|
Number of data transfers |
Medium |
|
DSMB meetings |
Medium |
|
Statistical outputs |
High |
|
CSR revisions |
High |
Negotiate Protocol Amendment Language
This is one of the most important topics.
Most contracts say:
"Protocol amendments will be billed separately."
This is dangerous.
Because almost every study experiences amendments.
Better Contract Language
For example:
Option A
One amendment included.
No additional fee.
Option B
The first 100 hours of amendment work included.
Option C
Only direct incremental costs billable.
Not overhead.
Not profit markup.
This greatly reduces surprises.
Put Caps on Change Orders
One of my favorite strategies.
Establish caps before the study starts.
Example
Project Management
15% annual variability.
Included.
No change order needed.
Monitoring
10% visit variability.
Included.
No change order needed.
Database Updates
Two minor updates included.
No change order needed.
Table 4. Suggested included buffers
|
Activity |
Recommended Buffer |
|
Monitoring Visits |
10-15% |
|
Data Management Hours |
10% |
|
Project Management Hours |
15% |
|
Safety Activities |
10% |
|
Statistical Programming |
10% |
|
Medical Writing |
10% |
Force Transparency
Every change order should contain:
Required Elements
- Root cause.
- Scope impact.
- Resource impact.
- Budget impact.
- Timeline impact.
- Alternative solutions.
Never approve:
"Additional work required."
That statement is meaningless.
Demand specifics.
Ask for Hourly Breakdown
If a CRO requests:
$75,000
Ask:
How many hours?
By whom?
At what rate?
For what tasks?
Table 5. Example change order review
|
Question |
Must Be Answered |
|
Why is change needed? |
Yes |
|
Who requested it? |
Yes |
|
Is it sponsor-driven? |
Yes |
|
Is it CRO-driven? |
Yes |
|
Hours required? |
Yes |
|
Billing rates? |
Yes |
|
Timeline impact? |
Yes |
|
Alternative solution available? |
Yes |
Watch Out for Hidden Scope Exclusions
Read the proposal carefully.
Look for phrases such as:
- Not included.
- Assumed.
- Sponsor responsibility.
- To be determined.
- As needed.
- Future discussion.
These phrases often become future invoices.
Establish Formal Governance
Never let project teams approve change orders directly.
Create a review committee.
Participants should include:
- Clinical operations.
- Finance.
- Procurement.
- Executive management.
Large sponsors often require approval above predefined thresholds.
For example:
Table 6. Change order approval process
|
Change Order Value |
Approval Level |
|
Under $10,000 |
Project Lead |
|
$10,000-$50,000 |
Department Head |
|
$50,000-$100,000 |
Executive Review |
|
Above $100,000 |
Senior Management |
Benchmark CRO Pricing
Always obtain competing proposals.
Before signing.
Compare:
- IQVIA
- ICON
- Fortrea
- Parexel
- Syneos Health
- Medpace
- Worldwide Clinical Trials
- Sofpromed
Do not compare only total cost.
Compare assumptions.
Many sponsors discover one CRO included services another CRO excluded.
That difference later becomes change orders.
Create a Change Order Tracker
Track every change order.
Most sponsors do not.
This is a mistake.
Table 7. Change order dashboard
|
Metric |
Target |
|
Total Number of Change Orders |
As Low As Possible |
|
Sponsor-Caused Change Orders |
Track |
|
CRO-Caused Change Orders |
Track |
|
Total Value |
Track |
|
Change Order % of Original Budget |
<10% Ideal |
|
Average Approval Time |
Monitor |
Warning Signs
If a CRO generates:
- 10 change orders in the first six months.
- Frequent budget surprises.
- Repeated assumption disputes.
- Recurring billing disagreements.
The problem is usually not the study.
The problem is contract management.
Or CRO behavior.
My Top 10 Recommendations
If you remember only ten things:
- Negotiate assumptions. Not price.
- Define scope in detail.
- Include protocol amendment buffers.
- Include monitoring buffers.
- Include project management buffers.
- Require hourly breakdowns.
- Challenge vague language.
- Create change order approval committees.
- Monitor change order metrics monthly.
- Select CROs with transparent contracting practices.
Not simply the lowest bid.
Key Takeaways
Most excessive change orders are predictable.
And preventable.
The best sponsors focus on:
- Detailed scopes.
- Strong contracts.
- Transparent assumptions.
- Strict governance.
Remember this.
A contract is not protection because it is signed.
A contract is protection because it is specific.
The more ambiguity. The more change orders.
The more clarity. The fewer surprises.
Final Words
If you are planning a clinical trial, spend extra time negotiating your CRO contract.
One day of contract review can save hundreds of thousands of dollars later.
And sometimes.
Millions.














