Chapter five is short compared to the rest of your research project, but it is also the last thing your supervisor and your defense panel read closely, which means it needs to land well. A lot of students treat it as a formality and rush through it, and it shows. Yes, it does. So, let's talk about how to close your research project properly.
Most universities would expect that in your chapter five, you need to include summary of findings, conclusion, recommendations, contribution to knowledge, and suggestions for further studies. Some departments also want limitations of the study here if it was not already covered in chapter one. Check your own department's format, but this covers the core of what you will almost always need.
This section is exactly what it sounds like, a brief recap of what your study set out to do and what you actually found, going through your objectives one by one. Keep it short, this is not the place to repeat your entire chapter four with all the tables again, just the key findings stated plainly. A good rule of thumb is one or two sentences per objective.
Your conclusion is where you step back and answer the bigger question that your whole project was built around. Based on everything you found, what can you now say about your original problem statement? This is different from your summary of findings because it is more interpretive, you are drawing a conclusion from the specific results rather than just listing them again.
A common mistake here is treating the conclusion as another summary. Instead, think of it as answering the question, so what? Given everything I found, what does it actually mean for the problem I identified back in chapter one?
This is where a lot of students confuse recommendations with findings, and it is worth being careful here. Your findings are what your data showed. Your recommendations are what should be done about it, based on those findings. Each recommendation should trace back to something you actually found, not a general suggestion that you just pulled from nowhere.
For use this as an example, if your finding was that lack of awareness was the main barrier to adoption of a particular service, your recommendation should be about addressing that awareness gap directly, maybe through targeted sensitization programs. In such a case, that would be your recommendation, rather than a vague statement like "the government should do more." So, what I am trying to say here is that you need to be specific about who should act and tell us roughly how.
This section, if your department requires it, asks you to state clearly what your study adds that did not exist before, what did your study actually contribute to gaps in existing literature. Maybe you studied a context that nobody had looked at yet, or you combined two variables in a way earlier studies had not. Keep this honest and specific rather than overselling your research project as groundbreaking when it is really a solid, well done piece of academic work within a known area.
This subsection is just telling you that you want to end the chapter five by pointing at what a future researcher could pick up from where you left off. This is usually connected to your scope or limitations of your study, if you only studied one state, you might suggest a similar study covering a wide region, or if your data was purely quantitative, you might suggest a follow up qualitative study to explore the reasons behind your numbers in more depth.
Turning the summary of findings into a second chapter four with all the tables repeated
Mixing up findings and recommendations so they read like the same thing twice
Vague recommendations with no connection to what was actually found
Overstating the contribution to knowledge
Skipping suggestions for further studies entirely
A good chapter five leaves your reader with a clear sense that your project actually went somewhere, not just that it ended. If you want help pulling your findings, conclusion, and recommendations together properly, I or any member of my team at ProjectPal can help you close out your project the right way. Message us on WhatsApp to get started.
Send your topic and department on WhatsApp and get support built around your actual project.