IMRaD is not a bureaucratic template. Each section has a job: the introduction asks a question, the methods explain how it was investigated, the results report what was found, and the discussion explains what it means. Knowing the job makes writing the section easier.
Sign in to mark this article as read and track your progress.
The most common writing mistake in a research report is starting at the wrong place — usually the introduction — when the methodology and results sections aren't settled yet. Structure is not an afterthought to impose once the content exists; it is the skeleton that keeps each section doing its own job.
The standard for empirical research is IMRaD: Introduction, Methods, Results, and Discussion. Every section has a distinct task:
| Section | Its Job |
|---|---|
| Introduction | State the question and justify why it is worth answering |
| Methods | Explain how the question was investigated so that another researcher could repeat it |
| Results | Report what the data showed, without interpretation |
| Discussion | Explain what the results mean, how they relate to prior work, and what they don't settle |
A fifth element — the References list — is not a section in the IMRaD sense but is just as non-optional.
A journal article is usually four to twelve pages. A thesis or major project report is fifty pages or more, which means the IMRaD backbone needs scaffolding around it:
Front matter — title page, declaration, acknowledgements, table of contents, list of figures, list of abbreviations, and an abstract. The abstract is especially important: it must stand alone because many readers will never go further.
An extended introduction — where a journal article might open a problem in two paragraphs, a thesis chapter may spend ten pages establishing context before the problem statement.
A separate literature review chapter — a journal article folds the literature review into the introduction; a thesis gives it its own chapter because the review is long enough to make an argument in its own right.
An extended methodology chapter — where a journal methods section might run two columns, a thesis chapter justifies every design choice and discusses its trade-offs.
Separate results and discussion chapters — a journal article can combine these; a thesis almost always keeps them apart to prevent results from being contaminated with interpretation.
Conclusion, recommendations, and appendices — the conclusion synthesises findings (it is not a results restatement); recommendations state what should be done differently next time or in practice; appendices carry raw data, questionnaire instruments, or code listings that the body text only mentions.
A report written for university examiners must demonstrate that the writer understands methodology, can engage with the literature, and can interpret findings critically. Every section contributes to that assessment, and the literature review and methodology chapters often carry the most marks.
A report written for a technical audience — say, a SOC manager who commissioned a penetration test — leads with an executive summary rather than an abstract, groups findings by severity, and moves recommendations earlier than a thesis would. The structure shifts because the reader's question shifts from "did this student understand the method?" to "what do I fix and in what order?"
A student submits a project report where the discussion section begins: "The results showed a mean detection rate of 94.3%. This is discussed in this chapter." Identify what is missing from that opening sentence, and explain what the discussion section is supposed to do that the results chapter already did not.
