Below: how many times an M.Tech dissertation is presented and what two universities’ regulations say about it, a slide-by-slide plan with suggested minutes for each of the four talks, a table comparing them, design rules, the questions panels ask at each stage and the mistakes to avoid. The free PowerPoint template at the top of this page has 22 widescreen slides for Stage-I and Stage-II, each with what to put on it and the panel’s question.
- One master deck, four talks. Build the Stage-I slides once; each later review recaps them in a slide or two and adds new evidence.
- Plan about one slide a minute and leave time for questions. The time slot is your department’s decision, not yours.
- Stage-I is about the plan: problem, gap, base paper, objectives, method and timeline. Results are not expected yet.
- Stage-II and the viva are about evidence: your results next to the base paper’s, on the same data and the same metric.
- Number every slide and keep backup slides, so you can answer a detailed question by jumping straight to the evidence.
How many times is an M.Tech dissertation presented?
Most M.Tech and M.E. programmes spread the dissertation over the last two semesters and review it more than once. The names change from one university to the next (Stage-I and Stage-II, Phase-I and Phase-II, Dissertation Review I, II and III), but the talks usually come in this order:
- Stage-I review (Phase-I): the problem, the literature gap, the base paper, your objectives, the method and the plan. Some departments hold a short topic-approval talk before it.
- Mid-term or progress review: what you have built since Stage-I, the reproduced baseline and what is left.
- Stage-II review (Phase-II): the finished work and its results. In some universities this review decides whether you may submit the thesis.
- Final viva voce: the whole dissertation defended before an external examiner, after the thesis has been evaluated.
Some departments merge two of these talks or add another. Rules and durations vary by university and department, so take the number of reviews, the time slot and the marks from your own regulations and your coordinator’s circular. Here is how two universities’ published regulations set the reviews out:
| Item | JNTUH (R22) | VTU (2022 scheme) |
|---|---|---|
| What the stages are called | Dissertation Work Review I, II and III, then the Dissertation Viva-Voce | Project Phase-I and Project Phase-II, then the viva-voce |
| First talk | Review I: you present the title, objective and plan of action to the Dissertation Review Committee for approval, within four weeks of the start of the II year I semester (7.10) | Not described in the regulations; ask your department |
| Who reviews | The Dissertation Review Committee: the Head of the Department as chair, your supervisor and one senior faculty member (7.8) | Phase-I is marked internally (CIE); the regulations do not name the panel |
| End of Stage-I | Review II, 100 internal marks (50 from the committee, 50 from the supervisor), on the problem definition, objectives, scope of work, literature survey in the same domain and progress (7.14) | Project Phase-I carries 100 internal (CIE) marks (22OMT8.1) |
| Gap between reviews | Progress reported in two stages, at least three months apart (7.12) | Not stated |
| Stage-II | Review III, 100 internal marks: you hand in a draft thesis and make an oral presentation, and the committee decides whether the thesis may be submitted (7.13, 7.15) | Project Phase-II carries 100 internal (CIE) and 100 semester-end (SEE) marks (22OMT8.1) |
| Before submission | Similarity index under 30%, and a research paper from the dissertation submitted to a UGC-approved journal, with a copy attached to the thesis (7.17, 7.18) | Plagiarism index of 25% or less (22OMT5.3) |
| Final viva | A board of your supervisor, the Head of the Department and the external examiner who evaluated the thesis; 100 external marks, 50% to pass (7.15, 7.21) | Held by the external examiner and the internal examiner or guide (22OMT5.10), once the external examiner accepts the dissertation (22OMT5.8) |
Sources, checked November 2026, clause numbers in brackets: JNTUH’s Academic Regulations of M.Tech (Regular/Full Time) Programmes, 2022-23 (R22), for its non-autonomous constituent colleges and its affiliated colleges; VTU’s Regulations Governing M.Tech. Programs, 2022 scheme (version 2). Autonomous colleges may issue their own regulations, and they override these.
Neither set of regulations fixes a presentation length or a slide count. The plans below assume 15 minutes for Stage-I, 10 for the progress review, 20 for Stage-II and about 18 for the viva; if your slot is shorter or longer, scale the minutes in proportion and keep the order.
What slides go in an M.Tech Stage-I presentation?
Stage-I has to convince the panel of three things: the problem is real, the gap is visible in published work, and the plan can be finished in the time left. Results are not expected yet; a reproduced baseline, if you have one, is a bonus. This plan fits a 15-minute talk, with questions after it.
| Slide | What to show | Minutes |
|---|---|---|
| 1. Title | Dissertation title, your name and roll number, guide, department, the review and the date | 0.5 |
| 2. Introduction | The domain in two lines and why the problem matters now, with one fact and its source | 1 |
| 3. Problem statement | The problem in one sentence that can be measured, who has it, and what a solution must achieve | 1 |
| 4–5. Literature survey | A table of recent papers: author and year, method, dataset, result, limitation | 2.5 |
| 6. Research gap | What those papers do not do, pointing at the table rows that show it | 1 |
| 7. Base paper | Title, venue, year, DOI, method, dataset, and its reported result with the table number | 1.5 |
| 8. Objectives and scope | Three or four objectives you can check at the end, and what is out of scope | 1 |
| 9. Proposed methodology | Your block diagram, redrawn in your own shapes, with the block you add or change marked | 2 |
| 10. Dataset, tools and evaluation | Dataset and split, tools, metrics, the baseline, and how many runs you will do | 1 |
| 11. Work done so far | Papers read, data obtained, the base paper’s code run or the date you will run it | 1 |
| 12. Plan to Stage-II | A month-by-month chart that ends with testing, the paper and the thesis | 1 |
| 13. References | The base paper first, then the surveyed papers, in IEEE style | 0.5 |
| 14. Thank you | Your name and an invitation to questions | Questions |
Given 10 minutes instead, merge the introduction into the problem slide and show one literature slide. For presenting the base paper itself, see our base paper presentation guide.
Put your effort into slides 6 to 9. The gap, the base paper, the objectives and the method decide whether the topic goes ahead as planned; the literature table only has to show that you read enough to find the gap. Your Stage-I report covers the same ground in writing: see what goes in the Stage-I report. Still choosing a paper? Our guide to choosing a base paper shows how to spot a gap you can test.
What do you show in an M.Tech mid-term or progress review?
The progress review checks that the work is moving and that you acted on the Stage-I comments. Keep the recap to one slide and spend the time on what is new. This plan fits about 10 minutes.
| Slide | What to show | Minutes |
|---|---|---|
| 1. Title | Title, your name, guide, the review and the date | 0.5 |
| 2. Recap | Problem, objectives and base paper, on one slide | 1 |
| 3. Comments from the last review | Each comment, and what you did about it | 1 |
| 4. Plan against progress | The Stage-I chart with finished, late and moved tasks marked | 1 |
| 5. Implementation so far | The block diagram with the built modules marked, and a screenshot or photo | 1.5 |
| 6. Baseline reproduced | The base paper’s number next to yours, on the same dataset and metric, and why they differ | 1.5 |
| 7. First results of your change | Early numbers labelled as preliminary, or the experiment you will run next | 1.5 |
| 8. Problems and fixes | What blocked you, and how you solved it or plan to | 1 |
| 9. Remaining work | Tasks and dates up to Stage-II, including the paper and the thesis | 0.5 |
| 10. Thank you | An invitation to questions | Questions |
If the base paper’s result does not reproduce, say so and show what you tried. A gap explained honestly (a different split, fewer epochs, a detail the paper leaves out) is far safer than a copied number. Our guide to implementing a base paper covers how to reproduce one.
What slides go in the M.Tech Stage-II final review?
Stage-II shows the finished work: what you built, how it compares with the base paper, and whether the objectives you set at Stage-I were met. In some universities this review also decides whether you may submit the thesis; under JNTUH’s R22 regulations, Review III does. This plan fits a 20-minute talk.
| Slide | What to show | Minutes |
|---|---|---|
| 1. Title | Title, your name, guide, department, the review and the date | 0.5 |
| 2. Outline | The sections of the talk | 0.5 |
| 3. Problem and objectives | A recap on one slide | 1 |
| 4. Gap and base paper | The gap in one line, the base paper and its reported result | 1 |
| 5. Proposed method | The final architecture, with your change marked | 2 |
| 6. Key algorithm or module | The new part, step by step or as an equation you can explain | 1.5 |
| 7. Implementation | Tools, hardware, dataset split, training or simulation settings | 1 |
| 8. Experimental setup | Metrics, baselines, number of runs, and how you kept the comparison fair | 1 |
| 9. Main results | One table: the paper’s reported number, your reproduction and your method, on the same metric | 2 |
| 10. Graphs | Curves, a confusion matrix or waveforms, one per slide, with labelled axes | 1.5 |
| 11. Ablation or analysis | Your method with and without the change, or across settings | 1.5 |
| 12. Demo or screenshots | A short video or screenshots of the working system | 1 |
| 13. Discussion and limitations | Where the method fails, or what was not tested | 1 |
| 14. Objectives met | Each Stage-I objective, with the slide or table that shows it was met | 1 |
| 15. Conclusion | What you did, the main number, and what it means for the problem | 1 |
| 16. Future scope | One or two concrete next steps | 0.5 |
| 17. Publications | Your paper’s title, venue and true status: submitted, accepted or published | 0.5 |
| 18. References | In IEEE style, the base paper first | 0.5 |
| 19. Thank you | An invitation to questions | Questions |
| 20. Backup | Extra results, settings and derivations, shown only if asked | If asked |
Every number on the results slides must match the draft thesis, because the panel may have it open. Format the thesis itself with our M.Tech thesis format guide, and if your department expects a paper before submission, see where to publish a research paper.
How do you structure the M.Tech final viva presentation?
The viva comes after the thesis has been evaluated, and the external examiner may be seeing the work presented for the first time. So the talk tells the whole story, from the problem to your contribution, and leaves more room for questions than the internal reviews. This plan fits a 15 to 20 minute talk; ask your department for the actual slot.
| Slide | What to show | Minutes |
|---|---|---|
| 1. Title | The thesis title exactly as on the bound copy, your name, guide and department | 0.5 |
| 2. Outline | A map of the talk that follows the thesis chapters | 0.5 |
| 3. Motivation and problem | Why the problem matters, and the one-sentence problem statement | 1.5 |
| 4. Literature and gap | A short version of the survey table, and the gap | 1.5 |
| 5. Objectives | As approved at Stage-I | 1 |
| 6. Contribution | What is new in your work, in two or three lines, kept apart from what the base paper did | 1 |
| 7. Methodology | The final architecture and the new part | 2 |
| 8. Implementation and setup | Data, tools, settings, and how the comparison was kept fair | 1 |
| 9. Results | The main comparison table | 2 |
| 10. Graphs and analysis | The two or three graphs that support the contribution | 1.5 |
| 11. Comparison with other work | Your result next to the base paper and other recent methods on the same data | 1 |
| 12. Demo | A short recorded video, or a live run on your own laptop | 2 |
| 13. Limitations | Where it fails, and what you did not test | 0.5 |
| 14. Conclusion and future scope | The main result and the next step | 1 |
| 15. Publications | Your paper and its status | 0.5 |
| 16. Thank you | An invitation to questions | Questions |
| 17 onwards. Backup | The slides you expect detailed questions on | If asked |
Prepare the questions as carefully as the slides. Our viva questions guide lists what examiners ask about the problem, the design, your own part and the results.
How do the four dissertation presentations differ?
| Talk | When, usually | Suggested length | Slides | What the panel checks |
|---|---|---|---|---|
| Stage-I review | Third semester | 15 minutes, then questions | 13 to 15 | A real problem, a gap shown in papers, a suitable base paper, objectives that can be checked and a plan that can finish |
| Progress review | Between Stage-I and Stage-II | About 10 minutes, then questions | 8 to 10 | Action on the last comments, a reproduced baseline, progress against the plan |
| Stage-II review | Fourth semester, before submission | About 20 minutes, then questions | 18 to 20 | Results against the base paper on the same data and metric, objectives met, a thesis ready to submit |
| Final viva | After the thesis is evaluated | 15 to 20 minutes, then questions | 15 to 18 | That you did the work and understand it, can defend the contribution and know its limits |
Timing follows the usual two-semester split, as in JNTUH’s R22 regulations (II year I and II semesters). Lengths and slide counts are suggestions: your department’s time limit and format come first.
How should M.Tech dissertation slides be designed?
- Use your department’s template if it has one. The logo, colours and title page come from it; the rules below fit inside any template.
- Font sizes: titles about 28 to 32 pt, body text 18 pt or larger, table text 14 pt or larger. The free template uses 30 pt titles and 20 pt text. If you must shrink text to make it fit, split the slide instead.
- One message per slide. Write the title as the point the slide makes, for example “[Your method] improves recall over the base paper on [dataset]”, rather than “Results”.
- Figures over text. A block diagram, a flowchart or a graph explains faster than bullets. Keep to about five bullets a slide, one line each, and never paste paragraphs from the report.
- Label every axis with the quantity and its unit, add a legend, and make tick labels large enough to read from the back of the room. Give your method the same colour in every graph.
- Number every slide, so the panel can say “go back to slide 9”. The template uses PowerPoint’s automatic slide number, which stays right when you delete slides.
- Show the source of every number and figure that is not yours, as “[3]” or “Base paper, Table 4” on the slide itself.
- Keep a backup slide or two after “Thank you”: extra results, settings, dataset details and derivations. Show them only when asked.
- Dark text on a light background holds up best on a projector in a lit hall, and lines in a graph should differ by more than red against green.
- No decorative animation. Use a build only to reveal a diagram step by step.
Review date fixed and the slides not ready?
Send your topic, your stage and the review date. We prepare the review slides in your department’s format and rehearse the likely questions with you, after a free consultation and a fixed quote. See our report, PPT and viva help.
What questions do panels ask at each review, and how should you answer?
At the Stage-I review
- “What exactly is the problem?” One sentence, with what you will measure. Avoid “to improve the efficiency of the system”.
- “Where is the gap? Show me.” Go to the literature table and point to the rows, or quote the base paper’s future-work line.
- “Why this base paper?” Recent, peer reviewed, its data and code available, and a limitation you can test.
- “What is new here? Is it M.Tech level?” Name the one change you will make beyond reproducing the paper, and how it will be measured.
- “Can you finish this in time?” Point to the plan: the data is in hand, the compute or hardware is available, and testing has its own month.
At the progress review
- “What did you change after the last review?” Go through each comment and its action, slide 3 of the plan above.
- “Have you reproduced the base paper?” Show both numbers and explain any gap. If it is not done, give the date.
- “Why are you behind?” Give the real reason in one line and the revised dates. Do not argue.
- “What is left, and will you finish?” The remaining tasks with dates, ending well before submission.
At the Stage-II review
- “Is the comparison fair?” Same dataset, same split, same metric and the same settings for every method in the table.
- “Is the gain consistent, or one lucky run?” Show the mean over several runs, or say how many runs you did.
- “What does this graph show?” Read the axes first, then give the one takeaway written in the slide title.
- “Which objective does this result meet?” Go to the objectives-met slide.
- “Where does your method fail?” Name the case. Knowing the limits counts in your favour.
At the final viva
- “Summarise your thesis in two minutes.” Problem, gap, what you did, the main number, what it means. Rehearse it.
- “What is your contribution?” Separate clearly what the base paper did from what you added.
- “Explain this block or equation.” Say what goes in, what comes out and why the step is needed.
- “Why did you choose this method, dataset or tool over another?” A reason tied to the problem, not “it is popular”.
- “Show me the code running.” Run it on your own laptop, already set up, with a recorded video as a fallback.
- “What would you do with six more months?” One concrete next step that follows from your limitations slide.
What mistakes weaken an M.Tech dissertation presentation?
- The same deck at every review. Each talk needs new evidence on top of a short recap.
- Slides full of text that you read aloud. The panel reads faster than you speak and stops listening.
- Figures pasted from papers, blurred and without credit. Redraw them, or cite them on the slide.
- Results with no baseline, or the base paper’s numbers shown as if they were yours. Label every number with its source.
- Graphs without axis labels, units or a legend.
- Numbers that differ between the slides and the thesis. One mismatch makes the panel doubt every other number.
- Objectives at Stage-I that the Stage-II results never mention. Close the loop on the objectives-met slide.
- Running over time and rushing the results, the slides that matter most at Stage-II.
- A demo that needs the internet or a laptop you have not tested on.
- No slide numbers, no references and no backup slides.
What is in the free M.Tech dissertation PPT template?
The download at the top of this page is a 16:9 PowerPoint with 22 slides:
- a title slide and an outline;
- Part A, Stage-I: introduction, problem statement, a literature table, research gap, base paper, objectives and scope, methodology, dataset and evaluation plan, and a work plan to Stage-II;
- Part B, progress, Stage-II and viva: review comments, implementation, a results table against the base paper, graphs and analysis, objectives met, conclusion, and publications with references;
- a thank-you slide and a backup slide.
Each slide has what to put on it in grey, to replace, and the question the panel asks at its foot. The speaker notes say which talk uses the slide and roughly for how long. For each review, delete or hide the slides it does not need; the slide numbers update themselves. Your department’s format overrides the template. If you are still choosing a topic, start with our M.Tech project ideas, or see how we build M.Tech projects from the base paper to the thesis.
What should you check the day before a dissertation review?
- The talk fits the slot, timed out loud at least twice.
- Every number on the slides matches the report or thesis.
- Slide numbers, references and sources are on every slide that needs them.
- Each comment from the last review has an answer on a slide.
- The deck opens on the hall’s computer: carry the PPTX and a PDF copy on a pen drive.
- Videos are embedded and also saved separately, and the demo runs without the internet.
- You can explain every block, equation and graph without notes.
Frequently asked questions
How many slides should an M.Tech dissertation PPT have?
About 13 to 15 for a Stage-I review, 8 to 10 for a progress review, 18 to 20 for the Stage-II review and 15 to 18 for the viva, at roughly one slide a minute. Your department’s time slot decides. The free template on this page has 22 slides covering both stages, and our base paper presentation guide covers the earlier base paper review.
What is the difference between the Stage-I and Stage-II presentations?
Stage-I presents the plan: the problem, the literature gap, the base paper, the objectives, the method and the timeline, usually without results. Stage-II presents the evidence: the implementation, your results against the base paper and whether each objective was met. They match the Stage-I and Stage-II reports described in our M.Tech thesis format guide.
What is asked in the M.Tech final viva?
Expect to summarise the work, explain your contribution beyond the base paper, walk through the method and a key block or equation, defend the results and the comparison, and name the limitations. You may also be asked to run the code. Our viva questions guide lists common questions with how to answer them.
Can I use the same PPT for every dissertation review?
Keep one master deck, but do not present it unchanged. Each review should recap the earlier slides in one or two and spend most of its time on what is new: the reproduced baseline at the progress review, the results at Stage-II and the contribution at the viva. A deck that has not moved since the last review tells the panel the work has not moved either.
What font size should dissertation slides use?
Titles of about 28 to 32 pt and body text of 18 pt or more stay readable from the back of a seminar hall, and table text should not drop below about 14 pt. If the text does not fit at those sizes, split the slide. If your department’s template sets sizes, follow it.
Can The Ultimate Project World help with my dissertation presentation?
Yes. Send your topic, your stage and the review date in the free consultation. We prepare the review slides in your department’s format, help you explain your results and rehearse the likely questions, and can help with the thesis and the paper too. See our report, PPT and viva help and M.Tech projects.
