Online exam software administers a test: it delivers questions, grades them, and files the result. That job is the same whether the paper is a recruitment screen, a professional certification or a school unit test. An exam simulator has a narrower job - make the clock, the penalty, the navigation rules and the on-screen furniture behave the way one named exam behaves, so a candidate who practises on it is rehearsing rather than merely answering. An institute that buys the first when it needed the second ends up with correctly graded papers that feel nothing like the hall.
This article is about telling the two apart before you commit to one. What a realistic paper has to get right, layer by layer, is a separate question answered in what makes a mock test realistic. What a format sheet has to pin down before you start building is in the paper setter's format reference.
What Exam Software Is Built to Do
Exam software is graded on administration. Its hard problems are identity and invigilation at a distance, candidate records that survive an audit, certificates, a question bank with tagging and reuse, exports into an HR or learning system, and billing. Those are genuinely hard, and a tool that solves them is worth paying for when they are your problems. Nothing on that roadmap is the question a simulator exists to answer, which is whether Section B behaves like Section B. A paper can be delivered flawlessly, scored correctly and stored forever while teaching a candidate the wrong instincts about time and risk.
What a Simulator Is Built to Do
A simulator asks one question: when the candidate presses Start, does the sitting force the same decisions the real paper forces? That reduces to four things you can check - the shape of the clock, the price of a wrong answer, what the candidate may and may not navigate to, and what the question palette tells them about their own progress. Everything else is decoration.
There is a sharp edge here that vendors tend to blur. A simulator is only as good as the one exam you point it at, and exam patterns change between cycles. What a tool owes you is not a preset named after an exam - it is settings fine-grained enough to reproduce whatever the current official bulletin says, including the parts that changed last year. Treat any button labelled with an exam name as a convenience, then verify every number behind it against the bulletin yourself.
Six Questions That Separate Them on a Demo
Ask these before money or a term's worth of question entry goes anywhere. Each one has a yes-or-no answer, and the answers together tell you which of the two categories the tool actually belongs to.
- Can two sections of one paper carry different marking? SSC MTS is the standard test case: 90 questions for 270 marks across two sessions of 45 minutes, where Session I is qualifying with no negative marking and Session II counts for merit and deducts one mark. A tool that sets one scheme per test cannot build that paper.
- Can a section carry its own clock - and can two adjacent sections share one pooled clock between them?
- Can section switching be locked, so a submitted section stays closed and time never carries over, and unlocked for the papers where a candidate roams freely?
- Does the student get a question palette with distinct states for answered, seen but unanswered, marked for review and never opened, or just a list of numbers?
- What happens when the clock expires while the tab is in the background, and what happens if the browser dies mid-paper?
- Where does the instructions screen get its numbers - from the live paper, or from prose somebody typed once and never revisited?
Exam software asks whether the test was administered correctly. A simulator asks whether the candidate was rehearsed. A paper can pass the first and fail the second completely.
Clock, Penalty, Navigation: What Has to Be Settable
On MockSetu the clock comes in three shapes. Locked is the default, and the default is load-bearing: an exam that has never been told otherwise is locked, not free. The student sits one section at a time on that section's own clock, and a submitted section stays closed. Turn section switching on and the paper runs instead as one timer over every section, with a tab strip to move between them. Between those sits the timing group - two or more adjacent sections sharing a single pool, free movement inside the pool, locked rules between pools. That third shape is what a two-session paper needs. A new section is created with 60 minutes on it, which you then set to whatever the bulletin says.
Marking lives on the question, not on the paper. A question uses its own rule if it has one, otherwise its section's, otherwise the exam default - so one test can hold a qualifying section at no penalty and a merit section at minus one. JEE Main Paper 1 happens not to need the split: 75 questions, 25 per subject, plus four and minus one in both Section A and Section B, 300 marks in 180 minutes. Every question on it is compulsory - the old choice of any five numericals out of ten went away with the 2025 cycle - so one scheme covers the paper. Plenty of other papers do need the split, and a per-test marking switch cannot express them.
A few smaller things matter more than they look. The palette carries four states - attempted, marked for review, viewed, untouched - because that grid is how a candidate decides what to go back to when the clock is short. And the paper table on the instructions screen is assembled from live exam data at the moment the student opens it, never parsed out of the stored instruction prose, so the section names, question counts, marks and sectional timings cannot drift away from the paper they describe. The declaration below it gates Start, and arrives un-ticked on every single arrival.
What Happens When the Clock Runs Out
This is the question that exposes the category difference fastest, because it never appears on a feature grid. The countdown runs in a background worker, so a student who switches tabs does not quietly gain time, and expiry submits automatically with whatever is on screen - the section in locked mode, the whole paper when one timer covers it. A warning fires at five minutes left. The deadline itself is stored server-side rather than in the browser, so a refresh resumes the same deadline instead of minting a fresh full-length clock, and a resumed sitting lands on the question it last touched rather than back at question one.
There is a limit on that generosity, and it is worth knowing before a student asks. If the same device has been away for longer than five minutes, the open sitting is sealed and filed as a normal ranked attempt with whatever answers it had, and the next Start begins a fresh one. A crashed browser is recoverable; a walk to the canteen is not.
Where MockSetu Is Not Exam Software
Being honest about this is the whole point of the comparison. There is no proctoring of any kind here - no webcam, no lockdown browser, no tab-switch detection. There are no payments or paywalls: a published paper is public, and anyone with the link may attempt it, so there is no private delivery to one paid batch. There is no CSV or Excel export of results and no per-student report card, no certificates, no white-labelling or custom domain, no mobile app, no LMS or Google Classroom integration, no question shuffling and no cap on attempts. Nothing notifies students about a test by email, SMS or WhatsApp - the only mail the product sends is transactional account mail for signup and password reset.
Three capabilities exist but are not simply switched on. Import from PDF, where the extraction happens server-side, is off by default and enabled per creator on request; the route open to everyone is the published extraction prompt from the JSON upload guide run in whatever AI you already use, followed by a JSON upload. That route brings single-correct and multiple-correct questions and leaves numeric, TITA and match-the-column for manual entry - which matters if you are mirroring a paper with a numerical section. The Mock versus Previous Year paper type is a per-creator grant, and the Verified Creator badge is granted on request rather than automatically.
If invigilated certification with audit exports is your actual requirement, buy exam software and do not pretend a simulator will cover it. If you are weighing what the paid tier of a test-series product buys over a free one, paid test series software vs free platforms is the comparison to read next.
Build the Simulator Half First
Whichever tool you land on, the build order is the same, because the two layers that decide a mock's value are also the two that are hardest to retrofit. Set the clock shape and the marking scheme before a single question goes in. Then write the instructions in the language the student reads, sit the paper yourself in preview, and only then worry about how it looks. A creator preview records nothing - no attempt, no marks, no entry in your own analytics - so you can walk the whole paper as a candidate would without polluting the data.
MockSetu is free and takes no card. What a creator can actually build here - sections with their own clocks, pooled timing groups, per-question marking, bilingual English and Hindi papers, a listing in the public library - is the simulator half of the category, built for people reproducing an Indian competitive exam rather than running a hiring funnel. The administration half is somebody else's product, and this page would rather say so than sell you a word for it.