A research network trades on shared protocols across many member sites, and the coordinating centre has to keep them all consistent without owning their IT. Capture gives each site a coordinator portal, each study one set of forms, and the network one audit trail, with by-site filtering for the data team.
Free sandbox · No credit card · 21 CFR Part 11 aligned
Member sites
8
Ready to enrol
5
Enrolled so far
112
What a network coordinating centre needs from its platform
How networks work
A clinical research network is a standing group of sites, practices or hospitals that agree to take part in studies together. Some are practice-based networks in primary care, some are disease-specific collaborations, some are university consortia or site networks run by a site management organisation. What they share is that membership outlasts any one study. A coordinating centre negotiates governance, trains staff and holds relationships, then runs one study after another with the same member sites.
That standing structure changes what the software has to do. In a single trial, the sponsor builds a system for one protocol and one site list. In a network, the same coordinators will see multiple studies over the years, staff turnover is constant, and the sites range from a research hospital with a dedicated unit to a clinic where one nurse does research on Tuesdays. The platform therefore needs a gentle learning curve, clear role separation, and reliable identification of who did what at which site. It also needs to avoid asking sites for infrastructure they do not have.
Capture is browser-based, so a site needs a sign-in and training. Each study is built once by the coordinating centre. Site coordinators then have a separate portal, participants enrol by QR code that is site-specific or study-specific, and the data team filters and exports by site. The general model is described under multi-site clinical trial management, and the SMO and site network software page covers networks run by site management organisations.
Networks that last agree a core set of data elements that every study collects in the same way: demographics, medical history, concomitant medication, adverse events, a few core outcomes. When the forms are designed identically from study to study, sites learn them once and pooled analysis becomes possible. The demographics, medical history, concomitant medications and adverse event templates are a reasonable core. Capture does not enforce a network-wide data model; the coordinating centre builds that discipline into its own form standards.
Randomized
166 / 240
Open queries
24
Fields verified
84%
3 open queries · 92% SDV
7 open queries · 85% SDV
14 open queries · 61% SDV
0 open queries · 100% SDV
Site risk
Site 03 query backlog
Data lock
Site 04 ready to lock
Governance and ethics
Network studies often need a single ethics review to avoid repeating submissions at every site. In the United States, a single IRB is commonly required for federally funded multi-site research under NIH policy and the Common Rule cooperative research provision, with exceptions, and other countries have their own national models. Whatever the route, the coordinating centre needs a record of what was approved, which sites rely on it, and which version of the consent is in use. Capture helps with the consent version and the form lock: forms move from draft to approved, approved forms are locked for live use, and only approved forms appear in the casebook. The approvals file itself stays with your study documents.
Delegation of duties is a perennial inspection finding in multi-site research. Who is allowed to consent, who may enter data, who signs off as investigator. Capture uses role-based access, with researcher, site coordinator and admin roles, and investigators countersign consent with password re-authentication. Keep the delegation record in the delegation log template and the file index in the investigator site file index.
Training is the cost networks underestimate. Use the sandbox as the training environment: it has every feature, a coordinator can enter fake participants, trigger queries and sign forms, and nothing touches live data. The EDC UAT sandbox page explains how to use it for user acceptance testing before go-live.
Network need to build
| Network need | What it looks like | Where it lives in Capture |
|---|---|---|
| Member site access | Coordinators sign in, see only their site | Role-based access; separate site coordinator portal |
| Participant identity | Unique ID per site, names kept at site level | Site-level numbering; PII segregation with coded IDs for researchers |
| Recruitment at clinics | Hand out a code, participant enrols on their phone | Site-specific or study-specific QR enrollment |
| Consent across sites | One consent text, signed and countersigned electronically | eConsent; multi-site consent template |
| Data quality across sites | Same edit checks, queries and audit trail everywhere | eCRF with edit checks, auto-queries, audit trail |
| Coordinating centre oversight | Per-site enrolment, query load, overdue visits | By-site filtering, compliance view and exports |
| Analysis-ready datasets | Pooled data with dictionary | CSV or Excel with data dictionary; SDTM export |
Site activation tracking and some multi-study portfolio views are not built-in features; keep those records in your own tools.
Build the study once, invite one or two coordinators into the sandbox, and let them practise consent, entry and queries before the first live participant. Free, every feature, no credit card.
Quality across sites
Visiting every member site frequently is expensive and often unnecessary. Networks commonly combine central review of the data with targeted on-site checks. In Capture, edit checks flag impossible values at entry, auto-queries go to the site when a rule is broken, and source data verification can be set per field so monitors verify what matters for eligibility, safety and the primary endpoint. The risk-based monitoring page explains the approach and the query management page shows how queries are raised and resolved.
Look at the patterns by site. A site with a long list of open queries, late visits or a high rate of protocol deviations often needs support rather than blame, and a coordinating centre that sees this early can retrain before a pattern becomes a finding. Keep the monitoring visit report template for on-site checks, and use by-site exports to compare sites on the measures you agreed in advance.
For safety, adverse events and serious events are captured on standard forms at every site, with severity, seriousness and relationship as separate answers. The network’s safety lead sees the same record as the site. Reporting timelines depend on the protocol and local regulation; the SAE deadline calculator can help plan, and the decision stays with the responsible people.
Rollout
Settle the common data elements and edit-check conventions before building study-specific forms.
Upload the protocol for an AI draft of visits and forms, then review with the study team. Nothing is saved without review.
Each site coordinator enters fake participants, answers a query and signs a form.
Start with two or three sites, fix what the first coordinators find, then add the rest.
Look at enrolment, query age and visit lateness by site, and support the sites that lag.
Site coordinators work in their own portal and see their site’s participants. Researchers and the coordinating centre see coded IDs, and data can be filtered and exported by site.
No. QR-code enrollment and questionnaires open in the phone browser. Codes can be site-specific or study-specific.
Not as a built-in feature. Keep approvals, contracts and delegation records in your own tools and file them with your study documents.
Yes. Capture is used from Phase 1 through Phase 3, with site-level numbering, a site coordinator portal and by-site exports for multi-center work.
Capture provides 21 CFR Part 11-aligned controls: field-level audit trail, electronic signatures and role-based access. Compliance is shared with the sponsor’s validated use. This is not legal advice.
Keep exploring
Multi-site clinical trial management
Site coordinator portal and by-site data.
SMO and site network software
Networks run by site organisations.
Clinical trial software for study sites
The site coordinator view.
Risk-based monitoring and SDV
Central monitoring approach.
Delegation log template
Record who may do what.
Build once and train in the free sandbox. No credit card, and you pay only when you go live with real participants.