Pre-Submission Review for Implementation Science Papers

Implementation reviewers often ask:

• what implementation problem is being solved?
• which implementation strategy was used, and is it described well enough to replicate?
• which framework, theory, or model guides the work?
• are implementation outcomes distinct from clinical or service outcomes?
• is context described at the setting, team, workflow, organization, and policy levels?
• are fidelity, adaptation, reach, feasibility, acceptability, adoption, and sustainment handled?
• is the right reporting checklist included?
• does the target journal expect implementation science rather than quality improvement or effectiveness research?

The paper has to generate transferable implementation knowledge, not just report a local improvement project.

In our pre-submission review work, implementation science manuscripts most often fail when the authors know the field vocabulary but do not use it to structure the evidence.

Framework decoration: CFIR, RE-AIM, EPIS, Normalization Process Theory, or another framework is named, but aims, data collection, analysis, and interpretation do not actually use it.

Strategy blur: the intervention is described, while the implementation strategy remains vague.

Outcome mixing: clinical outcomes, service outcomes, and implementation outcomes are combined as if they answer the same question.

Context gap: workflow, staffing, leadership, incentives, resources, and local adaptation are too thin for readers to judge transferability.

Reporting mismatch: TIDieR, CONSORT, StaRI, SQUIRE, COREQ, or another design-specific checklist is missing or incomplete.

A useful review should identify whether the manuscript is truly implementation science or an effectiveness paper with implementation language added late.

Implementation Science guidance tells authors to use design-appropriate reporting checklists and has published explicit reporting guidance for implementation science articles. Its reporting work points to EQUATOR and notes that TIDieR can improve intervention description across evaluative study designs, not only trials. CFIR user-guide materials emphasize matching constructs, questions, coding, and interpretation to the implementation project.

Those signals matter before submission. A paper that treats the framework as a label rather than an analytic tool is easy for reviewers to downgrade.

Send the manuscript, target journal, protocol, framework diagram, implementation strategy description, reporting checklist, intervention materials, stakeholder roles, fidelity or adaptation logs, outcome definitions, qualitative codebook if relevant, statistical analysis plan, and prior reviewer comments if available.

If the work is a hybrid trial, include the clinical and implementation outcome hierarchy. If it is qualitative, include sampling, coding, reflexivity, and framework-use details.

A useful implementation science pre-submission review should include:

• implementation-contribution verdict
• framework-use critique
• implementation strategy and TIDieR check
• context and adaptation review
• outcome-classification critique
• reporting-guideline check
• journal-lane recommendation
• submit, revise, retarget, or diagnose deeper call

The review should not only say "add context." It should identify which context determines whether the finding transfers.

Before submission, authors often need to:

• distinguish the intervention from the implementation strategy
• integrate the framework into aims, methods, analysis, and discussion
• separate implementation, service, and clinical outcomes
• add detail about actors, actions, dose, timing, and materials
• report fidelity, adaptation, and reach more clearly
• add a design-appropriate checklist
• narrow effectiveness claims
• retarget from an implementation journal to health services, quality improvement, public health, or clinical venues when the contribution is not implementation knowledge

These fixes can prevent a paper from sounding like an ordinary intervention study.

An implementation trial needs strategy description, cluster or site logic, implementation outcomes, fidelity, adaptation, and context. A hybrid study needs a clear hierarchy between effectiveness and implementation aims. A de-implementation paper needs the low-value practice, stakeholder incentives, and replacement behavior to be clear. A qualitative implementation paper needs framework-driven sampling, coding, and interpretation. A process evaluation needs a theory of change, mechanism evidence, and implementation detail.

The AI manuscript review can flag whether the blocking risk is framework use, strategy reporting, outcomes, context, or journal fit.

Use this page when the submission risk depends on implementation frameworks, strategy reporting, implementation outcomes, fidelity, reach, adoption, acceptability, feasibility, adaptation, or sustainment. Use health services research review when the manuscript is mainly about healthcare delivery, utilization, access, quality, EHR or claims data, workforce, or system management.

That distinction keeps the page focused on the implementation-science buyer's actual problem.

Do not submit an implementation science paper if the implementation strategy cannot be described as who did what, to change whose behavior, at what dose, through which materials, in which context. If that sentence is not answerable, reviewers will not see a transferable strategy.

Also pause if the framework is only decorative. The manuscript should show how the framework shaped the research question, data collection, coding, analysis, or interpretation. A named framework that does no work can hurt credibility more than no framework at all.

For hybrid studies, pause if readers cannot tell which finding is clinical effectiveness and which finding is implementation evidence. The manuscript can include both, but the abstract and tables must keep the logic separated.

For de-implementation work, pause again if the low-value practice and replacement behavior are not explicit. Reviewers need to know what behavior should stop, what should happen instead, and which implementation strategy is expected to move that behavior.