Best practices · Students
Final Year Project Proposal Best Practices
FreeA practical guide to the first and most important step of a final year project: choosing an idea, cutting it to a size your team can finish, and writing a proposal your supervisor and committee can approve. It covers the problem statement, objectives, a basic literature review, method, feasibility, timeline, risks and ethics, the approval process and the most common reasons proposals come back rejected.
Written by Tauseef Fayyaz8 chapters, 29 practicesAbout 26 min25 quiz questionsReviewed 31 October 2026What you will learn
8 chapters · about 26 min
1Choose an idea worth a year of your timeA good final year project starts from a real problem your team can understand, build for and evaluate. Pick the problem before you pick the technology.4 practices · 4 min
2Scope the project to fit the calendarMost final year projects that fail do not fail on ideas. They fail on scope. Fix the time you have and decide what fits inside it.4 practices · 3 min
3Write the problem statement and objectivesThe problem statement and objectives are what the committee reads first and what you are judged against at the end. Make them specific and testable.3 practices · 3 min
4Do a short, honest literature reviewA proposal does not need a full survey, but it must show you know what exists. Compare a handful of relevant works and explain where yours fits.3 practices · 3 min
5Method, feasibility and timelineThis part convinces the committee you can actually do what you propose. Show the approach, the evidence that it is feasible and a timeline tied to your evaluations.4 practices · 4 min
6Risks, ethics and dataEvery project has risks. Naming them with a plan shows maturity, and handling user data responsibly is part of doing the work properly.3 practices · 3 min
7Get the proposal approvedApproval depends on the document, the short defence and how you respond to feedback. Follow the template, involve your supervisor early and treat changes as normal.4 practices · 3 min
8Common reasons proposals are rejectedRejections tend to repeat the same few problems. Check your proposal against them before the committee does.4 practices · 3 min
About this guide
A final year project (FYP), also called a capstone or senior design project, is usually the largest piece of work a computing student does before graduating. It runs for one or two semesters, it is marked by people who did not watch you build it, and it often becomes the first project you talk about with employers or in a master's application. Almost everything that goes wrong later, from an unfinished demo to a thin report, can be traced back to the proposal: an idea that was too big, too vague or not really a problem at all.
This guide walks through the proposal stage in the order you meet it. The first chapters cover choosing an idea and scoping it to the calendar. The middle chapters cover the parts every proposal template asks for: problem statement, objectives, a short literature review, method, feasibility, timeline and risks. The last two chapters cover getting the proposal approved and the reasons committees most often send proposals back.
The advice is checked against real university material, including the FAST School of Computing BS Final Year Project Handbook (2023), the FYP guidelines published by the University of Lahore's Islamabad campus, the ACM Code of Ethics and Basecamp's Shape Up method for fixing time and flexing scope. Every department has its own template, marks split and deadlines, so treat your own handbook as the final word and use this guide to fill that template well.
It applies whether you study in Lahore, Pune, Dhaka or anywhere else with a capstone requirement. Each chapter ends with a short quiz. When the proposal is approved, continue with the FYP Report Best Practices guide and the FYP Team and Supervisor Checklist.
Common questions
How do I choose a good final year project idea?
Start from a real problem that specific people have, check what already exists, and pick something your team can mostly build with skills you have or can learn in a few weeks. Make sure it has at least one genuinely challenging part, such as a non-trivial algorithm, a model evaluated on real data or a hardware integration.
What should a final year project proposal include?
Most templates ask for a title, problem statement, objectives, a short literature review, method or architecture, feasibility, timeline, risks and references. Some departments add items such as the targeted UN Sustainable Development Goals or the core courses the project draws on. Always use your department's latest template.
Why do FYP proposals get rejected?
The most common reasons are scope that is too big to finish or too small to count, ideas that repeat existing work without a real difference, vague problems or objectives that cannot be tested, and technology chosen to sound impressive rather than to solve the problem.
How long should the literature review in a proposal be?
Short. Ten to fifteen relevant items compared on the points that matter for your problem is usually enough at proposal stage, ending with a clear statement of the gap your project fills. The full literature review belongs in the final report.
Can I change my FYP scope after the proposal is approved?
Usually yes, with your supervisor's agreement and sometimes the committee's, especially when switching to a planned fallback. Record the change and the reason in writing so it is clear at the mid and final evaluations.
Should my final year project be a development or a research project?
Choose based on your goal and your supervisor. A development project is judged on a working system for real users; a research project is judged on a new or improved approach backed by measured results. Many handbooks, such as FAST's, give each type its own report structure.
Sources (7)
Checked against these, last on 31 October 2026.
- BS Final Year Project Handbook 2023 (FAST School of Computing), FAST-NUCESnu.edu.pk/public/downloads/FYP-Handbook-2023.pdf
- General Instructions (Final Year Project), University of Lahore, Islamabad campussites.google.com/view/uol-isb-fyp/guidelines
- ACM Code of Ethics and Professional Conduct, ACMwww.acm.org/code-of-ethics
- Shape Up: Set Boundaries, Basecampbasecamp.com/shapeup/1.2-chapter-03
- IEEE Reference Guide, IEEEjournals.ieeeauthorcenter.ieee.org/wp-content/uploads/sites/7/IEEE_Reference_Guide.pdf
- Author-date citation system, APA Styleapastyle.apa.org/style-grammar-guidelines/citations/basic-principles/author-date
- Zotero quick start guide, Zoterowww.zotero.org/support/quick_start_guide
Related on Sefism
Picked from the other libraries by shared topics.
Best practices
See all- Final Year Project Report Best PracticesWrite a final year project report or thesis: chapters, literature review, design, testing and results, IEEE and APA citations, figures, similarity checks and honest AI use.
- Final Year Project Presentation and Defence Best PracticesPresent and defend your final year project well: clear slides, a live demo with a backup video, honest answers, explaining your own code and decisions, and team presentations.
- How to Learn a New Programming Language or FrameworkBest practices for learning a new language or framework fast: set a goal, start with official docs, build small projects, practise deliberately, use spacing, read real code, learn with AI wisely.
Checklists
See all- FYP Team and Supervisor ChecklistRun your final year project team well: pick teammates, choose a supervisor, meet and take notes, split work fairly, use Git as a team, keep evidence and handle a teammate who does not contribute.
- Career Switch into Tech ChecklistMove into software from another field step by step: choose a direction, follow a learning plan, build proof of skill, use your previous domain, network, plan your runway and target a first role.
Career questions
See all- Is a UK master's still worth it in 2026?It can be, but the maths has changed. Graduate tech jobs in the UK are harder to find, the Graduate visa drops from two years to 18 months for applications from 1 January 2027, and sponsored jobs have salary floors many junior roles miss. A UK master's is worth it if you want the degree itself, have a realistic plan for sponsorship, and can afford it without crushing debt.
- Should I do a master's abroad or get work experience first?For most software engineers, one to three years of work experience before a master's makes the degree more useful, the application stronger and the job search afterwards easier. Go straight away if you have a clear research goal, a strong scholarship, or a time-limited opportunity. Decide by your goal, not by what classmates are doing.
- AI is improving so fast. Is it still worth becoming a software engineer?Yes, but the job is shifting. Typing code is becoming cheaper; deciding what to build, judging whether it is correct, and owning it in production is not. Aim to be the engineer who directs and checks AI output, and build the judgement that makes that possible.
Stuck on something specific?
Writing only gets you so far. If you want an answer to your situation rather than the general case, book a session and we will work through it together. Sessions are free for approved Sefism members, and a few slots open each week.
- 1:1 Mentorship
- Fresh Graduate Mentorship
- Career Guidance
Brand deals, promos and partnerships: tauseeffayyaz@gmail.com