Final Year Project Presentation PPT Structure in 12 Slides
A 12-slide blueprint for final-year engineering reviews, with exact minute-by-minute timings, architecture diagram rules and the 5 questions external examiners always ask.
A 10-minute final year project review requires a 12-slide deck where you spend 45 to 60 seconds per slide. According to 2026 guidelines from CodeAJ, viva-voce and project demonstrations carry 30% to 50% of your total project marks across Indian technical universities like VTU, Anna University, JNTU, AKTU, and Mumbai University. If you waste your first five minutes reading literature survey paragraphs, the external examiner will cut you off before you reach your architecture or working output.
In short
- Cap your deck at 12 slides for a 10-minute slot, keeping your total group script between 1,000 and 1,500 words (100 to 150 words per minute).
- Spend 2 minutes on the problem (Slides 1–3), 6 minutes on system architecture and modules (Slides 4–9), and 2 minutes on results and references (Slides 10–12).
- Never live-code from a blank IDE during a viva; embed a 60-second pre-recorded offline video and use syntax-highlighted static blocks with line-range focus.
- Split group speaking turns by project modules rather than odd/even slide numbers, and use a scripted verbal handoff so the panel knows who built what.
How many slides should a 10 minute final year project presentation have?
A 10-minute final year project presentation should have 8 to 13 slides, following the one-slide-per-minute pacing rule confirmed by Adobe and Wonderslide. For engineering capstones, a 12-slide deck is the sweet spot: it covers all mandatory university sections while giving you roughly 50 seconds per slide before the 5-minute Q&A begins.
Different templates recommend slightly different numbers depending on depth. General presentation guides from Slidestack suggest 8 to 13 slides, whereas engineering-specific guides from CodeAJ and AIPPT stretch from 10 to 15 slides to fit requirements and verification data. Do not cross 15 slides. If your pace drops below 45 seconds per slide, you end up flipping through diagrams before the external examiner can read the labels.
At a normal speaking rate of 100 to 150 words per minute, Wonderslide notes that a 10-minute slot fits a total script of 1,000 to 1,500 words across your entire group. If your four-member team writes a 3,000-word script, you will get stopped at slide 6.
Format every slide using a minimum 30-point font size for body text, a rule Storyfiner recommends so examiners sitting at the back of a long lab can read your text without squinting. Pair that with the 6x6 rule from PPTMaker: put a maximum of 6 bullet points on a slide, and a maximum of 6 words per bullet.
The 12-slide wireframe and minute-by-minute budget
Use this exact 12-slide final year project presentation ppt structure for engineering students, which maps the mandatory Indian university sections from College Project Expert to the 2-6-2 minute time budget from Flyppt.
| Slide | Slide title | Time budget | Exact contents to put on the slide |
|---|---|---|---|
| 1 | Title and credentials | 0:00 – 0:30 (30s) | Project title, college logo, department name, team names with university roll numbers, and internal guide's name and designation. |
| 2 | Problem statement and motivation | 0:30 – 1:15 (45s) | One real-world failure or bottleneck, who it affects, and why current manual or legacy fixes fail. |
| 3 | Objectives | 1:15 – 2:00 (45s) | 3 to 4 measurable engineering targets (accuracy threshold, latency target, or hardware cost ceiling). |
| 4 | Existing vs proposed system | 2:00 – 3:00 (60s) | A two-column comparison table contrasting baseline limitations against your technical changes. |
| 5 | System architecture | 3:00 – 4:15 (75s) | Block diagram showing technical layers, service blocks, data flow arrows, and architectural pattern (MVC, three-tier, or IoT edge-cloud). |
| 6 | Database or hardware schematic | 4:15 – 5:15 (60s) | For CSE/IT: ER diagram, primary-foreign keys, and 3NF tables. For ECE/Electrical: circuit diagram, pinouts, and voltage/current ratings. |
| 7 | Tech stack and justification | 5:15 – 6:00 (45s) | Frameworks, languages, and sensors grouped by layer, plus a one-line reason why you rejected the main alternative. |
| 8 | Core module implementation | 6:00 – 7:00 (60s) | Split of the 3 to 4 functional modules, the core algorithm or mathematical pipeline, and one critical code block snippet. |
| 9 | Live demo / prototype video | 7:00 – 8:00 (60s) | Embedded 60-second screen recording or hardware run showing input, processing, and final output without cuts. |
| 10 | Experimental results and testing | 8:00 – 8:50 (50s) | Performance metrics table, test cases passed, confusion matrix or latency graph, and high-resolution UI or hardware output photos. |
| 11 | Limitations, conclusion, future scope | 8:50 – 9:35 (45s) | Honest system boundaries (e.g., works only on local Wi-Fi), summary of achieved objectives, and 2 specific upgrades for next phase. |
| 12 | References | 9:35 – 10:00 (25s) | Base research papers cited in strict IEEE format, displayed while you thank the panel and invite questions. |
If you want to build these 12 slides without fighting alignment boxes for three nights, the Canva AI Masterclass shows you how to use Magic Design and Magic Write to lay out clean technical decks fast.
What should be on the system architecture slide?
Your system architecture slide must map out core technical layers, separate service blocks, system boundaries, integration points, and directional arrows showing how data or requests flow between components, according to guidelines from Wondershare EdrawMax and Engineers Planet. It must also name your architectural pattern, such as MVC, three-tier, or microservices.
This is the single slide where external examiners decide your grade. A 2025 breakdown by Skillbolt notes that technical project panels weight technical understanding at 40%, implementation quality at 25%, innovation at 20%, and presentation skills at 15%. Examiners spend most of the viva staring at Slide 5 and Slide 6 while questioning you.
What most students get wrong on Slide 5 and Slide 10 (and how to fix it)
Most groups paste four commercial logos (React, Node.js, MongoDB, AWS) connected by double-sided arrows with no labels, and call it an architecture diagram. On Slide 10 (Results), they paste a zoomed-out laptop screenshot of a login page. Both mistakes tell the examiner you downloaded a GitHub repository last night.
Compare how a weak slide looks next to a slide that scores full marks:
| Slide | What most students put (gets grilled) | What you should put instead (passes review) |
|---|---|---|
| Slide 5: System architecture | Four unlabelled boxes (User ↔ Frontend ↔ Backend ↔ Database) with brand logos and bidirectional arrows. | A three-tier boundary box diagram: Client Layer (React PWA sending POST /api/predict with JSON payload) → Application Layer (FastAPI server running JWT middleware + YOLOv8 inference worker) → Data Layer (PostgreSQL 3NF schema + Redis cache), with one-way arrows labelled with protocol (HTTPS / TCP). |
| Slide 6: Schema or circuit | A bullet list of table names (users, orders, logs) or a photo of a messy breadboard with jumper wires. | For software: an ER diagram showing primary keys (PK), foreign keys (FK), and 1-to-many cardinalities normalized to 3NF. For hardware/IoT: a schematic showing microcontroller pinouts (GPIO 14), sensor models, and exact operating ratings (5V DC, 2A). |
| Slide 10: Results and testing | Full-screen browser screenshot of the Login and Sign-up UI where the text is 8pt and unreadable. | Cropped high-resolution output window paired with a 3-row verification table: Metric (Precision / API Response Time), Baseline System (78% / 1.4s), Proposed System (91.4% / 320ms). |
Before you walk into the exam hall, practice drawing your Slide 5 block diagram and Slide 6 ER schema freehand on paper. As Project Lab Hub and Engineers Planet point out, external examiners routinely hand students a marker and ask them to sketch the data flow or database relationships live on the whiteboard to verify authorship.
How do you present code or a live demo without wasting time?
Never live-code from a blank IDE or rely solely on a live localhost build during your 10-minute slot. Presentation guides from Slides.com, PPTMaker, and Edutech Projects recommend showing one syntax-highlighted code snippet with line-range highlights on Slide 8, followed by a 60-second pre-recorded video of the working prototype on Slide 9.
Live demos fail in Indian college labs for mundane reasons: college Wi-Fi blocks your database port, the HDMI projector changes your screen resolution, or a free-tier cloud API times out during cold start. Follow this 4-step protocol to show your build without losing a single minute:
- Replace raw IDE screenshots with native syntax-highlighted blocks. Screenshots of VS Code blur when projected on a large hall screen. Use a tool like Slides.com, which offers native syntax-highlighted code blocks and line-range selections so you can dim boilerplate lines and highlight only the 6 lines of your core logic (such as your bcrypt hashing middleware or custom loss function).
- Embed an interactive sandbox only if you have tested the room's internet. Web-based presentation tools like Gamma let you embed live CodePen or Replit iframes directly inside a slide. Use this only if your project is a pure frontend or algorithm visualizer and you are running on a mobile hotspot you control.
- Automate typing if your panel insists on seeing terminal execution. As Medium and Copypaster explain, typing live on stage leads to typos and dead air. If you must demonstrate a CLI tool or script live, use an automated code-pasting tool like Copypaster set to a controlled 120 WPM so the code appears smoothly while you explain what it does on the mic.
- Keep a 60-second offline
.mp4backup video embedded on Slide 9 and saved on a USB drive. Record a clean run of your software or hardware circuit the night before at 1080p, cropping out your browser tabs and taskbar. During the presentation, play the 60-second video and narrate over it while keeping your local server running in the background. If the examiner says, "Show me the actual code running," you Alt-Tab to your open IDE during the Q&A time, not during your 10-minute presentation clock.
How should team members divide speaking parts in a group viva?
Divide group speaking parts by logical project modules and individual technical contributions rather than splitting by odd and even slide numbers, a practice confirmed by Flyppt, Benjamin Ball Associates, and Engineers Planet. Each speaker must close their section with a scripted verbal handoff that names the next teammate and their module.
Under Visvesvaraya Technological University (VTU) guidelines cited by Thesisroom, undergraduate final year project groups can have a maximum of four members (most other Indian universities follow the same 3-to-4 member cap). What most teams get wrong is letting each student design their own 3 slides on their own laptop and merging them 20 minutes before the review. The result is four different fonts, conflicting architectures, and awkward silences when changing the clicker.
To prevent formatting clashes, Flyppt recommends splitting the prep work by functional roles days before the deadline: one student handles research and IEEE citations, one writes the 12-slide outline, one builds the visual deck in a single master template, and everyone rehearses their speaking module and Q&A defense.
During the actual 10-minute presentation for students/freshers in a 4-person group, assign speaking blocks by engineering module using the Engineers Planet role breakdown:
| Team member | Assigned slides | Time on mic | Exact speaking responsibility and outgoing handoff script |
|---|---|---|---|
| Member 1 | Slides 1, 2, 3 | 2 minutes | Introduces the problem statement, existing bottlenecks, and project objectives. Handoff: "That covers our target metrics. I will now hand over to [Member 2] to walk you through our system architecture and database schema." |
| Member 2 | Slides 4, 5, 6 | 3 minutes | Contrasts the existing vs proposed system and explains the system architecture diagram and ER/circuit schema. Handoff: "With the data pipeline and 3NF schema in place, [Member 3] will now explain our tech stack and core module implementation." |
| Member 3 | Slides 7, 8, 9 | 3 minutes | Justifies the technology stack, walks through the core algorithm snippet, and narrates the 60-second demo video. Handoff: "You have seen the working pipeline. [Member 4] will now cover our verification test cases, latency benchmarks, and future scope." |
| Member 4 | Slides 10, 11, 12 | 2 minutes | Presents the accuracy/performance tables, admits honest system limitations, states future upgrades, and opens the floor for the viva. |
If you freeze up when speaking in front of a panel or struggle with transitions, the Group Discussion and Speaking Masterclass gives you a repeatable structure and live speaking practice before your review day.
What are the most common questions external examiners ask after the PPT?
According to viva preparation guides from Skillbolt, Thesisroom, and Medium, the three most common external examiner questions are: "Explain your project in one minute," "Why did you choose this technology stack over alternatives?", and "What was your exact individual contribution?"
As Thesisroom notes, under Anna University Academic Regulations 2025 for BE and BTech programs, evaluation splits marks into three internal reviews (60%), the project report (20%), and the final viva-voce (20%), while other universities weight the final viva and demo up to 50% (check your university's current examination ordinance for your batch's exact split). Whatever your university's exact split, the 5-minute Q&A is where individual grades diverge inside the same group.
Prepare crisp, technical answers for these five high-frequency examiner checkpoints:
- "Keep the slides aside and explain your project in one minute." Project Lab Hub advises every student to memorize a 60-second elevator pitch covering four points: problem, solution, method, and result. Copyable answer template: "Manual inspection of [X] takes [Y minutes] and has a [Z%] error rate. We built an automated [web application / IoT node] that takes [input type], processes it through [algorithm or hardware module], and outputs [result]. In testing across [N samples], our system reduced processing time to [X seconds] at [Y%] accuracy."
- "Why did you choose React/Python/MongoDB instead of [Alternative]?" According to PPTMaker and Edutech Projects, examiners ask this to spot students who bought a ready-made project. Never answer "Because we knew Python" or "Because it is popular." Tie your answer to a project constraint on Slide 7: "We chose FastAPI over Django because our project only exposes three inference endpoints and needed asynchronous request handling without the overhead of Django's built-in ORM and admin panel."
- "What was your exact individual contribution to this group project?"
Both Project Lab Hub and Engineers Planet emphasize that examiners probe individual contributions to catch free-riders. Name the specific files, database tables, or hardware modules you wrote: "I designed the PostgreSQL schema in 3NF, wrote the JWT authentication middleware in
auth.js, and ran the unit tests for the payment webhook." - "Explain your database normalization and why you picked SQL over NoSQL (or vice versa)." Guides from Dhiman Rishav and Engineers Planet flag database architecture as a guaranteed viva topic. Be ready to point to your primary keys and foreign keys on Slide 6, explain how your tables satisfy Third Normal Form (3NF) by removing transitive dependencies, and justify SQL (ACID transactions, structured relational joins) vs NoSQL (unstructured sensor JSON logs, horizontal write scaling).
- "How are you handling user authentication and password security?"
As Dhiman Rishav notes, if your project has a login screen, an examiner will ask how passwords are stored. If you say plain text, you lose marks immediately. Explain how you salt and hash passwords using
bcrypt, how you sign and verify JSON Web Tokens (JWT), and which authorization middleware protects your private API routes.
Your 48-hour checklist before the final viva
Do not spend the night before your review nudging text boxes in PowerPoint. Follow this schedule over the next 48 hours to lock in your presentation:
- 48 hours before (Deck lock): Build your 12 slides using one master template with 30pt body text. Replace any logo-only architecture slide with a labelled component diagram showing protocols and arrows, and add IEEE-formatted citations on Slide 12.
- 24 hours before (Demo lock): Record a 60-second 1080p video of your working software or hardware build. Embed it on Slide 9 and copy the
.mp4file, your PPTX, and a PDF export of your slides onto two separate USB drives. - 12 hours before (Timed rehearsal): Run two full rehearsals with all four teammates standing up, using a phone stopwatch. Cut any slide script that pushes your total word count past 1,300 words or your timer past 9 minutes 30 seconds, and practice your outgoing handoff lines out loud.
Build a clean 12-slide project deck in one evening
If your project code is ready but your slides look cluttered and mismatched, join the Canva AI Masterclass. You will learn how to use Magic Design and Magic Write to turn rough project notes and system diagrams into a uniform, 30pt presentation deck that passes panel scrutiny.
Frequently asked questions
How many words should be in a script for a 10-minute technical presentation?
A 10-minute presentation script should contain 1,000 to 1,500 words in total across your entire group, based on an average speaking pace of 100 to 150 words per minute reported by Wonderslide. For a 4-member engineering team, that equals roughly 250 to 350 spoken words per student.
What font size should I use for a final year project PPT?
Use a minimum of 30-point font for all body text and bullet points, as recommended by Storyfiner, so evaluators at the back of the room can read your slides easily. Pair this with PPTMaker's 6x6 rule: no more than 6 bullets per slide and 6 words per bullet.
What if my live software or hardware demo fails during the viva?
Switch immediately to the 60-second pre-recorded backup video embedded on Slide 9 and saved on your USB drive. Presentation guides from PPTMaker and Edutech Projects advise carrying an offline screen recording or hardware run video so college Wi-Fi drops or compilation timeouts do not tank your evaluation marks.
How do CSE/IT project slides differ from ECE/Electrical project slides?
CSE and IT decks should use Slide 5 and Slide 6 for three-tier or MVC architecture, API routes, and 3NF database ER schemas. ECE, Electrical, and IoT decks should replace the database slide with a circuit schematic detailing microcontroller pinouts, sensor interfaces, and exact voltage and current ratings.
What format should references be in on the last slide of an engineering PPT?
List 4 to 6 core research papers in strict IEEE citation format on your final slide, as required by Indian engineering guidelines noted by College Project Expert. Number each source in square brackets ([1]) showing author initials, paper title, journal or conference name, volume, pages, and publication year.
How are marks divided between internal reviews and the final project viva?
Mark distribution varies by university between 20% and 50% for the final exam. CodeAJ notes that final vivas and demos carry 30% to 50% of total marks across VTU, JNTU, AKTU, and Mumbai University, while Thesisroom cites a 60% internal review, 20% report, and 20% viva split at Anna University.
Newsletter
Stay updated with our latest news and insights.
