A live quiz on MockSetu is one room, one question at a time, on the phones the class already has. You build the questions, publish the exam, put an eight-character code on the board, and unlock questions one by one while the room answers against a countdown you control. The part nobody warns you about: every student needs a signed-in student account, so have them sign up the night before.
The wall is a separate set of decisions, covered in how to project a live quiz on a classroom screen. A full-length paper rather than a warm-up is a different job again, in how to run a live mock test for a whole batch. This is the session itself.
Build the Quiz Before the Bell
A live exam is its own object, on its own tab in the creator dashboard, separate from your mock tests. You name it, choose English, Hindi or both, and add sections. Then the questions, each with its own timer. A new one starts at 60 seconds and the editor refuses anything under 5. That number is the length of the silence in the room, so it is the most consequential thing you set.
- Create the exam and add at least one section. A live exam with no sections cannot go live.
- Add the questions with their timers. Time each at your slowest reader's pace plus thinking time - the clock starts when you unlock, not when they finish reading.
- Publish. Go Live appears only once the exam is published, and Share refuses to copy a link until then. Drafts are hidden from students, so an unpublished code reads exactly like a wrong one.
- Let the publish check run. No sections, no questions, a blank question, a missing correct answer, or question counts that disagree between your two languages all block the publish. An uneven option count between languages is only a warning and goes through.
- Go Live opens the control room, where you confirm the start. Students who typed the code earlier sit in a waiting room, with nothing on screen until you unlock the first question.
The Code, and the Sign-In That Eats Your Lesson
Students get in two ways, both resolving to the same eight characters: the join link, or the code typed into Join with code on the public test library, beside the My Live Exams tab. The control room has a join panel you can pin to the screen - a QR square with the code beside it - so a late arrival does not send you back into a dialog. Treat typing as the real route in: camera autofocus on a bright projected surface from the back row fails often, and the code is set monospaced, in two blocks of four, so 0 and O cannot be confused.
Now the expensive part. A live exam requires a signed-in student account, every time. Someone who opens the link signed out is sent to sign in and returned to the room. Someone whose account was made at the classroom door must finish onboarding - name and user ID - before joining, or the standings would print an email prefix as their name. That queue is the difference between a quiz that starts on time and one that does not.
The join box checks the code before letting anyone through and names the exam when it matches, so a mistyped character is caught in place. Be clear what the code is, though: anyone with a student account who has it can walk in. There is no roster, no attendance list, and no way to restrict a live exam to one batch.
Putting a Question Up, and Taking It Back
Unlock is the whole job. One button reading "Unlock first question", then "Unlock Q2" and onwards; the space bar fires it too, which is why a double-tap is refused - the server would otherwise advance twice and skip a question in front of the class. The confirmation names the question and its seconds.
Three recovery controls exist because no live class runs to the plan you wrote the night before. Two sit beside the clock: while the countdown runs you can add 30 or 60 seconds, up to five minutes of extra time on one question, and when the room has plainly finished and the only thing still happening is a ring emptying itself, "Time's up" removes the seconds that are left and nothing else - the question then closes by the ordinary route, grading and reveal included.
The third is an undo. For five seconds after an unlock, and only until the first student answers, you can take the question back and the room returns to waiting. After that it is out, and the only repair is to say so out loud.
The code on the board is a door, not a lock. There is no proctoring here of any kind, so a live quiz is worth exactly what the room's attention is worth - which in a classroom you are standing in is quite a lot.
What You See While the Answers Land
Your screen is a cockpit, not a document. While a question is open you see how many have answered against how many are actually in the room - present now, from a heartbeat, not everyone who ever joined - plus the live split across the options and a line interpreting it.
Those option bars are built to be projected. They cannot mark an answer correct even if you wanted them to: fixed order, one neutral colour, no tick. A sharp student watching the wall learns how the room is divided and nothing about who is right.
The quietest readout is the count of students who pressed "I'm lost". On their phone that button gives nothing back - no count, just a tick and the words telling them only the teacher sees this. It resets every question, and the server takes one tap per student per question. Your side shows an exact number from one upward and vanishes at zero. It never goes on the projector: a public count turns an anonymous signal into a performance, and nobody presses it twice.
The Reveal, and Who Sees the Standings
When the visual timer ends the server keeps accepting answers for another two seconds, so a student who tapped as the clock hit zero is not punished for their network. Then the question is graded. Until that moment every answer comes back with the verdict withheld, so nobody learns they were right while the room is still deciding. The first submission is final, and only the open question is answerable.
After grading, every student sees the correct answer and the class distribution drawn into their own options. The wall is a separate decision: revealing the answer there is its own switch, which only exists while the wall is showing the choices at all. Standings are three choices, changeable mid-lesson without stopping anything:
- Everyone - the room sees the ranking. Fine for a warm-up, corrosive once it is the same names at the bottom every time.
- Just me - each student sees only their own result and nobody else's.
- Off - nobody has a place to look at while it runs, you included: a ranking read off the presenter's screen is still a ranking in the room.
Scores and ranks are recorded in all three, so turning the leaderboard off costs no data - your list comes back when the session ends, and so does the report. Hiding student names is separate: the room sees nicknames while you keep real names on your own screen, which is what you want when the ranking is useful and the shaming is not. On the big screen, standings appear only between questions.
Ending the Session
Ending asks once, warns you if questions are still locked, computes the final rankings, and cannot be undone. The room then goes read-only: anyone who was in it can reopen the same link for their own result and the standings. Anyone who was not is told the session has finished rather than being enrolled as an attendee who scored zero, which keeps your head count honest. What arrives next is the report, and reading a live exam report is a job of its own. To run the same quiz with the next batch, duplicate it - allowed in every status, ended included.
Shared Phones, Flat Batteries, and the Student With Nothing
Five classroom facts the feature cannot argue with.
- Two students on one phone are one student. Participation is keyed to the account, not the device, so a shared login is one row with one score. Pair them deliberately and say so, or give both an account and a device.
- A flat battery is recoverable. Signing in again on a borrowed phone returns that student to their own row and score; they lose only the questions that closed while they were away.
- Latecomers come in on the question the room is on and cannot answer the ones they missed. Say that out loud before someone discovers it and feels cheated.
- A student with no device has no row. There is no paper mode and no way to enter an answer for them. Seat them with a partner, let them argue the answer, and leave them out of the ranking.
- A colleague on a creator account cannot join as a student - creator accounts are blocked from other people's exams, and your own account in your own room is a watch-only preview that records nothing.
What a Live Quiz Here Cannot Do
Saying this now is cheaper than discovering it mid-session. There is no proctoring of any kind: no webcam, no lockdown browser, no tab-switch detection, no question shuffling. There is no mobile app either - it runs in the phone's browser. Nothing emails or messages your class that a room is open, so the code on the board is the announcement. Results do not export to CSV or Excel and there are no per-student report cards. Published papers are public, with no paywall or private delivery to one batch.
A very large sitting is the wrong shape for this. One room on one clock suits a class you are standing in front of; a whole centre is better served by a scheduled mock everyone sits in their own time.
Rehearse Once, in an Empty Theatre
The control room has a rehearsal mode: a simulated cohort who join, answer at plausible speeds, get things right and wrong, go quiet, and occasionally say they are lost. Every control is real and pressable, and nothing is written anywhere - the rehearsal has no network access at all, so it cannot leak a row into a real leaderboard. Spend one free period on it. The alternative is learning what Unlock does in front of a full class.
Then build it properly. Everything a creator can make here - live rooms, timed mocks on a real computer-based-test screen, bilingual papers, sections with their own clocks - sits behind one free account, and a live quiz is the fastest route to a first question.