Stop Emailing Quiz Links: How to Co-Host Live Assessments
The quiz is locked to a person who called in sick
Volunteer presenter shared folder access is the Tuesday problem. The primary host has the flu. The live assessment sits under their personal login. Someone emails a “quiz link.” It is the audience join URL, or a PIN screenshot, or a copied Kahoot nobody else can edit. The volunteer at the podium cannot open the actual quiz. The room waits. We have been that volunteer.
| What got emailed | What the volunteer can do | What fails |
|---|---|---|
| Audience join PIN | Sit in the lobby as a player | Cannot advance questions or reveal answers |
| A copied file in Drive | Read a question list | Cannot host the live session from a real account |
| Login and password in chat | Everything, including damage | Security incident, and it still fails when IT resets the password |
| Folder invite to their own email | Open the same quiz and host from their account | They needed the invite yesterday, not during the hold music |
Help centers for other live tools say the same thing in different words. Sharing the PowerPoint is not enough. Sharing the audience link is not enough. The backup needs access inside the engagement product, on a login that is theirs.
Harvard Business Review on meeting load is about time you never get back. A ten-minute hunt for a quiz file is that time, with 80 people watching. Atlassian’s process-documentation guidance names the same risk: if only one person handles a key process, an unplanned absence takes the knowledge with them.
What we actually share (view access, not a magic handover)
Smart folders let a team share quizzes, polls, and wheels instead of emailing a single-owner file. Invite by email. Access is view-only today. Access can be revoked. That is the product. We do not claim a live control-transfer button. We do not claim the volunteer silently takes over a session already in flight. The volunteer logs into their own account, opens the shared folder, and hosts.
That is still enough for the sick-day case. The asset is not orphaned on a laptop in a bedroom. The volunteer is not using a forwarded password.
Do this on Monday, not during the two-minute hold
- Create the event folder. Name it like the calendar: “Oct 14 manager assessment.”
- Put the live quiz in that folder. Put the poll and the wheel there too if the hour uses them.
- Bookmark the slide deck link inside the folder so AV is not hunting Slack.
- Invite the volunteer presenter by email. Invite AV if they need to see the same assets.
- Confirm they can see the quiz while logged in as themselves.
- Rehearse once: volunteer starts a lobby, you join as a phone, you end it.
If you skip step 6, you will discover on Tuesday that they never accepted the invite.
Use Smart Folders as the share surface. Use the live quiz as the thing you host. Do not paste the audience join link into a channel titled “BACKUP HOST.” That link is for attendees.
What “co-host” means here
It means a second human can run the same assessment without borrowing a password. It does not mean two mice on one live session. If the primary host drops mid-question, the honest recovery is ugly. End or abandon that session if you must. Open the same quiz from the backup account. Start a new lobby. Put the new PIN on the wall. We will not invent a seamless failover that we do not ship.
Tell the room one sentence if you restart. “We are reopening the same quiz. New code on the wall. Scores from the first minute will not merge.” Do not pretend the archive will stitch itself.
Revoke access after the season if the volunteer was temporary. View access is still access. Folders are private by default until you share them.
Why emailing the quiz link keeps happening
People copy the join URL because it looks like sharing. It is sharing the audience door. It is not sharing the host desk. Mentimeter’s help on presenting from a shared deck is the same class of failure: the file moved, the live object did not. Microsoft Forms collaboration links are a different model. Our model is folder plus email plus view.
We live-host only. There is no embed for the volunteer to “just click in the slides.” They need the workspace. That is a constraint. It is also why the folder matters.
If two volunteers show up, pick one host. Two people clicking next on two laptops is how you get two PINs. The second person can sit on the pending questions for a poll, or watch the lobby count, or run the room microphone. They should not start a second quiz. Write that on the run of show in one line. Rehearse the sentence they will say if they restart the lobby. Keep it to one breath.
Keep the PIN freeze in the same runbook. If the backup starts a new session, the badge QR from the morning may point at the old lobby. Have a wall slide that can change. Badges are for planned PINs. Failover is a wall job.
After the sick day, keep the folder
Do not move the quiz back into a private sandbox “for cleanliness.” The next volunteer will need it. Archive the session from the account that hosted. Export if L&D needs the scores. The folder is the run of show. The email invite is the staffing plan.
Contractors and agencies are the version of this that finance notices. If a freelancer built the quiz under a personal email, buying the “file” later is fiction. Create the folder on a company account first. Invite the freelancer in. When the contract ends, revoke. The quiz stays. That is cheaper than rebuilding 40 questions the night before a client workshop.
Stop emailing quiz links. Invite a volunteer presenter to the folder on Monday. Let them host from their account on Tuesday. That is co-hosting as it exists today.