Why this matters
One KPI layer; three windows. If everyone sees only what they can decide or do, meetings shrink and cycle time drops. The mistake most teams make is broadcasting the same “mega dashboard” to all audiences. That causes noise, unintentional unblinding, and slow decisions.
Terms used on this page (plain English):
- KPI (Key Performance Indicator): A small set of numbers we trust to run the study (e.g., % expected forms present, query aging, visit completion vs schedule).
- EDC (Electronic Data Capture): The system sites use to enter data.
- Other abbreviations: SAE = serious adverse event; IxRS = interactive response system (randomization and drug supply); PK = pharmacokinetics (drug concentration samples); VS = vital signs; ECG = electrocardiogram; HR = heart rate; BP = blood pressure; V3 = Visit 3; PI = principal investigator; CRA = clinical research associate; CRO = contract research organization.
- Blinding: Hiding treatment‑related information so decisions are unbiased.
- Expectedness: Whether a form/visit that should exist (per protocol schedule) is present; shown as % expected present. Not the safety meaning of the word (whether an adverse reaction is consistent with the reference safety information).
- Query aging: How long unresolved data queries have been open.
- RAG gate: A Red/Amber/Green status that signals whether a domain is “good enough” to pass an interim or lock gate (e.g., reconciliations, coding).
- Site contract / SOW: The site’s clinical trial agreement (CTA) and budget list what the site is paid for, e.g., each completed visit (milestone‑based payment), and any holdback: a share of payment retained until conditions the contract names are met (e.g., query aging back under the contract threshold, or site close‑out). Strictly, a statement of work (SOW) is a CRO’s or vendor’s contract; this page’s “SOW” means whichever contract applies.
Design rule: Build one shared KPI layer (definitions, filters, and thresholds) and render different views for Exec, ClinOps/Finance, and Sites. Avoid per‑audience calculations that drift. Stamp every view with the same data‑cut date and time so all three audiences discuss the same numbers.
Executive snapshot
Purpose: Give leadership a 2‑minute, blinding‑safe read: Are we on track? What could slip? Who owns the fix?
Show only three things
RAG gates for interim/lock Gate domains: Expectedness, Cleanliness (share of entered pages with no open queries, plus open critical queries; missing pages count under expectedness), Reconciliations (SAE, labs, IxRS, PK), Coding/Adjudication.
- Green: meets the gate threshold
- Amber: misses it by less than the agreed margin; needs an action plan
- Red: misses it by more than that margin; milestone at risk
Keep subject/site rows out of the exec view.
Burndown to milestone date (with confidence band) Remaining work to interim/lock (e.g., unresolved critical queries, missing expected forms). The band reflects recent completion velocity and known pauses (holidays, system maintenance). No raw tables.
Top 3 risks with owners/dates A one‑line risk, an owner, and a by‑when. Add a link to the mitigation plan, not to EDC records.
Blinding guardrails (Exec):
- Safe: progress to expected forms present, % coding complete, % SAE reconciliation complete.
- Unsafe: arm‑level event rates, response outcomes, or anything that hints at treatment assignment.
ClinOps/Finance view (payments)
Purpose: Decide “invoice now vs hold,” coach sites, and plan cash flow—without exposing unblinded signals.
Core tiles (site‑level aggregations):
Visit completion vs schedule For each site: percent of visits that should have occurred by today that are completed and entered in EDC. This is the most common basis for milestone‑based payments.
Timeliness
- Visit→Entry lag: median days from visit date to first entry in EDC.
- % Expected Present: share of expected forms/pages actually present.
Use these as readiness to invoice indicators.
Query aging % of open queries >14 days (or your contract threshold). When above threshold, trigger coaching or contractual holdback if applicable.
Payment notes Short text flags that affect release (e.g., “Missing source for VS at V3,” “Site placed on data freeze,” “PI on leave”).
Data definitions (keep them simple and inspectable):
- Expectedness: Derived from the protocol’s Schedule of Assessments. If Visit 3 requires VS+ECG+Labs for all randomized participants at Week 12, those items become “expected” for each participant once that participant’s Week 12 visit is due by its visit window (a form whose visit is not yet due does not count as missing).
- Completion: Visit marked complete and all required forms/pages present.
- Critical query: A query on data the Data Management Plan (DMP) defines as critical, such as primary endpoint, safety (e.g., missing SAE dates), eligibility or dosing data, tagged as critical in your KPI layer.
Blinding guardrails (ClinOps/Finance):
- Safe: counts and timeliness of visits/forms; invoice statuses; % coding complete.
- Unsafe: rates split by treatment arm, adjudication outcomes, endpoint results, any unblinded metadata in notes, IxRS kit or dispensing details, and PK concentrations or other drug‑level results (a count of PK samples received is safe).
Contract alignment tips:
- Mirror SOW milestones literally (e.g., “V3 completed” not “all queries resolved”).
- If your contract uses holdbacks tied to query aging or timeliness, display the exact threshold and current delta.
Site action board
Purpose: Give coordinators a one‑page to‑do list that reduces clicks: what’s missing, what’s aging, what to do next.
What to show
Missing expected (by subject → visit → form/page) Example row: SUBJ‑102 • Visit 3 • VS page missing • Due: 2025‑03‑12.
Open queries sorted by age and criticality Show every open query the site must answer. Each should cover a single issue (one fix per query), as DM writes them; multi‑issue queries stall progress.
Quality prompts Small tips, quoted verbatim from the protocol or the CRF completion guidelines, that prevent rework, e.g.,
- “VS: record posture and arm, repeat if HR >120.”
- “ECG: confirm machine time sync with site clock.”
One‑click deep links to EDC Each row links directly to the exact form or query. Respect role‑based access (each site sees only its own participants; staff open EDC with their own accounts) and audit trails.
Noise control (what not to show):
- No study‑wide charts or forecasts.
- No arm‑level anything.
- No aged metrics the site can’t influence (e.g., sponsor coding backlog).
Worked examples (CV trial)
Study context (self‑contained):
A Phase III cardiovascular (CV) trial has Visit 3 at Week 12 requiring Vital Signs (VS), ECG, and Safety Labs for all randomized participants. Contracts pay sites when Visit 3 is completed (all required forms present in EDC). The sponsor uses a 14‑day query aging threshold for coaching/holdback.
Site action board snapshot (Site B)
Missing expected:
- 11 VS pages missing at Visit 3 (subjects: 104, 109, 121, 125, 134, 142, 147, 152, 158, 163, 170).
Open queries:
- 9 queries >14 days old, 3 critical (missing visit dates for V3, inconsistent BP units on VS, ECG date/time mismatch).
Prompts shown:
- “VS: capture posture; if automated device used, round per device manual.”
- “ECG: verify device clock; enter 24‑hr time.”
Clickthroughs: Each row links straight to the subject’s V3 VS/ECG form in EDC.
What the coordinator does next (guided by the board):
- Finish the 11 missing VS pages for Visit 3.
- Prioritize the 3 critical queries (>14d).
- Answer the remaining aged queries from the source documents, correcting values in EDC with a reason for change; DM (or the CRA, for its own monitoring queries) reviews each answer and closes the query.
ClinOps/Finance view for Site B
- Visit completion vs schedule: 76% (out of 45 V3s expected by today, 34 are complete and entered; the 11 with a missing VS page are not).
- Timeliness: Median Visit→Entry lag = 5 days; % Expected Present = 92% for V3 forms (124 of 135: 45 visits × 3 required forms, minus the 11 missing VS pages).
- Payment milestone: “Visit 3 completed” not yet met for 11 subjects → partial invoice only (the 34 completed visits).
- Query aging: 22% of open queries (9 of 41) are >14 days old → triggers site coaching; holdback applies per the site contract.
Exec snapshot (roll‑up including Site B)
- RAG gates: Expectedness = Amber (several sites at 85–90%); Cleanliness = Amber (critical queries still open, e.g., 3 at Site B); Reconciliations = Amber (SAE‑EDC mismatches pending); Coding = Green.
- Burndown: On track to interim in 3 weeks if Site B and Site F clear V3 missing pages in the next 5 business days and the open critical queries are answered and closed before the interim data cut.
- Top risks: Site B staffing gap (owner: CRA; due: Friday), IxRS‑EDC visit date drift (owner: Data Eng; due: Wednesday), Central lab file delay (owner: Vendor PM; due: Monday).
Pitfalls & misconceptions
- Anti‑pattern: Re‑using the same “study dashboard” for all audiences.
- Anti‑pattern: Including unblinded fields in exec or site views (arm‑level rates, outcome‑bearing adjudications).
- Misconception: Paying on “queries resolved.” Most contracts pay on visit completion and expectedness; query status, where a contract uses it at all, usually affects only a holdback.
- Process smell: Multi‑issue queries. They confuse ownership and slow closure.
- Governance gap: Different definitions per audience (e.g., “complete” means different things). Fix by centralizing the KPI layer.
Practice checklist
- Build all views from the same KPI layer (one definition of expectedness, completion, criticality).
- Strip unblinded fields from exec/ClinOps/site views.
- Align finance metrics exactly to contract/SOW milestones and holdback triggers.
- Sort site queries by age and criticality; prefer single‑issue queries.
- Provide one‑click deep links from every site item to the exact EDC form/query.
- Show execs only RAG gates, burndown, top risks with owners/dates.
- Publish definitions next to metrics (hover/footnote) so teams can self‑audit.
- Review the views in a blinding check before go‑live.
Key points to remember
- One truth layer, many windows: Build a single KPI layer (shared definitions, filters, thresholds) and render tailored views for Exec, ClinOps/Finance, and Sites. Publish definitions alongside metrics to prevent drift and enable self‑audit.
- Expectedness vs completion: Expectedness comes from the Schedule of Assessments; completion means required forms/pages are present and the visit is marked complete. Payments typically map to milestone/visit completion, not generic “queries resolved.”
- Blinding guardrails: Share counts and timeliness (e.g., % expected forms present, % coding complete, query aging). Do not expose arm‑level rates, endpoint outcomes, or adjudication results in Exec/Finance/Site views.
- Executive snapshot (2‑minute read): Show only RAG gate status, burndown with a confidence band, and top risks with owners/dates—no subject/site rows or raw tables.
- ClinOps/Finance (payments): Site‑level visit completion vs schedule, Visit→Entry lag, % expected present, query aging vs threshold (e.g., >14 days), and brief payment notes. Mirror SOW milestones and holdback rules exactly; display thresholds and current deltas.
- Site action board (one page): Answer what’s missing, what’s aging, and what to do next. Use single‑issue queries and one‑click deep links to the exact EDC item. Exclude study‑wide charts and sponsor backlog items the site can’t influence.
- Gate readiness via RAG domains: Track Expectedness, Cleanliness, Reconciliations (SAE, labs, IxRS, PK), and Coding/Adjudication to signal interim/lock readiness.
- Burndown shows remaining critical work: Focus on unresolved blocking items (missing expected forms, critical queries). Reflect recent completion velocity and known pauses (holidays, system maintenance); avoid dumping raw tables.
- Manage query aging explicitly: Monitor % of open queries over the contract threshold as a trigger for coaching/holdbacks; make the threshold and current status visible.
- Governance & compliance: Keep all views sourced from the shared KPI layer, perform a blinding check before go‑live, and ensure deep links respect role‑based access and audit trails.