Solutions · Site coordination

Assign, support and track sites without forwarding spreadsheets.

For central offices and site networks coordinating several research sites on the same trial: who has which candidates, which site is falling behind, and what each site has recorded.

Each site, its workload and its alerts — on one page.

Select a site. Alerts are rules over the records: no activity in seven days, the largest backlog, or a record that has waited more than two weeks.

SYNTHETIC

Fictional sites

SITE-03 · SYN-CKD-201 active

Easton Ridge Clinical Research Center

Last activity: 9 d ago
Assigned
24
Awaiting review
15
More info required
2
Investigator review
2
Median wait (awaiting)
12 d

Enrolled 0 of target 10 · consent recorded 1

Consent and enrollment are events recorded by site staff.

Operational alerts

  • No screening activity in 9 days (threshold: 7).
  • Oldest awaiting record has waited 16 days.

Contact roles

  • Site principal investigator assigned in workspace
  • Lead coordinator assigned in workspace
  • Data contact optional
Fig. S1 — Site profile, SYN-CKD-201. Three fictional sites. Counts computed from synthetic screening records; consent and enrollment are site-entered events.

Workload you can see — and rebalance.

Candidates are assigned to a site when they enter screening. When one site’s queue grows, a manager can reassign records to another active site; the move is recorded and the original site’s history is kept.

  • Spot it

    SITE-02 holds 21 of the trial’s 54 awaiting records.

  • Check it

    Open the site’s backlog by age before moving work.

  • Rebalance it

    Reassign to a site that is active for the trial, with a reason.

Site workload by status

Each site’s assigned candidates, split by current screening status.

  • SITE-01Northfield Research Clinic38
  • SITE-02Calder Valley Medical Research Unit33
  • SITE-03Easton Ridge Clinical Research Center24
  • Awaiting Review
  • More Information Required
  • Potentially Eligible
  • Investigator Review
  • Not Eligible
Calculation. Count of screening records per site and current status. Synthetic sample · SYN-CKD-201

Sites see their own candidates. Nothing more.

Access is granted per site. Signing in grants nothing by itself.

Site-scoped access by role
RoleCan seeCan do
Research coordinatorOwn sites’ candidates and evidenceReview, request information, refer
Site investigatorCandidates referred to them at their siteRecord investigator decision
Recruitment managerAll sites in the trialAssign, reassign, reopen
Read-only stakeholderAggregate counts onlyView shared reports

Site events, recorded by site staff.

TrialBridge doesn’t contact candidates or hold consent forms. Sites record milestones so the central team sees progress without asking for it.

In the first release, candidates are pseudonymous. Sites resolve identity in their own authorised systems — not in TrialBridge.

  • Contacted

    Site staff contacted the candidate through their own systems

  • Consent recorded

    Consent obtained under the site’s process; the form stays in the site’s system

  • Screen failed at site

    Failed at the site’s formal screening visit, with reason

  • Enrolled

    Enrolled in the study; the record of truth remains the study’s own system

  • Withdrawn

    Withdrew after consent, with optional reason

Reports scoped to what the reader may see.

Reports are generated as jobs, limited to the requester’s sites, and every download is logged.

  • Site workloadAssigned, awaiting, more-info and referred per site · CSV · PDFMVP scope
  • Recruitment progressFunnel and events by site over a date range · CSV · PDFMVP scope
  • Screening outcomesOutcomes and screen-fail reasons by site · CSV · PDFMVP scope
  • Scheduled site summariesWeekly report to site leads · Email linkPlanned · V2

Coordinating several sites on one study?

Show us how work moves between your sites today. We’ll map it to site-scoped queues, alerts and reports.