Most students lose time on their final year project before writing a single line of code. They pick a topic that is too big, write a vague proposal and then get sent back by the supervisor to start again. A good FYP title and a solid proposal fix most of that. They force you to decide what you are building, for whom, and how you will prove it works.
This guide walks through how to choose a good FYP, write a clear title and structure a proposal that gets approved. If you are still looking for ideas, start with our 20 best FYP project ideas for computer science students.
How to Choose a Good FYP Topic
1. Start with a problem, not a technology
"I want to build something with AI" is a technology. "Clinics in my city lose hours to paper appointment books" is a problem. Problems give you users, requirements and a way to measure success. Technology follows.
2. Check that you can finish it
Count the weeks you actually have, then subtract time for testing, documentation and the viva. Choose a scope you can complete in about 70 percent of the time that is left. Anything more is a risk.
3. Confirm you can get the data, tools and users
Do you have a dataset, an API, hardware or real users to test with? If a key ingredient is missing, change the topic now, not in month four.
4. Pick something you can demonstrate
Your viva is a live demo. A project that shows a clear before-and-after in five minutes will always land better than one that needs a long explanation.
5. Make it a little bit unique
You do not need a world-first idea. A familiar system with a new angle, a local need or a specific group of users is enough. For example, an appointment system built for one type of clinic, or a marketplace for one local craft.
What a Good FYP Title Looks Like
A strong title says what the system is, who it is for and, when useful, the method or technology. It is specific and honest.
| Weak title | Stronger title |
|---|---|
| Hospital System | Web-Based Appointment and Patient Record Management System for Small Clinics |
| AI Chatbot | Retrieval-Based University Admissions Assistant Using Large Language Models |
| Online Shopping | Multi-Vendor E-Commerce Platform for Local Artisans with Secure Payments |
| Attendance App | QR-Code Attendance System with Anti-Proxy Checks for University Classes |
How to Write an FYP Proposal
Every university has its own template, so follow yours first. Most good proposals contain the following sections.
What should an FYP proposal include?
Most proposals include a title, an introduction and problem statement, objectives, scope and limitations, a literature or existing-systems review, the proposed methodology and technology, a project timeline, expected deliverables and references. Check your department's template and follow its headings and page limits exactly.
Problem statement
Two or three sentences describing who has the problem, what it costs them and why current solutions fall short. Use numbers or examples if you can find them.
Objectives
Write three to five measurable objectives that start with a verb, such as "Design a database schema for...", "Implement role-based access for...", "Evaluate response time under 100 concurrent users". Vague objectives such as "improve efficiency" cannot be marked.
Scope and limitations
List what is in, and just as clearly what is out. Stating limits protects you when the examiner asks why the system does not do everything.
Existing systems review
Compare two to four existing products or papers in a small table: what they do well, what they lack and how your project differs. This shows you understand the field.
Methodology and tech stack
Explain your development approach (for example agile with weekly iterations), your architecture and why you chose your tools. Justify each choice in one sentence.
Timeline
Break the project into phases with dates: requirements, design, development, testing, documentation and viva preparation. Leave a buffer of at least two weeks.
A Simple Proposal Checklist
- The problem is specific and real.
- Objectives are measurable.
- Scope and limits are written down.
- The timeline fits the weeks you have.
- You have access to the data, tools or users you need.
- Your supervisor has approved the scope.
How to Prepare for the Viva
- Prepare a five-minute demo that works offline, with a backup recording.
- Know your architecture, database schema and every technology choice.
- Be ready to explain what you would do differently and what you would build next.
- Practise answering questions about testing, security and limitations.
FAQ: Choosing an FYP and Writing the Proposal
How long should an FYP proposal be?
It depends on your university, but most proposals are between 5 and 15 pages. Follow your department's template and page limit, and keep every section focused.
Can I change my FYP topic after the proposal is approved?
Usually only with your supervisor's approval, and changes late in the year are risky. If you must change, keep the new scope smaller and update your proposal and timeline.
What is the best FYP for getting a job?
A complete, deployed project that uses a stack employers hire for, such as Laravel, React, Node.js or Python, with clean code on GitHub and a clear write-up. See our FYP ideas for IT students and software engineering FYP ideas for options.
Can someone help me build my FYP?
You can get guidance, code review and mentoring while still doing the core work yourself. Always follow your university's academic integrity rules and make sure you understand every part you present. Read our guide on how much FYP help costs before you decide.
Need Help With Your Proposal?
YourSiteFactory can help you shape a topic, scope it properly and plan the build. See the FYP student offer or get a free quote.
