GuidesFor CRCs scheduling visits
What Actually Counts as an Out-of-Window Visit
Jul 9, 2026GuideVisit Window CalculatorAdministrative reference · Zero-PHI examples only
visit windowout-of-windowschedulingICSZero-PHI
How protocol visit windows are calculated from anchor dates, where weekend/holiday confusion creeps in, and how Visit Window Calculator turns ± days into clear calendar bounds.
The problem on the clinic floor
“Out of window” sounds binary until you try to schedule it. Protocols define a target day offset from an anchor (screening, randomization, Cycle 1 Day 1, last dose) plus a ± window. Manual counting across months produces off-by-one errors, especially when someone counts calendar days one way and business days another.
Weekends and holidays create a second argument: the target lands on Sunday; is the nearest clinic day still inside the window? Coordinators schedule the convenient day and only later discover it sat outside the allowable range — which is how a routine visit becomes deviation paperwork.
Multi-subject clinics multiply the math. Each subject has a different anchor. Doing the arithmetic fresh every time is slow and inconsistent between staff.
Anchor date changes make old mental math wrong. A randomization date shifts after a screen failure replacement; someone still uses the previous anchor on a sticky note. The scheduled visit looks reasonable on the calendar but fails the protocol’s actual bounds.
Partial windows across cycles confuse teams new to oncology schedules. Cycle 2 Day 1 may anchor differently than Cycle 1 Day 1; applying the wrong offset template is an easy copy-paste error in a spreadsheet.
Practice context
Whether a visit is out of window is defined by the protocol’s window rules and the site’s scheduling against those bounds — not by informal “close enough” judgment. Deviations should reflect actual allowable dates, not a spreadsheet formula that drifted.
Visit window tools should stay Zero-PHI: anchor dates and offsets are calendar math. Do not store subject names or subject IDs in the calculator workspace; keep identifiers in the systems of record your site already uses.
Sponsor visit schedules and IWRS sometimes echo the same windows with different labels. The site’s job is to compute bounds from the protocol-approved anchor and offset, then schedule inside those dates — not to negotiate “close enough” at check-in.
Documenting an out-of-window deviation later is harder when nobody recorded the earliest and latest allowable dates at scheduling time. A printed or exported window calc attached to the scheduling note (without identifiers) gives QA a contemporaneous reference.
How to use Visit Window Calculator for this
Compute the window once from the protocol numbers, then schedule against the earliest/latest bounds — not against a gut feel. Run the calculation before offering appointment slots, especially when anchors change after randomization or cycle starts.
- Open Visit Window Calculator and enter the anchor date, target day offset, and ± window days from the protocol. Double-check whether the protocol counts day 1 as the anchor day or the day after — that single rule causes many off-by-one errors.
- Read the returned target date plus earliest/latest allowable calendar bounds before offering the patient a slot. Write those bounds down in your scheduling system of record — not in the calculator with identifiers.
- Check weekend/holiday highlighting and choose the nearest allowable clinic day that still sits inside the window. If the target falls on a closed day, pick the nearest in-window clinic day, not the nearest open day.
- Use the schedule generator when you need a recurring series from the same limits; export TSV or .ics for the clinic calendar if helpful. Regenerate if the anchor changes — do not edit old exports by hand.
- Persist settings in the local workspace if you reuse the same protocol windows; never enter subject identifiers into the tool. Clear or backup the workspace on shared PCs when the scheduling block ends.
An out-of-window deviation should mean the visit missed the protocol’s dates — not that the mental math did. Compute bounds once, schedule inside them, and keep identifiers out of the helper. That is how routine rescheduling stays routine.