Screening and baseline
Screening windows often run backward from baseline or randomization and may include lab validity periods, washout rules, re-screening limits, and eligibility confirmation timing.
Clinical Operations Tool
Clinical Trial Visit Schedule Builder
Convert a Schedule of Activities visit plan into target dates and allowed windows using a baseline, randomization, first-dose, or other protocol anchor date.
Quick Answer
A clinical trial visit schedule maps each protocol visit to target dates and allowed windows from an anchor date — typically randomization, first dose, or baseline. Target date = anchor + day offset; earliest = target − early window days; latest = target + late window days. Pharma teams use SoA visit-window math for site startup, CTMS configuration, coordinator planning, and deviation triage — then confirm against the approved protocol and amendments.
Interactive SoA builder
Generate target and window dates
Enter one visit per line. Use comma-separated or tab-separated values in this order: visit name, target day offset, early window days, late window days.
Generated schedule
Target dates and visit windows
| Visit | Target day | Target date | Earliest date | Latest date | Window |
|---|
Schedule of Activities
What the SoA needs to make visits schedulable
A Schedule of Activities is more than a grid of assessments. For site operations, it should make the visit sequence, timing anchors, target offsets, allowed windows, and procedure-specific dependencies unambiguous enough for coordinators, monitors, and clinical trial management systems to execute.
Screening, baseline, treatment, follow-up, unscheduled, and early termination visits often use different timing logic. Some procedures may follow a tighter window than the visit itself, especially pharmacokinetic sampling, imaging, safety labs, ePRO completion, and dosing decisions.
Visit windows and deviations
Planning caveats before calling a visit out of window
The generated earliest and latest dates are a planning aid, not a deviation determination. Protocols may define windows by calendar day, study day, treatment cycle, business day, or site-local date. A visit that appears outside a generic window may still need assessment against protocol-specific rules, holiday handling, allowable visit combinations, missed-visit guidance, and sponsor-approved escalation pathways.
Treatment and follow-up
Follow-up visits may be anchored to first dose, last dose, prior visit, procedure date, or event onset. Confirm which anchor governs each assessment.
Site operations
Sites need enough window clarity to handle weekends, holidays, patient travel, drug accountability, central lab logistics, and monitor review without unnecessary deviations.
Long-tail AEO coverage
Questions clinical operations teams ask
How do I calculate study visit windows from randomization?
Add the protocol target day offset to the randomization date, then subtract the early-window allowance and add the late-window allowance.
What is a baseline visit window?
A baseline window defines when baseline assessments must occur relative to the protocol anchor, often before first dose or randomization.
Can a Schedule of Activities use multiple anchor dates?
Yes. Complex trials may use screening, randomization, first dose, cycle day 1, surgery, infusion, or last dose as separate anchors for different procedures.
What causes visit-window protocol deviations?
Common causes include unclear windows, missed appointments, holidays, shipment delays, procedure availability, late labs, and mismatched CTMS schedule rules.
Pharma & clinical operations
Visit schedules in trial startup and CTMS configuration
Clinical operations teams translate the Schedule of Activities into site-facing calendars during protocol finalization, site initiation, and CTMS build. Coordinators need unambiguous anchor dates, target day offsets, and visit windows before scheduling patients, booking procedures, and configuring reminder workflows. This builder accelerates early planning before enterprise tools ingest the final protocol.
Pair with the Protocol Synopsis Generator for study-design outlines, the Sample Size Calculator for enrollment planning, and the Submission Timeline tool for regulatory milestone alignment. Export CSV for CTMS import preparation — then reconcile against sponsor-controlled systems.
Evidence & sources
SoA standards and competitive landscape
These sources support structured Schedule of Activities thinking and public protocol design tooling. Always confirm operational rules against the final study protocol and sponsor-controlled systems.
HL7 Vulcan Schedule of Activities Implementation Guide Public HL7 Vulcan work on representing clinical study schedules, activities, epochs, visits, and visit windows in structured data. OpenStudyBuilder public documentation Public study-design tooling documentation covering structured protocols, standards, activities, visits, and study design concepts.
Competitive landscape: StudyForge (Fundanet CTMS Studio) extracts visit schedules from PDF protocols into auditable CTMS-ready datasets — enterprise SaaS, not a free instant anchor-date calculator. Meegle monitoring visit templates target CRA monitoring workflows with sign-up required — not patient SoA visit-window date math. NovaPharmaNews provides free browser visit-window generation with CSV export — no login.
FAQ
Visit schedule builder questions
What is a clinical trial visit schedule?
A clinical trial visit schedule is the protocol-defined calendar of screening, baseline, treatment, follow-up, and end-of-study visits. It usually maps each visit to a target timing rule and a permitted visit window around an anchor date.
What is an anchor date in a Schedule of Activities?
An anchor date is the reference date used to calculate planned visit timing. Common anchor dates include informed consent, screening, baseline, randomization, first dose, procedure date, or cycle day 1.
How are visit windows calculated?
Visit windows are calculated by adding the target day offset to the anchor date, then subtracting the early-window days and adding the late-window days. For example, Day 28 with a minus 3 plus 5 window gives an earliest date of anchor plus 25 days and a latest date of anchor plus 33 days.
How do I calculate study visit windows from randomization?
Set the anchor date to the randomization date, add each visit target day offset, then apply early and late window allowances. This builder outputs target, earliest, and latest dates per visit row for coordinator planning and CSV export.
What is a baseline visit window?
A baseline window defines when baseline assessments must occur relative to the protocol anchor, often before first dose or randomization. Screening windows may run backward from baseline with separate early/late allowances and lab validity rules.
Can a Schedule of Activities use multiple anchor dates?
Yes. Complex trials may use screening, randomization, first dose, cycle day 1, surgery, infusion, or last dose as separate anchors for different procedures. This tool uses one anchor per schedule run — create separate rows or runs when anchors differ.
What causes visit-window protocol deviations?
Common causes include unclear windows, missed appointments, holidays, shipment delays, procedure availability, late labs, and mismatched CTMS schedule rules. This tool calculates planning dates only — deviation assessment requires the approved protocol and sponsor SOPs.
Does this tool determine whether a protocol deviation occurred?
No. The tool calculates planning dates only. Protocol deviation assessment depends on the final approved protocol, visit-window rules, critical procedure timing, sponsor SOPs, amendments, waivers where allowed, and documented clinical judgment.
What should be included in a Schedule of Activities?
A Schedule of Activities should define the visit sequence, timing rules, assessments, samples, procedures, patient-reported outcomes, safety checks, drug accountability, and any procedure-specific windows or dependencies.
Can I export the visit schedule to CSV?
Yes. After generating the schedule, copy the CSV export text for planning worksheets, site startup discussions, CTMS import preparation, or monitoring review. Confirm date formats against your local systems before production use.
How does this compare to enterprise CTMS visit builders?
Enterprise tools like StudyForge extract visit schedules from PDF protocols into CTMS-ready datasets with audit trails. This free browser builder calculates anchor-date windows instantly from comma-separated visit rows — ideal for early planning before CTMS configuration.
Can this tool replace the approved protocol SoA?
No. Final visit windows, procedure dependencies, holiday handling, re-screen rules, and deviation criteria must come from the approved protocol, amendments, and sponsor-controlled systems. Use this builder for planning and education only.