Free scoping read. A written assessment of your manuscript in two business days, at no cost.

Start one
Contents

Academy · Research Data Analytics & AI · Statistical risk monitoring

Monitoring Clinical Risk with Biostatistics: Key Risk Indicators and Central Statistical Monitoring

Statistical monitoring of trial risk is effective in one specific sense and unproven in another, and the distinction determines how it should be used. Flagged sites reliably improve afterwards, a finding well documented across thousands of sites. Whether these methods correctly identify the sites that have problems is a separate question, and the published classification performance is sufficiently poor that a flag should be treated as a question to be investigated rather than a finding to be acted upon.

Pubrica AcademyWritten by the medical writing and biostatistics teams Reviewed byPubrica biostatistics team Published9 October 2026 Last checked9 October 2026 Reading time11 minutes Sources30 peer-reviewed

When a central monitoring report names four sites, the immediate question is whether these are the sites with problems, and it is this question that the literature answers least well. Among the reviewed methods reporting classification statistics, only one of seven reached a sensitivity of 90% or more, whereas five of six reached a negative predictive value of 90% or more. These methods are therefore effective at indicating that a site is probably functioning well but poor at detecting the sites that are not. This asymmetry should inform the entire monitoring design, although many monitoring plans are written as though the opposite were the case.

Learning objectives

  • What a key risk indicator is, and the four properties that distinguish a usable indicator from one that is merely reportable
  • What central statistical monitoring looks for that a key risk indicator cannot capture
  • What the evidence on post-flag improvement shows, and why the before-and-after design limits the inference
  • How to interpret sensitivity, specificity and predictive values for a monitoring method, and which of these is most relevant at a given base rate
  • How to set a threshold when the consequence of a false positive is damage to a site relationship
  • What to record when a signal is investigated, so that a programme accumulates its own validation data

Common misconceptions

  • “A statistical flag means the site has a problem.” Among the reviewed methods reporting classification statistics, only 1 of 7 reached a sensitivity of at least 90% and only 1 of 6 reached a positive predictive value of at least 90%. A flag should therefore be regarded as a hypothesis.
  • “The absence of a flag means that the site is functioning well.” This is closer to the truth than the reverse, since 5 of 6 methods reached a negative predictive value of at least 90%; however, negative predictive value is inflated when problems are rare, so it reflects reassurance about the base rate as much as about the site.
  • “The improvement data prove that these methods work.” The data show that flagged sites improve. Among 1,111 sites across 159 studies, 83% of statistically monitored sites improved, compared with 56% in historical studies without such monitoring; across 212 studies and 1,676 flagged sites, 82.9% improved on the statistical score. These are before-and-after comparisons on sites selected for extreme values, so regression to the mean contributes to the effect and cannot be separated from it.
  • “A larger number of indicators provides better coverage.” At a fixed threshold, more indicators produce more false positives and a review that is unlikely to be completed. An indicator set that is not linked to named critical-to-quality factors tends to grow without limit.
  • “Risk-based monitoring replaces on-site monitoring.” It redirects on-site monitoring rather than replacing it. The value of a signal lies in indicating where monitoring staff should be deployed; a programme that generates signals but deploys no one has automated the reporting rather than the monitoring.

The function of statistical risk monitoring

Two distinct techniques are grouped under a single heading, and they fail in different ways.

Key risk indicator monitoring defines a metric set in advance — query rate per form, time from visit to data entry, screen failure proportion, protocol deviation rate, adverse event rate per participant-month, withdrawal rate — attaches a threshold to each, reviews them on a schedule and specifies an action when a threshold is crossed 3,6. Its strength is that it is explicit and auditable. Its weakness is that it can detect only the problems anticipated when the metrics were chosen.

Central statistical monitoring models the accumulating data and asks which sites are statistically atypical across many dimensions at once — distributions, variances, digit patterns, inter-visit intervals, correlation structures that should hold and do not 12,17. Its strength is that it can detect patterns that were not specified in advance. Its weakness is that atypical data are not necessarily erroneous: a site enrolling a genuinely different population will appear atypical for legitimate reasons.

Neither method directly monitors clinical risk in the sense of participant safety. Both monitor the data and draw inferences about the conduct that produced them 4. That inferential step is the principal source of uncertainty, and it is routinely omitted from the presentation of results. Our page on trial quality strategies places both techniques within the wider quality framework, and biostatistics support addresses model specification.

Properties of a usable key risk indicator

Four properties are required. An indicator lacking any of them is likely to be reported and then ignored.

It traces to a named critical-to-quality factor. If the aspect of trial integrity or participant safety that the indicator protects cannot be stated, it is a metric rather than a risk indicator, and it will compete for attention with the indicators that matter 21.

It has a numeric threshold set in advance. Not “monitored for unusual values”, but a value at which action is required, chosen before the data arrive, because a threshold chosen after the distribution has been seen describes the data rather than setting a standard.

It has a denominator that makes sites comparable. Raw counts penalise large sites. Rates per participant, per visit or per participant-month allow a site with 8 participants and a site with 80 to appear in the same report meaningfully.

It has an owner and an action. A named role that receives the signal, a period within which a response is required, and a defined first action. Indicators without owners are the main reason that monitoring reports become long without changing practice.

A practical consequence: a set of six to ten well-constructed indicators, each traceable to a critical factor, outperforms a dashboard of forty. The open-source {gsm} package used in risk-based quality management evaluates 12 key risk indicators, which is a reasonable order of magnitude to aim at — see our page on R for trial analysis for the tooling side.

Evidence on post-flag improvement

Two reasonably large data sets point in the same direction.

In a review of 1,111 sites across 159 studies at 23 organisations, sites monitored with statistical data monitoring improved on data inconsistency and risk-signal metrics in 83% of cases, against 56% of sites in two historical studies run without it 1. Across a central monitoring platform covering 212 studies and 1,676 sites with key risk indicator signals at 23 sponsor organisations, 82.9% of flagged sites improved on the statistical score and 81.1% improved on the observed indicator value, with mean movements of 66.1% and 72.4% respectively 3.

These are substantial effects, consistent across independent data sets, and they constitute the strongest argument for such a programme. They are, however, before-and-after comparisons on sites that were selected because their metrics were extreme 1,3. Sites selected for extreme values tend to move toward the average at the next measurement whether or not any intervention occurs; this is regression to the mean, and no feature of these study designs separates it from the effect of the monitoring. The comparison against 56% in historical studies partially addresses this, since those sites were not selected in the same way, but it is a historical rather than a concurrent control.

In summary, flagged sites improve substantially, the programmes are associated with better metrics than historical practice, and the available designs cannot establish how much of that improvement is attributable to the intervention. This is sufficient to justify such programmes. It is not sufficient to support the claim that the method identifies the right sites, which is a separate question with a separate answer.

The improvement evidence, and what each study design can support

StudyScaleFindingWhat the design cannot show
Statistical data monitoring review1,111 sites, 159 studies, 23 organisations83% of monitored sites improved on data inconsistency and risk-signal metrics (95% CI 80% to 85%), against 56% of sites in two historical studies without itControl is historical rather than concurrent, so secular change in data practices is not excluded
Central monitoring platform analysis212 studies, 1,676 flagged sites, 23 sponsor organisations82.9% improved on the statistical score and 81.1% on the observed indicator value; mean movements of 66.1% and 72.4%Before-and-after on sites selected for extreme values, so regression to the mean is not separable from the intervention effect

Both findings concern improvement in flagged or monitored sites. Neither addresses whether the flagged sites were the ones with real problems, which is the question the classification statistics above answer.

83%of statistically monitored sites improved
56%of sites improved in historical studies without it
82.9%of 1,676 flagged sites improved on the statistical score

Site improvement associated with statistical monitoring. The first two figures come from a review of 1,111 sites across 159 studies at 23 organisations, with a 95% confidence interval of 80% to 85% on the 83%. The third comes from a central monitoring platform analysis of 212 studies and 1,676 sites with key risk indicator signals, in which 81.1% also improved on the observed indicator value.

Limitations in classification performance

A scoping review of dynamic site-level risk assessment methods included 30 reports; among those reporting classification statistics, the results were as follows 4. Sensitivity of at least 90% was reached by 1 of 7 methods, specificity of at least 90% by 4 of 7, positive predictive value of at least 90% by 1 of 6, and negative predictive value of at least 90% by 5 of 6.

Each of these four measures answers a different question, and conflating them is the most common error in discussions of performance by vendors and sponsors.

Sensitivity is the proportion of genuinely problematic sites that are flagged. That only one method in seven reached 90% indicates that most of these methods miss a substantial share of real problems. An assurance strategy that relies on central monitoring to detect misconduct or systematic error is undermined by this figure.

Specificity is the proportion of sound sites correctly not flagged. Four of seven at 90% or above is respectable, but it still implies that roughly one in ten sound sites is flagged even by the better-performing methods.

Positive predictive value is the measure of greatest practical relevance when a report arrives: given a flag, the probability that a real problem exists. That only one of six methods reached 90% indicates that, for most methods, a meaningful share of flags are false. Moreover, because positive predictive value depends on the base rate, in a trial in which serious site problems are genuinely rare the proportion of false flags will be higher than any single study reports.

Negative predictive value is the reassurance value of the absence of a flag, and it is the measure on which these methods perform best, with 5 of 6 at 90% or above. The same base-rate arithmetic, however, inflates it: when problems are rare, almost any method that indicates “no problem” will usually be correct.

Taken together, these figures indicate that statistical monitoring is better at reassurance than at detection 4. It is a useful tool when the monitoring design accounts for this limitation, and a hazardous one when it is treated as an assurance mechanism for the most consequential failures.

Classification performance of reviewed site-level risk assessment methods

MetricWhat it answersMethods reaching 90% or above
SensitivityOf the sites that genuinely have a problem, the proportion that are flagged1 of 7
SpecificityOf the sound sites, the proportion correctly not flagged4 of 7
Positive predictive valueGiven a flag, the probability that a real problem exists1 of 6
Negative predictive valueGiven no flag, the probability that the site is sound5 of 6

From a scoping review of dynamic site-level risk assessment that included 30 reports; denominators differ because not every report provided every statistic. Positive and negative predictive values depend on the underlying frequency of site problems, so both will differ in any given trial from the values reported in a single study.

Threshold setting when false positives carry costs

Every threshold represents a trade-off between missing real problems and querying sound sites, and the second cost is usually underestimated because it is incurred in site relationships rather than in budgets. A site that receives three unfounded queries tends to stop regarding the fourth as informative, and the monitoring programme loses the cooperation on which it depends.

Three principles apply. First, the threshold should be set against a consequence rather than a percentile: the relevant question is not “which sites are in the worst 5%” but “at what value would we want someone to look”. A percentile threshold guarantees a constant number of flags whether or not anything is wrong. Second, thresholds should be differentiated by the severity of what the indicator protects. An indicator attached to eligibility or safety reporting warrants a sensitive threshold and the resulting false-positive load; an indicator attached to data entry timeliness does not. Third, the first action should be proportionate — a data query rather than a visit, an enquiry rather than an accusation — so that the cost of a false positive is small enough for a sensitive threshold to be affordable.

The base rate is the quantity that most teams never estimate, and it governs the interpretation of every other measure. If serious conduct problems are expected at perhaps a handful of sites in a hundred, even a highly specific method will produce more false flags than true ones; this follows from arithmetic rather than pessimism. Designing the response pathway on that assumption, rather than on the assumption that a flag indicates a problem, preserves the credibility of the programme.

Responding to a signal and recording its disposition

The value of a signal depends on the response to it. Four elements make a response defensible.

A named recipient and a period. The person who receives the signal and the deadline for action are both specified in the monitoring plan rather than decided for each signal.

A proportionate first action. Usually a documented query to the site asking a specific question, not a general request for explanation. “Fourteen of your 22 participants have a baseline weight recorded as a round multiple of five kilograms; please tell us how weight is measured and recorded at your site” elicits an answer, whereas “Your data shows anomalies” elicits defensiveness.

A disposition record. A record of what was flagged, what the investigation found, what was done, and whether the signal was judged true or false. This is the most valuable practice in the area, because it is the only source of classification data on a programme’s own performance that will ever exist 11,18. After a year, a programme can state its own positive predictive value, which is more relevant to its next protocol than any published figure.

A feedback loop into the indicator set. Indicators that have never produced a true positive in two years are candidates for removal; a recurring true positive that no indicator caught is a candidate for a new one.

This complements the wider documentation requirements in the risk management plan and with trial operations support.

The query that follows a central monitoring signal (figures below are illustrative)

Invites defensiveness

Our central statistical monitoring has identified your site as an outlier on several data quality metrics. Please review your data entry processes and confirm that all source documentation is complete and accurate. A monitoring visit may be scheduled if concerns persist.

No specifics. “Several data quality metrics” gives the site nothing to check, so the only possible reply is a general assurance, which is uninformative.

Treats the flag as a finding. With a positive predictive value of 90% or more in only 1 of 6 reviewed methods, a flag is not a finding, and presenting it as one expends credibility that will be needed later.

Implied threat. “A monitoring visit may be scheduled” converts an enquiry into a sanction, which makes the site’s answer defensive rather than informative.

No comparison data. The site cannot tell whether it is mildly or grossly atypical, so it cannot judge how seriously to take the query.

No disposition. Nothing will be recorded about what the signal turned out to be, so the programme learns nothing from it.

Invites an answer

Our central monitoring review of data to 31 March flagged one specific pattern at your site: of 22 participants with a baseline weight recorded, 14 are recorded as an exact multiple of five kilograms, against 3 of 19 and 4 of 24 at the two other sites in your region. This may simply reflect how your scales display and how staff transcribe the reading, which is why we are asking rather than assuming. Could you tell us what equipment is used for baseline weight, whether the reading is recorded directly into the case report form or transcribed from a separate note, and whether more than one person performs the measurement? No action is required on existing records at this stage. We will record your answer against this signal in the monitoring log; if the explanation is the measurement equipment, we will note the pattern as explained and exclude this indicator from escalation for your site.

The pattern is named precisely with its comparison, so the site can check it and either explain or correct it in a single reply.

The most likely innocent explanation is offered first, which is accurate given the predictive values and keeps the relationship usable for the next signal.

The questions asked are the ones that distinguish the innocent explanation from the problematic one, so the reply is diagnostic rather than reassuring.

Stating that no retrospective action is required at this stage prevents the site from making unnecessary data changes that would obscure the pattern.

The disposition is recorded, which builds the only dataset capable of establishing the programme’s own false positive rate.

A monitoring programme depends on site cooperation, and every unfounded accusation reduces it. The second version elicits a usable answer and preserves the relationship, which matters because most flags will prove to be explicable.

Limits of statistical monitoring

Three limits warrant explicit statement, because a programme that claims to cover them is likely to be believed.

Anything that is not in the data. A participant who was not properly consented, a source document created retrospectively, a device calibrated on paper only — none of these leaves a statistical trace if the resulting data appear ordinary. Statistical monitoring detects implausible data, not implausible conduct that produced plausible data 12.

Small sites. Each of these methods works by comparing a site against the others, and a site with eight participants supports almost no inference. The sites with the fewest participants are therefore the least amenable to statistical monitoring, and they are also the sites at which single-operator variation has the largest effect.

Early trial stages. Before data accumulate, there is nothing to model. Risk monitoring is weakest in the period in which protocol misunderstandings are most likely to develop, which argues for front-loading training and conducting early targeted visits rather than waiting for a signal.

This does not make the technique a poor investment; rather, it makes it one layer of a quality system whose other layers — prospective design, protocol feasibility review, training and documented escalation — perform the work that statistics cannot 9,10,16. Our page on imprecision addresses the related problem of interpreting small numbers as though they were informative.

Key points

Key points

Statistical risk monitoring performs better at reassurance than at detection, and monitoring design should reflect this. Among reviewed site-level risk assessment methods, a sensitivity of at least 90% was reached by 1 of 7 and a positive predictive value of at least 90% by 1 of 6, whereas a negative predictive value of at least 90% was reached by 5 of 6; the absence of flags is therefore informative, while a flag is a hypothesis. The improvement evidence is encouraging: 83% of 1,111 statistically monitored sites improved, compared with 56% in historical studies without such monitoring, and 82.9% of 1,676 flagged sites improved on their statistical score. Both, however, are before-and-after designs on sites selected for extreme values, so regression to the mean cannot be separated from the effect of the intervention. Indicator sets should be small and traceable to named critical factors, thresholds should be set against consequences rather than percentiles, the first action should be a specific question rather than an accusation, and the disposition of every signal should be recorded, since that record constitutes the only classification data a programme will possess.

Application to your study

Application to your study

  1. The indicator set should be small and traceable. Six to ten indicators are appropriate, each mapped to a named critical-to-quality factor, with any untraceable indicator reclassified as information only.
  2. Every indicator should have a denominator. Rates should be expressed per participant, per visit or per participant-month, so that a site with 8 participants and one with 80 can be compared meaningfully in the same report.
  3. Thresholds should be set against consequences rather than percentiles. A percentile threshold flags a fixed number of sites regardless of whether any problem exists.
  4. The base rate should be estimated before predictive values are interpreted. Where serious site problems are rare within a programme, most flags will be false positives irrespective of the specificity of the method.
  5. The first action in response to a flag should be a specific question. The query should name the pattern, provide the comparison, offer the innocent explanation and pose the questions that distinguish it from the problematic one.
  6. The disposition of every signal should be recorded. The record should state what was flagged, what it proved to be, what action was taken, and whether the signal was a true or false positive. The programme’s own positive predictive value should be reviewed at 12 months.
  7. Statistical monitoring should not be relied upon for small sites or early phases. Both are structurally unsuited to this form of monitoring and should instead be covered by training and targeted early visits.

Frequently asked questions

Less reliably than its use implies. Among reviewed site-level risk assessment methods reporting classification statistics, only 1 of 7 reached sensitivity of at least 90% — so most methods miss a substantial share of genuinely problematic sites — and only 1 of 6 reached a positive predictive value of at least 90%, so a meaningful share of flags are false. The methods perform better in the other direction: specificity of at least 90% in 4 of 7 and negative predictive value of at least 90% in 5 of 6. The usable conclusion is that an absence of flags is reasonably reassuring, a flag is a hypothesis worth investigating, and neither constitutes assurance that misconduct would be detected.

Reasonable evidence of association, with design limits. In a review of 1,111 sites across 159 studies at 23 organisations, sites monitored with statistical data monitoring improved on data inconsistency and risk-signal metrics in 83% of cases, with a 95% confidence interval of 80% to 85%, against 56% of sites in two historical studies run without it. Across a central monitoring platform covering 212 studies and 1,676 flagged sites, 82.9% improved on the statistical score and 81.1% on the observed indicator value. Both are before-and-after comparisons on sites selected for extreme values, so regression to the mean contributes an unknown part of the effect, and the comparison group in the first study is historical rather than concurrent.

Few enough that each one is reviewed properly and each one traces to something you have named as critical — in practice six to ten for most trials. For reference, the open-source {gsm} package used for risk-based quality management evaluates 12. The failure mode of a large indicator set is not statistical but organisational: at a fixed threshold, more indicators mean more flags, the review becomes a reporting exercise, and signals stop being investigated. If an indicator has no named critical-to-quality factor behind it, no numeric threshold, no denominator that makes sites comparable, or no owner with a response period, it will be reported and ignored, which is worse than not collecting it.

Positive predictive value indicates, given a flag, the probability that a real problem exists, which is the relevant measure when a report arrives. Negative predictive value indicates, given no flag, the probability that the site is sound. The reviewed methods perform far better on the second, with 5 of 6 reaching 90% or more, than on the first, with 1 of 6. Importantly, both depend on how common site problems actually are. When problems are rare, negative predictive value is inflated almost automatically and positive predictive value is depressed, so a method with good published predictive values in a high-problem sample will perform worse in a programme with few problems. The base rate should be estimated before either measure is interpreted.

Thresholds should be set against a consequence, not a distribution. The relevant question is at what value someone should look, rather than which sites fall in the worst five per cent; a percentile threshold generates a constant flag count whether or not anything is wrong. Thresholds should then be differentiated by severity: an indicator protecting eligibility or safety reporting warrants a sensitive threshold and the associated false positives, whereas one tracking data entry timeliness does not. Finally, the first action should be inexpensive, so that a sensitive threshold is affordable: a specific written query rather than a visit. If the false positive load makes the review unworkable, the remedy is usually fewer indicators rather than looser thresholds.

Sometimes, but not dependably enough to serve as an assurance mechanism. It can detect fabricated data that are statistically implausible — digit preference, impossibly low variance, patterns that are too regular, correlations that should exist and do not. It cannot detect misconduct that produces plausible data, nor anything that is absent from the data altogether: a participant consented after the first procedure, a source document written retrospectively, a device calibrated on paper. The sensitivity figures reinforce this point, with only 1 of 7 reviewed methods reaching 90%. Statistical monitoring should be treated as one layer, with training, documented escalation and targeted on-site verification performing the work it cannot.

Because each of these methods works by comparing a site against the others, and a site with a handful of participants supports almost no inference. Variance estimates are unstable, digit-pattern tests have no power, and a single unusual participant alters every rate. This limitation is significant because small sites are also where a single operator’s habits dominate the data and where a protocol misunderstanding is least likely to be identified by a colleague. The appropriate response is not to impose statistical monitoring on such sites but to cover them differently: more initial training, early targeted review of the first few participants, and a lower threshold for a visit.

What was flagged and when, what the investigation asked, what the site answered, what was concluded, what action followed, and — the field most often omitted — whether the signal was judged true or false in retrospect. That final field converts a monitoring log into validation data. After a year of signals, a programme can state its own positive predictive value, which is more relevant to its next protocol than any published figure, and can retire indicators that have never produced a true positive. Given that only 1 of 6 reviewed methods reached a positive predictive value of 90%, knowledge of a programme’s own rate distinguishes a calibrated programme from an uncalibrated one.

References

  1. de Viron S, Trotta L, Steijn W, Young S, Buyse M. Does Central Statistical Monitoring Improve Data Quality? An Analysis of 1,111 Sites in 159 Clinical Trials. Therapeutic Innovation & Regulatory Science. 2024;58(3):483-494. doi:10.1007/s43441-024-00613-w read 9 October 2026. doi.org/10.1007/s43441-024-00613-w
  2. Schauberger G, Klug SJ, Berger M. Random forests for the analysis of matched case-control studies. BMC Bioinformatics. 2024;25(1):253. doi:10.1186/s12859-024-05877-5 read 9 October 2026. doi.org/10.1186/s12859-024-05877-5
  3. de Viron S, Trotta L, Steijn W, Young S, Buyse M. Does Central Monitoring Lead to Higher Quality? An Analysis of Key Risk Indicator Outcomes. Therapeutic Innovation & Regulatory Science. 2022;57(2):295-303. doi:10.1007/s43441-022-00470-5 read 9 October 2026. doi.org/10.1007/s43441-022-00470-5
  4. Cragg WJ, Hurley C, Yorke-Edwards V, Stenning SP. Dynamic methods for ongoing assessment of site-level risk in risk-based monitoring of clinical trials: A scoping review. Clinical Trials. 2021;18(2):245-259. doi:10.1177/1740774520976561 read 9 October 2026. doi.org/10.1177/1740774520976561
  5. Wan F, Colditz GA, Sutcliffe S. Matched Versus Unmatched Analysis of Matched Case-Control Studies. American Journal of Epidemiology. 2021;190(9):1859-1866. doi:10.1093/aje/kwab056 read 9 October 2026. doi.org/10.1093/aje/kwab056
  6. Agrafiotis DK, Lobanov VS, Farnum MA, Yang E, Ciervo J, Walega M, et al. Risk-based monitoring of clinical trials: an integrative approach. Clinical Therapeutics. 2018;40(7):1204-1212. read 9 October 2026. journals.sagepub.com
  7. Stenning SP, Cragg WJ, Joffe N, Diaz-Montana C, Choudhury R, Sydes MR, et al. Triggered or routine site monitoring visits for randomised controlled trials: results of TEMPER, a prospective, matched-pair study. Clinical Trials. 2018;15:600-609. read 9 October 2026. journals.sagepub.com
  8. von Niederhausern B, Orleth A, Schadelin S, Rawi N, Velkopolszky M, Becherer C, et al. Generating evidence on a risk-based monitoring approach in the academic setting - lessons learned. BMC Medical Research Methodology. 2017;17(1):26. doi:10.1186/s12874-017-0308-6 read 9 October 2026. doi.org/10.1186/s12874-017-0308-6
  9. Brosteanu O, Schwarz G, Houben P, Paulus U, Strenge-Hesse A, Zettelmeyer U, et al. Risk-adapted monitoring is not inferior to extensive on-site monitoring: results of the ADAMON cluster-randomised study. Clinical Trials. 2017;14:584-596. read 9 October 2026. journals.sagepub.com
  10. Buyse M, Squifflet P, Coart E, Quinaux E, Punt CJA, Saad ED. The impact of data errors on the outcome of randomized clinical trials. Clinical Trials. 2017;14(5):499-506. read 9 October 2026. journals.sagepub.com
  11. Hurley C, Shiely F, Power J, Clarke M, Eustace JA, Flanagan E, Kearney PM. Risk based monitoring (RBM) tools for clinical trials: a systematic review. Contemporary Clinical Trials. 2016;51:15-27. read 9 October 2026. journals.sagepub.com
  12. Knepper D, Lindblad AS, Sharma G, Gensler GR, Manukyan Z, Matthews AG, Ahn H. Statistical monitoring in clinical trials: best practices for detecting data anomalies suggestive of fabrication or misconduct. Therapeutic Innovation & Regulatory Science. 2016;50:144-154. read 9 October 2026. journals.sagepub.com
  13. Olsen R, Bihlet AR, Kalakou F, Andersen JR. The impact of clinical trial monitoring approaches on data integrity and cost - a review of current literature. European Journal of Clinical Pharmacology. 2016;72(4):399-412. read 9 October 2026. journals.sagepub.com
  14. Sheetz N, Wilson B, Benedict J, Huffman E, Lawton A, Travers M, et al. Evaluating source data verification as a quality control measure in clinical trials. Therapeutic Innovation & Regulatory Science. 2014;48(6):671-680. read 9 October 2026. journals.sagepub.com
  15. Tudur Smith C, Williamson P, Jones A, Smyth A, Hewer SL, Gamble C. Risk-proportionate clinical trial monitoring: an example approach from a non-commercial trials unit. Trials. 2014;15:1-10. read 9 October 2026. journals.sagepub.com
  16. Macefield RC, Beswick AD, Blazeby JM, Lane JA. A systematic review of on-site monitoring methods for health-care randomised controlled trials. Clinical Trials. 2013;10(1):104-124. read 9 October 2026. journals.sagepub.com
  17. Kirkwood AA, Cox T, Hackshaw A. Application of methods for central statistical monitoring in clinical trials. Clinical Trials. 2013;10(5):783-806. read 9 October 2026. journals.sagepub.com
  18. Bakobaki J, Joffe N, Burdett S, Tierney J, Meredith S, Stenning S. A systematic search for reports of site monitoring technique comparisons in clinical trials. Clinical Trials. 2012;9(6):777-780. read 9 October 2026. journals.sagepub.com
  19. Tudur Smith C, Stocken DD, Dunn J, Cox T, Ghaneh P, Cunningham D, Neoptolemos JP. The value of source data verification in a cancer clinical trial. PLoS ONE. 2012;7(12):e51623. read 9 October 2026. journals.sagepub.com
  20. Balshem H, Helfand M, Schunemann HJ, Oxman AD, Kunz R, Brozek J, et al. GRADE guidelines: 3. Rating the quality of evidence. Journal of Clinical Epidemiology. 2011;64(4):401-406. doi:10.1016/j.jclinepi.2010.07.015 read 9 October 2026. doi.org/10.1016/j.jclinepi.2010.07.015
  21. Journot V, Pignon JP, Gaultier C, Daurat V, Bouxin-Metro A, Giraudeau B, et al. Validation of a risk-assessment scale and a risk-adapted monitoring plan for academic clinical research studies - the Pre-Optimon study. Contemporary Clinical Trials. 2011;32:16-24. read 9 October 2026. journals.sagepub.com
  22. Schulz KF, Altman DG, Moher D. CONSORT 2010 Statement: updated guidelines for reporting parallel group randomised trials. Trials. 2010;11(1):32. doi:10.1186/1745-6215-11-32 read 9 October 2026. doi.org/10.1186/1745-6215-11-32
  23. Bassler D, Briel M, Montori VM, Lane M, Glasziou P, Zhou Q, et al. Stopping randomized trials early for benefit and estimation of treatment effects: systematic review and meta-regression analysis. JAMA. 2010;303:1180-1187. read 9 October 2026. school16.sipta.org
  24. Brosteanu O, Houben P, Ihrig K, Ohmann C, Paulus U, Pfistner B, et al. Risk analysis and risk adapted on-site monitoring in noncommercial clinical trials. Clinical Trials. 2009;6(6):585-596. read 9 October 2026. journals.sagepub.com
  25. von Elm E, Altman DG, Egger M, Pocock SJ, Gotzsche PC, Vandenbroucke JP; STROBE Initiative. Strengthening the reporting of observational studies in epidemiology (STROBE) statement: guidelines for reporting observational studies. BMJ. 2007;335(7624):806-808. doi:10.1136/bmj.39335.541782.AD read 9 October 2026. doi.org/10.1136/bmj.39335.541782.AD
  26. von Elm E, Altman DG, Egger M, Pocock SJ, Gotzsche PC, Vandenbroucke JP; STROBE Initiative. The Strengthening the Reporting of Observational Studies in Epidemiology (STROBE) statement: guidelines for reporting observational studies. Epidemiology. 2007;18(6):800-804. doi:10.1097/EDE.0b013e3181577654 read 9 October 2026. doi.org/10.1097/EDE.0b013e3181577654
  27. Montori VM, Devereaux PJ, Adhikari NK, Burns KEA, Eggert CH, Briel M, et al. Randomized trials stopped early for benefit: a systematic review. JAMA. 2005;294:2203-2209. read 9 October 2026. school16.sipta.org
  28. King G, Zeng L. Estimating risk and rate levels, ratios and differences in case-control studies. Statistics in Medicine. 2002;21(10):1409-1427. doi:10.1002/sim.1032 read 9 October 2026. doi.org/10.1002/sim.1032
  29. Pogue JM, Yusuf S. Cumulating evidence from randomized trials: utilizing sequential monitoring boundaries for cumulative meta-analysis. Controlled Clinical Trials. 1997;18:580-593. read 9 October 2026. school16.sipta.org
  30. Pocock SJ, Hughes MD. Practical problems in interim analyses, with particular regard to estimation. Controlled Clinical Trials. 1989;10:209S-221S. read 9 October 2026. school16.sipta.org

Every source above is a peer-reviewed article, a publisher’s record of one, or a standard issued by the body that owns it. Each carries the date it was last read. Where a standard moves, this article is revised rather than left up with a note.

How to cite this article

Pick your referencing style and copy it. Your university or target journal may vary the punctuation — check its guide if it has one.

Pubrica Academy. (2026, October 9). Monitoring Clinical Risk with Biostatistics: Key Risk Indicators and Central Statistical Monitoring. Pubrica. https://pubrica.com/academy/statistical/effective-strategies-to-monitor-clinical-risks-using-biostatistics/

This article is written to be learned from. Cite it if you are referring to what it says; if you are using the evidence behind it, cite the sources listed above instead.

Risk indicator definition and signal disposition log

The template has two parts. Each indicator is defined before the first participant is enrolled, and every signal it produces is then logged. The disposition column is the most important and the one most often left blank.

PART 1 - INDICATOR DEFINITION (one block per indicator)

Indicator name: ______________________________________
Critical-to-quality factor it protects: _______________
  (If this is blank, the indicator is information only.)
Why failure of that factor matters: __________________

Definition
  Numerator: __________________________________________
  Denominator: ________________________________________
  Period of calculation: ______________________________
  Minimum data for the indicator to be calculated: ____
    (sites below this are not assessable - list them
     separately rather than flagging them)

Threshold
  Value at which action is required: __________________
  Basis for that value:
    [ ] consequence-based - explain: __________________
    [ ] percentile-based  - justify why: ______________
  Severity tier: [ ] safety/eligibility [ ] endpoint
                 [ ] process/timeliness
  Expected flag rate at this threshold: ______ per review

Response
  Review frequency: ______________
  Owner (role, not person): ______________
  First action: _______________________________________
  Response required within: ______ working days
  Escalation if unresolved after ____ reviews: ________

Review of the indicator itself
  Date added: ____________  Last reviewed: ____________
  True positives to date: ______  False: ______
  [ ] Candidate for retirement (no true positive in 24 months)


PART 2 - SIGNAL DISPOSITION LOG (never leave the last column blank)

Date | Site | Indicator / pattern | Comparison given to site
---- | ---- | ------------------- | ------------------------
.... | .... | ................... | ........................

Query sent (date) | Site response summary
----------------- | ---------------------
................. | .....................

Conclusion | Action taken | TRUE or FALSE signal
---------- | ------------ | --------------------
.......... | ............ | ....................

PROGRAMME REVIEW AT 12 MONTHS
  Signals raised: ______
  Judged true: ______   Judged false: ______
  Our positive predictive value: ______%
  Real problems found by other routes that no indicator caught:
    ..................................................
  Indicators to retire: ______________________________
  Indicators to add: _________________________________

Pubrica AcademyWritten and maintained by Pubrica’s subject matter experts. Articles are revised when the underlying standards change, and each article states the date on which it was last reviewed.

How Pubrica can help

Pubrica defines risk indicators that trace to named critical-to-quality factors, with denominators that make sites of unequal size comparable and thresholds set against consequences rather than percentiles. The central monitoring analysis is built so that each flag is accompanied by the comparison data a site requires in order to respond, and Pubrica drafts the query text, because a specific question elicits a diagnostic reply whereas a general warning does not. For programmes already in operation, Pubrica audits the disposition log and reports the programme’s own positive predictive value, which has frequently not been calculated before.

Find something else

Search the Pubrica Academy

Access is free and requires no account. Enter a topic, or open the full library to filter by category, sub-topic or resource type.

Pubrica reviews submitted indicator sets and identifies which indicators can be acted upon.

A scoping assessment is free and takes two business days. It provides a written assessment of what the work requires and which specialist would undertake it.

Get a free quote

Regulations

Check your project against this rule

  1. 1Your work
  2. 2Your details
  3. 3Send
What do you need?

Material you send is held under signed confidentiality, with access limited to the assigned team and encrypted transfer. It is not used to train anything and is not passed to third-party tools. Ask for the agreement before you send anything you would rather cover first.