10 Structural Mistakes That Get Research Papers Rejected — And How to Fix Every One

Cluster Post 7  |  Module 1: Understanding the Structure of Research Papers and Theses

From Concept to Submission Series  |  February 2026

← Back to Pillar Post: The Complete Guide to Research Paper Structure

10 Structural Mistakes That Get Research Papers Rejected — And How to Fix Every One

Your pillar post named six common structural mistakes. This post goes further: ten named mistakes with a precise diagnosis for each, a before-and-after example, and a specific fix — plus a pre-submission checklist you can use on any paper or thesis chapter before it goes anywhere.

Why Structural Mistakes Are the Most Preventable Cause of Rejection

Journal rejections and thesis examination concerns have many causes — weak methodology, insufficient literature, overclaiming from limited data. But structural mistakes are unique among them: they are entirely preventable without collecting more data, reading more literature, or running more analyses. You already have everything you need to fix them. You just need to know what they are.

UGC examiner reports consistently identify structural problems as the most common weakness in Indian PhD theses — more common than methodology gaps, more common than literature gaps. The ten mistakes below cover the patterns that appear most frequently across disciplines.

Mistake 1: Burying the Research Question

The research question is the most important sentence in your paper. If readers have to search for it, their patience — and confidence in your work — erodes before they have evaluated a single finding.

Buried: “…and so, given the importance of this area, the present study aims to examine some of these issues in the Indian context.”  Explicit: “This study examines whether peer mentoring frequency and quality predict first-year retention at Indian government colleges, controlling for financial need and prior academic performance.”

The fix: State your research question in its own sentence, in the final paragraph of your introduction. It should name the construct, the population, the context, and the relationship being examined. If someone reads only that one sentence, they should know exactly what your study investigates.

Mistake 2: Front-Loading Too Much Background

Context matters. But context that runs for four pages before the reader knows what you are studying works against you. By the time you state your research question, the reader is exhausted and the question feels like an afterthought.

The fix: Give readers exactly enough background to understand why your question matters, then state the question. Ask of every background paragraph: does this help the reader understand my specific research question, or does it just demonstrate how much I know about the topic? The latter belongs in the literature review, not the introduction.

Mistake 3: A Gap That Is Implied Rather Than Stated

Many researchers gesture toward a gap without ever stating it plainly. The Introduction describes what previous research has found, then announces the research question — but never explicitly names the thing that is unknown, contested, or unresolved that the study addresses.

Implied gap: “Several studies have examined peer support in educational settings. Smith (2019) found… Jones (2021) found… This study examines peer support in Indian government colleges.”  Explicit gap: “Existing research on peer support has been conducted predominantly in Western residential university settings. The specific mechanisms through which peer support influences retention in Indian government colleges — where students typically attend far from home without established social networks — remain unstudied. This gap matters because interventions designed for Western contexts may not transfer to settings with different social infrastructure.”

The fix: Write one sentence that begins: “However, what remains unclear / unstudied / unresolved is…” Then write one sentence explaining why this matters. These two sentences are your gap statement. If you cannot write them, your gap is not yet clearly defined in your own thinking.

Mistake 4: Methods That Describe Without Justifying

A methods section that lists what you did without explaining why gives a sceptical reviewer nothing to evaluate except whether you followed convention. Reviewers are not asking what you did. They are asking whether what you did was the right approach to your research question.

Description only: “Semi-structured interviews were conducted with 30 students.”  Description with justification: “Semi-structured interviews were conducted with 30 students because the research question concerns how students experience peer support — a question about meaning and interpretation that closed-ended survey instruments cannot adequately capture.”

The fix: For every significant methodological choice, add one sentence beginning “because” or “in order to.” Why this design rather than alternatives? Why this sample size? Why this instrument? One sentence of justification transforms a procedure list into a defended research design.

Mistake 5: Mixing Results and Discussion

This is the most common IMRAD violation and the one that most damages credibility with reviewers. When you present a finding and immediately explain what it means in the same sentence, you make it impossible for readers to evaluate your data separately from your interpretation of it.

Mixed: “Students in the intervention group showed higher retention (82%), which demonstrates that peer mentoring is an effective strategy for improving persistence.”  Separated — Results: “Students in the intervention group showed higher retention (82%) than control students (71%), χ²(1, N = 450) = 8.92, p = .003.” Separated — Discussion: “The 11-percentage-point retention gap suggests peer mentoring addresses social integration factors that financial or academic support alone cannot provide.”

The fix: Search your Results section for the words “suggests,” “demonstrates,” “indicates,” “because,” and “therefore.” Every sentence containing these words is mixing results with interpretation. Move the interpretive half to Discussion.

Mistake 6: Vague Statistical Reporting

Reporting “p < .05” and nothing else tells a reviewer almost nothing. Statistical significance says only that an effect exists — not how large it is, not whether it is meaningful in practice. Incomplete statistical reporting is one of the most common reasons quantitative papers attract revision requests.

Incomplete: “There was a significant difference between groups (p = .003).”  Complete: “Intervention students showed significantly higher retention (82% vs. 71%), χ²(1, N = 450) = 8.92, p = .003, φ = .14.”

The fix: Every statistical result needs four elements: the test statistic, degrees of freedom, p-value, and effect size. Effect size (Cohen’s d, η², φ, r) is the element most consistently omitted and most consistently required by reviewers. Add it to every result.

Mistake 7: Limitations Listed, Not Analysed

A limitations section that reads as a list of apologies — “the sample was small,” “self-report measures may be inaccurate,” “more research is needed” — signals that the researcher has not thought carefully about what their study can and cannot support. Examiners and reviewers find this more damaging than the limitations themselves.

Apologetic: “This study has several limitations. The sample was small and from only one region. The design was cross-sectional.”  Analytical: “The three-college Rajasthan sample limits generalisability to other regional contexts — government colleges in tribal and hill regions, or in other states with different social infrastructure, may show different retention patterns. The cross-sectional design also means causation cannot be established: students who were already more likely to persist may have sought out mentoring rather than being retained because of it. A longitudinal randomised design would resolve this ambiguity.”

The fix: For each limitation, write two sentences: one naming the limitation, one explaining what it means for the conclusions you can draw. What can your study support? What cannot it support? Analytical limitations are a sign of methodological sophistication, not weakness.

Mistake 8: Implications That Are Generic

“This study has important implications for policy and practice” is a sentence that could appear in any paper in any field. It communicates nothing. Implications that do not specify who should do what, based on which specific finding, are indistinguishable from filler.

Generic: “These findings have important implications for educational policy in India.”  Specific: “Government college principals can implement structured peer mentoring within existing staff capacity — our model required eight hours of mentor training and bi-weekly coordinator check-ins. UGC should link peer mentoring implementation to the retention performance metrics already required under NEP 2020 reporting, creating an incentive for evidence-based adoption rather than ad hoc approaches.”

The fix: For every implication, name the specific actor (a principal, UGC, a legislative committee), the specific action (implement, revise, fund), and the specific finding that supports it. If you cannot link an implication to a specific finding, cut it.

Mistake 9: Inconsistent Organisation Across Sections

If your Results section organises findings by three research questions — RQ1, RQ2, RQ3 — your Discussion must follow the same order. If your Results presents quantitative then qualitative findings, your Discussion should interpret them in the same sequence. Inconsistency forces readers to mentally reorganise your work, and it suggests the researcher does not have a clear grasp of their own argument’s structure.

The fix: Before you write your Discussion, create a simple map: list your Results subheadings in column one, and match each to its corresponding Discussion subheading in column two. If the match is not one-to-one, restructure before you write. This five-minute exercise prevents hours of revision.

Mistake 10: A Conclusion That Summarises Instead of Concludes

A conclusions chapter or section that simply summarises the Discussion — which already summarised the Results — is the academic equivalent of ending a speech by reading your slides aloud. It adds nothing and leaves the reader with a sense of anticlimax at exactly the moment when your work should feel most significant.

Summary disguised as conclusion: “This study examined peer mentoring at three government colleges in Rajasthan. It found that intervention students had higher retention rates. The study also found that mentoring frequency and quality were important predictors.”  Genuine conclusion: “This study provides the first quasi-experimental evidence that structured peer mentoring improves first-year retention in Indian government college contexts — a finding that matters because it identifies a low-cost mechanism for addressing the retention gap that NEP 2020 expansion has widened rather than closed. The navigational function of peer mentors — helping first-generation students access institutional resources they did not know existed — extends social integration theory in ways that have implications for how colleges design induction programmes across India.”

The fix: A genuine conclusion answers three questions your reader has after reading the whole paper: What is new that we now know? Why does it matter? What should happen next? If your conclusion cannot answer all three specifically, it is summarising rather than concluding.

Pre-Submission Checklist

Use this before submitting any paper or thesis chapter. These questions are sharper than the standard element-based checklists because they test whether sections are doing their intellectual jobs, not just whether they exist.

Introduction

  • Is my research question stated in a single explicit sentence — not implied, not buried?
  • Is there a gap statement that names specifically what is unknown, not just that more research is needed?
  • Does the opening paragraph earn its place — specific enough to be informative, not so broad it could open any paper in the field?

Methods

  • Does every significant choice have a rationale, not just a description?
  • Could a researcher at another institution replicate this study exactly from my description?
  • Have I addressed ethics approval, consent process, and — for qualitative work — positionality?

Results

  • Have I searched for “suggests,” “demonstrates,” “because,” and “therefore” and moved every instance to Discussion?
  • Does every statistical result include test statistic, degrees of freedom, p-value, and effect size?
  • Is every table and figure referenced in the text before it appears, with a note on what to notice?

Discussion

  • Does the opening restate findings in fresh language — not repeat them in the same language as Results?
  • For each major finding, have I explained why — the mechanism — not just what?
  • Are limitations described analytically (what they mean for conclusions) rather than listed apologetically?
  • Are there practical, theoretical, and policy implications — not just one type?
  • Are future research directions specific enough that another researcher could design a study from them?

Overall

  • Does the organisation of my Discussion match the organisation of my Results?
  • Does my conclusion answer: what is new, why it matters, and what should happen next?
  • Is every source cited in-text present in the reference list — and vice versa?

🔱  For Law Students

Legal research has its own structural mistakes, distinct from those above. The four below appear most frequently in Indian law theses and journal submissions.

Mistake 1: Forcing doctrinal research into IMRAD

Applying Introduction–Methods–Results–Discussion to doctrinal research produces a Methods section that misdescribes case selection as a laboratory procedure and a Results section that presents legal analysis as though it were statistical data. Legal examiners and reviewers recognise this immediately as a sign that the researcher does not understand their own methodology.

The fix: Doctrinal research follows Framework–Analysis–Critique–Proposal, not IMRAD. Use IMRAD only when you are conducting genuine empirical research — surveys, interviews, statistical analysis of court records.

Mistake 2: Case summary without legal analysis

Describing what a court decided — the facts, the holding, the outcome — is not legal analysis. Analysis requires you to identify what principle the court established, why the court reasoned as it did, and what the decision means for the doctrinal question you are investigating.

Summary: “In Puttaswamy (2017), the Supreme Court held that privacy is a fundamental right under Article 21.”  Analysis: “Puttaswamy established privacy as an intrinsic component of Article 21’s guarantee of life and personal liberty, not merely an incidental protection. Critically, the Court’s proportionality framework — requiring that any state limitation be legally authorised, pursue a legitimate aim, and be proportionate in scope — provides the doctrinal foundation for evaluating AI surveillance, though the judgment itself did not address automated systems.”

Mistake 3: No explicit thesis argument

Legal papers without a clear thesis argument — a specific doctrinal claim the paper is arguing for — read as descriptive surveys rather than scholarly contributions. A doctrinal argument is not a research question. It is a claim about what the law means, should mean, or ought to be.

The fix: State your doctrinal argument explicitly in the introduction: “This paper argues that…” It should be a specific claim about a legal principle, interpretation, or framework — not a general statement about the importance of the topic.

Mistake 4: Skipping the legal framework before jumping to analysis

Beginning case analysis without first establishing the constitutional or statutory framework leaves readers — including examiners who may not be specialists in your exact area — without the context they need to evaluate your analysis. Establish the framework first, then show how cases apply or depart from it.

References

End of Module 1 — all 7 Cluster Posts complete.

← Back to Pillar Post: The Complete Guide to Research Paper Structure