Key takeaways
- Study timelines usually slip in operations: an unsigned site contract, a missing approval letter, a late visit report.
- GeniOS connects site emails, team chat, trackers and documents to each milestone in the study plan.
- The study manager gets one piece of intelligence per milestone at risk, with one owner and a date.
- It covers operations and paperwork only, never clinical decisions or participant records.
The problem
A study manager at a mid-sized biotech is running a study across 14 sites in three countries. The plan says all sites active by June and the enrolment target reached by December. On a normal Tuesday her inbox holds a site budget counter-offer, a question from an ethics committee about a consent form version, a monitoring visit report from a clinical research associate, a courier note about a delayed supply shipment and three reminders from finance about unpaid site invoices.
Each of these is small. Together they decide the timeline. Site 07 has had its contract "with legal" for five weeks. Site 11 is waiting for an approval letter that the ethics committee says it sent. A monitoring report from site 04 lists twelve open data queries with no answer in two weeks. The study manager knows all of this in pieces, spread across email, chat and the study tracker, and she has thirteen other sites to think about.
When a site starts six weeks late, the study does not just lose six weeks at one site. It loses the enrolment that site would have brought, which pushes the last participant date and every milestone behind it. Leadership hears about it at the monthly review, when the chart is already behind plan.
Why it slips today
Study teams have trackers, a study management system and weekly calls with sites and vendors. These record status once someone updates it. They do not notice that a promise in an email was not kept.
| Where it lives | Who sees it | How it slips |
|---|---|---|
| Site and legal email threads | Study manager, contracts lead | A contract waits weeks for one clause and nobody escalates |
| Study team chat | The study team | A visit is booked before the approval letter is in the file |
| Monitoring visit reports | The research associate | Open queries and follow-up actions age without an owner |
| Enrolment tracker | Study team and leadership | Shows the shortfall, not the paperwork causing it |
A dashboard of enrolment against plan shows the result, not the cause. The cause is usually one document, one signature or one reply that nobody owned this week, which is why company intelligence is required on top of records.
The solution
GeniOS reads email, calendar, chat, shared documents and the study tools a team already uses, read-only to start. It forms the study's goals from the team's own plans, decks and meetings, and checks every site's pending work against them.
- Site activation blockers. Contracts, budgets, approvals and initiation visits that are late against the date each site needs to start.
- Promises not kept. A site, vendor or colleague who said a document would follow and it has not.
- Ageing visit actions. Open queries and follow-up items from monitoring reports with no reply or owner.
- Milestones at risk. Site gaps that will push a study milestone, raised with the reason, not just the shortfall.
It works in the same way as Goal and Execution Monitoring, applied to the steps of a study.
See it on the whiteboard
Here is one site contract moving from a stuck email thread to a signed agreement.
Site 07 cannot start without its contract
How: send site 07 the agreed fallback clause today and book a call with their legal team.
- Your tools. The site says the contract is with legal, the team chat shows a visit booked for the 18th, and the tracker shows four sites still not active.
- GeniOS thinks. It sees a contract stuck for five weeks on a clause that also held up two other sites, with a visit booked that cannot happen without it.
- Intelligence. Meera, the study manager, gets one note: send the fallback clause today and get site legal on a call.
- Delegated. She hands the note to a Reply Drafter agent and the call to the contracts lead, and approves the note.
- Goal moves. The signed contract lands in the shared folder, GeniOS closes the item and the site activation goal moves.
How GeniOS thinks and plans
For each site and milestone GeniOS connects four things. What happened: the documents sent and received, the promises made by sites, vendors and colleagues, and the visits booked. The pattern: the same clause slowing several contracts, one site that answers queries late every month, or a vendor whose shipments keep slipping. The impact: which study milestone moves if this step slips, and by roughly how much. The owner: the person who can move the step, whether that is the contracts lead, the research associate or the study manager.
It checks each gap against the study's goals, such as sites active by a date or an enrolment target for the quarter. A missing letter that blocks next week's initiation visit rises; a routine invoice query with weeks to spare stays quiet. Then it picks one next step, one owner and one date, the single action that keeps the milestone on plan.
GeniOS does not look at participant records or make any clinical judgment. It works only with the operational record: contracts, approvals, visit schedules, reports, aggregate counts and the conversations around them.
How it delegates and gets it done
The owner answers with Delegate, Done, Later or Not relevant. Delegate hands the work to a person, such as the contracts lead or a research associate, or to an AI agent, such as a Reply Drafter for a note to a site or a Scheduler for a call with site legal. Nothing is sent outside the company until a person approves it.
An item closes only on proof: the signed contract in the shared folder, the approval letter filed, the visit report uploaded, the queries answered in the study tool. If a step is marked Done without proof, GeniOS asks again. When proof arrives, the goal's progress moves, and GeniOS learns which sites and clauses need earlier attention next time. Handoffs between the study team, contracts and finance are covered in Cross-Team Handoffs.
How it reaches you
Intelligence arrives on its own in the GeniOS Mac app, from the menu bar, and in the web dashboard. The study manager sees the few site steps that need her today, each with a reason and a date.
What she no longer does: rebuild the site tracker from her inbox before every weekly call, chase colleagues for status, read every visit report to find the open actions, or decide which of 14 sites to worry about first. Leadership sees the milestones at risk and why, without asking for a slide.
A worked example
The company, names, dates and numbers in this example are made up to explain the idea. A 200-person biotech is running a study at 14 sites across the United States and Europe, with a site budget of about $180,000 per site. Meera is the study manager. Ten sites are active; four are not.
Site 07 has had its contract with its legal team for five weeks over an indemnity clause. The research associate has already booked the initiation visit for 18 March. Meera's company accepted a fallback wording for the same clause at sites 03 and 11 last quarter, but the person who negotiated it has since moved teams.
On 4 March Meera gets one note from GeniOS: site 07 cannot hold its visit on the 18th without a signed contract, the hold-up is the indemnity clause, and the fallback wording used at sites 03 and 11 is in the shared contracts folder. It suggests sending that wording today and booking a call with the site's legal team this week.
Meera delegates the note to a Reply Drafter and the call to the contracts lead, who books it for 6 March. She approves the note with one change. Site legal accepts the wording on the call, and the signed contract is filed on 11 March. GeniOS closes the item on seeing it, the visit goes ahead on the 18th, and the "all sites active by June" goal moves from 50% to 57%.
How to measure it
- Days from site selection to activation. Tracked per site, so slow steps show up early.
- Days a contract or budget waits. The time each site agreement spends waiting for a reply from either side.
- Age of open visit actions. How long monitoring report actions and data queries stay open.
- Milestones met on the planned date. The share of study milestones reached on time, with the cause recorded when they are not.
Where it applies
It fits sponsors, contract research organisations and research sites that coordinate study operations by email, documents and trackers.
- Domains: Operations, Legal & Compliance, Finance
- Industries: Pharmaceuticals & Life Sciences, Healthcare
- Roles: Executives, Managers
Questions about study milestone tracking
Does GeniOS read participant data?
No. It works with operational records such as contracts, approvals, visit schedules, reports and aggregate counts. Participant records and clinical decisions stay out of scope.
Does it replace our study management system?
No. Your study tools stay the record of status. GeniOS reads them alongside email, chat and documents, and raises the steps where a promise or date is slipping.
Can it send messages to sites?
An agent can draft a note or offer meeting times, but a person approves it before it goes out. The study team stays the owner of every site relationship.
How does it know which milestone is at risk?
It links each site step to the study plan the team already wrote. When a step is late and blocks a milestone, it tells the owner what to do and by when.
Status
Exploring This is an application area we are exploring with early customers. If study timelines are slipping on paperwork, book a call and we will show how it would work on your own study documents and inboxes, starting read-only.