Research sites, site networks, hospitals and academic medical centers choosing a CTMS to run their own studies, participant visits and site finances. Sponsor and CRO CTMS products are out of scope.
Scope This list serves research sites, not sponsors and CROs. A site CTMS runs participant visits, site budgets and sponsor invoicing; a sponsor or CRO CTMS oversees many sites and countries (monitoring, country start-up, portfolio views). Their workflows differ, so sponsor and CRO products (Veeva Vault CTMS, Oracle Siebel CTMS, Medidata CTMS, IQVIA) belong on a separate list with their own criteria. Products that support participant follow-up alongside a site CTMS are also included; the feature notes distinguish this from dedicated CTMS operations.
These notes describe the products in the CTMS guide.
RealTime-CTMS
Best for
Independent research sites and site networks that want CTMS, eSource, eReg and participant payments from one vendor.
What to consider
RealTime pairs strong participant and visit tracking with a full set of its own site tools. It publishes no customer count or prices and lists no EHR integration.
Research sites and study teams that need ongoing participant engagement, screening, consent, questionnaires and follow-up across clinical trials and research studies
What to consider
WeGuide supports the participant-engagement side of running clinical trials and research studies. Screening, consent, questionnaires, reminders and remote follow-up work together in one study program, and dashboards show participant check-ins and questionnaire progress. The Integration Engine connects existing study systems where needed. Sites requiring study budgets, sponsor invoicing or site-wide operational management can use a dedicated CTMS alongside it; the need for additional software depends on those workflows.
Less suitable for
Replacing a site CTMS for study budgets, sponsor invoicing, billing compliance or site-wide operational management.
Single and double checks describe documented support for an individual feature. Double checks use the extended definition for that feature. Unknown means the available evidence does not establish support.
Expand a feature definition or support note for context and its original source.
RealTime-CTMS vs WeGuide (CTMS): category feature evidence and sources. Products are not ranked.
Category feature
RealTime-CTMS
WeGuide
Study, participant and visit trackingFeature definitions
Supported
Study participants or visits can be tracked.
Extended support
Participant outreach or pre-screening plus visit scheduling are documented.
RealTime-CTMS
Extended support
RealTime-CTMS tracks subjects from referral to completion, calculates visit target dates with window enforcement, and supports recruitment database queries and pre-screening tracking.
Recruitment queries and pre-screening combine with visit target dates and window enforcement.
WeGuide
Supported
Dashboards show participant check-ins and questionnaire progress. This is participant follow-up, not a claim of full site visit-calendar or monitoring management.
Participant progress is documented; site-wide visit scheduling is not established here.
Site financesFeature definitions
Supported
Study budgets, invoicing, receivables or payment reconciliation are documented.
Extended support
Study finance workflows include research billing designations or billing-grid links to an EHR.
RealTime-CTMS
Supported
It tracks budgets, completed visits, invoices with aging reports, receivables, payables and subject stipends through SitePay, but RealTime does not describe research billing compliance features.
Study finances and stipends are stated; research billing compliance is not described.
WeGuide
Unknown
No public evidence reviewed establishes study-budget, sponsor-invoicing or site-receivables workflows in WeGuide. Its published role is a participant layer alongside the CTMS.
Native trial tools are named alongside the RealTime Connect API.
WeGuide
Extended support
The Integration Engine connects participant data with REDCap and other EDC systems using REST or FHIR APIs. Confirm any specific CTMS connector and field mapping.
Named client evidence establishes base adoption without a published customer or site count.
WeGuide
Supported
BRACE and INHERIT document participant research deployments. These examples are not CTMS customer counts or evidence that WeGuide performs full site operations.
Trial/security standards are stated; the note establishes neither a SOC report type nor public report access.
WeGuide
Supported
WeGuide states ISO 27001:2022 certification and support for GDPR, HIPAA and 21 CFR Part 11. The public material does not provide the certificate or an audit report.