Write a final-year project proposal your committee will approve

A good proposal convinces the committee of three things: the problem matters, your plan is realistic, and you can finish in two semesters.

Choose a scope you can finish

Pick a problem that is narrow enough to complete and test. "Smart city" is a theme; "IoT-based water-level monitoring for a hostel tank with SMS alerts" is a project.

Suggested structure

Title: specific and descriptive.
Problem statement: what is wrong today, for whom, and why it matters. Two short paragraphs.
Objectives: three to five measurable objectives, e.g. detect bearing faults with at least 90% accuracy on test data.
Literature review: five to ten recent, relevant sources, and the gap your project addresses.
Methodology: hardware, software, data, and how you will test the result.
Timeline: a Gantt chart across both semesters, with time reserved for testing and writing.
Budget: a component list with realistic local prices.
Expected outcomes: what you will demonstrate at the end.

Mistakes evaluators notice

Objectives that cannot be measured.
No testing or validation plan.
A budget that ignores shipping, spares and failed parts.
A literature review that is only definitions.

Before submitting

Agree the scope with your supervisor in writing, and keep a shared folder with references from day one. It saves weeks when you write the final report.

Looking for a starting point? Browse the FYP idea bank.