Research Policy Review Time

The current Research Policy ScienceDirect page lists 24 days from submission to first decision, 111 days from submission to decision after review, 469 days from submission to acceptance, and 14 days from acceptance to online publication. It also lists Research Policy's scope: work on the interaction between innovation, technology or research and economic, social, political, and organizational processes, with policy or management implications.

The current Research Policy guide for authors confirms double-anonymized peer review and the requirement to submit a title page separately from an anonymized manuscript. It also says Research Policy articles should offer empirically and theoretically grounded work in science, technology, innovation, policy, management, and related fields.

The Research Policy FAQ is unusually useful for timing because it explains the front-end filter: approximately half of new submissions are desk-rejected, and just under 10% are published. It also warns authors to choose a handling editor whose expertise matches the topic and to disclose related work or conflicts clearly.

The current SciRev community page for Research Policy shows 21 reviews, 4.3 months for the first review round, 6.6 months total handling time for accepted manuscripts, 48 days for immediate rejection, 1.6 review rounds, 1.9 reports, and difficult reviewer comments. That is not official publisher data, but it is a useful author-side stress test.

Research Policy is not only a management journal, economics journal, science-policy journal, or innovation-practice journal. It sits across those communities. That makes routing and review harder.

Reviewers often ask:

• Does the paper contribute to innovation studies or science and technology policy, not only to a nearby discipline?
• Is the theory contribution clear enough for a multidisciplinary readership?
• Are policy or management implications built into the argument rather than appended at the end?
• Does the empirical design support the causal or interpretive claim being made?
• Is the paper positioned against Research Policy's core literatures, not only strategy, economics, entrepreneurship, geography, or public policy?
• Are related papers, prior versions, working papers, or thesis chapters disclosed correctly under double-anonymized review?

Those checks explain the long reviewed-manuscript path. A paper can be technically strong but slow if reviewers disagree about whether it is truly Research Policy-shaped.

Silence is not a positive or negative signal by itself. At Research Policy, the more useful read is whether the elapsed time resembles desk screening, reviewer assessment, or editor synthesis.

• Innovation-studies contribution is implicit. Reviewers can see a good paper, but not why it belongs in Research Policy.
• Policy or management implication is bolted on. The implication needs to follow from the theory and evidence, not from the conclusion paragraph alone.
• Handling-editor fit is unclear. Authors are asked to choose an editor whose expertise matches the topic, and poor matching creates routing friction.
• Double-anonymized related-work disclosure is weak. Prior working papers, thesis chapters, conference papers, or adjacent submissions need careful disclosure.
• Empirical identification is overclaimed. Quantitative papers slow when the method cannot support causal language; qualitative papers slow when case logic is underexplained.
• Multidisciplinary audience mismatch. A paper may satisfy strategy, economics, geography, or public-policy readers but not the innovation-studies core.

These are timing risks because they create extra editor and reviewer work.

Research Policy contribution is described as topic relevance, not knowledge contribution. In Research Policy-targeted manuscripts we review, authors often argue that a topic is important because it concerns innovation, technology, entrepreneurship, or science policy. That is not enough. The manuscript has to say what existing Research Policy readers will know after reading the paper that they did not know before. The component to fix is the introduction: research question, literature gap, theoretical mechanism, empirical setting, and contribution paragraph should all point to the same knowledge claim.

Research Policy policy implication is not earned by the evidence. A common slow-review pattern is a strong empirical paper with a generic policy paragraph. Reviewers then ask whether the paper really has implications for policy or management, which the journal explicitly expects. The implication should be traceable to the empirical design, not pasted onto the discussion. If the paper studies patents, R&D subsidies, university-industry links, regional clusters, green transitions, or mission-oriented policy, the implication has to follow from the actual mechanism tested.

Research Policy method section overstates causal leverage. Quantitative manuscripts often use panel data, surveys, patents, bibliometrics, policy shocks, firm data, regional data, or network measures. Reviewers slow down when the method language claims causal identification but the design supports association, mechanism exploration, or comparative inference. The fix is testable: align the abstract, hypotheses, model table, robustness checks, limitations, and conclusion so the claim does not outrun the design.

Research Policy case logic is not auditable enough for a multidisciplinary reviewer. Qualitative or mixed-methods papers can be strong fits, but they need transparent case selection, data sources, coding logic, interview protocol, archival material, and triangulation. A management reviewer, policy reviewer, and innovation-systems reviewer may read the same case differently. If the manuscript does not make the evidentiary chain auditable, review slows because each reviewer reconstructs the case logic independently.

Research Policy related-paper disclosure is thin. The FAQ is direct about related work, prior publication, and salami publishing risk. In pre-submission reviews, we see authors preserve double anonymity by hiding too much context. That can backfire. The handling editor needs enough disclosure to judge originality, even when the blinded manuscript cites prior work as Author-date. Weak disclosure can turn a review issue into a desk or integrity issue.

The timing lesson is that "review time" is not one number. The journal's front-end filter and long accepted-manuscript path both matter.

Papers that move more cleanly usually make the editor's job easier:

• the abstract names the innovation-studies or science-policy contribution;
• the introduction states a precise research question and theory gap;
• the paper explains why Research Policy owns the audience;
• the empirical design matches the strength of the claim;
• policy or management implications are connected to evidence;
• related work and prior versions are disclosed clearly;
• the handling-editor choice is defensible from the topic and keywords;
• limitations are honest about identification, generalizability, and data constraints.

That package can still take months. But it lowers the chance that reviewer reports split around field fit or claim strength.

This page uses current ScienceDirect journal insights, Research Policy's current Elsevier guide for authors, the Research Policy FAQ, the live Editorial Manager route, SciRev's current Research Policy page, and Manusights pre-submission review work with innovation-studies and policy/management manuscripts.

The timing limitation matters. ScienceDirect's 24 days to first decision includes desk-screen decisions; 111 days after review is more relevant for papers that reach reviewers; 469 days to acceptance shows the long successful-publication path; SciRev's 21 reviews provide author-side evidence but are not official publisher statistics. Treat these as planning ranges, not guarantees.

In our pre-submission review work with Research Policy and adjacent innovation-studies manuscripts, review-time risk usually comes from contribution fit, not grammar or formatting.

Research Policy introduction does not name the field-level contribution. Reviewers need to see whether the paper advances innovation studies, science and technology policy, or technology-management theory. A polished introduction that only says the topic is important will not shorten review. The contribution paragraph should make the journal fit obvious.

Research Policy methods table promises more than the design can prove. If the abstract says "effect" or "impact" but the identification strategy supports association, comparative mechanism, or descriptive mapping, reviewers will press hard. That turns into extra rounds because authors have to revise language, robustness checks, and conclusions together.

Research Policy policy implication is detached from the empirical result. The fastest revisions are not the ones with more policy prose. They are the ones where the implication follows directly from the model, case comparison, mechanism, or theory. Reviewers can then argue about the evidence instead of whether the implication belongs.

Research Policy related-paper disclosure creates unnecessary editorial risk. Authors sometimes over-anonymize because double-blind review feels safer. The FAQ makes clear that the handling editor still needs related-work disclosure. A clean cover-letter note can prevent a slow originality dispute later.

The common thread is that Research Policy reviewers do not only ask "is the paper rigorous?" They ask whether the manuscript earns its place in the innovation-studies conversation. In our reviews, the fastest improvement usually comes from aligning five components: abstract contribution, theory positioning, empirical design, policy implication, and related-paper disclosure. If those five components point in different directions, the review path slows because each reviewer finds a different version of the paper.

Before upload, a Research Policy submission-readiness check can test whether the contribution, evidence, policy implication, related-paper disclosure, and venue fit are strong enough before you commit to a long review path.