Why this matters
Status reports are decision tools, not diaries. A predictable rhythm and a narrow scope help the study team see what is ready, what is blocked, and who must act next. In Clinical Data Management (DM), the most useful updates focus on data the DM function directly controls:
- How current the electronic Case Report Form (eCRF) data are against what is expected for enrolled participants (currency).
- How clean the database is—fewer open queries, especially critical ones, and aging under control (cleanliness).
- Whether external data are present and reconciled (labs, devices, pharmacovigilance (PV)/safety, randomization) (reconciliations).
When DM keeps the update short, on‑time, and owner‑segmented, actions actually happen and database locks hold on schedule.
Scope: what to include vs exclude
Include (DM‑owned)
Currency What it means: The percent of expected eCRF pages/fields that are entered and, where applicable, verified (source data verification, SDV, or equivalent), based on visit schedules and data cuts to date. What to show:
- % entered vs expected, plus the count of overdue forms (expected minus entered) by site and visit
- Median days from visit to entry (entry lag)
- % verified vs expected (if verification is in scope)
- 6–8 week trend line (steady or improving is good)
Cleanliness What it means: How close the database is to “query‑free.” What to show:
- % forms with no open queries
- Open critical queries (count): queries on critical data, such as primary endpoint, safety, eligibility and dosing fields, as the Data Management Plan (DMP) defines them
- Query aging: median days open and % older than 14 days (aging “tail”)
- Short note for any negative spike (e.g., new edit checks deployed)
Reconciliations (externals) What it means: Two layers—presence (is an expected record present in both sources?) and value (do the key values match within tolerance?). What to show (by domain: central lab, device/wearable, PV/SAE, randomization, electronic patient‑reported outcomes (ePRO), imaging as applicable):
- Presence gaps (count), last data cut date, owner
- Value mismatches (count) and oldest open age
- Planned delivery windows and whether met
Coding & adjudication progress (if DM tracks execution) What it means: Where DM is responsible for dictionary coding (e.g., MedDRA/WHO‑DD) or tracking endpoint adjudication readiness. What to show:
- % coded vs total terms; pending auto‑coding rules; version info if relevant
- Endpoint packets assembled vs required; any blinding constraints
Risks & actions Every risk line should read: Owner → Action → Due date → Status (one line each).
Exclude (owned elsewhere—reference, don’t reproduce)
- SAE case narratives/timelines → PV/Medical Monitor (MM) owns.
- Enrollment vs plan / site staffing → Clinical Operations/Project Management (PM) owns.
- Protocol deviation review and classification → Clinical Operations/monitoring owns, with the Medical Monitor.
Tip: If stakeholders ask for these, link to the source dashboard; do not copy into DM status.
Cadence & roles
Frequency
- Weekly during active enrollment and during the final 8–10 weeks before database lock.
- Biweekly (every two weeks) in steady state (slower mid‑trial periods).
Audience
- Core study team (DM Lead, Clinical Lead, PM, Safety/PV lead as needed).
- Vendors join for their own item when their domain is red/blocked (e.g., lab presence gaps).
- Scope per audience: the core team gets the full page; sponsor leadership and governance committees get the top bar, lock gates and top risks; a vendor or a site (through its clinical research associate, CRA) sees only its own rows. While the study is blinded, no status view shows data by treatment arm.
Owners
- Each metric shows a named owner (e.g., Site 203 — CRA Smith; Lab Vendor — Jane Doe, PM; Coding — DM Analyst Lee).
- Escalation path is clear in the footer (e.g., PM → Sponsor DM Lead → Governance).
Why this rhythm? It balances signal vs noise: often enough to steer, not so frequent that teams ignore it.
Update structure (one‑page pattern)
Keep it to one page. Same layout, same day, every cycle.
Top bar
- Data cut timestamp (UTC or the study time zone), Study Week, LPLV ETA (Last Patient Last Visit), next governance date (e.g., a data safety monitoring board (DSMB) meeting or a lock rehearsal).
- One‑line risk headline (e.g., “Lab presence gaps persist at 2 sites; plan agreed.”)
Scorecards (owner‑segmented) Show Sites, Vendors, and Domains as three small blocks. Use simple Red/Amber/Green (R/A/G) or ✔/✖ indicators with 2–3 metrics each.
- Sites: % currency, % query‑free, % queries >14d
- Vendors: presence gaps, value mismatches, last delivery met?
- Domains: coding %, adjudication packets ready, randomization reconciled?
Lock‑gates snapshot A short checklist for readiness: expectedness (share of expected forms present, i.e., study‑level currency; not the safety meaning of the word), reconciliations, coding, adjudication, open criticals, user acceptance testing (UAT) defects affecting production (if any). Mark each gate R/A/G.
Backlog burndown (8‑week trend) Small sparkline or bullet trend: open criticals and % queries >14d. The aim is a downward slope or stable low line.
3–5 action notes Write them as: Owner → Action → Due date → Status. Avoid more than five; add or remove only as items close.
Suggested thresholds (tune to your SOPs):
- Currency green ≥95%; amber 90–94%; red <90%.
- % forms query‑free green ≥90%; amber 80–89%; red <80%.
- % queries >14d green ≤10%; amber 11–20%; red >20%.
- Presence gaps and value mismatches: green 0; amber 1–5; red >5 (per domain).
Worked examples (CV trial)
Context: Phase III cardiovascular (CV) outcomes study; eCRF in Rave; central lab and wearable heart‑rate device feeds; PV handled by a safety vendor. Data cut: Monday 06:00 UTC (Week 34).
Top bar
- Data cut Mon W34 06:00 UTC | Study Week 34 | LPLV ETA: Week 52 | Next Lock Rehearsal: Week 36
- Headline: Lab presence gaps at Sites 108 & 214 remain after cut; re‑delivery committed by vendor.
Scorecards
Sites (sample)
- Site 108: Currency 92% (amber); % query‑free 82% (amber); %>14d = 27% (red) → Owner: CRO Lead
- Site 214: Currency 96% (green); % query‑free 88% (amber); %>14d = 19% (amber) → Owner: CRA Patel
- Site 305: Currency 98% (green); % query‑free 94% (green); %>14d = 7% (green) → Owner: CRA Nguyen
Vendors
- Central Lab: Presence gaps = 12 (red), Value mismatches = 3 (amber). Last scheduled drop missed by 1 day. → Owner: Lab Vendor PM
- Wearable Device: Presence gaps 0 (green); downstream value QC pass; last drop on time. → Owner: Device Vendor PM
Domains
- Coding (AEs/ConMeds): 92% coded (amber); auto‑coding rules refined; backlog mostly new AEs from Site 108. → Owner: DM Analyst
- Endpoint Adjudication: Packets ready = 78% (amber); blinded data extracts on schedule; next adjudication meeting Week 35. → Owner: Clinical Lead
Lock‑gates snapshot
- Expectedness 97% (green)
- Reconciliations: Lab presence = red, Value = amber; Wearable green
- Coding amber; Adjudication amber
- Open criticals 18 (amber); % queries >14d = 15% (amber)
Backlog burndown (last 8 weeks)
- Open criticals: 31 → 29 → 26 → 24 → 22 → 20 → 19 → 18 (steady decline)
- %>14d: 24% → 23% → 22% → 21% → 20% → 18% → 17% → 15% (moving toward ≤10%)
Action notes (3–5 lines, self‑contained)
- Lab Vendor PM → Re‑deliver Week 34 cut with corrected patient‑ID mapping for Sites 108/214; Due Fri W34; Status: in progress.
- CRO Lead → Site 108 coaching: the CRA reviews query triage on site so staff answer critical and oldest queries first; DM adds 2 analysts for 2 weeks to review the answers and close resolved queries (the site makes every data correction); Due Fri W35; Status: scheduled.
- DM Analyst → Refine auto‑coding rules to capture common AE phrases seen at Sites 108/214; Due Wed W34; Status: done in UAT; promoting.
- Clinical Lead → Adjudication packet push: send next 40 packets; Due Thu W34; Status: on track.
How to read this page
- Presence gap = an expected external record (e.g., lab) exists in eCRF but is missing from the external feed (or vice‑versa).
- Value mismatch = records exist in both sources but key values differ beyond tolerance (e.g., a unit conversion error or a different collection date; rounding within tolerance is not a mismatch).
- %>14d = percent of open queries older than 14 days (aging tail).
Pitfalls & misconceptions
- Vanity counts (e.g., “queries closed last month”) don’t predict lock; aging and criticals do.
- Mixed denominators (e.g., using enrolled subjects for one metric and expected visits for another) make trends meaningless—state the denominator in the header.
- No data‑cut timestamp leads to “which numbers are these?” confusion. Always date/time‑stamp.
- Copy‑pasting cross‑functional charts (enrollment, staffing, PV narratives) bloats DM status and hides the signal. Link out instead.
- Definition drift (changing how currency is calculated mid‑study) breaks trendlines—lock definitions early and document them.
- Too many actions (15 bullets) ensures none get done. Cap at 3–5.
- Ownerless risks = no progress. Every red/amber needs a named owner and a due date.
Practice checklist
- Publish a one‑page template with sections: Top bar, Scorecards, Lock‑gates, Burndown, Actions.
- Always include data cut timestamp and denominators.
- Segment by owner (site/vendor/domain) with R/A/G or ✔/✖.
- Keep a 6–8 week trend for currency, cleanliness, and %>14d.
- Cap to 3–5 action notes; each = Owner → Action → Due date → Status.
- Use presence vs value for reconciliations; show both.
- Define and stick to thresholds (green/amber/red) agreed in the study plan.
- Clarify the escalation path in the footer.
Key points to remember
- Status reports are decision tools: keep them short, on‑time, and predictable—same day, same layout, same owners each cycle.
- Scope only what DM owns: currency, cleanliness, query aging, reconciliations; include coding/adjudication only if DM tracks execution; link out to PV narratives, enrollment, and staffing instead of duplicating them.
- Cadence: weekly during enrollment and the final 8–10 weeks pre‑lock; biweekly in steady state.
- Currency is the % of expected data entered and, where applicable, verified; always state the denominator and the data‑cut timestamp.
- Cleanliness is tracked with % query‑free, open criticals, and aging; define the aging tail as the % of open queries older than 14 days (or your study’s threshold).
- Reconciliations are reported as presence gaps and value mismatches by domain (lab, devices, PV/SAE, randomization, ePRO, imaging); show owner and last delivery met/missed.
- Use owner‑segmented views (site/vendor/domain) over global averages to drive action and accountability.
- Keep a 6–8 week trend for currency, cleanliness, and %>14d; avoid vanity counts and ensure denominators are consistent across metrics.
- Structure every update to one page: Top bar (cut timestamp, study week, LPLV ETA, next governance), Scorecards (site/vendor/domain with 2–3 metrics), Lock‑gates snapshot (R/A/G), Backlog burndown, and 3–5 action notes.
- Lock‑gates to show and color‑code: expectedness, reconciliations, coding, adjudication, open criticals.
- Agree and document thresholds per SOP/study plan (e.g., currency ≥95% green; %>14d ≤10% green) and do not change definitions mid‑study.
- Write actions as Owner → Action → Due date → Status; cap to 3–5 items to ensure closure.
- Every red/amber line needs a named owner and a clear escalation path in the footer.