This is a ready-to-use controlled log for issues found through sponsor oversight of a CRO or service provider. The tell that separates real oversight from theater is the closed loop: a signal detected, escalated, investigated, corrected, and verified, with the trail intact. This log is where that trail lives. Replace every <<FILL: ...>> placeholder with your own specifics and route it through document control. A filled sample row follows. This content is general educational reference, not legal or regulatory advice.
Purpose
Capture every oversight issue for a study or provider relationship, from signal to verified closure, so the sponsor can demonstrate it knew about problems in time to act and drove them to resolution. A program that can show even one or two such closed loops demonstrates oversight far more convincingly than a binder of unbroken green metrics.
Scope
Any issue surfaced by oversight: a KPI or quality tolerance limit (QTL) breach, a deviation cluster, an audit-trail anomaly, an access-control gap, a safety-reporting failure, a TMF backlog, a failed metric trend, an audit finding, or a whistleblower report, for <<FILL: study / provider>>.
Field definitions
| Field | Format | Required | Who enters | When |
|---|---|---|---|---|
| Issue ID | Controlled unique ID | Yes | Oversight owner | On detection |
| Date detected | Date | Yes | Oversight owner | On detection |
| Source / signal | Text | Yes | Oversight owner | On detection |
| Provider / activity | Text | Yes | Oversight owner | On detection |
| Classification | Minor / Major / Critical | Yes | QA | On triage |
| CTQ factor affected | Text / None | Yes | QA | On triage |
| Escalated to | Role(s) | Yes | Oversight owner | On escalation |
| Escalation date | Date | Yes | Oversight owner | On escalation |
| Within target timeline? | Yes / No | Yes | QA | On escalation |
| CAPA reference | Doc number | If raised | QA | On CAPA open |
| Correction / corrective action | Text | Yes | CAPA owner | During resolution |
| Effectiveness check | Text + date | Yes for Major/Critical | QA | On closure |
| Status | Open / In progress / Closed | Yes | Oversight owner | Ongoing |
| Sponsor-knew gap (days) | Number | Yes | QA | On review |
The sponsor-knew gap is the days between when the provider first knew and when the sponsor knew. A large gap is itself a finding about the oversight, regardless of the issue.
The log
| Issue ID | Detected | Source / signal | Provider / activity | Class | CTQ affected | Escalated to | Esc. date | On time? | CAPA ref | Corrective action | Effectiveness check | Status | Knew-gap (d) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
<<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> |
<<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> |
Classification and timeline (define once, apply consistently)
| Class | Trigger examples | Escalation target | Timeline |
|---|---|---|---|
| Critical | Data integrity concern, safety reporting failure, serious GCP breach, chain-of-identity break | Sponsor QA head + study director; steering committee | <<FILL: within 1 business day>> |
| Major | QTL breach, deviation cluster, access-control gap, repeated KPI miss | Sponsor oversight lead + QA | <<FILL: within 5 business days>> |
| Minor | Isolated KPI miss, minor documentation gap | Provider PM, tracked | Next governance meeting |
Acceptance criteria for the log
- Every oversight issue is logged with a classification and the CTQ factor it affects (or none).
- Critical and major issues show an escalation within the target timeline; misses are visible.
- Major and critical issues link to a CAPA with a correction and an effectiveness check.
- The sponsor-knew gap is recorded and reviewed; a large gap prompts a look at the oversight itself.
- At least one fully closed loop (signal to verified effectiveness) is demonstrable for the study.
References
ICH E6(R3) Good Clinical Practice, sponsor oversight and quality management. 21 CFR 312.50 and 312.56 (sponsor responsibilities and monitoring). ICH E8(R1), critical-to-quality factors.
Confirm the in-force version for every region the study touches before issue.
Retention
Retain this log as a controlled quality record for not less than <<FILL: retention period tied to essential-records retention>>, and retain superseded versions per the records retention schedule.
Revision history
| Version | Date | Author | Summary of change |
|---|---|---|---|
<<FILL: 1.0>> | <<FILL: date>> | <<FILL: author>> | Initial issue. |
Filled sample rows
Illustrative rows for study XYZ-201.
| Issue ID | Detected | Source / signal | Provider / activity | Class | CTQ affected | Escalated to | Esc. date | On time? | CAPA ref | Corrective action | Effectiveness check | Status | Knew-gap (d) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| OI-014 | 04 Feb 2026 | Audit-trail review: edits to eligibility fields near lock | Prime CRO / data management | Critical | Endpoint integrity | Sponsor QA head + study director | 04 Feb 2026 | Yes | CAPA-2026-031 | Locked field permissions corrected; all edits reviewed and justified | 06 Mar 2026, no further unexplained edits over 30 days | Closed | 1 |
| OI-018 | 18 Feb 2026 | QTL breach: important protocol deviations 6.1% vs 5% | CRO / site conduct | Major | Data reliability | Oversight lead + QA | 20 Feb 2026 | Yes | CAPA-2026-035 | Retraining at two high-deviation sites; monitoring intensified | 15 Apr 2026, deviation rate back to 3.8% | Closed | 2 |
| OI-021 | 02 Mar 2026 | KPI: query resolution 12 days vs 10 | EDC vendor | Minor | None | Provider PM | 03 Mar 2026 | Yes | n/a | Extra data-management resource added | Reviewed next governance, resolved | Closed | 0 |
Row OI-014 is the closed loop an inspector wants to see: the sponsor found the signal itself through audit-trail review, escalated it the same day, drove a CAPA, and verified over 30 days that the fix held, with a knew-gap of one day. That single traced loop is stronger evidence than a year of green KPIs.
Common inspection findings this log prevents
- The sponsor learned of a material problem only at the inspection, with no record of detection or response.
- Issues raised in meetings but never escalated, tracked, or closed.
- Escalation with no CAPA linkage, so a real problem produced an email thread and nothing more.
- No effectiveness check, so a “closed” issue recurred.
- A large sponsor-knew gap that nobody noticed, meaning the oversight was slow even when it eventually worked.
How to adapt this log
- Set the classification triggers and timelines once, in your oversight plan, and apply them here consistently.
- Record the sponsor-knew gap on every issue; it is the metric that grades your oversight, not just the issue.
- Link every major and critical issue to a CAPA with an effectiveness check; do not close on the correction alone.
- Use the log to prove closed loops in an inspection. Pair it with the sponsor oversight plan and the article sponsor oversight of CROs and vendors.