Published at MetaROR
March 4, 2026
Table of contents
Risk of bias in robustness reports
1. University of Sydney
Originally published on November 17, 2025 at:
Editors
Kathryn Zeiler
Kathryn Zeiler
Editorial assessment
by Kathryn Zeiler
The author provides rationale to support the author’s suggestion that journal editors require Synchronous Robustness Reports (SRRs) to be preregistered. The reviewer suggests distinguishing between robustness checks, which are generally included in the original article and performed by the original study’s author to defend the main results and reanalyses, which are performed by others after a paper is published. This distinction likely arises given different uses of the terms across fields (e.g., economists use “robustness checks” to refer to author analyses that are included in the original study and designed to increase confidence in the main results). The reviewer is skeptical about requiring preregistration given that much can be learned from exploring the data and reanalysis options.
Recommendations from the editor
The author cautions against the usefulness of SRRs in cases where SRR authors observe the data prior to deciding on their analysis plan, which stands as an alternative to the plan executed in the original study. Given existing evidence of high rates of irreproducibility in the absence of preregistration, the suggestion to require preregistration of SRR analysis plans seems important. In addition, the claim suggesting that liking or disliking the original results can bias SRR results seems plausible considering existing evidence on researcher biases the author relies on. The idea that editors issue open calls for SRRs is a great one. Editor bias is as potentially harmful as analyst bias.
Suggestions:
- The author notes that “SRRs are submitted before the target article is published” (2), but Bartoš et al. suggest that a “journal can…choose either to publish the target article first or to delay the publication of the target article until the SRRs are ready to be published alongside it” and that “the gap between the potential publication of the target article and the accompanying SRRs is, at most, six weeks.” (2) Thus, the author might want to propose a fuller alternative workflow.
- The author suggests embargoing the data used in the original study until SRRs are submitted, but what about the fact that an increasing number of authors are posting not only preprints prior to publication but also data and analysis scripts to invite scrutiny as soon as possible. Might a policy embargoing data used to produce the original results lead to a delay in reliability checks? This begs the question whether we need to adjust how we perform original research. Specifically, should researchers (or editors of Registered Reports) invite SRR research plans after submission of the original research plan but prior to the original author’s performance of the analysis? In other words, imagine a journal that publishes only Registered Reports. Accepted plans for original research would trigger a call for plans for SRRs. All accepted SRR plans, just like the original plan, would be conditionally accepted before any analyses are performed by either the original author or SRR authors. Could we imagine an alternative method for conducting research that includes authors themselves issuing open calls for SRRs that get added to the original paper prior to submission (with authors including all SRRs along with author comments on each)?
Recommendations for Enhanced Transparency
- Add a Data Availability Statement to report that no data are used in the article.
- Add author ORCID iD.
- Add a funding source statement. Authors should report all funding in support of the research presented in the article. Grant reference numbers should be included. If no funding sources exist, explicitly state this in the article.
For more information on these recommendations, please refer to our author guidelines.
Peer review 1
This paper crisply argues in favor of preregistration of reanalysis of published studies. The author uses the term “robustness reports,” which I gather is standard terminology, but I have to admit that this term bothers me, in that I think it inappropriately pushes people toward an attitude that the goal is to find out whether the original published finding was “robust” or not. Rather than framing this in terms of “robustness,” I’d prefer to just think of these as reanalyses. This complaint of mine is not a criticism of this paper; it’s just more of a general concern which perhaps the authors could think about and mention in a revision.
What is the distinction between “robustness study” and “reanalysis”? I’m not quite sure. In one sense, a reanalysis is literally a check of robustness to an alternative specification. I guess the difference to me is that “reanalysis” sounds like it can stand on its own, whereas “robustness” is typically defined relative to the original choice of analysis. To put it another way, “reanalysis” sounds like it’s coming from an outsider, whereas a “robustness study” is typically done defensively, so as to provide a result with some buffer against criticism.
Here’s how Uri Simonsohn [1] put it: “Robustness checks involve reporting alternative specifications that test the same hypothesis. Because the problem is with the hypothesis, the problem is not addressed with robustness checks.” I added some discussion of my own [2]. So maybe my problem is with the cultural baggage surrounding the idea of robustness.
To return to the main point, the proposal to have a formal system combining preregistration with reanalysis seems fine to me—as long as this were not taken to rule out non-preregistered reanalyses. Over the years, I’ve done many many reanalyses of studies published by others, and none of these were preregistered. I wouldn’t want them to be preregistered. When I reanalyze data, I need to try out different things and see how they work, and I learn a lot after looking at the data.
I think it’s great to have preregistered reanalyses. I just don’t think this should be any kind of requirement.
References
[1] Uri Simonsohn (2016). P-hacked hypotheses are deceivingly robust. http://datacolada.org/48/
[2] Andrew Gelman (2018). Robustness checks are a joke. https://statmodeling.stat.columbia.edu/2018/11/14/robustness-checks-joke/


