Final Year Project
VU Final Year Project (FYP) Guide: Proposal, OAR Report, PPT & Viva — Complete Roadmap
Every stage of a VU Final Year Project — choosing an organization, writing an OAR or Internship Report that doesn't get rejected, PPT preparation, and the viva itself — with real approved case studies as reference points.
A Final Year Project is where most VU degrees actually get held up. Course exams have a fixed date and a fixed syllabus — an FYP has neither. Proposals get sent back for revision, reports get "conditionally accepted" with no clear next step, and vivas catch students off guard when they can't explain their own report in their own words. This guide walks through the entire journey — proposal to viva — the way it actually plays out for VU students, referencing real approved projects rather than theory.
The VU FYP journey: what actually happens, stage by stage
Regardless of subject code — CS619, MGT619, HRM620, MGIT661/662, FIN619 and others all follow a similar shape:
- Proposal / synopsis — a short document naming your organization or project idea, submitted for initial approval.
- Report drafting — an OAR (Organizational Analysis/Attachment Report), Internship Report, or a full project report depending on your subject, built around real organizational data.
- Instructor review — your report comes back with comments: "Accepted," "Conditionally accepted," or a request for revisions. This round can repeat more than once.
- PPT preparation — a presentation summarizing your report for the viva session.
- Viva — a live or recorded session where your instructor asks you to explain and defend the report.
Every one of these stages can independently delay your graduation by a semester if it goes wrong. A rejected proposal, a report stuck in revision limbo, or a shaky viva are three separate ways to lose months — which is why treating FYP as "one big task due at the end" is the most common mistake.
Choosing and getting your FYP topic/organization approved
Most VU report-based FYP subjects (OAR, Internship Report) require a real organization — a bank, company, or institution you have some access or reference to. The most common reasons a proposal stalls:
- The organization is too small or informal to produce enough material for a full analysis
- No actual reference, permission, or contact point inside the organization
- Picking a topic that doesn't match the subject's required report type (e.g., treating an OAR like a marketing case study)
Real approved examples on this site used well-documented organizations students had a genuine reference into — United Bank Limited (UBL) for an HRM620 OAR, Nestlé for an MGIT661 OAR, Chenab Limited for an MGIT662 Internship Report, and Meezan Bank for a FIN619 project. In each case, having real, checkable organizational detail is what made the report defensible at viva.
Writing an OAR / Internship Report that doesn't get rejected
An Organizational Analysis/Attachment Report or Internship Report is graded on whether it reflects the actual organization, not generic textbook theory with the company's name inserted. The most common reasons instructors send reports back:
- Plagiarism or heavily templated content that doesn't match the specific organization
- Missing required sections from the report format VU provides for that subject code
- Analysis that doesn't connect back to real data, structure, or practices of the organization named in the proposal
The Results page shows the real instructor comments on two OAR reports built this way — an HRM620 OAR on UBL declared "PASS" by the instructor, and an MGIT661 OAR on Nestlé declared PASS and approved by Dr. Imran Sarmad — both prepared to follow VU's exact report format for that subject rather than a generic template.
Financial projects (FIN619) and ratio analysis — what's different
Finance-track final projects like FIN619 combine an OAR-style report with a ratio analysis section — current ratio, profitability ratios, liquidity ratios and similar, calculated from the organization's actual financial statements. This is a different skill from a management-track OAR: instructors expect you to explain how each ratio was calculated and what it means for that specific company, not just present the numbers.
A real FIN619 project on Meezan Bank went through an initial "Conditionally accepted" round before the OAR, ratio analysis, PPT and viva were all approved in one go — the full case, including the actual instructor comments, is documented on the Results page.
PPT and viva preparation: where students lose the most marks
A polished report doesn't guarantee a smooth viva. The viva tests whether you can explain your own report — where the data came from, why you chose certain ratios or frameworks, and what your conclusions actually mean. Students who memorize a script rather than understanding their own analysis are the ones who struggle when the instructor asks a follow-up question.
A structured PPT — one slide per major report section, not a copy-paste of paragraphs — combined with a practice run answering "why" questions about your own findings, is what turns a nerve-wracking viva into a formality. One student's own words after a guided viva session: "You guided me very well, handled everything efficiently, and explained everything clearly."
Real approved FYP case studies
Every Final Year Project and OAR/Internship Report supported through Nibaha Haq has been approved — 0 rejections in 3 years across CS619, CS519, HRM620 OAR (UBL), MGIT661 OAR (Nestlé), MGIT662 Internship Report (Chenab Limited), FIN619 (Meezan Bank) and more. The real WhatsApp screenshots and instructor comments for each are posted openly on the Results page — not summaries, the actual conversations.
Frequently asked questions
What is an OAR report?
An Organizational Analysis Report (or Organizational Attachment Report) analyzes a real organization's structure, practices, or a specific function, following the report format your VU subject code requires.
How long does FYP approval usually take?
It varies by subject and instructor, but expect at least one review round even for a strong report. Building the report around real, well-documented organizational data from the start reduces the number of revision rounds needed.
What if my proposal or report gets rejected?
A rejection or "conditionally accepted" status almost always comes with specific instructor comments — the fix is addressing exactly what was flagged, not starting over. Message your instructor's comments on WhatsApp and get guidance on the specific revision needed.
Do you help with viva preparation specifically?
Yes — guided viva sessions walk through likely questions on your own report content, not a generic script, so you can explain your analysis confidently.
Which VU FYP subjects do you support?
CS619, CS519, HRM620 OAR, MGIT661, MGIT662, FIN619 and other report-based and project-based final year subjects. Message your exact subject code on WhatsApp to confirm.
Can you help if my FYP is already in progress?
Yes — send your current report draft and the instructor's latest comments, and get guidance on exactly what to revise rather than starting over.
Stuck on your own FYP proposal, OAR report, or viva prep right now? Message it directly on WhatsApp and get guidance specific to your subject code and stage.
Related guides
Ready to get your FYP approved the first time?
Send your subject code, organization, and current stage — get guided from proposal to viva.