Last verified: 31 October 2026. The exam pattern figures below (Class 6: 300 marks; Class 9: 400 marks; no negative marking; 25% per-section and 40% aggregate qualifying marks) follow the AISSEE 2026 bulletin pattern, expected to repeat for 2027. The AISSEE 2027 notification itself is still awaited — confirm the final pattern in the NTA bulletin when it releases.
Photo: Pexels
You know the feeling. Mock one: 198. Mock two: 203. Mock three: 197. Your child is studying, the hours are going in, and the scoreboard refuses to budge. Parents usually react to this in one of two ways — panic-buy a new book set, or add more study hours. Both feel productive. Neither fixes a plateau, because a plateau is almost never a “more” problem. It is a “which” problem: which specific thing is capping the score.
Here’s the thing — a flat mock score is actually useful information. It is telling you, quite precisely, that your child’s current preparation has a ceiling, and that ceiling has a name. Your job this week is to find that name.
Before diagnosing anything, be clear about what “around 200” means for your child’s class, because the same number means two different things:
Either way, the qualifying rule is 25% in each section plus 40% overall (not applicable to SC/ST candidates), so a plateau is only dangerous if one section is dragging below its 25% floor. Check that first. A child scoring 200 overall but 15% in one section has a different problem — and a different fix — than a child scoring evenly across sections.
Take the last three full mocks your child attempted under real exam conditions — timed, no phone, OMR-style bubbling if possible — and sort every lost mark into one of three buckets. Our error-log method walks through exactly how to do this, but the short version is:
| Ceiling | The symptom in the error log | The fix |
|---|---|---|
| Speed | 15+ questions left unattempted, or the last section rushed | Timed section drills; a fixed attempt order; skip-and-return discipline |
| Accuracy | Most questions attempted, but 20+ wrong — especially silly errors | Slow down the first pass; a 10-minute checking window; error-type tracking |
| One weak section | One section scores far below the others in all three mocks | Two weeks of section-only work before the next full mock |
Honestly, most plateaus turn out to be one of these, not a mix of all three. The parent who tries to fix speed, accuracy and GK all in the same fortnight usually fixes none of them. Pick the biggest bucket and attack only that for two weeks.
A child who leaves questions unattempted is not losing marks to ignorance — they are losing marks to the clock. The usual culprit is getting stuck: spending four minutes on one maths problem while five easy questions wait untouched at the end of the paper.
The fix is mechanical, not motivational. Set a per-question time budget (roughly a minute per question in Class 6, a little more in Class 9), practise a strict skip-and-return rule — if a question takes more than 90 seconds, mark it and move on — and run timed drills on the slowest section only. Our maths speed guide has the drill structure, and our paper attempt strategy covers the first-pass/second-pass order that stops the clock from eating the easy marks.
One more thing worth saying plainly: AISSEE has no negative marking, so an unattempted question and a wrong answer score exactly the same — zero. There is no reason, ever, to leave a question blank in the last five minutes. Our honest answer on negative marking explains why blind guessing still is not a strategy, but educated elimination in the final minutes always beats a blank.
This is the most frustrating plateau, because the child “knows” the material. The error log usually reveals the truth: the same two or three error types, repeated. Misread questions. Calculation slips in the last step. Bubbling the right answer in the wrong row. These are not knowledge gaps, and more chapters will not fix them.
The fix is a checking window. Reserve the last 10 minutes of every mock — and of the real exam — for verification only, and spend it on the highest-risk items: questions where the child hesitated, calculations with borrowing or carrying, and the OMR row alignment. Then track error types across mocks, not just scores. When “misread the question” drops from 12 occurrences to 3, the score moves — even if no new chapter was studied that week.
This is the commonest Class 6 pattern: maths and intelligence fine, GK dragging; or language strong, maths weak. The temptation is to keep revising the strong sections because it feels good. Resist it. For two weeks, give the weak section the first study hour of the day — when concentration is freshest — and do section-only practice sets instead of full mocks. Then take one full mock to measure. If the weak section rises and the total moves, you have found your lever. If it doesn’t, the diagnosis was wrong, and that itself is useful information.
| Week | Focus | Measure |
|---|---|---|
| Days 1–3 | Analyse three mocks; name the single biggest bucket | Error log complete, one ceiling named |
| Days 4–10 | Daily 45-minute drills on that ceiling only | Drill accuracy or speed tracked daily |
| Day 11–12 | One full mock under exam conditions | Compare section scores, not just the total |
| Days 13–14 | Fix what the mock exposed; rest before the next mock | Second mock confirms the direction |
Two rules for the whole fortnight. First, no new books, no new coaching material — the plateau is not a resource shortage. Second, judge progress by section scores and error counts, not by the headline total. The total is the last thing to move; the section scores move first.
Do not add two extra study hours the week you discover a plateau — tired children make more silly errors, and accuracy plateaus get worse, not better. Do not switch your child’s entire strategy after one bad mock; one mock is noise. And do not compare your child’s 200 with another child’s 260 without comparing their error logs. The other child may simply have fixed their bottleneck a month earlier. Plateaus break in order: diagnosis, one fix, measurement, repeat. It is slower than panic, and it is the only thing that actually works.
What does a mock score stuck around 200 mean in AISSEE?
It depends on the class. Class 6 is marked out of 300, so 200 is two-thirds of the paper; Class 9 is marked out of 400, so 200 is exactly half. In both cases a flat score across several mocks means one specific bottleneck, not a general lack of preparation.
Should my child attempt more questions to break a mock score plateau?
Not blindly. AISSEE has no negative marking, so attempting is free, but random guessing does not raise scores. The fix is to convert attempted-but-wrong questions into correct ones, usually by fixing one weak section or one error type.
How many mocks should we analyse before changing the study plan?
Three full mocks under exam conditions. One mock is noise, two is a hint, three with the same section pattern is a diagnosis you can act on.
Is speed or accuracy the bigger problem when scores plateau?
Check the error log. If 15 or more questions are left unattempted, speed is the ceiling. If most questions are attempted but many are wrong, accuracy is the ceiling. Fix the bigger one first.
How long does it take to break an AISSEE mock plateau?
Usually two to three weeks of targeted work on one bottleneck, measured by the next two mocks. A plateau built over months does not break in a weekend, and a plan that tries to fix everything at once usually fixes nothing.
How helpful was this article?
