How a mock gets made here.

Anyone can publish a thousand MCQs. The hard part — the part that decides whether a candidate walks out of the hall smiling — is making each question carry the weight, phrasing and subject mix of the bench that wrote the original. Here's how we do it.

1. We start from the real paper, not a syllabus PDF

Before we generate anything for an exam, we sit with its previous-year papers. How many questions? What's the split between CPC, Evidence, the local Land Revenue code, and general knowledge? Does it have one sitting or two? UP PCS-J and Bihar run two papers; Rajasthan asks 100; MP asks 150. We match those numbers exactly, because a 100-question mock for a 150-question exam teaches the wrong stamina.

2. We anchor every note to a canonical source

Judges quote specific commentaries. So do examiners. Our notes are written against the textbooks and bare Acts that the exam itself rewards — then verified against two independent sources before they go live. If we can't confirm a case citation, party name and holding, we don't print it.

3. We obsess over the answer key

Open most free question banks and you'll find the correct answer is "B" forty percent of the time — a tell that trains pattern-guessing instead of knowledge. We deliberately balance our keys so the correct option is spread evenly across A, B, C and D. You can't game our mocks. You can only know the law.

4. We make the analytics point at the fix

A score is a verdict; we wanted a map. After each mock, Law Mock breaks your performance down by subject, per state exam — and every weak subject links directly to the chapter notes that repair it. The loop is meant to close: practise, see the gap, read the fix, practise again.