Milestones such as site activation or first patient in are made up of tasks: collecting documents, getting ethics approval, executing the agreement, completing the initiation visit. In Cloudbyz, tasks are linked to milestones, so when the last task is completed the milestone status updates automatically, at site level and rolled up to study level, and any payment tied to that milestone is reflected in Cloudbyz CTFM. Teams see real-time status instead of chasing updates. It is used by large pharma, global multinationals, biotechs, CROs and device companies.
One completed task can move a site milestone, a study milestone and a payment, with no one updating a tracker in between.
How milestone tracking works today
- Tasks live in personal to-do lists, emails and spreadsheets.
- Someone updates the milestone tracker when they remember the task is done.
- Study-level status is rebuilt by hand from site trackers each week.
- Finance learns a milestone payment is due only when someone tells them.
Why it matters
- Regulatory notifications. Under the EU Clinical Trials Regulation, sponsors notify each Member State of milestones such as the start of the trial, the first visit of the first participant and the end of recruitment, generally within 15 days (Regulation (EU) No 536/2014, Articles 36 and 37). Late milestone updates can mean late notifications.
- Oversight. ICH E6(R3) expects sponsors to oversee trials in proportion to risk (ICH E6(R3), EMA Step 5). Slow site activation is a risk that needs to be visible early.
- Payments. Start-up fees, milestone payments and holdback releases depend on milestones, and sites expect to be paid when they reach them.
Site level and study level
|
Level
|
Example milestones
|
Built from
|
|
Site
|
Agreement executed, ethics approval, site initiated, first patient enrolled, close-out
|
Site tasks: documents collected, submissions made, visits completed
|
|
Study
|
First site activated, all sites active, first patient in, last patient out
|
Site milestones rolled up across sites
|
What task-driven milestones change
|
Question
|
Today
|
Cloudbyz
|
|
Is this site activated?
|
Ask the CTM
|
Milestone updates when the last task is done
|
|
How many sites are active?
|
Rebuild from trackers
|
Rolled up at study level in real time
|
|
What's holding a site up?
|
Unknown
|
Open tasks are visible on the milestone
|
|
Is a milestone payment due?
|
Finance is told later
|
Reflected in CTFM when the milestone is reached
|
|
Is the record complete for audit?
|
Scattered
|
Tasks, dates and owners on the record
|
For large pharma and global multinationals
Across many studies and countries, manual trackers can't keep up. Task-driven milestones give clinical operations leaders a live portfolio view of activation and enrolment, show exactly which tasks are holding sites back in each country, and give regulatory and finance teams the dates they need without asking.
For biotechs and emerging sponsors
A small team can't spend hours updating trackers. Linking tasks to milestones means the milestone updates itself as work is done, investors and boards can be given current dates at any time, and milestone payments to sites happen on time.
How Cloudbyz does it
Cloudbyz CTMS and CTFM are built natively on Salesforce as one platform. In Cloudbyz, tasks are linked to site and study milestones; when the tasks for a milestone are completed, its status updates automatically, site milestones roll up to study level, and dashboards show real-time status. Because CTFM shares the platform, milestone-linked payments such as start-up fees and holdback releases are reflected as soon as the milestone is reached. Book a demo or visit cloudbyz.com.