To present a research paper at a conference, you turn the paper into a short spoken argument: one problem, one gap, your method in a single picture, two or three results, and what they mean, delivered inside the time the session chair gives you, usually 10 to 15 minutes including questions. The paper holds every detail; the talk only has to make the right people want to read it.
This guide gives a slide-by-slide structure for a 10–15 minute talk, timing rules, how to make figures readable from the back of the hall, what to leave out of the paper, how to rehearse, what changes online or in a hybrid session, and how to handle questions, including awkward ones. Whether a conference paper counts for your PhD is a separate question, answered in our guide to conference and journal papers. Last reviewed September 2026.
How long is a conference paper presentation, and how many slides do you need?
It depends on the conference, and the presenter instructions will tell you. Published IEEE guidelines show the range: the 2014 IEEE Nuclear Science Symposium allotted 15 minutes, with about 12 to present and 3 for questions; IEEE MMSP 2021 and IEEE IST 2025 used 10 minutes of talk and 5 of questions; the 2026 IEEE EIC and IPMHVC conference gives contributed papers 15 minutes plus 5 for questions, and states that session chairs will strictly enforce these times.
- Plan for the talk time, not the slot. A “15-minute slot” often means 12 minutes of talk and 3 of questions, or 10 and 5. Read the presenter instructions, and if they are silent, ask the organisers.
- Budget about one slide per minute, fewer if a slide carries a complex figure. Twelve slides for twelve minutes is a sensible ceiling.
- Put the time on your slide notes: where you should be at 4, 8 and 10 minutes. If you are behind at 8, skip to the comparison slide.
- Build a skip slide. Know in advance which result you will drop if the session is running late and the chair asks you to finish in 8 minutes.
- Finish early rather than late. The last minute of a talk that runs over is the minute the chair uses to stop you, and it takes away the questions, which are the main reason to present.
What this looks like at an Indian conference
Many conferences held in Indian engineering colleges and universities publish through IEEE (as technically co-sponsored events) or in a Springer proceedings series. Sessions often run in parallel tracks with many papers each, and the chair has to finish on time for the next session. Many chairs signal with a bell or a raised card a couple of minutes before your time ends, and most will stop you if you run over. Meet the session chair in the break before your session, hand over your file, and check that it opens on the hall computer.
Presenting is usually not optional. The IEEE Sensor Array and Multichannel Signal Processing workshop (SAM 2026), for example, states that an accepted paper not presented by an author or qualified proxy will not be distributed as part of the proceedings. Read your conference’s no-show policy before you register, because a paper that is not presented may be left out of the published proceedings.
What should each slide contain in a 10–15 minute talk?
The structure below suits most empirical and engineering papers. A theory paper replaces the results slides with the main result and a sketch of why it holds; a qualitative study replaces them with two or three themes and one quotation each.
| Slide | What goes on it | Time in a 12-minute talk |
|---|---|---|
| 1. Title | Paper title, authors, affiliations, conference name. Say who you are and move on. | 20 seconds |
| 2. The problem | One picture or example of the problem, and one sentence on why it matters. | 1 minute |
| 3. What is already known | Three to five closest studies and what each leaves open, ideally as a small table. | 1–1.5 minutes |
| 4. The gap and your objective | The gap in one sentence and what this paper sets out to do. | 1 minute |
| 5–6. Method | A block diagram, flowchart or design summary; dataset or sample; key settings. | 2–2.5 minutes |
| 7–9. Results | The two or three results that support your claim, one per slide, each with a one-line takeaway as the slide title. | 4 minutes |
| 10. Comparison | Your result beside the closest published results, same metric, same data where possible. | 1 minute |
| 11. Conclusion and limits | Three lines: what you found, what it does not show, what comes next. | 1 minute |
| 12. Thank you | Your email and, if you have one, a QR code to the paper. Leave it on screen during questions. | 10 seconds |
Two habits make this structure work. First, write each slide title as a sentence that states the point (“Our method cuts training time by 40% at the same accuracy”) instead of a label (“Results”). Someone who reads only the titles should follow the argument. Second, keep the background short. The audience in a specialist session already knows the field; they need to know the gap, not its history.
A pre-submission or thesis-level talk to your committee is a different job, longer and organised by objective. That structure is in our guide to the pre-submission seminar.
What should you cut from the paper when you make the slides?
More than feels comfortable. A paper of eight pages holds far more than twelve minutes of speech can carry. Cut in this order:
- The literature review. Keep the three to five studies closest to yours. Drop the rest.
- Equations and derivations. Show the one equation that defines your method, if any, and explain it in words. Point to the paper for the rest.
- Secondary results. Every table in the paper does not need a slide. Keep the results that support the main claim, and one that shows where the method does less well.
- Implementation detail. Hyperparameters, software versions and full sample characteristics belong in a backup slide after the thank-you slide, ready if someone asks.
- Full sentences. If a slide can be read aloud as a paragraph, it has too much text. Keep phrases on the slide and the sentences in your mouth.
What you should never cut is the limitation. One honest line about what the result does not show earns more trust from a specialist audience than any amount of confident claiming.
How do you make figures and tables readable from the back row?
Assume the person you most want to reach is sitting in the last row of a hall with a weak projector. Conference guidelines give the numbers: IEEE IST 2025 asks for 36-point titles and at least 18-point main text, with no more than three colours per visual, and the 2014 IEEE NSS guidelines recommended 18 to 20 point fonts.
- Redraw figures for the slide. A figure copied from the paper was designed for a printed column. Enlarge axis labels, thicken lines, and remove gridlines and legends you can replace with direct labels.
- Turn tables into one message. Show only the rows and columns that matter and highlight your result in bold or colour. A 12-row results table on a slide is unreadable from the fifth row of chairs.
- Use colour that survives projection and colour blindness. Pale yellow and light green often vanish on projectors. Red and green together are hard for many viewers; use blue and orange instead.
- Dark text on a light background is safest in a lit room. Test the file on a projector if you can.
- Number your slides. Questioners can then say “slide 8” instead of “the graph with the blue line”.
The same rules, pushed further, apply to posters; our guide to making an academic poster covers them.
How should you rehearse, and what changes online or in a hybrid session?
Rehearsal
Run the talk aloud against a clock three times or more: first on your own to find the length, once recorded so you can watch yourself, and once in front of your lab group with instructions to interrupt and ask hard questions. The first run is nearly always too long. Cut slides, not speaking speed.
Learn the first minute nearly by heart, because nerves are worst at the start. Don’t memorise the rest; know the point of each slide and say it in your own words. If English is your second language, practise the technical terms you find hard to pronounce, and slow down. Audiences at Indian conferences come from many states and countries, and clear speech matters more than speed.
Online and hybrid presentations
- Know who controls the slides. At IEEE MMSP 2021, remote presenters shared their own screen and controlled their own slides; other conferences ask for a pre-recorded video. Read the instructions early.
- Test the setup the day before: camera at eye level, a wired connection if possible, a headset microphone, and your laptop plugged in.
- Keep a backup. Email the PDF of your slides to the session chair or host, so someone can share it if your connection fails.
- Watch the chat. In hybrid sessions, the chair often reads out questions from online attendees. Pause after each one so the room can hear it.
How do you handle questions, including hostile or off-topic ones?
Questions are the most useful part of presenting, because they tell you what a reviewer or examiner will ask later. Leave the thank-you slide on screen, then:
- Repeat or rephrase the question briefly. It gives you a few seconds to think and lets the room hear it, which matters in large halls and hybrid sessions.
- Answer in two or three sentences. If the answer is in a backup slide, show it. Long answers take time from other questioners and from the next speaker.
- Say “I don’t know” when you don’t. “I haven’t tested that. It’s a good idea for the next step; may I take your email?” is a strong answer.
Hostile questions
Some questioners challenge the whole premise, or suggest your method is wrong. Stay calm and treat it as a technical point. Separate what you agree with (“You’re right that the sample is small”) from what you don’t, and give the evidence for your position in one or two sentences. If the disagreement is going nowhere, offer to continue after the session. The audience judges how you answer more than who wins.
Off-topic and long questions
If a question is about something your paper does not address, say so politely and give a short answer if you can: “That is outside this study, but briefly…”. If someone makes a long statement rather than asking a question, thank them, respond to the one point you can, and look to the chair. Moving the session on is the chair’s job, and a good chair will do it.
After the session, write down every question you were asked. If you later extend the paper for a journal, those questions are the first draft of the reviewer comments.
Want a specialist to help with this in your own work? Research Paper Writing Support: a free first consultation, then a written scope and fixed quote.
Sources
- IEEE NSS-MIC 2014, Oral presentation guidelines (15 minutes, about 12 to present and 3 for questions)
- IEEE EIC and IPMHVC 2026, Presentation guidelines (session chairs enforce times)
- IEEE IST 2025, Presentation information (10 + 5 minutes, slide type sizes)
- IEEE MMSP 2021, Instructions for presenting authors (hybrid sessions)
- IEEE SAM 2026, Non-presented paper (no-show) policy (PDF)
- The Writing Center, University of North Carolina at Chapel Hill: Conference papers
- The Writing Center, George Mason University: Conference presentations
FAQ
Questions scholars ask
Should I read my paper aloud from a script?
In most science and engineering sessions, no. Speak from the slides and your notes. Some humanities conferences still expect papers to be read; if so, a double-spaced page takes roughly two to two and a half minutes to read aloud, so a 15-minute slot fits about six or seven pages.
Can someone else present my paper if I can’t travel?
Many conferences allow a co-author or an approved proxy, and some allow online presentation. Ask the organisers in writing well before the event, because a paper that is not presented may be left out of the proceedings.
What if I run out of time before the conclusion?
Jump straight to the conclusion slide and say the three lines. A talk that ends on its main point is better than one cut off during a results slide. Rehearse this jump so it feels natural.
Do I get a certificate for presenting?
Most Indian conferences issue a presentation certificate, often from the session chair at the end of the session or by email later. Keep it: many universities ask for presentation proof in RAC progress reports or at thesis submission.
How many backup slides should I prepare?
Three to six is typical: extra results, the full parameter table, a derivation, and a slide on the limitation most likely to be questioned. Put them after the thank-you slide so they never appear by accident.
