Recruitment
How the main trial record connects to recruitment workflow in TrialStack.
Trials define the governed trial context. Recruitment is the workflow surface for population, enrollment-target, channel, and recruitment-strategy planning.
Population ownership
Protocol populations are defined in Plan > Recruitment > Population Segments.
- Mark exactly one segment as
Design Population. This overall trial population is available to Randomization and trial-arm relationships. - Mark a separate protocol-defined subgroup as
Study Cohortwhen subgroup-specific relationships are needed in eligibility criteria, Randomization, 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 trial moves into recruitment planning
- recruitment work needs to stay anchored to the source trial
- teams need to review enrollment assumptions and goals in trial context
From each side
- Use Trials for the overall trial record.
- Use Trial Recruitment for recruitment-specific work.