Abstracts, Introductions and Conclusions Compared
The material overlaps because all three describe the same study. What separates them is who is reading, and when — and once you have that, the writing decisions stop being guesswork.
The distinction the source opens with
That sentence is the reason this passage is worth a page. The problem it names is real and most writers hit it late: you finish the report, sit down to write the front and back matter, and find yourself with one pile of material and three places to put it. The study, the question, the design, the findings and what they mean all belong in all three.
The source's answer is that overlap is expected and is not the problem. Sameness of treatment is the problem. The three sections cover the same study because they have to; they are written differently because each is answering a different reader in a different situation.
THREE SECTIONS, THREE STATED PURPOSES
| Section | Purpose, as the source states it | Content or order given | Length given |
|---|---|---|---|
| Abstract | "to preview or summarise the whole thesis or report" | Contents, conclusion, new information and relevance; the order usually follows the paper's own main points | None here — the week's slides give a separate figure |
| Introduction | "to locate or situate your chapter/paper in the broader field or area of study and to link your main topic to the field"; the topic itself is the main focus | Five moves, general to specific | None |
| Conclusion | "to provide generalisations based on your findings, implications of those findings and recommendations for future work" | Generalisations, then implications, then recommendations for future work | None |
All three purposes are quoted from the same section of the week's study notes. The length column is empty because the notes state no length for any of the three.
Preview and summary — one text, two jobs
Nothing about the text changes. The reader's situation changes, and that changes what the text is being asked to do. Attached to the paper, the abstract is a routing device: it tells someone holding the full document what is coming and in what order, so they can decide whether to read on and where to start.
Detached — in a database record, a search result, a conference programme, a circulated reading list, a slide in someone else's presentation — the same paragraph is the entire study as far as most of its readers will ever encounter it. They will cite it, quote it, act on it or dismiss it without opening the paper.
Attached — the abstract as preview
- The reader has the full text in front of them
- Job: tell them what is coming, in what order
- Failure mode: it reads as a contents page in sentences
- Test: does this help someone decide whether to read on?
Detached — the abstract as summary
- The reader has the abstract and nothing else
- Job: convey the study whole — problem, design, findings, significance
- Failure mode: it announces topics without ever stating a finding
- Test: could someone describe your study correctly from this alone?
The distinction is the source's. The two columns are this library's working out of what follows from it, and the practical consequence is one rule: write for the detached reader. An abstract that says "this paper first reviews the literature, then presents the method, and finally discusses the implications" functions adequately as a preview and fails completely as a summary, because separated from the paper it conveys nothing whatever about what was found.
The reverse does not happen. An abstract that states the problem, the design, the findings and what they mean serves the detached reader fully and still previews the paper perfectly well for the attached one. One of the two functions subsumes the other, which is why it is worth knowing which is which. The worked example at The Anatomy of an Abstract is a summary in this sense throughout — it announces nothing and states everything.
The introduction: general to specific, in five moves
- The field, and what is known
- How your research fits it
- Why it is needed
- Your specific aims
- Outline of the sub-sections
Each move narrows. That is the whole organising principle and it is stated plainly, which makes the introduction the most straightforwardly delivered of the three sections. The source also says something easy to skim past: the topic itself is the main focus of the introduction. Not your study — the topic, and your study's place in it.
Note where the fifth move puts you. "An outline of the main sub sections" is the point at which an introduction and an attached abstract come closest together, and the difference is one of proportion: the outline is one move of five here, and it would be the whole of a preview-only abstract. That observation is this library's; the source does not draw the comparison.
TWO INTRODUCTIONS IN ONE WEEK'S NOTES
| Paper or chapter introduction | Proposal introduction | |
|---|---|---|
| Where it is stated | Section 3 of the notes | Section 2 of the same notes |
| Number of items | Five moves | Eight components |
| Organising principle | General to specific, stated | A flat list, no principle stated |
| Names the gap | No — move three justifies "the need for your research" without using the word | Yes — "a concise description of the 'gap' within the literature", to be repeated at the end of the literature review |
| Includes methods | No | Yes — "a concise description of the methods and methodology" |
| Includes definitions | No | Yes — "concise definitions of any specialized terms used throughout the proposal" |
Both lists are in the same document. The genres genuinely differ — one introduces a paper or chapter, the other a proposal — but the source sets them side by side nowhere and never says how they relate.
The difference is defensible: a proposal introduction does work a paper introduction does not, because there are no findings yet and the reader is deciding whether to approve the study. It is still two lists, in one week's notes, unreconciled. The proposal version is at Writing the Proposal Introduction.
The conclusion: generalisations, implications, recommendations
- Generalisations
- Implications
- Recommendations for future work
The order is a widening, and it is the exact mirror of the introduction. The introduction narrows from the field to your aims; the conclusion widens from what your findings support, to what follows from that, to what someone should do next. The symmetry is this library's observation — the source states both orders and never remarks on the pairing.
The only definition of a recommendation in fourteen weeks
The previous week's analysis sequence names Recommendations as a closing step and never explains what one is. Here, for the first and only time in the whole subject, the word is given content: a recommendation is a recommendation for future work. It is addressed to the next researcher and it concerns what should be studied next.
That closes a gap this library has been recording. It also opens a different one immediately, because for the reader this material is aimed at, the word does not mean that.
What the source defines
- A recommendation is for future work
- Addressed to the next researcher
- Concerns what should be studied next
- Sits third in the conclusion's order, after generalisations and implications
- This is the only definition of the word anywhere in fourteen weeks
What a project audience usually means
- A recommendation is addressed to a sponsor or decision-maker
- Concerns what to do about the findings
- Carries an owner, a cost and a date
- Is often the only part of the report the commissioner reads closely
- The supplied source does not support this reading. It is set out here because your readers will assume it
The two accounts of the abstract, in one week
The week describes the abstract twice — once on its slides and once in its study notes — and the two accounts are not the same. Neither cross-references the other, and a reader working from one of the two files would never know the other existed.
THE SLIDE ACCOUNT AND THE NOTES ACCOUNT
| The slides | The study notes | |
|---|---|---|
| Purpose | Not stated as a purpose — the slide describes what an abstract does | "to preview or summarise the whole thesis or report" |
| Length | "usually … 300 words or less" | None |
| Form | "one paragraph" | None |
| Content | Purpose and problem; the basic design of the study; major findings or trends — list truncated in the file | Contents, conclusion, new information, relevance |
| Ordering rule | "a prescribed sequence" | The order usually follows the paper's own main points |
| Style rules | Four — voice, sentences, tense, and written last | None |
| Preview and summary | Not mentioned | Stated here, and only here |
Two accounts of one section, in one week's material. They overlap without matching: "the basic design of the study" appears only in the slide account, and the preview and summary distinction only in the notes.
Neither account is wrong and neither is complete. Taken together they are more useful than either alone, which is a fair description of this week generally. The slide account, and how tightly each part of it binds, is at Writing an Abstract.
What is not specified
Deciding what goes where
One pile of material, three destinations
What to carry forward
- Overlap between the three sections is expected. Identical treatment is the failure the source is warning about.
- Preview and summary are the same text read in two situations. Write for the detached reader and both are served; write for the attached one and only one is.
- The introduction narrows in five moves. The conclusion widens in three. They are mirrors, and knowing that settles most placement questions on its own.
- A recommendation, as this material defines it, is for the next researcher. If yours is for a sponsor, that is a second and different thing — label both.
- The conclusion's main purpose is stated as generalisation, and the previous week was careful about exactly that. Say what you claim to generalise to, and on what basis.
- No length is given for any of the three. Where your submission is silent, so is the material, and the judgement is yours.
Frequently asked questions
What is the real difference between an abstract and an introduction?
The abstract's purpose is to preview or summarise the whole document; the introduction's is to situate the paper in its field, with the topic as the main focus. The abstract conveys your study; the introduction largely talks about the field your study sits in. That is why an introduction that opens with your findings feels wrong, and why an abstract that only describes the field is useless once separated from the paper.
Is it a problem if the abstract repeats sentences from the conclusion?
Not in itself. The source's own framing is that all three sections require similar details and differ in treatment rather than in subject. The test is whether the treatment differs: the abstract should state the finding, the conclusion should state the generalisation drawn from it, and if the two sentences are identical then one of them is doing the wrong job.
Does "recommendations" mean recommendations to my sponsor?
Not in this material. The only definition given anywhere in fourteen weeks is "recommendations for future work" — addressed to the next researcher, about what should be studied next. The sponsor-facing sense of the word is the one a project audience will assume, and the source does not cover it. Label the two kinds separately if your report carries both.
How long should the introduction and the conclusion be?
The material does not say. No word count, proportion or ratio is given for any of the three sections, which is notable in a week that argues word limits discipline a writer. The only figure anywhere is the abstract's hedged 300 words. Where your own submission specifies proportions, follow those.
My study is qualitative and the conclusion is supposed to generalise. What do I do?
You are between two statements the subject makes a week apart and never reconciles: generalisation is the conclusion's main purpose here, and the previous week is careful about whether generalising across time and space is meaningful at all. Neither is withdrawn. The workable answer is to state explicitly what you claim your findings apply to and on what basis, rather than generalising silently or refusing to conclude.
References and source attribution
- The supplied teaching source: weekly study notes, slide decks and assessment activities for a master's-level research methods subject in project management. Author, institution and year not stated in the supplied files.
- Week 13 study notes, section 3, on abstracts, introductions and conclusions. Supplied as two textually identical documents under different filenames, neither dated, versioned nor marked as current.
- Week 13 slide deck, 'The Challenge of Writing Up', slides 19-21, which give a second and non-identical account of the abstract together with the only annotated worked example in the material.
- The supplied Week 12 material on analysing qualitative data and results, which carries the caution about generalisations across time and space and names Recommendations as a closing step without defining it.
Suggested questions for Ask KEVOS
- Read my abstract as though the paper were not attached — what is missing?
- Check my introduction against the five moves and tell me which one is absent.
- Split my recommendations into recommendations for future research and recommendations for practice.
- Is my conclusion in the order the source requires — generalisations, implications, recommendations?
- What exactly does the supplied source define a recommendation as?
- Compare what my abstract claims with what my conclusion claims and flag any mismatch.