Free editable template
A ready-to-fill project synopsis with all ten sections and a project plan table.
Synopsis sections
- Title of the project
- Group members, guide and department
- Introduction (half a page)
- Problem statement (3 to 5 lines)
- Objectives (4 to 6 bullet points, measurable)
- Literature survey or existing system (2 to 4 references)
- Proposed system and methodology with a block diagram
- Scope and limitations
- Hardware and software requirements
- Project plan: phases with weeks
- Expected outcome and applications
- References
Sample objectives (attendance system using face recognition)
- To capture and store face data for at least 60 students
- To mark attendance automatically with at least 90% recognition accuracy in classroom lighting
- To generate daily and monthly attendance reports for faculty
- To alert the admin on repeated absentees
What gets a synopsis approved
- A problem your guide recognises as real
- Scope that fits your semester and team size
- A block diagram that shows you know how it will work
- Something that is yours: a dataset, a feature, a comparison, a local use case
- A realistic timeline
What gets it rejected
- A title copied from a list of readymade projects
- Objectives like “to study” or “to learn” with nothing to demonstrate
- A topic done by seniors last year with no change
- Technology chosen without a reason
FAQs
How many pages should a synopsis be?
Three to six pages. Some universities give a one-page abstract form plus a detailed synopsis.
What is the difference between synopsis and abstract?
A synopsis is a proposal written before the project. An abstract is a 150 to 250 word summary written after it is complete.
Can I change my topic after synopsis approval?
Small changes in scope are usually fine with your guide's consent. A completely new topic normally needs a fresh synopsis.
Last reviewed: 2026-10-11. Always follow the format your own department gives you.