1. Purpose
This SOP sets how the Network Office of [NETWORK NAME] oversees the quality and performance of member sites: the metric set and quarterly scorecard, central QA audits, CAPA trending across sites, escalation tiers with site support plans, and sharing of findings.
2. Scope
This SOP applies only when [NETWORK NAME] has adopted Model N. Network terms are defined in SOP-N1 section 4.
In scope: the metric set and F-903-01; central QA audits; cross-site CAPA; escalation tiers and F-903-02; sharing of sponsor, IRB and FDA findings.
Out of scope: each member site's own QC, quarterly quality review and CAPA (SOP-14, SOP-08), which continue; allocation decisions, which use scorecard results under SOP-N3; onboarding and exit (SOP-N2).
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. Compiles F-903-01, plans and assigns central audits, runs cross-site CAPA trending, assigns tiers and manages Tier 2 and above. |
| Network Clinical Operations Lead | Supplies start-up and enrollment data, reviews scorecards with sites and leads operational support. Where not appointed, the Network Quality Lead does this. |
| Network Executive | Approves Tier 3 and Tier 4 plans and may add operational metrics (5.3.4). |
| Network Quality Committee | Owns and approves metric thresholds, the annual central audit plan and site risk ranks. |
| Network Medical Director | Optional. Reviews safety and eligibility results with PIs. Advisory only. |
| Site Director | Supplies site data on time, reviews the scorecard, owns the site response and carries out F-903-02 actions. |
| Site Quality Lead | Runs site QC and CAPA, supports central audits and sends the quarterly CAPA extract. |
| Principal Investigator (PI) | Reviews and signs results for the PI's studies, approves study-level actions, and decides any sponsor or IRB report and any enrollment pause. |
4. Definitions
| Term | Definition |
|---|
| Metric | A measure with a fixed numerator, denominator, data source and period, used the same way at every member site. |
| Threshold | The metric value that triggers review (Tier 1 level) or escalation (Tier 2 level), recorded on F-903-01. |
| Study activation | As in SOP-03: the point at which F-205-01 is approved and the sponsor has given written notice that the site may enroll. |
| Network-wide CAPA | A CAPA the Network Office opens and owns when one root cause appears at more than one member site or traces to a network SOP, system or service. |
| Lessons learned summary | A short account of a finding, root cause and fix, with no participant identifiers or staff names, shared with all member sites. |
5. Procedure
5.1 Day-one minimum
5.1.1The day-one items for this SOP are in SOP-N1 5.1.1: metric definitions with interim thresholds set by the Network Quality Lead for the first two quarters, escalation tiers, the same-day safety route (5.6.2) and the finding-report rule (5.8.1). For each separate member site entity, the network agreement covers the SOP-N4 terms in SOP-N1 5.8.1.
5.1.2The first scorecard is issued for the first full quarter after the network start date. The first central audit plan is approved within [DEFAULT: 6 months].
5.2 Principles
5.2.1Network oversight adds to each PI's oversight (SOP-02) and replaces none of it.
5.2.2Metrics are used to find where a site needs support and to protect participants and data. They are never used to pressure staff to enroll ineligible participants, shorten consent, or under-report deviations, adverse events or screen failures. The Network Office sets no enrollment target above a site's PI-approved feasibility estimate without the PI's written agreement. Compensation linked to enrollment follows SOP-N3 5.7.6.
5.2.3Staff at any member site may report pressure to enroll ineligible participants or to misreport data directly to the Network Quality Lead, to [NETWORK GOVERNING BODY CONTACT], or under SOP-M5, without going through site management.
5.3 Metric set
5.3.1The Network Quality Lead keeps the quality metric set below. Definitions are the same at every member site and change only by revision of this SOP.
| Metric | Definition | Source |
|---|
| Start-up time | Calendar days from receipt of the final protocol at the site to study activation, for studies activated in the period. Median and range. The site selection notice date is recorded as a secondary field and not used in the metric. | F-205-01 |
| Enrollment against target | Participants enrolled or randomized in the period divided by the period target. The target is the CTA enrollment commitment prorated by month or, where the CTA sets none, the PI-approved expected estimate on F-200-01 prorated; the Network Clinical Operations Lead records it on F-903-01 at activation. | F-303-01 |
| Screen-fail rate | Consented participants not enrolled for eligibility divided by consented participants who completed screening. | F-303-01 |
| Deviation rate and important deviation rate | Deviations, and important deviations, in the period per enrolled participant on study. | F-308-01 |
| Query aging | Open EDC queries older than [DEFAULT: 30 calendar days] at period end, number and percent. | 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 |
| Consent error rate | Consents with a major or critical QC finding divided by consents reviewed in QC. | F-301-01; F-700-01 |
| Aged monitoring actions | Monitoring actions open more than 30 calendar days past due at period end. | F-600-02 |
| Training compliance | Staff with all required training current divided by active research staff. | F-103-01 |
| CAPA on-time closure | CAPAs closed by the due date divided by CAPAs due in the period. | F-703-02 |
5.3.2SAE timeliness is tracked from dates only. The Network Office never assesses seriousness, causality or expectedness. A separate member site entity sends, for each SAE, the days from awareness to sponsor report and the protocol timeline, with no dates, study IDs or narrative, unless a pathway on F-905-01 covers more.
5.3.3Metric data contain no names, medical record numbers or other direct identifiers. Data sent with study IDs or dates follow SOP-N6 5.6. A site's own scorecard goes only to that site and the Network Office. Any scorecard, pack or report shared beyond them, including Network Quality Committee packs, suppresses small counts as SOP-N6 5.6.1 sets.
5.3.4The Network Quality Committee records in its minutes the reason for each threshold change; a threshold is never loosened to avoid a tier or a disclosure. The Network Executive may add operational metrics (for example contract cycle time, invoice aging, revenue per study) by a dated memo attached to F-903-01, with one definition used at every site. Operational metrics are never used for any purpose 5.2.2 forbids and do not set tiers.
5.3.5Where shared systems hold the data, the Network Quality Lead pulls them. Otherwise the Site Director submits the F-903-01 data template by [DEFAULT: the 10th business day after quarter end]. Data from a separate member site entity cross to the Network Office only as listed on F-905-01.
5.4 Scorecard review
5.4.1The Network Quality Lead compiles F-903-01 for each member site each quarter, showing each metric, the prior [DEFAULT: 4] periods, the network median, thresholds and open escalations. The Site Director may correct data errors within [DEFAULT: 5 business days]; corrections are recorded with the reason.
5.4.2Within [DEFAULT: 30 calendar days] of quarter end, the Network Quality Lead (and Network Clinical Operations Lead where appointed) reviews the scorecard with the Site Director, Site Quality Lead and PIs, and records notes, actions, owners and dates on F-903-01. Each PI reviews the study-level results for the PI's studies and signs the review record. The site may use this meeting as its SOP-14 quarterly quality review where it covers the SOP-14 inputs.
5.4.3A screen-fail rate or enrollment against target at Tier 1 level or above is reviewed for eligibility errors, and the Network Quality Lead may request an eligibility QC sample.
5.4.4The Network Quality Lead presents all scorecards to the Network Quality Committee at least [DEFAULT: twice a year].
5.5 Central QA audits
5.5.1Each year the Network Quality Lead prepares a central audit plan on F-700-02, approved by the Network Quality Committee. Where Appendix B assigns internal audit centrally, the plan gives each such member site the annual internal audit SOP-14 requires. Every other member site runs its own SOP-14 audit and receives a central audit at least every [DEFAULT: 2 years]. Sites in the top [DEFAULT: third] of the risk rank receive at least one central audit a year.
5.5.2Risk rank uses scorecard results; number, complexity and risk of active studies; new PI, site, location or key staff turnover; open critical or major findings and failed effectiveness checks; sponsor, IRB or FDA findings in the last [DEFAULT: 2 years]; and time since the last audit. Any weights and the resulting rank are recorded on F-903-01.
5.5.3Audit types are study, process and for-cause. A for-cause audit follows a Tier 3 assignment, a critical finding, a credible integrity concern, or a request from a sponsor, IRB or PI.
5.5.4The auditor is independent of the work audited: no one audits a site where they work, supervise or hold a study role, or a central service they manage or deliver. Central functions run by the Network Quality Lead are audited by an external auditor or a Site Quality Lead from another site.
5.5.5Audits are run and reported as in SOP-14. The report goes to the audited site's PI, Site Director and Site Quality Lead and to the Network Quality Lead. Findings that are deviations are logged by the site on F-308-01 under SOP-08.
5.5.6For a separate member site entity, the Network Office audits only as the network agreement allows, including access to PHI under a pathway on F-905-01. Where the agreement does not cover an activity, the Network Office asks the site to commission the audit and share a summary.
5.6 Escalation tiers and support plans
5.6.1The Network Quality Lead assigns a tier at each scorecard review and when a trigger occurs:
- Tier 0, routine: metrics within thresholds; no open critical finding.
- Tier 1, watch: a metric at review level, or a major audit finding. 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, a Form FDA 483, or a sponsor letter of concern. F-903-02 required.
- Tier 3, intervention: a critical finding, a repeat major finding after a closed CAPA, a Form FDA 483 observation the Network Quality Lead grades major or critical, a warning letter, an IRB suspension, or missed F-903-02 milestones. The Network Executive approves the plan and a for-cause audit is scheduled.
- Tier 4, restriction: a risk to participant safety or data integrity that cannot be corrected, or protected by an interim measure the PI documents, within [DEFAULT: 5 business days], or a credible integrity concern. The Network Quality Lead makes the call and records it on F-903-02. The Network Executive may pause new allocation (SOP-N3) and recommend that the PI pause enrollment.
5.6.2Anyone who finds a matter that could put a participant at immediate risk tells the PI first and the Network Quality Lead the same day.
5.6.3The Network Quality Lead and Site Director complete F-903-02 within [DEFAULT: 15 business days] of Tier 2 or 3 and within [DEFAULT: 5 business days] of Tier 4. It records the trigger, immediate protective actions, related CAPAs, Network Office support (for example extra QC, a floating CRC, retraining), site actions with owners and dates, sponsor and IRB reporting decided by the PI, and measurable exit criteria. The PI of each affected study signs it. The Network Quality Lead reviews progress at least [DEFAULT: monthly]; a tier moves down only when exit criteria are met and the evidence is recorded.
5.6.4Pausing enrollment in an ongoing study is a PI decision made with the sponsor and, where required, the IRB. For a site that is the network entity, the Network Executive may also direct staff as their employer, but the PI makes and records the study decision. The Regulatory Coordinator notifies the sponsor and IRB as SOP-09 requires.
5.7 What the Network Office can require
5.7.1For a member site that is the network entity, the Network Office can require use of network SOPs, data submission, central audits, network-wide CAPA actions and F-903-02 actions, subject to each PI's investigator duties.
5.7.2For a separate member site entity (Hybrid Rule, SOP-N1 5.2.2), the Network Office can require only what the network agreement allows. Before the site joins, the Network Executive confirms the agreement covers the terms in SOP-N1 5.8.1 that point to this SOP. Everything else is a recommendation, and the Network Quality Lead records on F-903-02 whether the site accepted or declined it and why.
5.8 Cross-site CAPA and shared findings
5.8.1The Site Director tells the Network Quality Lead within [DEFAULT: 2 business days] of receiving a sponsor audit report, IRB noncompliance determination, Form FDA 483, warning letter or RRA observation.
5.8.2Each Site Quality Lead sends a quarterly extract of the site CAPA log (root cause category, severity, status, effectiveness result) and privacy incident counts by type, without PHI. The Network Quality Lead opens a network-wide CAPA on F-703-01, logged on F-703-02, when the same finding or root cause appears at two or more sites within [DEFAULT: 12 months], or a finding traces to a network SOP, shared system or central service. Each affected site keeps its own CAPA, linked by number, and may close it when its local actions are verified. Changes to network SOPs go through SOP-N1. A separate member site entity takes part as its agreement requires; otherwise the Network Office recommends and records the site's decision.
5.8.3Where a finding could apply elsewhere, the Network Quality Lead writes a lessons learned summary within [DEFAULT: 30 calendar days], checks it against CTA confidentiality, and removes sponsor and study names unless the sponsor agrees. Each Site Quality Lead records the review and any local check.
5.8.4The Network Quality Lead keeps F-903-01, F-903-02, audit plans and reports, network-wide CAPAs and summaries in [NETWORK QUALITY FILE LOCATION]. Study-specific records are also filed or referenced in the site ISF. Retention follows SOP-12.
- F-903-01 Member Site Performance and Quality Scorecard
- F-903-02 Escalation and Site Support Plan
- F-205-01 Study Activation Checklist
- F-303-01 Screening and Enrollment Log
- F-308-01 Protocol Deviation Log
- F-501-01 SAE Reporting Tracker
- F-600-02 Monitoring Follow-Up Action Tracker
- F-700-01 Internal QC Review Checklist
- F-700-02 Annual Audit Plan and Audit Report
- F-703-01 CAPA Record
- F-703-02 CAPA Log
- F-905-01 Cross-Entity Data Flow Register
- SOP-02 Roles, PI Oversight, Delegation and Conflicts of Interest
- SOP-08 Protocol Deviations and CAPA
- SOP-09 Safety Reporting (AEs, SAEs, IRB-Reportable Events, Pregnancy)
- SOP-12 Privacy, Electronic Systems and Record Retention
- SOP-14 Quality Control and Quality Review
- SOP-M5 Research Integrity and Misconduct Reporting
- SOP-N1, SOP-N2, SOP-N3, SOP-N6
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 |
| FDA Compliance Program 7348.811 | Clinical Investigators and Sponsor-Investigators (BIMO) |
| Reference Edition SOP-903 | Network Oversight of Member Sites (background and full wording) |