Request a demo specialized to your need.
Subscribe to our Newsletter
Smit Shah
Tufts CSDD has reported average Phase III budgets above $65 million for oncology protocols and $54 million for non-oncology protocols (Tufts CSDD Impact Report, 2022). At that scale, a forecast that is a few months out of date is a large number to get wrong at quarter-end.
Most trial forecasts are built from the plan: expected enrolment, expected visits and contracted fees. Then the study starts, sites enrol faster or slower than planned, visits are missed or added, and amendments change fees. The plan stops describing the study, but the forecast keeps following it, because the data that would update it sits in another system.
|
Forecast input |
Plan-based |
Live data on one platform |
|---|---|---|
|
Enrolment |
Planned enrolment curve |
Actual randomised patients by site |
|
Visits |
Visits expected from the schedule |
Visits completed in EDC |
|
Earned to date |
Estimated from enrolment |
Calculated from completed visits and procedures |
|
Remaining cost |
Plan minus invoices received |
Contracted budget minus earned, projected from actual pace |
|
Accruals |
Estimated at month-end |
Earned but not yet invoiced, at any time |
|
Amendments |
Updated when someone remembers |
Applied to the affected visits |
Some sites enrol ahead of target and others behind. A forecast built on the planned curve misses both. Using actual enrolment by site shows where spend will land, and how much budget is tied up in sites that are not enrolling.
Work is done before it is billed. If the forecast only sees invoices, it lags the study by a payment cycle or more. When completed visits create earned amounts automatically, the gap between earned, invoiced and paid is visible at any point, which is what finance needs for accruals.
A protocol amendment that adds a procedure changes the cost of every visit that includes it. Unless the change reaches the site budgets, the forecast keeps using the old fees. Comparing budget versions shows exactly what each amendment changed.
For CROs and sponsors with partners, the timing of money matters as much as the total. The gap between what has been paid to sites and what has been received from the sponsor or partner is a cash-flow risk that a total-budget forecast does not show.
When forecasts are rebuilt from exports each month, variances surface at quarter-end. When the inputs are live, a site spending ahead of its enrolment, or a country running over budget, shows up while there is still time to act.
Cloudbyz CTFM is built natively on Salesforce on the same platform as Cloudbyz CTMS and EDC, so enrolment, completed visits and earned amounts sit in one data model. Budgets are built from templates by study arm, amendments are applied to the affected visits and procedures, and completed visits generate invoices, so earned, invoiced and paid amounts can be compared at any time.
The Cloudbyz Financial Navigator, an Agentforce agent, is a read-only analyst inside CTFM. It answers plain-language questions on payments, invoices and budgets, traces payables from earned to billed to paid, compares budget versions, flags site concentration risk and invoices ageing past 90 days, and surfaces the gap between what sites have been paid and what the sponsor has received. It never changes records. How detailed forecasts are depends on how budgets and payment terms are configured.
Book a demo or visit cloudbyz.com.
Subscribe to our Newsletter