How to Write the Conclusion and Future Scope of a Project
By Vivek Singh · · 3 min read
In short
The conclusion restates what the project set out to do and says, objective by objective, what was achieved or found. It adds nothing new. Limitations then state honestly what the project does not do, and future scope lists two to four specific things that could be added next. Together they usually run one to three pages.
Key takeaway
The conclusion closes the loop with Chapter 1. Take your objectives one by one and say what was achieved or found for each. Then be honest about limitations, and turn each limitation into a specific item of future scope. Nothing new is introduced in this chapter.
What the conclusion contains
- One or two sentences restating the aim
- What was done: the system built, or the study carried out, in brief
- What was achieved or found, objective by objective
- What it means: who benefits and how
Write it in the past tense, in plain statements. Avoid praise for your own work; the results do that.
Sample conclusion: software project
The project set out to replace the paper complaint register of the hostel with an online system. A web-based complaint tracking system was designed and developed with separate access for residents, the warden and maintenance staff. All four objectives were met: residents can raise and follow complaints online; complaints are assigned automatically by category; the warden can see open complaints by age and block; and monthly reports are generated. The system was tested with [number] test cases, all of which passed after correction. It gives the hostel office a complete record of every complaint and the time taken to resolve it, which the paper register could not provide.
Sample conclusion: research study
The study examined the awareness, usage and problems of UPI among small shopkeepers in [your area]. Data collected from [number] shopkeepers showed that [finding for objective 1]. On usage, [finding for objective 2]. The main problems reported were [finding for objective 3]. The hypothesis that [your hypothesis] was [accepted or rejected]. The study concludes that [the overall meaning, in one sentence], and that [who] can act on this by [your main suggestion].
Every bracket is filled from your own analysis chapter. If a sentence in the conclusion cannot be traced to a table or a test, remove it.
Limitations
State them plainly. Examiners ask about limitations in almost every viva, and a student who names them looks more credible than one who claims there are none.
For a software project: features left out, the scale it was tested at, platforms it does not support, dependence on an internet connection, security measures not yet added.
For a study: sample size, one area only, convenience sampling, a short period, reliance on what respondents chose to say.
Future scope
Each item should be specific and should follow from a limitation.
| Limitation | Future scope |
|---|---|
| Works only in a browser | An Android app with push notifications |
| Tested with one hostel | Support for several hostels under one admin |
| Sample of [number] in one area | A larger sample across several areas |
| Percentage analysis only | Statistical tests of the relationships found |
Write two to four items as short paragraphs or bullets. "The project can be enhanced in future" says nothing; "online payment of mess fees can be added to the same resident login" says something.
Where these go
Colleges differ. Some put conclusion, limitations and future scope in one final chapter; some give limitations to Chapter 1 or the methodology chapter; commerce reports often separate findings and suggestions from the conclusion. Follow your department's chapter list, which is compared across streams in Final Year Project Report Chapters.
Common mistakes
- Repeating the abstract word for word
- Claiming objectives were met that the results do not show
- New features or data mentioned for the first time
- No limitations at all
- Future scope that is a wish list unrelated to the project
A report written with BlackBook ends with this chapter drawn from its own objectives and results, and you then correct it against what you actually built or found. The abstract is written after it, as the last step.
Frequently asked questions
How long should the conclusion of a project report be?
+
Usually one to two pages, with limitations and future scope taking another page between them. A conclusion that runs longer is usually repeating the results chapter.
What is the difference between findings and conclusion?
+
Findings are the specific results, point by point, each tied to a table or test. The conclusion steps back and says what those findings mean taken together, in relation to your objectives.
Can I write new information in the conclusion?
+
No. Everything in the conclusion should already be supported somewhere in the report. New data, new features and new citations do not belong there.
What should I write in future scope?
+
Two to four specific additions that follow from your limitations: a feature you did not have time to build, a larger sample, another city, a comparison you could not make. Avoid vague lines such as "the system can be improved".
Written by
Vivek Singh
Founder of BlackBook
University of Mumbai graduate and software engineer. He built BlackBook so students can put their time into studies and exams, not months of formatting. More about BlackBook
Tools for your final year project
- AI Blackbook MakerEvery chapter, diagram and front-matter page, generated from your project details.
- Project topicsTopics for every course, grouped by subject, with what each needs.
- Blackbook formatFonts, margins, numbering and page order in one checklist.
- Blackbook by courseChapters, ideas and what examiners look for, course by course.