MRMedRigorResearch

Study design, methods & statistics

Test the reasoning before it becomes a reviewer’s objection.

Focused technical review for protocols, analysis plans, datasets, results, or manuscripts requiring careful assessment of design, bias, statistical methods, reporting, and interpretation.

Technical review

Questions matched to the study design.

A checklist cannot replace judgment. The review is adapted to the research question, design, outcome structure, data limitations, and intended inference.

01

Research question and estimand

Population, exposure or intervention, comparator, outcomes, time horizon, and the effect the analysis is intended to estimate.

02

Design and bias

Selection, measurement, confounding, clustering, repeated observations, missingness, temporality, and other design-specific threats.

03

Analysis strategy

Model choice, assumptions, variable handling, effect measures, uncertainty, multiplicity, sensitivity analyses, and internal consistency.

04

Statistical reporting

Denominators, descriptive summaries, effect estimates, confidence intervals, exact methods, software, diagnostics, and reproducibility information.

05

Interpretation

Alignment of conclusions with the design, analysis, precision, limitations, and distinction between association, prediction, and causation.

Defined output

What you receive

One focused report addressing the technical questions included in the confirmed scope.

Technical assessment

Prioritized findings on design, analysis, assumptions, reporting, and interpretation.

Correction pathway

Specific recommendations distinguishing essential corrections, preferable improvements, and unresolved limitations.

Transparent limitations

A record of files reviewed, information unavailable, and questions that cannot be resolved from the supplied material.

Transparent scope

Review is not automatic reanalysis

  • Data cleaning, coding, model fitting, or full reanalysis unless separately agreed
  • Verification that supplied data are authentic, complete, or correctly collected
  • Prospective sample-size calculation without adequate design assumptions
  • Regulatory, clinical, or legal approval of a protocol
  • Retrospective justification of an inappropriate analysis
  • Guaranteed acceptance or favorable statistical conclusions

When analysis execution is requested, feasibility, software, data sensitivity, reproducibility materials, and deliverables require a separate written scope.

Start with the technical question

Tell us what needs to be tested.

Provide the study stage, design, main outcome, principal concern, available files, and desired timeline. Do not upload identifiable or highly sensitive data.

Request a Project Review ↗