Schedule

Trials hold the governed study record. Design owns schedule timelines, visits, and treatment-cycle definitions. Activities structures activity assignments and presents the same schedule through Grid, Flow, and Timing views, with visit sections directly below the selected visualization.

Why it matters

• a study needs a formal schedule or visit structure
• reviewers need to understand the planned timeline in trial context
• schedule updates need to stay attached to the governing trial
• downstream standards outputs need a traceable projection without rewriting the authored design

Schedule views

The timeline marked Main Timeline is selected by default. When a design contains multiple timelines, the timeline selector changes all three views together:

• Grid is the activity-by-timepoint Schedule of Activities matrix.
• Flow is a read-only diagram of visit order, predecessor links, and transition conditions.
• Timing is a read-only diagram of planned days, relative timing, and visit windows.

The visit sections are the timepoint-oriented editor. They remain below the selected visualization and appear individually in the table of contents, so Timepoints is not duplicated in the view selector. Selecting a visit in any view scrolls to its section. A generated cycle visit opens its authored source visit because generated instances cannot be edited directly.

The section header shows the active view and its icon in a split control. Every menu option has its corresponding view icon, and the active icon is reused by the Schedule of Activities section and table-of-contents entry. Open the menu to switch to another view, or use the adjacent fullscreen icon to open the active view centered in a fullscreen modal.

The Cycles ArrayTable in Design defines which authored visits repeat, the cycle range, and the cycle length. When cycles exist, Activities projects the derived visits and activity assignments automatically and keeps only generated rows read-only. Existing page and visit actions remain available for authored schedule data. The projection never writes generated cycle instances back into Design.

Deleting an authored visit is a confirmed governed change. Before deletion, TrialStack summarizes the affected activity placements, successor links, and repeating-cycle groups. On confirmation it removes the visit, its legacy and structured placements, predecessor references, and relative links to deleted scheduled activities. Activity definitions shared by another placement are preserved, while unreferenced definitions are pruned.

The repeating-cycle configuration is cascaded and rebased in the same governed save as the Trial Design transaction. Deleted visits, scheduled activities, and overrides are removed from cycle groups; a group whose final source visit is deleted is removed. The design and cycle versions therefore commit together or roll back together, and the change remains visible in Activity history.

From each side

• Use Trials for the study record.
• Use Design to define timelines, visits, and repeatable cycles.
• Use Activities to assign activities and inspect the selected timeline through any schedule view.
• Use the Trial Summary Standards section for standards preferences and Exports under Build for export history and conformance verification.