Applied-study data-collection schedule replanning after recruitment delay or site-capacity constraint¶

Canonical pattern(s): Schedule adjustment and replanning Source Markdown: instances/research/applied-study-data-collection-schedule-replanning-after-recruitment-delay-or-site-capacity-constraint.md

Linked pattern(s)¶

schedule-adjustment-and-replanning

Domain¶

Research.

Scenario summary¶

An applied research program already has an approved data-collection plan that sequences site activation, screening ramp checks, cohort recruitment targets, protocol-defined visit windows, specimen-processing cutoffs, source-data verification preparation, and a fixed interim data-cut handoff for internal analysis planning. Then the baseline plan stops being feasible: recruitment at one site lags below the expected accrual curve, a high-volume site loses coordinator capacity for several weeks, or both shifts compress the original path to the interim data cut without changing the non-waivable visit-window rules. The workflow should recompute a revised data-collection timeline, document which site milestones can move and which checkpoints must stay fixed, and prepare a coordination-ready replanning packet for the study operations lead, site managers, recruitment analytics partner, data management lead, and biostatistics liaison rather than deciding whether enrollment criteria should change, approving a protocol amendment, contacting participants, or executing the revised collection plan itself.

flowchart TD A["Recruitment delay or site-capacity constraint detected"] B["Refresh baseline collection plan, site accrual state, visit-window status, and fixed data-cut checkpoints"] C["Verify source freshness, capacity assumptions, and non-waivable study constraints"] D{"Any in-policy revised schedule preserves visit-window rules and the fixed interim data-cut handoff?"} E["Build revised data-collection timeline with resequenced site and cohort milestones"] F["Record moved milestones, fixed checkpoints, blocked alternatives, and residual timing risk"] G["Assemble coordination-ready replanning packet"] H["Study operations lead and required partners review for adoption"] I["Hold with escalation packet for infeasible constraints or uncertain inputs"] A -->|"Refresh current study state"| B B -->|"Run verification checks"| C C -->|"Fresh and usable"| D C -->|"Stale or uncertain inputs"| I D -->|"Yes"| E D -->|"No"| I E -->|"Document impacts"| F F -->|"Prepare handoff"| G G -->|"Route for adoption"| H I -->|"Escalate within planning boundary"| H

Target systems / source systems¶

Study-operations planner with the approved baseline collection schedule, site-level recruitment targets, cohort milestones, visit-window assumptions, and prior schedule versions
Recruitment dashboards, screening logs, and site-capacity trackers showing current accrual velocity, coordinator coverage, room or equipment availability, and blocked visit slots by site
Electronic data capture and specimen-tracking systems showing completed visits, upcoming protocol-window deadlines, source-data verification readiness, and any non-waivable collection cutoffs
Internal analysis-planning calendar or milestone register containing the fixed interim data-cut handoff, downstream cleaning checkpoints, and already-committed review dates that the revised schedule must preserve
Planning and coordination tools that can model dependency shifts, site-specific impacts, rejected alternatives, and versioned replanning packets for handoff
Restricted study-coordination workspace where rationale, unresolved blockers, stakeholder acknowledgements, and adoption status of the revised plan are recorded

Why this instance matters¶

This grounds the replanning pattern in research operations where the main problem is restoring a feasible data-collection path after recruitment or site-capacity changes invalidate the original study schedule. The valuable output is a revised timeline, an explicit dependency and impact ledger, and a coordination-ready handoff packet for human adoption. The workflow stays inside the planning family boundary by stopping before enrollment-policy changes, protocol amendment decisions, participant outreach, scientific tradeoff adjudication, or study execution.

Likely architecture choices¶

flowchart LR SOP["Study-operations planner approved baseline collection schedule, site-level recruitment targets, cohort milestones, and prior versions"] DASH["Recruitment dashboards, screening logs, and site-capacity trackers"] EDC["Electronic data capture and specimen-tracking systems"] CAL["Internal analysis-planning calendar or milestone register"] PLAN["Planning and coordination tools that model dependency shifts, site-specific impacts, and versioned replanning packets"] WORK["Restricted study-coordination workspace for rationale, unresolved blockers, stakeholder acknowledgements, and adoption status"] subgraph HUMAN["Human adoption boundary"] OWNERS["Study operations lead, principal investigator delegate, or data management owner"] end SOP -- "Baseline schedule, targets, milestones, and versions" --> PLAN DASH -- "Current accrual velocity, coverage, capacity, and blocked visit slots" --> PLAN EDC -- "Completed visits, protocol-window deadlines, readiness, and collection cutoffs" --> PLAN CAL -- "Fixed interim data-cut handoff, cleaning checkpoints, and review dates" --> PLAN PLAN -- "Recommendation-only revised timeline, site-specific impacts, and rejected alternatives" --> WORK WORK -- "Coordination-ready replanning packet, blockers, and adoption status" --> OWNERS OWNERS -- "Human adoption or escalation recorded without execution" --> WORK

An orchestrated multi-agent workflow fits because one role can refresh recruitment, visit-window, and site-capacity state, another can test candidate schedules against fixed data-cut and protocol-window constraints, and another can package the accepted replanning proposal with site-specific impacts and unresolved blockers.
Human-in-the-loop adoption remains necessary because the study operations lead, principal investigator delegate, or data management owner must approve any material movement of cohort milestones, site sequencing, or downstream handoff timing before the revised schedule becomes authoritative.
Recommendation-only autonomy is the right ceiling: the workflow can propose a feasible updated collection timeline and identify dependency risk, but it should not alter visit-window rules, authorize enrollment-policy changes, approve a protocol amendment, or trigger site execution steps.

Governance notes¶

Hard constraints should remain explicit throughout replanning: protocol-defined visit windows, fixed interim data-cut timing, specimen-processing or data-ingestion cutoffs, required source-data verification lead time, and any non-waivable site-activation or staffing rules.
The rationale and impact ledger should preserve lineage from the baseline collection plan to the revised proposal, including which site milestones moved, which checkpoints remained fixed, what alternatives were rejected, and what residual timing risk still remains.
Source freshness matters because a revised schedule built on stale accrual, visit-completion, or site-capacity assumptions can create false confidence and trigger another avoidable replanning cycle.
The coordination-ready handoff packet should share only role-relevant timing, dependency, blocker, and site-readiness detail rather than participant identifiers, health information, sensitive screening notes, or draft scientific interpretation.
The workflow should escalate instead of improvising when no in-policy timeline can preserve both the visit-window rules and the fixed interim data cut, when a proposed revision would effectively require enrollment-policy or protocol changes, or when unresolved site-capacity uncertainty makes any revised plan misleading.

Evaluation considerations¶

Time from recruitment-delay or site-capacity trigger to a revised data-collection timeline with explicit dependency impacts and adoption-ready handoff
Rate of replanning events resolved with an accepted revised schedule without forcing a full manual rebuild of the study collection plan
Frequency of adopted revised timelines that still miss visit-window or interim data-cut checkpoints because constraint interactions were not surfaced early enough
Audit usefulness of the rationale ledger for reconstructing which site milestones moved, which checkpoints stayed fixed, what residual timing risk remained, and why human owners accepted or escalated the revised plan