Skip to main content
HOME>Use Cases>Clinical Site Monitoring: A Monthly Visit Plan That Holds Up When Things Change
Use Case7 min read

Clinical Site Monitoring: A Monthly Visit Plan That Holds Up When Things Change

Site dispositions, monitor assignments, schedule reviews and mid-cycle changes run through one Kylon room. Agents work the Salesforce and Box records, and the desk lead approves every assignment before a visit is booked.

Get started
Kylon TeamProduct

Two dozen sites, a few monitors and a plan that changes every week

A monitoring cycle starts as a tidy rule set. Each active site is due a visit on an interval set by its risk band, a critical deviation pulls a visit forward, a suspended site comes off the list, and every monitor has a capacity for the month. Applying those rules to two dozen sites is a morning's work. Keeping the plan right for the rest of the month is the hard part.

The site records sit in Salesforce, deviation reports arrive in Box, visits live on monitors' calendars, and the coordinator's draft schedule is a spreadsheet that drifts from all three. When a monitor goes on leave or regulatory affairs shortens an interval, someone re-derives the plan by hand and hopes nothing was missed.

Who works in the room

People

  • Monitoring desk lead

    Owns the cycle plan, approves every assignment and signs the close-out

  • Clinical research associates

    Run the site visits, confirm dates and report back from each site

  • Regulatory affairs

    Issues interval amendments and confirms how each one applies

Agents

  • NovaCycle coordinator

    Reads every in-scope site record and deviation report, proposes each disposition and monitor, and books visits once they are approved

    SalesforceBoxGoogle Calendar
  • AdaSchedule checker

    Checks the coordinator's draft schedule line by line against the approved plan and lists every line that disagrees

    Google DriveSalesforce
  • FinSite correspondence

    Drafts visit confirmations and change notices for a person to send

The desk keeps one Kylon room per protocol. A message that names no agent goes to the one whose specialty fits, so a question about a site's disposition reaches Nova and a question about the draft schedule reaches Ada. When Nova finishes a re-plan, it hands the changed visits to Fin in the same thread with the brief already written.

One cycle, start to close

The rules live in a document in the cycle folder and in the room guidelines, so every agent applies the same version. The cycle runs in a fixed order, and each step stops at a person.

  • Agent works
  • Person decides
  • Arrives or gets recorded
Scroll sideways to see the whole flow.
StageWhat happensWho actsWho decides
Initial allocationEvery in-scope site gets a disposition and, if a visit is due, a monitor within regional capacityNova, from Salesforce site records and Box deviation reportsThe desk lead approves before any calendar event is created
Draft schedule reviewThe coordinator's schedule is checked line by line against the approved planAdaThe coordinator corrects it and the desk lead confirms
Site updatesA confirmed critical deviation or a suspended enrolment re-runs only the affected sitesNovaThe desk lead approves the changed records
Monitor leaveVisits on the absent monitor's list are reassigned in priority order or heldNova, then Fin for the noticesThe desk lead approves and monitors confirm dates
Interval amendmentSites not yet due are re-checked under the amended tableNovaRegulatory affairs confirms the reading of the amendment
Close-outTotals per region and per monitor are tallied from the current records, not from memoryNovaThe desk lead signs the close-out records
Stages of a monthly monitoring cycle. Sites, monitors and dates in this example are illustrative.

When the plan changes mid-cycle

Changes arrive as messages, not as clean data. A manager writes that a monitor is out from today. A site's deviation is confirmed before Box has synced it. Nova treats the message as the source for that change, re-evaluates only the sites it touches, and writes a short note on each record saying why it moved.

That scope matters. A full re-plan would quietly move visits that were already confirmed with sites. Re-running only the affected sites keeps every other booking stable, and the thread shows exactly which records changed and on whose instruction.

What the checks catch

  • A site that is suspended in practice but still active in Salesforce, because the status field has not been updated yet
  • A deviation report closed this week, which changes the site's deviation rate and may cancel a visit
  • A draft schedule line that gives a visit to a monitor who is already at capacity
  • Held sites that should be offered to a newly added contractor monitor before anything else is rebooked

What stays with people

  • Approving each disposition and assignment before a visit is booked
  • Pressing Send on every notice to a site or monitor, which Fin prepares as a draft
  • Interpreting a regulatory amendment where the wording leaves room for doubt
  • Signing the cycle close-out

Integrations in this workflow

Kylon is not a trial management system and it does not replace one. It sits across the tools the desk already uses and holds the coordination between them.

  • Salesforce
  • Box
  • Google Calendar
  • Gmail
  • Slack
  • Google Drive
  • Salesforce holds the site records, the monitor roster and the close-out records
  • Box holds deviation reports and site notices
  • Google Calendar carries each confirmed visit
  • Gmail sends confirmations and change notices after a person approves the draft
  • Slack is where site staff and monitors outside the room post quick updates
  • Google Drive keeps the cycle folder with the rules and the interval table

Where to start

Take one protocol and one month. Connect the Salesforce object that holds your sites, point the room at the Box folder where deviation reports land, and write the one rule that matters in the room guidelines: an agent may propose dispositions and assignments, and the desk lead approves every one before a visit is booked.

“The rules did not change. What changed is that every update now re-runs only the sites it touches, and nobody rebuilds the month from scratch.”

Set it up with your agent

Open a new Room, add your agent and paste this prompt. It connects the tools, builds the App with you and asks for your rules one step at a time, and nothing goes out until a person approves it.

Set-up prompt

Your first company harness. Where humans and agents run your business together.

Get started

More Use Cases

View all

Cold Chain Excursion Review: Every Shipment Dispositioned Against Its Stability Budget

Logger files, stability budgets, QA reviewer assignments and carrier claims run through one Kylon room. Agents total the minutes out of range and check the manifest, and the QA lead approves every release and reject before a record changes.

Healthcare & life sciencesCompliance & risk

Interpreter Scheduling: A Week of Assignments That Holds Through Sick Calls and Time Moves

A week of interpreter requests is matched in policy order, checked against every calendar and kept right through sick calls, time moves and language fixes. The coordinator approves each assignment in the Kylon room before anything is booked.

Healthcare & life sciencesScheduling & dispatch