How to conduct an online exam for thousands of students

To conduct an online exam for thousands of students, fix the exam window and rules first, rehearse the whole flow with a free practice test, and confirm your platform can take the rush when everyone starts and submits at once. Make sure answers are saved as students go, so a dropped connection costs them nothing. Then run the day from a written runbook, and publish results only after the answer key has been checked.

Plan the exam window

The biggest decision is when students may start, because it shapes fairness, load and support calls all at once.

Then decide the rules and publish them before exam day, so nobody argues them during it:

• How late a student may join, and whether a late start shortens their time.
  
  
• What happens if a student disconnects. Keeping the clock running is the simplest and fairest rule, which is why saving answers continuously matters.
  
  
• Which devices and app version are supported, and which languages the paper comes in.
  
  
• When the provisional answer key, final results and ranks will come out, and how students can raise objections.
  
  

Announce the schedule a week ahead, and remind students the day before and an hour before through your app, SMS and WhatsApp groups. Two or three days before the exam, run a short free practice test on the same app. Students update the app, log in and learn the interface when mistakes cost nothing, and you get a small rehearsal of your own.

Test the platform before students do

1. Build the paper early and have a second person check every question, the answer key, the marking scheme (such as +4 and −1), sectional timers and each language version.
   
   
2. Take the test yourself from a student account on a low-end Android phone on a slow connection. Close the app mid-test, switch between Wi-Fi and mobile data, and check that you land back where you were with every answer intact.
   
   
3. Pilot with one batch of a few hundred students a week before the big day.
   
   
4. Load test the rushes, not the average: thousands of students pressing "Start" in the same minute, and again submitting in the last few minutes. The technical side is covered in scaling for exam-day traffic.
   
   
5. Get logins out of the way. Ask students to log in the day before, so thousands of OTP messages don't go out at 9:59.
   
   
6. Freeze changes 48 hours before: no new app release and no edits to the paper.
   
   

If a platform provider runs your tests, ask them directly:

• What happens if 20,000 students press "Start" in the same minute?
  
  
• Are answers saved on the server as students go, or only when they submit?
  
  
• What happens if the app closes or the phone loses signal mid-test?
  
  
• Does the server or the phone decide when time is up?
  
  
• How are double taps, retries and late submissions handled?
  
  
• When will ranks be ready, and who is on call during the exam?
  
  

Autosave, reconnects and bad networks

Many of your students will write the exam on a budget phone, on mobile data, in a room with one bar of signal. Design for that, not for the office Wi-Fi.

• Save every answer as it is marked, not only at submission, and save again whenever the app goes to the background, for example when a call comes in.
  
  
• Resume exactly where the student left off after a crash, a closed app or a lost connection, with every saved answer in place.
  
  
• Keep the clock on the server. Phone clocks can be wrong or changed. The app can show a countdown, but the end time should come from the server.
  
  
• Queue submissions made without signal on the phone and retry them automatically, with a short grace period after time-up, then refuse further edits.
  
  
• Count each submission once, even if the student taps twice or the app retries.
  
  
• Tell students what is happening. A visible "saved" tick and a calm message beat an error screen.
  
  

Prepare one message for the support team to send the moment someone panics: "If your app closes, open it again and tap Resume. Your answers are saved and your timer continues."

Integrity settings

A mock test is only worth its rank if the rank is honest. Settings to switch on:

• Shuffle questions and options where the exam pattern allows it.
  
  
• Lock sections once their time ends, so students can't return to them.
  
  
• Allow one attempt per student, and decide what happens if the test is opened on two devices.
  
  
• Keep answer keys off students' phones until the test is submitted, and grade on the server.
  
  
• Release solutions only after the window has closed for everyone.
  
  
• Ask students to accept a fair-play pledge, and say clearly what happens to rule-breakers.
  
  

For proctoring, browser lockdown and their false positives, see preventing cheating in online exams, and for keeping papers and solutions off Telegram, preventing question paper leaks.

Results, ranks and analysis

1. Publish a provisional answer key soon after the exam, with a fixed objection window, for example 24 hours.
   
   
2. Review objections, correct the key, and regrade every attempt with the final key. This is why raw answers must be stored, not just scores.
   
   
3. Rank only the students who took the test, and publish the tie-break rule in advance, such as fewer wrong answers ranking higher.
   
   
4. Explain the percentile. For example: the percentage of test-takers who scored at or below you. Whatever definition you use, state it.
   
   
5. Handle shifts deliberately. If different shifts had different papers, rank within each shift or normalise scores, and tell students which.
   
   

Analysis is a big part of what students pay for. Give them section-wise scores, accuracy, time spent per question, a comparison with the topper, and solutions they can filter to their mistakes. Give your faculty the most-missed questions and any question where most strong students chose the same "wrong" option, which can mean the key itself is wrong.

Exam-day runbook

For the engineering behind a smooth start, our guide to handling 100,000 concurrent users explains how platforms absorb that first minute.

After a big mock, the recorded solutions and PDF notes that go with it need protecting as much as the paper. On Upclass, VidSafe protects that content with VidSafe proprietary encryption, dynamic watermarking, PDF watermarking, screen- and camera-recording detection and account-sharing prevention. For the tests themselves, see our test series software.

Key takeaways

• Choose the exam format first: a fixed start gives fair ranks but the biggest rush; an entry window spreads it.
  
  
• Rehearse with a practice test, a pilot batch and a load test of the start and submission rushes.
  
  
• Save answers continuously, keep the clock on the server and make submissions count once.
  
  
• Switch on integrity settings, and release solutions only after everyone has finished.
  
  
• Publish a provisional key, take objections, regrade, then rank with a published tie-break rule.
  
  

Frequently asked questions

How to do online exam for students?

Choose a platform that supports your exam pattern, then plan the exam window and rules, build and double-check the paper, and announce the schedule early. Run a free practice test so students can install and learn the app, and pilot with a small batch. On exam day, keep support channels open and monitor progress. Afterwards, publish a provisional answer key, take objections, regrade, and release ranks and analysis.

How to conduct online test for students?

Start with the test itself: pick questions from your question bank, set the marking scheme including negative marks, set section timers if the real exam has them, and write clear instructions. Preview it from a student account on a phone. Decide when it opens and closes, whether results appear instantly or later, and whether solutions unlock after the window. For regular class tests, a fixed weekly slot helps students plan their revision.

How to conduct online exam free?

For small, low-stakes quizzes, free tools work. Google Forms can turn a form into a quiz with an answer key, points and automatic grading, and lets you release scores immediately or after review. Before relying on any free tool for a real mock test, check whether it supports timers, sectional timing, negative marking, question shuffling, ranks and a mobile experience your students can use on weak networks.