English for Vivas, Project Defences and Class Presentations

Explaining a technical project in English while answering unpredictable questions is one of the hardest speaking tasks a student faces. Here is a structure, the phrases, and a one-week plan.

Why this is harder than a normal English test

A final-year project defence, a thesis viva or a class presentation asks you to do three difficult things at the same time: explain something technical, speak in front of an audience, and answer unpredictable questions from people who are also assessing you. If you have spent years reading and writing English for coursework but rarely speaking it, the gap between what you understand and what you can say under pressure is at its widest here.

This guide gives you a structure, ready-made phrases for each part, a way to handle questions (including the ones you cannot answer), and a list of common slips. It is written for university students in Pakistan, but the structure works for any project presentation in English.

A five-to-eight minute structure

Part	Job	Typical tense
1. Opening	Greet, name the project, say what you will cover	Present / future
2. Problem	Why does this matter? Who is affected?	Present simple
3. Approach	What did you build or do, and why that way?	Past simple, often passive
4. Results	What happened? What is the evidence?	Past simple
5. Limitations and future work	What does it not do? What next?	Present, "could / would / plan to"
6. Conclusion	One sentence to remember, then invite questions	Present perfect / present

Phrases you can use for each part

Opening

"Good morning, everyone. My name is ..., and today I'll be presenting our final year project, which is called ..."
"I'll start with the problem we wanted to solve, then explain our approach, show the results, and finish with limitations and next steps."

Problem

"The problem we focused on is ..."
"At the moment, most students / companies / hospitals have to ..., which means ..."
"This matters because ..."

Approach

"We chose ... because ..., compared to ..., which would have needed ..."
"First, we collected data from ... Then we cleaned it by ... Finally, we trained / built / tested ..."
"The system is made up of three main parts."

Results

"As you can see in this graph, ..."
"Our model reached an accuracy of 91%, compared with 84% for the baseline."
"The results suggest that ..." (safer than "prove")

Limitations and future work

"One limitation is that ..."
"Because of time constraints, we were only able to ..."
"In future work, we would like to ..."

Conclusion

"To sum up, we built ..., and it showed that ..."
"Thank you for listening. I'm happy to take any questions."

A sample 60-second opening (adapt it to your project)

"Good morning, everyone. I'm Ayesha, and this is my teammate Bilal. Today we'll present StudyMatch, a mobile app that helps university students find study groups for their courses.

The problem is simple: in large classes, students who want to study together often don't know each other, so they study alone. Our app matches students by course, schedule and preferred study style.

I'll start with the problem, then explain how we designed the matching system, show our test results with 40 students, and finish with limitations and future work. After that, we'd be glad to answer your questions."

Notice how short the sentences are. Long, complicated sentences are harder to deliver under pressure and harder for the audience to follow.

Handling questions: the part that scares most people

The questions are unpredictable, but the types of question are not. Prepare short answers for these:

Question type	Example	Answer structure
Why this approach?	"Why did you choose this method?"	Choice → reason → alternative you considered
Evidence	"How do you know it works?"	How you tested → what you found → what it means
Limitations	"What are the weaknesses?"	Name one honestly → say what you'd do about it
Novelty	"What is new about this?"	What exists → what is different in yours
Hindsight	"What would you do differently?"	One thing → why → how

Buying time to think

"That's a good question. Let me think about that for a moment."
"Let me make sure I understand: are you asking about ... or about ...?"
"I'd like to answer that in two parts."

When you did not understand the question

"Sorry, could you repeat the question, please?"
"Could you rephrase that? I want to be sure I answer it properly."

When you do not know the answer

Bluffing is usually easy to spot, and a short, honest answer tends to go over better. A good structure is honest + related knowledge + next step:

"I'm not sure about that, I didn't test it directly. What I can say is that in our data ..., so I would expect ..., but we'd need to verify it."
"We didn't cover that in this project, but it's a good direction for future work. To do it, we would ..."

When you disagree with a comment

"That's a fair point. In our case, though, we chose ... because ..."
"I see what you mean. The reason we didn't do that is ..."

Avoid "No, you are wrong" or "You didn't understand". Acknowledging first keeps the discussion calm even when you are right.

Common slips in presentations

Wrong"Now I will tell you about the methodology of this project, sir."

Correct"Now I'll explain our method." / "Next, our approach."

WhyShorter and more direct. "Sir" once at the start is enough.

Wrong"We discussed about the results and did the comparison between two algorithm."

Correct"We discussed the results and compared two algorithms."

Why"Discuss" takes no preposition, "do a comparison" becomes the verb "compare", and "two" needs a plural. See our prepositions guide.

Wrong"We have collected the data last month, and then we are training the model."

Correct"We collected the data last month, and then we trained the model."

WhyCompleted steps in a method use the past simple. Present perfect ("have collected") does not go with "last month".

Wrong"Our result is proving that this method is the best."

Correct"Our results suggest that this method performs better."

Why"Prove" is a very strong word that an examiner may challenge; "suggest", "show" and "indicate" are safer. "Performs better" is also more precise than "is the best", and results are normally reported in the simple present ("The results show...").

Fillers: "basically", "actually", "like", "so"

Everybody uses fillers, and a few are harmless. The problem starts when every sentence begins with "So basically..." or when "like" and "actually" appear several times per sentence, which makes you sound unprepared even when you are not. Replace them with a short pause. Silence feels very long to the speaker and almost unnoticeable to the audience.

How to prepare in one week

Days 1-2: write out your first two sentences and your last two sentences word for word, and memorize them. Starting and finishing smoothly removes much of the fear.
Days 3-4: for each slide, write one sentence stating its message. Practice saying only that sentence, without reading the slide.
Day 5: list the ten most likely questions (use the table above) and prepare a 20-second answer to each. Say them aloud, not in your head.
Day 6: run the whole presentation aloud with a timer, then again while recording yourself. Listen for fillers and long sentences.
Day 7: present to a friend, and ask them to interrupt with two difficult questions. Rest before the real day.

Two tips on delivery: keep slides to one message each, with as little text as possible (so you speak rather than read), and speak a little more slowly than feels natural. Under stress, everyone speeds up.

FAQ

Should I memorize the whole presentation?

No. A memorized script sounds flat and falls apart the moment you lose your place. Memorize the opening and closing, and know the message of each slide, so you can say it in different words if you have to.

What if the examiners and I all speak Urdu? Can I switch languages?

That depends on your department and on the assessment rules, so check with your supervisor beforehand. If the presentation is assessed in English, stay in English, and if you cannot find a word, use a short pause or "what I mean is..." and explain it in other words.

How do I stop shaking or speaking too fast?

Breathe out slowly before you begin, plant both feet, and start with your memorized first sentence. Then aim for one slow breath at the end of each slide. Nervousness is normal; a steady first minute usually settles it.

You can rehearse this in Speak & Fix: tell it you are presenting your project, ask it to play an examiner, and practice answering unexpected questions out loud. Corrections are saved as flashcards for review. Start a practice conversation.