Recruitment

Trials define the governed study context. Recruitment is the workflow surface for enrollment planning, tracking, and supporting operational decisions.

Population ownership

Protocol populations are defined in Plan > Recruitment > Population Segments.

• Mark exactly one segment as Design Population. This is the overall population intended for the study.
• Mark a separate protocol-defined subgroup as Study Cohort when it must be selectable in eligibility criteria, trial arms, enrollment goals, or Statistical analysis populations.
• Do not mark one segment as both roles.

Recruitment-only targeting segments can remain unflagged. They support operational planning without becoming protocol cohorts or USDM populations.

Generated Recruitment proposals may refer to criteria, indications, or steering members by a human-readable code or label. TrialStack resolves those references to a governed record only when the match is unique; ambiguous references remain unlinked for review instead of being guessed. Demographic representation uses separate race and ethnicity designations, and biological sex planning remains distinct from persona gender identity.

Why it matters

• a study moves into recruitment planning or execution
• recruitment work needs to stay anchored to the source trial
• teams need to review enrollment activity in trial context

From each side

• Use Trials for the overall study record.
• Use Trial Recruitment for recruitment-specific work.