SOP-903
Network Oversight of Member Sites (Metrics, Central QA, Escalation)
- Number
- SOP-903
- Category
- Network
- Edition
- Reference Edition 1.3
- Approx. pages
- 9
[YELLOW] the site fills in. [DEFAULT: green] a value the site may keep or change.
On this page
1. Purpose
This SOP describes how the Network Office of [NETWORK NAME] oversees the quality and performance of its member sites. It sets a small, defined metric set, the quarterly scorecard, risk-based central QA audits, CAPA trending across sites, escalation tiers with site support plans, and the sharing of inspection and audit lessons across the network. It does not move any investigator duty away from the PI at each member site.
2. Scope
This SOP applies only when [NETWORK NAME] has adopted operating Model N under SOP-100 Writing, Approving and Controlling SOPs. A Model S site ignores it.
In scope:
- the network metric set and the Member Site Performance and Quality Scorecard (F-903-01)
- central QA audits of member sites by the Network Office
- cross-site CAPA trending and network-wide CAPA
- escalation tiers and the Escalation and Site Support Plan (F-903-02)
- sharing of sponsor, IRB and FDA findings across the network as lessons learned
Out of scope:
- QC and internal audits run by each member site for its own studies, which stay under SOP-700 Internal Quality Control and Quality Assurance Audits
- study allocation decisions, which use scorecard results but are made under SOP-902 Network Study Feasibility, Allocation and Central Contracting
- onboarding a new member site and exit of a member site (SOP-901 Member Site Onboarding, Integration and Exit)
Who performs each activity at the Network Office or the member site follows Appendix B, Central and Site Responsibility Matrix (Appendix B, SOP-903 rows). Where a protocol, sponsor or IRB requirement is stricter than this SOP, follow the stricter requirement.
3. Responsibilities
| Role | Responsibilities |
|---|---|
| Network Quality Lead | Owns this SOP. Maintains the metric definitions, compiles F-903-01, plans and assigns central QA audits, runs cross-site CAPA trending, opens network-wide CAPAs, and manages escalations at Tier 2 and above. |
| Network Clinical Operations Lead | Provides startup and enrollment data, reviews the scorecard with each member site, and leads operational support actions in F-903-02. |
| Network Medical Director (where the network has one) | Reviews safety and eligibility metrics and findings with each PI and advises on clinical support actions. Advisory only: never assesses adverse events, confirms eligibility or signs for a PI. |
| Network Executive | Approves Tier 3 and Tier 4 escalation plans and actions. |
| Network Quality Committee | Approves the metric thresholds and the annual central audit plan with site risk ranks, and reviews scorecards for all member sites (SOP-900). |
| Site Director (each member site) | Supplies site data on time, reviews the site's scorecard, owns the site's response, and carries out F-903-02 actions. |
| Site Quality Lead (each member site) | Runs site QC and audits under SOP-700, keeps F-703-01 current, supports central audits, and reports site trends to the Network Quality Lead. Where Appendix B assigns the role centrally, the Network Quality Lead performs it. |
| Principal Investigator (PI) | Keeps full responsibility for the conduct of their studies. Reviews scorecard results and audit findings for their studies, approves study-level corrective actions, and decides any sponsor or IRB reporting. |
| All Research Staff | Record data accurately in the source systems the metrics draw on, and cooperate with central audits. |
4. Definitions
| Term | Definition |
|---|---|
| Network Office | The central organization of [NETWORK NAME], acting collectively. |
| Member site | A site location or legal entity that conducts studies as part of [NETWORK NAME] under its own PI or PIs. |
| N-Integrated | Model N in which one legal entity owns all member sites. N-Integrated defaults apply only where the member site and the network entity are the same legal entity. A separate subsidiary, or a professional corporation under a management services arrangement, follows the N-Affiliated rows for PHI, direction of staff, contract signature, records custody and payments unless counsel confirms otherwise (SOP-900, 5.2.1). |
| N-Affiliated | Model N in which member sites are separate legal entities bound by a network or affiliation agreement. |
| Network agreement | The written affiliation, management services or membership agreement between the Network Office and a member site that is a separate legal entity (N-Affiliated, or a subsidiary or professional corporation under SOP-900 5.2.1). |
| Metric | A defined measure with a fixed numerator, denominator, data source and reporting period, used the same way at every member site. |
| Threshold | The value of a metric that triggers review or escalation. Thresholds are set by the Network Office and recorded on F-903-01. |
| Important protocol deviation | As defined in SOP-308 Protocol Deviations and Noncompliance, using the sponsor's criteria. |
| Critical, major and minor finding | Severity grades for QC and audit findings as defined in SOP-700. |
| Network-wide CAPA | A CAPA opened and owned by the Network Office when the same root cause is found at more than one member site, or when a site finding shows a gap in a network SOP, system or service. |
| Lessons learned summary | A short written account of a finding and its root cause and fix, with all participant identifiers and PHI removed, shared with all member sites. |
5. Procedure
5.1 Principles
5.1.1
Network oversight adds to, and does not replace, each member site's own QC and audit program (SOP-700) and the PI's oversight of delegated work (SOP-302 Delegation of Authority, section 5.7). The PI at each member site stays responsible for the studies conducted there (21 CFR 312.60; 21 CFR 812.100; ICH E6(R3) Annex 1, 2.3).
5.1.2
Metrics are used to find where a member site needs support, and to protect participants and data. They are never used in a way that pressures staff to enroll ineligible participants, to skip or shorten the consent process, or to under-report deviations, adverse events or screen failures.
5.1.3
The Network Office does not set enrollment targets for a member site that exceed the site's own feasibility estimate for that study (SOP-200 Study Feasibility and Selection; SOP-902) without the PI's written agreement.
5.1.4
Staff at any member site may report pressure to enroll ineligible participants, or to misreport data, directly to the Network Quality Lead or under SOP-704 Research Misconduct and Fraud Reporting, without going through their site management.
5.2 Metric set
5.2.1
The Network Quality Lead maintains the metric set below. Each metric uses the same definition at every member site, so results can be compared. The Network Office may add or remove metrics only through a revision of this SOP under SOP-100 and SOP-900 Network Governance, SOP Hierarchy and Local Addenda.
| Metric | Definition | Data source |
|---|---|---|
| Startup cycle time | Calendar days from receipt of the final protocol (or site selection notice, as recorded) to site activation, for studies activated in the period. Median and range. | F-205-01 Study Activation Checklist; CTMS |
| Enrollment against target | Participants randomized or enrolled in the period divided by the agreed target for the period, by study. | F-303-01 Screening and Enrollment Log; CTMS |
| Screen-fail rate | Participants who signed consent and were not enrolled because they did not meet eligibility, divided by all participants who signed consent and completed screening, by study. Compared with the sponsor's expected rate where known. | F-303-01 |
| Deviation rate | Protocol deviations logged in the period per enrolled participant on study during the period, by study. | F-308-01 Protocol Deviation Log |
| Important deviation rate | Important protocol deviations in the period per enrolled participant on study, by study. | F-308-01 |
| Query aging | Number and percentage of open EDC queries older than [DEFAULT: 30 calendar days] at period end, by study. | Sponsor EDC reports |
| SAE reporting timeliness | SAEs reported to the sponsor within the protocol timeline divided by all SAEs reported in the period. | F-501-01 SAE Reporting Tracker |
| Consent error rate | Consents with at least one major or critical QC finding divided by consents reviewed in QC in the period. | F-700-01 Internal QC Review Checklist; F-301-01 |
| Aged monitoring findings | Monitoring follow-up actions open more than 30 calendar days past their due date at period end. | F-600-02 Monitoring Follow-Up Action Tracker |
| Training compliance | Staff with all required training current divided by all active research staff at period end. | F-103-01 Staff Training Log; F-103-02 |
| CAPA on-time closure | CAPAs closed by their due date divided by CAPAs due in the period. | F-703-01 CAPA Record |
5.2.2
SAE reporting timeliness is tracked centrally from dates only: date the site became aware, date reported to the sponsor, and the protocol timeline. The Network Office does not assess seriousness, causality or expectedness, which stay with the investigator (SOP-501 Serious Adverse Event and Expedited Safety Reporting). N-Affiliated: dates linked to a participant are PHI, so the site sends, for each SAE, the number of calendar days from awareness to the sponsor report and the protocol timeline, with no dates, participant IDs or event narrative, unless a pathway on F-905-01 covers more.
5.2.3
Rates with small denominators (for example, fewer than [DEFAULT: 5] enrolled participants in a study) are reported as counts and reviewed case by case, not compared as percentages.
5.2.4
The Network Quality Committee approves thresholds for each metric and records them on F-903-01. Thresholds are set in two levels: a review level (Tier 1) and an escalation level (Tier 2). A metric outside a threshold is a reason to look, not a finding in itself.
5.2.5
Where the network uses shared systems (CTMS, eReg, eSource) under SOP-905 Network Data, Systems, Privacy and Records Across Sites, the Network Quality Lead pulls metric data from those systems. Where a member site uses its own systems, the Site Director or Site Quality Lead submits the data on the F-903-01 data template by [DEFAULT: the 10th business day after quarter end].
5.2.6
Metric data sent to the Network Office contain no participant names, medical record numbers or other direct identifiers. Participant study ID numbers are used only where needed to check a data point. N-Affiliated: data crossing from a member site to the Network Office follow SOP-905 and are listed on F-905-01 Cross-Entity Data Flow Register.
5.3 Scorecard and review cadence
5.3.1
The Network Quality Lead compiles F-903-01 Member Site Performance and Quality Scorecard for each member site at least [DEFAULT: quarterly]. The scorecard shows each metric for the period, the prior [DEFAULT: 4] periods, the network median, the thresholds, and open escalations and CAPAs.
5.3.2
Before issue, the Network Quality Lead sends the draft scorecard to the Site Director, who may correct data errors within [DEFAULT: 5 business days]. Corrections are recorded on the scorecard with the reason.
5.3.3
The Network Quality Lead and Network Clinical Operations Lead review the scorecard with the Site Director, Site Quality Lead and PIs of each member site within [DEFAULT: 30 calendar days of quarter end]. The review notes, agreed actions, owners and dates are recorded on F-903-01.
5.3.4
Each PI reviews the study-level metrics for their own studies, in particular screen-fail rate, important deviations, SAE timeliness and consent errors, and signs the scorecard review record.
5.3.5
The Network Quality Lead presents scorecards for all member sites at a Network Quality Committee meeting at least [DEFAULT: twice a year], and feeds the results into each member site's management review under SOP-700, section 5.8.
5.3.6
A high screen-fail rate, or an enrollment rate far above target, is reviewed for eligibility errors as well as recruitment quality. The Network Quality Lead may request an eligibility QC sample under 5.4.
5.4 Central QA audits
5.4.1
The Network Quality Lead prepares a central audit plan each year as part of F-700-02 Annual Audit Plan and Audit Report, extending the site audit program in SOP-700, section 5.5. The plan covers every member site at least once every [DEFAULT: 2 years], with more frequent audits for higher-risk sites.
5.4.2
The Network Quality Lead rates each member site's risk using:
- scorecard results and trends
- number and complexity of active studies, first-in-class or high-risk products, vulnerable populations and decentralized elements
- new PI, new site, new location or staff turnover at key roles
- open critical or major findings, failed CAPA effectiveness checks
- sponsor, IRB or FDA findings in the last [DEFAULT: 2 years]
- time since the last audit
5.4.3
The Network Quality Lead may weight these factors to rank member sites. Any weights, and the resulting risk rank of each site, are recorded on F-903-01 and approved by the Network Quality Committee with the audit plan (SOP-900, 5.1.5).
5.4.4
Audit types include study audits, process audits (for example consent, IP management, safety reporting, delegation and training) and for-cause audits. A for-cause audit is triggered by a Tier 3 escalation, a critical finding, a credible integrity concern (SOP-704) or a request from a sponsor, IRB or PI.
5.4.5
The auditor is independent of the work audited. The Network Quality Lead assigns auditors so that:
- no one audits a member site where they work, supervise staff or hold a study role
- no one audits a central service they manage or deliver (SOP-904 Shared Staff, Cross-Site Coverage and Central Services)
- central functions run by the Network Quality Lead are audited by a qualified external auditor or by a Site Quality Lead from another member site
5.4.6
Site Quality Leads may audit other member sites on a rotation set by the Network Quality Lead. Auditors are trained on SOP-700 and this SOP, and the training is recorded on F-103-01.
5.4.7
Audits are notified, conducted and reported as in SOP-700, sections 5.6.2 to 5.6.8, using F-700-02. The report goes to the PI, the Site Director and Site Quality Lead of the audited site, and the Network Quality Lead.
5.4.8
N-Affiliated: the Network Office audits a member site only to the extent the network agreement allows. Before the first audit, the Network Quality Lead confirms in writing that the agreement covers audit rights, access to records and systems, confidentiality of audit reports, and access to PHI (with a BAA, DUA or other pathway under SOP-905 where PHI is viewed). Where the agreement does not cover an activity, the Network Office asks the member site to commission the audit itself and share a summary.
5.4.9
Central audit findings that are protocol deviations are logged by the member site on F-308-01 and handled under SOP-308.
5.5 Cross-site CAPA trending and network-wide CAPA
5.5.1
Each member site runs CAPA under SOP-703 Corrective and Preventive Action (CAPA). The Site Quality Lead sends the Network Quality Lead an extract of F-703-01 each quarter, including root cause category, severity, status and effectiveness result.
5.5.2
The Network Quality Lead reviews the extracts for:
- the same root cause at more than one member site
- the same finding type across sites after a change in a network SOP, system or central service
- overdue CAPAs and failed effectiveness checks by site
- privacy incidents by type and site, from each site's incident log (SOP-400 Participant Privacy and HIPAA in Research, section 5.10.9), as counts and categories without PHI
- repeated monitoring findings across sites and studies, from F-600-02
- late SAE reports by site and cause, from the data in 5.2.2
5.5.3
When the same finding or the same root cause appears at two or more member sites in a rolling [DEFAULT: 12 months], or a finding traces to a network SOP, shared system or central service, the Network Quality Lead opens a network-wide CAPA on F-703-01 in the network quality file. The network-wide CAPA follows SOP-703 for RCA, plan, effectiveness check and closure.
5.5.4
Each affected member site keeps its own CAPA open and links it to the network-wide CAPA by number. A site CAPA may close when its local actions are complete and verified, even if the network-wide CAPA is still open.
5.5.5
Actions that change a network SOP go through SOP-900. Actions that change site practice are carried out by the member site and verified by the Site Quality Lead.
5.5.6
N-Affiliated: the Network Office can require a member site to take part in a network-wide CAPA only where the network agreement says so. Otherwise it recommends the actions and records the site's decision on the network-wide CAPA record.
5.6 Escalation tiers
5.6.1
The Network Quality Lead assigns each member site an escalation tier at each scorecard review and whenever a trigger occurs. Tiers and triggers are:
- Tier 0, routine: all metrics within thresholds and no open critical findings. Normal quarterly oversight.
- Tier 1, watch: one or more metrics at review level, or a major audit finding. The Site Director explains the cause at the scorecard review and agrees actions recorded on F-903-01.
- Tier 2, support: a metric at escalation level for [DEFAULT: 2] consecutive quarters, three or more metrics at review level, an overdue major CAPA, or a sponsor letter of concern. The Network Quality Lead and Site Director prepare F-903-02 Escalation and Site Support Plan.
- Tier 3, intervention: a critical finding, a repeat major finding after a closed CAPA, a Form FDA 483 or warning letter, an IRB suspension, or failure to meet F-903-02 milestones. The Network Executive approves the plan, and a for-cause audit is scheduled.
- Tier 4, restriction: participant safety or data integrity at risk that the site cannot correct quickly, or a credible integrity concern under SOP-704. The Network Executive may pause new study allocation to the site (SOP-902) and recommend that the PI pause enrollment in affected studies.
5.6.2
Any staff member who finds a matter that could put participant safety at immediate risk reports it to the PI first and then to the Network Quality Lead the same day, without waiting for the scorecard cycle.
5.6.3
A tier moves down only when the exit criteria in F-903-02 are met and the Network Quality Lead records the evidence.
5.7 Escalation and Site Support Plan (F-903-02)
5.7.1
The Network Quality Lead and Site Director complete F-903-02 within [DEFAULT: 15 business days] of a Tier 2 or higher assignment, and within [DEFAULT: 5 business days] for Tier 4. The PI of each affected study reviews and signs the plan.
5.7.2
F-903-02 records:
- the trigger and supporting data
- the tier and the date assigned
- immediate actions to protect participants, if any
- related CAPAs (site and network-wide)
- support from the Network Office (for example extra QC, a floating CRC under SOP-904, retraining, regulatory help, workload reduction)
- actions at the member site, with owners and dates
- reporting to sponsors and IRBs, as decided by the PI
- exit criteria and the date of the next review
5.7.3
The Network Quality Lead reviews progress at least [DEFAULT: monthly] while a site is at Tier 2 or higher and records each review on F-903-02.
5.7.4
Pausing enrollment in an ongoing study is a PI decision made with the sponsor and, where required, the IRB. The Network Office may recommend it; in N-Integrated, where the member site is the same legal entity as the network entity, the Network Executive may also direct the member site's staff as their employer, but the PI makes and documents the study decision. The Regulatory Coordinator at the member site notifies the sponsor and IRB as required under SOP-502 Unanticipated Problems and Reportable New Information.
5.8 What the Network Office can require and recommend
5.8.1
N-Integrated, for member sites that are the same legal entity as the network entity: the Network Office can require use of network SOPs, the metric set, data submission, central audits, network-wide CAPA actions and F-903-02 actions, subject to the investigator duties that stay with each PI. N-Integrated defaults apply only where the member site and the network entity are the same legal entity. A separate subsidiary, or a professional corporation under a management services arrangement, follows the N-Affiliated rows for PHI, direction of staff, contract signature, records custody and payments unless counsel confirms otherwise (SOP-900, 5.2.1).
5.8.2
N-Affiliated: the Network Office can require only what the network agreement allows. Before a member site joins (SOP-901), the Network Executive confirms under SOP-900 5.9.1 that the agreement covers:
- the metric set and data submission timelines
- central audit rights and record access
- participation in network-wide CAPA
- escalation tiers and the consequences of Tier 3 and Tier 4 (for example pause of new allocations, termination of membership)
- confidentiality of scorecards and audit reports
- handling of PHI under SOP-905
5.8.3
Everything else is a recommendation. The Network Quality Lead records on F-903-02 whether the member site accepted or declined each recommendation and why.
5.9 Sharing findings across the network
5.9.1
The Site Director tells the Network Quality Lead within [DEFAULT: 2 business days] of receiving any sponsor audit report, IRB audit or noncompliance determination, FDA Form FDA 483, warning letter, RRA observation or untitled letter, at any member site (SOP-701 Sponsor and IRB Audits; SOP-702 FDA Inspections and Remote Regulatory Assessments).
5.9.2
The Network Quality Lead decides whether the finding could apply at other member sites and, if so, writes a lessons learned summary within [DEFAULT: 30 calendar days]. The summary states the finding, root cause, fix and what other sites should check. It contains no participant names, identifiers or PHI, and does not name staff.
5.9.3
Before release, the Network Quality Lead checks that the summary does not breach a CTA confidentiality term or reveal sponsor confidential information. Sponsor and study names are removed unless the sponsor has agreed.
5.9.4
Each Site Quality Lead confirms review of the summary and records any local check or action on F-703-01.
5.10 Records
5.10.1
The Network Quality Lead keeps F-903-01, F-903-02, central audit plans and reports, network-wide CAPAs and lessons learned summaries in the network quality file at [NETWORK QUALITY FILE LOCATION]. Retention follows SOP-402 Record Retention, Archiving and Destruction.
5.10.2
Records about a specific study (for example an audit finding that is a deviation, or a CAPA affecting the study) are also filed or referenced in that member site's ISF.
6. Related Forms and SOPs
- F-903-01 Member Site Performance and Quality Scorecard
- F-903-02 Escalation and Site Support Plan
- F-700-01 Internal QC Review Checklist
- F-700-02 Annual Audit Plan and Audit Report
- F-703-01 CAPA Record
- F-308-01 Protocol Deviation Log
- F-303-01 Screening and Enrollment Log
- F-501-01 SAE Reporting Tracker
- F-600-02 Monitoring Follow-Up Action Tracker
- F-103-01 Staff Training Log
- F-205-01 Study Activation Checklist
- F-905-01 Cross-Entity Data Flow Register
- Appendix B Central and Site Responsibility Matrix (SOP-903 rows)
- SOP-100 Writing, Approving and Controlling SOPs
- SOP-200 Study Feasibility and Selection
- SOP-302 Delegation of Authority
- SOP-308 Protocol Deviations and Noncompliance
- SOP-502 Unanticipated Problems and Reportable New Information
- SOP-700 Internal Quality Control and Quality Assurance Audits
- SOP-701 Sponsor and IRB Audits
- SOP-702 FDA Inspections and Remote Regulatory Assessments
- SOP-703 Corrective and Preventive Action (CAPA)
- SOP-704 Research Misconduct and Fraud Reporting
- SOP-900 Network Governance, SOP Hierarchy and Local Addenda
- SOP-901 Member Site Onboarding, Integration and Exit
- SOP-902 Network Study Feasibility, Allocation and Central Contracting
- SOP-904 Shared Staff, Cross-Site Coverage and Central Services
- SOP-905 Network Data, Systems, Privacy and Records Across Sites
7. References
| Reference | Title |
|---|---|
| 21 CFR 312.60 | General responsibilities of investigators |
| 21 CFR 812.100 | General responsibilities of investigators (devices) |
| ICH E6(R3) Principle 6 | Quality by design and critical to quality factors |
| ICH E6(R3) Annex 1, 2.3 | Investigator Responsibilities |
| ICH E6(R3) Annex 1, 3.12 | Noncompliance (sponsor) |
| FDA Guidance (2009) | Investigator Responsibilities: Protecting the Rights, Safety, and Welfare of Study Subjects |
| FDA Compliance Program 7348.811 | Clinical Investigators and Sponsor-Investigators (BIMO) |
Independent Site SOP Library. Licensed CC BY-NC 4.0 by the American Institute for Medical Research (AIMR), with added permission for any site's internal use (license terms). Not legal advice: each adopting site confirms state law, IRB and sponsor requirements with its own counsel and owns every step it approves.