A pre-submission manuscript review is a working order, not a mood. Run the checks in the sequence a reader actually hits them, and most desk rejections stop happening.
Authors tend to check a manuscript from the inside out: read the Methods again, tighten a sentence in the Discussion, fix a typo in the abstract. An editor reads it from the outside in. The first question they answer is whether the paper belongs in front of them at all, before they read a word of the argument.
That ordering matters. A flawless analysis submitted to the wrong journal gets the same one-line rejection as a flawed one. Check journal fit first, because every later check is wasted effort if this one fails.
Open the journal's aims and scope page and read it against your manuscript, not against your memory of it. Journals narrow their scope over time, and the issue that published a paper like yours three years ago may have since split into a sister publication.
Check the article type separately from the scope. A journal that welcomes your topic may only welcome it as a brief report, a case series, or a full research article, and each type carries its own word limit, abstract structure, and reference cap. Submitting a 6,000-word manuscript to a 3,000-word article type gets it returned unread.
Read three recent papers from the target journal on an adjacent topic. Not for content, for shape: how long is the Introduction, how many subheadings does the Discussion carry, does the journal print a Limitations section as its own heading or fold it into the Discussion. Match the shape before you match the sentences.
This is the check authors skip most often, because by submission time the design is finished and rereading it feels like second-guessing work that is already done. Do it anyway. State the question in one sentence, then ask whether the design in front of you, run correctly, could produce an answer to that exact sentence.
A cross-sectional design cannot establish that one variable preceded another. An observational cohort cannot rule out an unmeasured confounder no matter how large the sample. A single pre-post measurement without a control group cannot separate the intervention's effect from everything else that changed over the same period. None of these are flaws in the paper. They are properties of the design, and the paper fails only if the Discussion claims something the design cannot support.
If the design cannot answer the full question, narrow the question in the paper to what the design can answer, and say so. A reviewer who reads a narrowed, honest claim has nothing to object to. A reviewer who reads an overreaching claim on a limited design has an easy first comment to write.
Pair the test in your Methods against the structure of your data, not against what your statistics software offered by default. Repeated measurements on the same subject need a test that accounts for that dependence. Count data compared across more than two groups needs a test built for counts, not a t-test run three times. A continuous outcome measured before and after treatment in the same people needs a paired test.
Check the assumptions the chosen test actually requires, and check them against your data rather than assuming they hold. Small groups, skewed distributions, and unequal variances each call for a different adjustment or a different test entirely.
If more than one hypothesis test was run on the same dataset, state in Methods what correction was applied, or state plainly that none was and why. A reviewer who finds several p-values near a threshold and no mention of multiple comparisons will ask about it. Answering the question before it is asked reads as careful rather than defensive.
Read every number that appears in both a table and the running text, side by side, and confirm they match. This sounds too basic to need saying, and it is also one of the most common things a careful reviewer finds wrong: a mean reported as 4.2 in the Results and 4.8 in Table 2, a sample size that shifts between the Methods and a table footnote, a percentage in the abstract that does not recompute from the numerator and denominator given in the body.
Recompute derived numbers rather than trusting them. If the text reports a percentage, divide the two counts yourself. If it reports a change score, subtract the two means yourself. These errors are almost always transcription mistakes from an earlier draft, not fabrication, but a reviewer cannot tell the difference from the page, and either reading damages the paper.
Confirm the totals. If a table breaks a sample into subgroups, the subgroups should sum to the total reported elsewhere in the paper. A subgroup total that is off by a handful of participants, with no explanation for the missing cases, is a frequent and avoidable objection.
Read the Discussion section on its own, without the rest of the paper open, and list every claim it makes. Then go back to the Results and check whether each claim traces to a specific number or test. A claim that cannot be traced back is either an interpretation that needs to be labeled as one, or a claim that does not belong in the paper.
Watch for causal language attached to non-causal designs. "X reduced Y" implies an intervention and a mechanism. "X was associated with lower Y" describes what an observational design actually showed. The difference between those two sentences is often the difference between a comment asking for revision and one asking for rejection.
Watch for generalization beyond the sample. A finding in 140 adult outpatients at a single center does not extend to children, to inpatients, or to a different health system without a stated reason. If the Discussion wants to generalize, it needs to say what supports the extension, not just assert it.
Some rejections never reach a reviewer. An editorial office returns the manuscript on a technical failure before anyone reads the science. These checks take an afternoon and prevent a wasted submission cycle.
None of these checks require a subject-matter expert. They require someone willing to go through the list item by item rather than skimming it, which is exactly why they are so commonly missed. The person who wrote the paper is the person least likely to notice a missing reference, because they know what the sentence is supposed to say.
Consider a manuscript reporting an eight-week workplace mindfulness program and its effect on self-reported stress in one company's customer service team, with no comparison group. Working through the order above catches three separate problems before submission.
Journal fit: the target journal's scope statement asks for occupational health studies with a comparator arm. This design has none. Either find a journal that accepts single-arm pilot data, or add a wait-list comparison before submitting.
Design versus question: the Introduction asks whether the program "reduces" stress. Without a control group, the design cannot separate the program's effect from regression to the mean, seasonal workload changes, or simply completing a survey twice. The question in the Introduction needs to be rewritten as a question about change over time in this specific group, not about an effect of the program.
Tables versus text: the Results state that 34 of 40 participants completed both surveys, but Table 1 lists n = 36 for the baseline group. The two numbers need to be reconciled and the reason for the discrepancy, likely incomplete follow-up surveys, stated in the text.
Fixing all three before submission does not guarantee acceptance. It removes the objections a reviewer would otherwise spend their first paragraph raising, which leaves the rest of the review free to engage with the actual contribution.
A checklist finds structural and mechanical problems reliably. It is weaker at judging novelty: whether the field already knows what this paper reports, and whether the contribution is large enough to matter to this particular journal's readership. That judgment depends on reading widely in the current literature, which a checklist cannot substitute for.
It also will not resolve a genuine disagreement about interpretation. Two careful readers can look at the same regression output and reasonably weigh the confounders differently. A pre-submission review can force that disagreement into the open, by requiring the Discussion to state its assumptions plainly, but it cannot settle which reading is right. That is what peer review is actually for.
Run the list in this order, not alphabetically and not by whichever section you last edited. A journal-fit problem found first saves the time spent perfecting statistics for a journal that was never going to accept the article type in the first place.
The reasons editors decline manuscripts before review, and how to avoid each one.
The errors reviewers catch most often, from misused tests to overstated effects.
How the process works, who decides what, and what reviewers are actually asked to do.
Structure the response letter, disagree well, and handle contradictory reviewers.
The Reviewer 2 Generator reads an abstract free. The free assessment reads a whole manuscript and tells you where it stands. For a full review, PeerGenius runs a panel of specialist reviewers over the paper and returns their objections before an editor sees it.
PeerGenius is built by Neon Peach, LLC, a product studio.
A pre-submission manuscript review catches what a checklist can catch. A panel of specialist reviewers catches the rest.
Get free assessment