11:18:22 AM NPT Arduino, Robotics & IoT tutorials for Nepal
Beginner

How to Write a Final Year Project Proposal (BE / BSc CSIT): Template + Block Diagram

A one-page structure for your BE or BSc CSIT final year project proposal: problem, measurable objectives, scope, literature review, block diagram and Gantt chart.

On this page
How to Write a Final Year Project Proposal (BE / BSc CSIT): Template + Block Diagram

Proposal season arrives faster than anyone expects. One week you are choosing an idea, the next week your supervisor wants a document and a short presentation. The good news: a proposal is not a mini report. It is a plan that answers four questions clearly. What problem are you solving? What exactly will you build? How will you build it? How will you know it works?

This guide gives you a section-by-section template, shows how to turn vague goals into objectives an examiner can test, and explains how to draw a block diagram that makes your whole project easy to understand.

Important: every college and department has its own proposal format, page limit and submission process. Use this as a thinking guide, then check your department's format and follow it exactly.

If you have not picked your idea yet, start with How to Choose and Plan Your Final Year Project first.

The proposal on one page

Before writing anything long, fill in this one-page skeleton. If you cannot fill every row in one or two sentences, your idea is not ready yet.

Scroll sideways to see all columns.

Section What it answers Length guide
Title What the system is, in plain words One line
Problem statement Who has what problem, and why it matters 3 to 5 sentences
Objectives What you will deliver, in testable terms 2 to 4 bullet points
Scope and limitations What is in, and what is deliberately out Short list
Literature review What others did and the gap you fill A table plus a paragraph
Methodology Block diagram, tools, steps, testing plan The longest section
Feasibility Can you finish it with your skills, time and parts? A short paragraph each
Timeline Gantt chart of the work One chart
Expected output What the examiner will see on demo day A few lines
References Sources you actually read As many as you used

Once the skeleton works, each row expands into a section of your document.

Title: plain and specific

A good title tells the examiner what the system does. Compare:

  • Weak: "Smart IoT System"
  • Better: "Water Tank Level Monitoring and Leak Alert System Using ESP32"

If your project uses machine learning, say what it predicts, not just "AI-based".

Problem statement: start from people, not parts

Write who faces the problem, what happens now, and why that is a problem. Use a real situation you have seen. In Nepal, rooftop water tanks that overflow or run dry, crowded attendance registers in big classes and crops that get watered at the wrong time are all problems students have built good projects around.

Do not start with "Arduino is a microcontroller...". The board is a tool, not the problem.

Objectives: bad vs good

This is the section examiners read most carefully, because your final results will be compared against it. An objective should use a measurable verb and, where possible, a number you can test.

Scroll sideways to see all columns.

Bad objective Why it is weak Good objective
To make a smart water system Cannot be tested To measure tank water level and display it as a percentage on a phone
To make attendance easy "Easy" is not measurable To record student attendance using RFID cards and store it with date and time in a database
To use AI for crops No output defined To classify leaf images into healthy or diseased and report accuracy on a test set
To study IoT A study is not a deliverable To send sensor readings to a web dashboard at a fixed interval

A useful rule: one objective should become one test in your final report. If you cannot imagine the test, rewrite the objective.

Keep it to two to four objectives. A short list you fully achieve looks far better at the defence than a long list you half achieve.

Scope and limitations

Scope protects you. State what the project covers and what it does not. For example: "The prototype monitors one tank of known depth. It does not control the pump. The demo runs on low voltage only." Writing limitations early is honest, and it stops the panel from expecting features you never promised.

A handy trick is to think in three levels:

  • Minimum: the version you will finish even if everything goes wrong.
  • Target: what you plan to deliver.
  • Dream: extras if time allows.

Put the target in your objectives, and mention the dream items as future work.

Literature review in three steps

Copying ten abstracts is not a literature review. A review shows that you understand what already exists and where your project fits.

  1. Find around five relevant sources. Journal or conference papers, final year projects from other colleges, well-documented open-source projects and component datasheets all count. Your supervisor or library may suggest databases.
  2. Put them in a table. Read each one and fill in the same columns.
  3. Write the gap. One paragraph that says what the existing work does not do, and how your project addresses it.

Scroll sideways to see all columns.

Source Method used Result Limitation
Paper or project 1 Float switch with buzzer Alerts at full tank only No level percentage, no remote view
Paper or project 2 Ultrasonic sensor with LCD Shows level locally Must climb to the roof to read it
Paper or project 3 GSM SMS alert Remote alert Only at fixed levels, ongoing SMS cost

The "Limitation" column is where your project idea comes from. If every limitation is something your project solves, your gap is clear.

Methodology and the block diagram

The methodology explains how you will build and test the system. It usually includes a block diagram, a flowchart or system architecture, the hardware and software tools, and the testing plan.

How to draw a block diagram

Draw the block diagram before you buy parts or write code. It forces you to think about every signal.

  1. Put inputs on the left: sensors, buttons, RFID readers, cameras, user input.
  2. Put processing in the middle: the microcontroller, server, or model.
  3. Put outputs on the right: displays, buzzers, motors, dashboards, databases, notifications.
  4. Add power as its own block at the bottom, with arrows to everything it feeds.
  5. Label every arrow with what flows along it: "distance in cm", "I2C", "Wi-Fi / HTTP", "PWM".

Example for a tank monitor:

Scroll sideways to see all columns.

Block Type Connects to Signal on the arrow
Ultrasonic sensor Input ESP32 Trigger and echo pulses
ESP32 Processing Sensor, Wi-Fi router GPIO, Wi-Fi
Wi-Fi router Link ESP32, phone HTTP over local network
Phone browser Output Router Level percentage page
Buzzer Output ESP32 Digital HIGH/LOW
5 V supply Power ESP32, sensor 5 V and GND

Every arrow is something you should be able to explain in the viva. If you cannot explain an arrow, simplify the diagram.

For software-heavy CSIT projects, the same idea becomes a system architecture diagram: client, server, database and any external API, with arrows labelled by request type. Many departments also expect a use case diagram or data flow diagram, so check what yours asks for.

Tools and testing plan

List your hardware, software, languages and libraries in a table. Then write one line per objective about how you will test it. "Compare the displayed level against a measuring tape at five known water depths" is a testing plan. "We will test the system" is not.

Feasibility

Many proposal formats include a feasibility study. Keep it honest and short:

  • Technical: do you or your team know the tools, or can you learn them in time?
  • Economic: are the parts available in Nepal and within a student budget? A component list is enough; you do not need exact costs unless your format asks for them.
  • Operational: will people actually be able to use it?
  • Schedule: does it fit your semester?

Timeline: a Gantt chart with five bars

You do not need thirty tasks. Five clear bars work well:

Scroll sideways to see all columns.

Phase What happens
Study and design Literature review, block diagram, part list
Build version 1 Minimum working system
Integrate and improve Target features, dashboard, enclosure
Test and measure Run the tests from your testing plan
Report and defence prep Write chapters, slides, mock viva

Leave a buffer before every deadline. Parts arrive late, boards get damaged, and team members have exams.

Before you submit: checklist

  • Every objective is measurable and maps to a test.
  • Scope and limitations are written down.
  • Literature review has a table and a clear gap.
  • Block diagram has labelled arrows and a power block.
  • Gantt chart is realistic, with a buffer.
  • References are real sources you read, in the style your department asks for.
  • The document follows your department's template, page limit and font rules.

FAQ

How long should a final year project proposal be?

It depends entirely on your college. Some ask for a few pages, others for a longer document. Check your department's format and ask your supervisor.

Can we change our objectives after the proposal is approved?

Small adjustments are often possible after discussion with your supervisor, but follow your department's process. Writing realistic objectives at the start saves you from this problem.

Do I need a circuit diagram in the proposal?

A block diagram is usually enough at the proposal stage. Detailed circuit diagrams normally belong in the final report, but check what your department expects.

Where do I find ideas if I do not have one yet?

Browse our final year project ideas for electronics and computer engineering or the BSc CSIT project ideas with tech stacks, then come back to this template.