A live poll in PowerPoint has three dependencies you do not control
The add-in worked on your laptop all week. Then the venue hands you their presentation machine, the one with a perpetual Office licence and nobody signed in, and the poll slide renders as a grey box with a warning. We have stood next to that grey box. A live poll in PowerPoint depends on three things the presenter rarely controls: the licence on the machine, the build of PowerPoint on it, and the account that owns the deck. We built RiLiFi to live-host polls in a separate browser tab instead, and the table below is the honest version of that trade-off.
| Poll add-in inside the deck | Separate live host tab | |
|---|---|---|
| Licence | Microsoft Forms polls: Office 365 Education or Microsoft 365 Apps for business, PowerPoint 1807 or later, on a PC. Third-party add-ins: Office 2016 or later with the Edge webview on Windows, PowerPoint 15.24 or later on Mac | Any current browser, no install, no Office licence |
| Who owns the poll | The signed-in deck owner | A shared folder; any collaborator with access can host |
| Deck exported to PDF, Keynote or Google Slides | The poll object does not travel | Unaffected; the deck is just slides |
| Venue machine without the add-in | Grey box, or a sign-in prompt mid-talk | Open a tab, sign in, start |
| Attendee join | Phone browser via link or QR, depending on the add-in | Phone browser via PIN or QR, no app |
| Results afterwards | Inside the add-in vendor's account | Session History, with every vote saved and a download for stakeholders |
| Cost model | Included with a qualifying Microsoft 365 licence, or per vendor | Free tier of 100 participants per session; monthly billing above it |
Both columns are real workflows. We are not going to pretend the add-in never works. We are going to show you the three moments it stops working, because we have watched each one happen on a stage.
What breaks when the poll lives inside the deck
The licence check happens at the worst moment
The documentation is precise about who qualifies. Microsoft says inserting a form "is only available to Office 365 Education and Microsoft 365 Apps for business customers with version 1807 (Build 16.0.10711.20012) or later of PowerPoint for Microsoft 365 on a PC". You must also be signed in with a school or work account (Insert a form or quiz into PowerPoint). Read that as a checklist for the venue laptop. Business licence. Recent build. PC. Signed in. Miss any one and the poll is not there.
Third-party add-ins carry their own floor. Microsoft's platform requirements list Office 2016 or later on Windows, with the Microsoft Edge webview installed, and specific minimum versions on Mac (Requirements for running Office Add-ins). None of that is unreasonable. It is a dependency that lives on a machine you may meet for the first time at 8:40 in the morning.
The deck changes format and the poll does not survive
Decks travel. The keynote speaker sends a PDF to the organiser. The organiser rebuilds it in Keynote because the stage runs on a Mac. The regional team drops it into Google Slides for their own session. An embedded poll is a web object sitting inside a slide. Every one of those conversions keeps the slide and drops the object. The presenter finds out when the slide with the big question has no question on it.
A separate host tab does not care what the deck is made of. The deck keeps one static slide with the PIN and the QR code. That slide survives PDF, Keynote, Google Slides, and a photo of the screen.
The poll belongs to one laptop
An add-in signs in as one person. The poll, the results, and the ability to run it again all live in that account. When that person is sick on the morning of the all-hands, the backup presenter has a deck full of slides that say "poll goes here" and nothing else. We wrote about what happens when the host drops. The fix is structural: the poll has to live somewhere the team can reach. In RiLiFi it lives in a shared folder, next to the quiz and the wheel, shared by email with whoever might have to stand up and run it.
The separate-tab workflow, step by step
The objection we hear is always the same. Switching windows breaks the flow. Fair. So here is the exact routine that removes the fumbling.
- Bookmark the deck in the same folder as the poll. Our folders hold labelled links, so the run-of-show, the deck, and the poll sit together. We covered the habit in put the speaker deck next to the poll.
- Open the host tab before doors open. Sign in, open the poll, leave it on the waiting view. One tab, already loaded, already tested on the venue's network.
- Keep a static join slide in the deck. PIN, QR code, one line of instructions. It is the slide you show while people pull out their phones.
- Switch once, at the cue. Alt-tab or Cmd-tab to the host tab, start the poll, watch the bar chart fill, close it with the timer or the manual stop, then switch back. The American Psychological Association summarises the research on task switching. Switch costs are "relatively small, sometimes just a few tenths of a second per switch," and they add up only when people bounce back and forth repeatedly (Multitasking: Switching costs). One deliberate switch per poll is not the problem. Hunting for the window is. Rehearse the switch twice and it disappears.
- Leave the results where the next person can find them. Every vote is saved in Session History. The deck owner's account is not the only key.
Why we refuse to build an add-in
We live-host only. Quizzes, polls, and wheels are not embedded in third-party slide decks, and that is a decision, not a gap in the roadmap. Every dependency in the first column of the table above is a dependency we would be importing into your event. We would rather own the whole join flow, the waiting room, the live bar chart, and the archive in one place we can test. Shipping a web object that behaves differently on each machine it lands on is the alternative, and we do not want it.
There is a case where the add-in is the right call, and we will say it plainly. If your entire organisation runs the same Microsoft 365 for business licence, every presenter uses their own managed laptop, and the deck never leaves PowerPoint, the native route fits. Microsoft Forms inside the deck is convenient there, and it is included. We built for the other rooms: the conference with a venue machine, the hybrid all-hands with a backup presenter, the training deck that gets forwarded as a PDF.
Questions we get about live polls in PowerPoint
Can you add a live poll to PowerPoint for free?
Microsoft Forms is included with qualifying business and education licences, so for those customers the native route costs nothing extra. For everyone else, the separate-tab route is free up to 100 participants per session on our plan, with no Office licence involved.
Do attendees need to download an app?
No. For a RiLiFi poll, attendees open the join page in their phone browser, enter the PIN, and tap to vote. There is nothing to install on either side of the room.
Does the separate host tab work in a virtual meeting?
Yes, and it is simpler than on a stage. Share the host tab as your screen for the poll, or keep the deck shared and read the results from a second monitor. Remote attendees vote from the same phone browser as anyone in the room.
Keep the slide. Move the poll.
A live poll in PowerPoint trades portability for convenience. If the deck will only ever open on one managed laptop, take the convenience. If it will be exported, forwarded, rebuilt, or handed to a backup presenter, keep a static join slide in the deck and run the poll from the live poll host view. The pricing page lists the free tier and the monthly plans, and neither one asks what version of PowerPoint the venue runs.