Checklist

Statistical analysis & reporting checklist

Interactive checklist to ensure statistical analyses are planned, executed, diagnosed, and reported with transparency, reproducibility, and appropriate error control.

Interactive Tool

Statistical analysis & reporting checklist

This checklist helps teams confirm that statistical analyses are planned, executed, checked, and reported in a transparent, reproducible way. Use it during analysis, code review, and manuscript/report preparation. For each item, mark completion, add evidence links (protocols, code, data), and include brief notes or justifications.

Suggested use: complete the checklist before finalizing results, attach links to code/data, and save the checklist as part of the project record for reproducibility and audit trails.

Was an analysis plan, protocol, or preregistration created before seeing the outcome data?
Provide a link or repository path to the analysis plan, protocol, or preregistration record.
Is there a documented plan describing how missingness is handled and any imputation methods?
Describe the approach (e.g., multiple imputation, complete-case, models) and justification.
Select diagnostics performed for primary models.
Summarize key diagnostic results and any actions taken (transformations, robust SEs, alternative models).
Choose the approach used to control type I error or explain why none was used.
Provide rationale, corrections applied, and relevant code references.
Are effect estimates accompanied by confidence intervals (and, where useful, standardized effect sizes)?
Describe the effect metrics used and any interpretation guidance provided.
Was a priori power/sample-size calculation performed or post-hoc power discussed?
Provide brief details or link to the calculation and assumptions (effect size, alpha, power).
Were sensitivity analyses run to test key assumptions or alternative specifications?
Summarize key robustness checks and whether conclusions changed.
Were subgroup analyses planned and appropriately powered or clearly labeled as exploratory?
Select transparency practices applied in reporting.
Indicate what reproducibility artifacts are available.
Provide URLs or repository paths where code/data can be accessed (or note access restrictions).
1 = low confidence, 5 = high confidence
1.0 10.0
Name of analyst, reviewer, or responsible person.
Date of checklist completion (YYYY-MM-DD).
Anything else the team should record (e.g., outstanding data access issues, planned follow-ups).
You can explore this tool now. Sign in or create an account to save your responses and return to them later.
Sign In to Save Create an Account
Make this tool part of your work

Save a personal copy, bring it to your team, or tailor the questions and workflow to fit what you are hungry to improve.

Member customization and team collaboration are coming soon.
Discuss Ask the Librarian

Discussion

Comments and conversation will live here.