How to Write About Your Final-Year Project in an SOP
Write a B.Tech final-year project into an MS SOP with the four facts Berkeley lists: with whom, title, your responsibilities, outcome. A team rewrite.
How to Write About Your Final-Year Project in an SOP
Write your final-year project as one paragraph built on four facts. UC Berkeley's Graduate Division lists them in one line: "with whom, the title of the project, what your responsibilities were, and the outcome." In a team project, the third fact is most of the paragraph.
A project paragraph can describe the system in careful detail and still never say what you did. That is the failure this page fixes. In a US statement of purpose (SOP) for an MS, Berkeley's guidance says faculty read the statement, and a faculty reader can only credit work they can attribute to you. When the paragraph is drafted, a free Quick Review against the CS, AI and data SOP rubric reads it for exactly that: what you produced and whether a reader could check it.
The Berkeley, Purdue and UC San Diego graduate-school pages quoted below were checked on October 31, 2026. None of them states a cycle year, so recheck each page, and your department's own SOP instructions, before you submit. This page is part of our graduate school essays hub.
What three graduate schools ask a project paragraph to contain
These are campus-wide instructions from graduate divisions, not department rules. Your department may add its own.
| School | What its page says | What it adds |
|---|---|---|
| UC Berkeley Graduate Division | Under "Research you conducted": "Indicate with whom, the title of the project, what your responsibilities were, and the outcome. Write technically, or in the style of your discipline. Faculty are the people who read these statements." | The four facts, and the register: technical, for faculty |
| Purdue Graduate School | "If you describe a research or scholarly experience, include information on the topic, research mentor, your role, and outcomes." | The same four facts, with your guide named as "research mentor" |
| UC San Diego Graduate Division | "Briefly describe what you did in each experience. Also, make sure to articulate what you have learned about the field and how those lessons stimulated you to pursue an advanced degree." | A fifth fact: what the project taught you and how it points to the degree |
Read the scope carefully. Berkeley's four-fact line sits under research. Berkeley lists a thesis project as a separate item, "Important paper or thesis project you completed, as well as anything scholarly beyond your curricular requirements", and gives it no formula of its own. Purdue's line covers "a research or scholarly experience". A B.Tech final-year project is not always research.
Our view: use the four facts for any final-year project you write about, research or not, and add UC San Diego's fifth. The basis: all three schools ask what you did, Berkeley and Purdue also ask for the outcome, and none of them asks for a description of the system. The countercase: if your project was a solo build with an unusual result, the outcome is the point, and the "responsibilities" sentence can shrink to a clause.
The five-slot paragraph
This is the decision aid. Fill every slot before you write a sentence of prose.
| Slot | What goes in it | What does not |
|---|---|---|
| 1. Title and problem | The project title and the technical problem, in one sentence | Why the topic is "important for society" |
| 2. With whom | Your guide's name and title, and the team size | A list of every teammate's name |
| 3. Your part | The module, decision or analysis you owned, with "I" | "We designed and implemented the system" |
| 4. Outcome | A measured result, or a limit you found and documented | "The project was a success" |
| 5. What it pointed to | The question the project left you with, which the MS addresses | "This project ignited my passion" |
How long should it be? No school on this page publishes a paragraph length. Berkeley's guidance, for the whole statement, is "Approximately 500 to 1,000 well-selected words" unless the program says otherwise. Our recommendation: about 150 words for your main project. By our arithmetic, that is 15% of a 1,000-word statement and 30% of a 500-word one. Your department may set its own limit; our SOP length guide shows how to find it.
Team projects: the verb test for claiming your part
If your project was a team project, run this test on every sentence about it:
Could each of your teammates write this exact sentence about themselves and be telling the truth?
- If yes, it is team credit. Keep one such sentence, with "we", for context.
- If no, it is yours. These sentences carry the paragraph.
"We built an IoT attendance system" passes for all four teammates, so it is context. "I wrote the face-matching service and cut its response time from 4.1 to 0.9 seconds" (a constructed line, based on the example below) is true of one person. That sentence is the one Berkeley's "what your responsibilities were" is asking for.
Three rules follow from the test:
- Say the split once, plainly. "Of the four modules, I wrote the face-matching service; my teammates built the mobile app, the RFID reader and the database." The reader now knows what you are not claiming.
- Name your guide once, with their title. Purdue asks for the "research mentor" by role. If your guide is also writing one of your recommendation letters, the paragraph and the letter describe the same project, so make sure the module you claim is the one your guide saw you build.
- Use verbs that point at a decision. "Chose", "measured", "rewrote", "compared" and "found" carry more information than "worked on", "was involved in" or "contributed to".
The countercase: some teams really did share everything, for example pair programming every module. Then say so in one clause, and name the decision you were responsible for. Do not invent a solo role your guide would not recognize.
When the project was weak, failed or is not finished
A routine project. If the project followed a standard tutorial build and you made no real decision in it, it does not need a full paragraph. Give it a clause in your preparation paragraph and let the resume carry it. Our guide to how many projects belong in a CS SOP shows how to choose which project gets the main paragraph.
A project that did not work. The outcome slot does not need a success. A constructed line such as "The model reached 91% on our test set and failed on low-light images, which I traced to the training data" is an outcome. It shows you measured something and found a limit. If the project is your only technical evidence, our guide to writing an SOP with no research experience covers what else can carry preparation.
A project still in progress. If you apply in your final year, your project may not be finished when you submit. Write the outcome slot as what exists now and what you will test next, and label the plan as a plan. Do not write expected results as results. Our guide to an SOP project with no results yet was written for PhD applicants, but its rule on projected results applies to a master's statement too.
Constructed example: a four-person attendance project, before and after
Constructed example, written by us, not a real applicant statement. Context (invented): Ananya Rao, a final-year B.Tech student in computer science at an invented college, built an attendance system with three teammates under her guide, Dr. S. Menon.
Before (67 words): "For our final year project, we developed a Smart Attendance System using IoT and Machine Learning. The system uses RFID cards and face recognition to mark attendance automatically. We used Raspberry Pi, Python, OpenCV and Firebase. The project was successfully completed and appreciated by our faculty. Working on this project taught me teamwork and time management, and it increased my interest in the field of artificial intelligence."
After (134 words): "My final-year project, a two-factor attendance system, was built by a team of four under Dr. S. Menon, Associate Professor of Computer Science. I owned the face-matching service; my teammates built the RFID reader, the mobile app and the database. My first version ran face detection on every camera frame and took 4.1 seconds per student on a Raspberry Pi, too slow for a class of 60. I changed the design so detection ran only after an RFID tap, which cut the time to 0.9 seconds. Testing on 300 taps from 62 consenting classmates, I found that false rejections clustered at one doorway with poor light. I could fix the latency, but I could not explain why the model failed in that light. That gap is why I want graduate coursework in computer vision."
Why the revision works, slot by slot:
- Slots 1 and 2 take the first two sentences: title, guide with title, team size and the split. The tools list is gone; tools belong on the resume.
- Slot 3 is the core: one design decision, before and after, with the number that forced it.
- Slot 4 reports a measured result and a found limit. "Appreciated by our faculty" is cut because the reader cannot check it, and the letter can say it if it is true.
- Slot 5 ends on a gap the project exposed, which is UC San Diego's "how those lessons stimulated you to pursue an advanced degree", without the word "passion".
The revision is about 70 words longer. It earns them because every added sentence is one the reader could ask Ananya's guide to confirm.
Check the paragraph before you keep it
Run these on your draft. Each has a pass condition.
- Title and problem. Pass: a reader outside your college understands the problem from one sentence.
- Guide. Pass: your guide is named once, with their title.
- Split. Pass: one sentence says which part was yours and which parts were not.
- Verb test. Pass: at least two sentences could be written truthfully only by you.
- Outcome. Pass: there is a number, a measured comparison or a documented limit. "Successfully completed" is not one.
- Tools. Pass: no sentence is only a list of languages, libraries or boards.
- Direction. Pass: the last sentence names something the MS teaches, not a feeling.
- Consistency. Pass: the project as described matches your resume entry and what your guide's letter will say.
Questions about final-year projects in an SOP
My final-year project is not related to the MS I am applying for. Should I still write about it?
Only for what transfers. If the project gave you a method the MS uses, such as measurement, data handling or a design trade-off, write that part in two or three sentences. If nothing transfers, keep it on the resume and give the paragraph to more relevant work, such as an internship in your MS SOP.
Can I write about the project if it is not finished yet?
Yes. State what exists now, what you have measured so far, and what you will test next, labelled as a plan. Never present an expected result as a result.
Should I add the project's GitHub link?
Follow the application's instructions on links, and write the paragraph so it makes sense without a click. Our guide to GitHub links in a CS SOP covers which document should carry the link.
Is my final-year project "research"?
Only if it asked a question and tested an answer. Berkeley lists "Research you conducted" and "Important paper or thesis project you completed" as separate items. Calling a build project research invites a faculty reader to judge it as research. For FPGA and RTL projects in a VLSI SOP, report the clock target, the number you reached and the decision behind it.
Switching from mechanical to CS? The mechanical to computer science SOP shows how to present a mechanical project as evidence of code.
Applying to a UK course? The MSc computer science and AI personal statement for the UK maps a project to Edinburgh's published maths lines.
If the project became a paper, describe the co-authored paper by your role, not your author position.
Get a free review of your statement of purpose
Get a free Quick Review of your statement of purpose against GradPilot's MS SOP rubric for computer science, AI and data. It reads what your statement shows you producing, whether a reader could check it, and whether your stated direction fits that evidence. Applying in electronics, mechanical or another engineering field? Use the engineering MS SOP rubric instead. Both start from the master's SOP review page.
- Mentioning NPTEL and Coursera courses in an SOP: when an online course fills a gap.
More guides on what goes in an MS SOP:
- How to write about an internship in your MS SOP: one task, one result, one lesson.
- Summer research internship in your SOP: what ten weeks of research can and cannot show.
- Hackathons and competitive programming in an SOP: when a rating or prize earns a sentence.
Sources
Retrieved October 31, 2026, except where noted.
- UC Berkeley Graduate Division, Writing Your Statements (no cycle stated): the four facts for research, the separate thesis-project item, "Faculty are the people who read these statements", and the 500 to 1,000 word guidance.
- Purdue University Graduate School, How to Apply (no cycle stated): topic, research mentor, role and outcomes for a research or scholarly experience.
- UC San Diego Graduate Division, Statement of Purpose (no cycle stated): "Briefly describe what you did in each experience" and what you learned.
Get feedback on your statement of purpose
Paste your draft. The free Quick Review shows what to fix against an admissions rubric before you submit.