Weak chapters, ranked
The two or three topics costing a student the most marks, ordered by marks lost rather than by percentage — so effort goes where it actually pays.
A percentage tells a student they did badly. It does not tell them what to do on Saturday. Every result here breaks down to the chapter, so the answer is two topics and a practice set rather than a number and a shrug.
Every report answers the same thing — what needs practice and what is already secure — framed for whoever is looking at it.
The two or three topics costing a student the most marks, ordered by marks lost rather than by percentage — so effort goes where it actually pays.
What a student has genuinely mastered, so revision is not spent on the chapter they already score ninety in because it feels comfortable.
When most of a division misses the same chapter, that is a teaching signal rather than a student one — and it shows up as a column, not a scatter.
The same chapter tracked across every assessment in a term, so improvement is visible and a dip is caught in week six rather than in the final.
How 9-A and 9-B compare on the same paper, and how a subject performs across an institute. Visible to the owner, not to the staff room.
Every weak-chapter report ends in a generated practice set on exactly those chapters. The analytics are only finished once they have produced work.
The whole point of chapter-level marking, in one grid. Read a row and you have a student's revision plan. Read a column and you have next week's lesson.
Chapter 7 is a column, not a scatter. Every student in the division is weak on it, including the two who top the class. That is a teaching signal rather than six revision plans — and it is the one thing a class mean of 68% hides completely.
Because every question already carries its chapter from the moment the paper was drafted, none of this is a reconciliation. It is arithmetic on data that arrived correctly tagged.
Per-question scores land, each already tagged with its chapter and difficulty.
3.1sMarks earned against marks available, per chapter. No mapping step, because the tag was never lost.
<1sWeak chapters ranked by marks lost, strengths confirmed, trend updated against previous papers.
<1sThe heatmap above. Columns where the whole class dropped are surfaced as teaching signals.
2sA targeted set per student on their own weak chapters, drawn from the same generator that wrote the paper.
8sStudent, teacher, parent and institute views refresh together. Nobody is reading yesterday's number.
<1sUnder fifteen seconds from the last script submitted to four dashboards showing the same, current truth.
The same division, read as a waterfall. A mean of 68% is one number; this is where the missing 26 marks actually went, and it is the view heads of department ask for first.
Three chapters account for twenty-four of the twenty-six lost marks. Which is the useful sentence, because it turns a disappointing result into three lessons. Chapter 7 alone is worth eleven marks to this division — more than the other four columns combined.
Illustrative figures in the shape of a real report. The method is fixed; the numbers are whatever your division actually did.
A mean tells you there is a problem. A chapter tells you what to teach on Monday. Same paper, same marks, read by chapter instead of by student — so the answer is a lesson plan rather than a percentage.
Analytics that end in a chart end in nothing. This is the sequence a single weak column sets off, and who does each part.
The teacher releases the division. Chapter-level breakdowns are computed and attached to every script at the same moment, not as a later batch.
TeacherNot a rank against classmates. Two named topics, the marks each one cost them, and what to read. A student who came third still gets told what they got wrong.
Automatic · Student viewOne per student, on their own weak chapters, from the same generator that wrote the paper. Different students get different sets from the same exam.
AutomaticChapter 7 is flagged as class-wide rather than individual, with the distribution shown so it is obvious this is not two weak students dragging a mean down.
Teacher viewThe chapter is added to the division's plan and stays flagged until a later assessment clears it. Nobody has to remember; the next paper checks.
Teacher · trackedThe grid shows that Chapter 7 cost them eleven marks. It has nothing to say about whether they were ill that fortnight, cannot see the board, or simply never did the reading. That conversation is still yours.
We report division performance, not teacher rankings, and the comparison view is deliberately limited to the institute owner. A division's intake explains more of its mean than its teacher does, and league tables inside a staff room do damage.
A single assessment is a data point, not a trend. Chapter flags need two results before they are treated as settled, and the interface says so rather than presenting one bad Tuesday as a verdict.
This measures what was demonstrated on one paper against one syllabus. It is not an aptitude score, we will not build one, and no part of the product predicts a ceiling for a child.
The most useful thing analytics can say is "not enough data yet". A flag that appears after one paper and vanishes after the next teaches a teacher to ignore flags.
The four that come up almost every time.
Because it was tagged when the paper was drafted, not inferred afterwards. Scope is chosen per chapter in the generator, and every question carries that tag through marking and into the report. There is no classification step that could get it wrong, and no reconciliation job that could fall behind. If you upload a paper set outside Intellicamp you tag the questions once, and it behaves the same from then on.
They see their own child's chapter breakdown, trend and practice sets, plus the class mean for context. They do not see other students, a rank, or a position in the division. Schools ask for this boundary more often than any other, and the default is the conservative one — an institute can widen it, but has to choose to.
One paper gives you a usable chapter breakdown of that paper. Trends need three or four before they mean anything, and chapter flags stay marked provisional until a second result agrees. Most schools find the division-level view useful immediately and the per-student trend useful from about the second month — and the interface is explicit about which of those you are looking at.
Yes. Every view exports to CSV and PDF, and chapter-level results are available over an API keyed to your institute so an existing school MIS can pull them on a schedule. Nothing is locked in a dashboard you have to log into to read, and the export contains the same numbers as the screen rather than a reduced summary.
Book a free 30-minute demo. We'll build the chapter breakdown from a paper you already ran and show you the columns.