સહાય લાઇબ્રેરી

સહાય કેન્દ્ર

વિદ્યાર્થીઓ માટે ઓનબોર્ડિંગ ગાઇડ: ક્યારે અભ્યાસ કરવો, ક્યારે પ્રેક્ટિસ કરવી, ક્યારે રિવિઝન કરવું અને કયો ફીચર ક્યારે વાપરવો.

StudyPhysics
PracticeMath
ReviseChem
ડૅશબોર્ડ પર પાછા

વિદ્યાર્થી માર્ગદર્શિકા

પ્રદર્શન

AI insights માર્ગદર્શિકા: marks કેમ ઘટે છે, આગળ શું કરવું, અને practice, mocks અને revision સાથે improvement loop કેવી રીતે બંધ થાય છે.

Why Analytics is a must for JEE students#

JEE preparation is not won only by solving more questions. Many students work hard but lose marks because they repeat the same hidden patterns: over-attempting MCQs, ignoring high-weightage weak areas, forgetting old chapters, collapsing late in mocks, or dismissing repeated mistakes as "silly." Analytics exists to make those patterns visible before they become rank damage.

Think of Analytics as your post-practice mentor. It studies your Practice PYQs, Mock Tests, Mistake Review, and revision outcomes, then tells you what is actually blocking your score and what action should happen next.

End-to-End Flow#

This is the complete student improvement loop. The important part is not one AI insight; it is the cycle from real exam behaviour to diagnosis, action, and proof.

01StudentPractise or take a mock

Solve Practice PYQs, complete a Full Test, or reattempt mistakes.

02EvidenceAttempts become data

Correctness, timing, subject, topic, difficulty, score, and session behaviour are saved.

03AnalyticsAI explains the pattern

Insights detect score leaks: speed, accuracy, negative marking, fatigue, weak topics, and strategy gaps.

04CoachRevision Helper creates action

The diagnosis becomes a daily session, n-day recovery plan, drill, mistake review, or mock strategy task.

05ExecutionStudent completes the work

You revise traps, solve targeted PYQs, repair mistakes, rate confidence, or take the next mock with a rule.

06FeedbackNext outcome proves progress

New PYQ/mock results show if the issue resolved, improved, returned, or needs escalation.

InputPractice PYQs, Full Tests, Mistake Review, confidence, timing, score.
AI coach layerExplains why marks are leaking and which action has the highest ROI.
Action layerRevision Helper, targeted drills, post-mock recovery, n-day plan.
Proof layerNext outcome confirms resolved, improved, repeated, or escalated.

Core Concept: AI Insights#

AI Insights are coach-style diagnostic cards generated from your attempt history and mock-test behaviour. They are not meant to repeat raw dashboard numbers. Their job is to explain why your performance is moving the way it is and what action should happen next.

ObservationThe pattern the app found, ideally with numbers such as wrong MCQs, late accuracy, speed, topic accuracy, or score gap.
ActionThe next concrete step: revise, practise, reattempt, build skip discipline, or create a Revision Helper recovery plan.
Progress summaryAfter multiple runs, Analytics can compare whether your previous issues improved or returned.
AcknowledgementMarking an insight addressed is not just dismissal. The app can later compare the metric to see whether the behaviour actually improved.

Insight Categories#

Categories help you triage the kind of problem you are facing. The shipped app starts with six mentor-style categories, and the roadmap adds more precise categories for topic priority, mistake fingerprints, retention, and confidence.

Speed / AccuracyShows whether you are rushing, overthinking, guessing, or spending too long on questions you already know.
Negative MarkingFinds wrong MCQ attempts that are pulling marks down and helps build skip discipline.
ConsistencyChecks whether your practice rhythm, subject balance, and weekly performance are stable enough for exam prep.
FatigueDetects late-test collapse, stamina issues, and accuracy drops after long sessions or subject shifts.
LearningShows whether topics are improving, stuck, decaying, or plateauing despite more practice.
Exam StrategyLooks at attempt rate, subject time allocation, question ordering, and full-test decision quality.
Topic PriorityFuture category for high-ROI weak areas and score levers: what to fix first for maximum marks.
Mistake PatternsFuture category for silly errors, conceptual gaps, traps, misreads, and repeat wrongs.
Revision RetentionFuture category for forgetting, overdue reviews, due notes, decayed topics, and maintenance work.
Confidence CalibrationFuture category for confident-wrong answers, low-confidence correct answers, and low-confidence MCQ leakage.

Insight Severity#

Severity tells you how quickly to act. Use it to avoid spreading energy across too many problems at once.

▲ CriticalAct first. This pattern is likely costing marks now or will hurt the next mock if ignored.
◆ ModeratePlan within the next 1-2 weeks. These issues may not be urgent today, but they can become score leaks.
● LowTrack and maintain. These are smaller patterns, useful for polishing once major gaps are under control.

The edge you get by using this approach#

You stop guessing what to studyAnalytics turns raw attempts into a ranked diagnosis: which subtopics are costing marks, whether the issue is speed, accuracy, negative marking, fatigue, revision decay, or exam strategy.
You see marks, not just percentagesA 60% accuracy topic is not always urgent. Analytics should connect performance to JEE weightage, scoring potential, predicted score gap, and rank impact so your effort goes where it can move marks.
You get coach-style feedback after mocksInstead of only seeing a score, you get a debrief: what went wrong, why it happened, what to fix first, and which action should happen before the next test.
You close the loopInsights become Revision Helper sessions, PYQ drills, Mistake Review, and post-mock recovery. The next Practice or Mock outcome then proves whether the issue improved.

What Analytics should detect for you#

The best students do not treat all mistakes equally. Analytics helps classify the real problem so the solution is precise.

Speed vs accuracyAre you fast and correct, slow and correct, fast and wrong, or genuinely stuck? Each needs a different fix.
Negative marking riskFind low-confidence or reckless MCQ attempts that reduce your score even when your syllabus coverage looks fine.
Priority-weighted weak areasCombine your accuracy with topic weightage, priority score, difficulty, scoring potential, and frequency so high-ROI topics rise first.
Mistake fingerprintsSeparate silly errors, conceptual gaps, known traps, slow-skip candidates, panic/fatigue, and misread questions.
Fatigue and staminaDetect whether accuracy drops in the last part of a paper or after a subject/time-pressure shift.
Learning trajectorySee which topics are improving, plateauing, decaying, or still below target after repeated practice.
Exam strategyCheck attempt rate, subject time allocation, over-attempting, under-attempting, and full-test decision quality.
Target gapTranslate current performance into predicted score/percentile direction and the smallest set of score levers for the next phase.

The closed improvement loop#

The strongest part of this approach is that Analytics does not stop at advice. It connects to Revision Helper, Practice PYQs, Mistake Review, and Full Tests so the app can measure whether an action actually worked.

1
Practice or mock creates evidencePractice PYQs and Full Tests save correctness, timing, topic, difficulty, wrong MCQs, score, subject split, and session context.
2
Analytics explains the patternThe app studies your attempt history and shows the few behaviours that most affect marks, not every possible statistic.
3
Revision Helper turns it into actionHigh-priority insights become Daily Coach sessions, n-day recovery plans, mistake drills, due reviews, or mock-recovery work.
4
You execute the actionYou solve the targeted PYQs, reattempt mistakes, revise traps, complete a recovery session, or take the next mock with a specific rule.
5
Outcomes feed backThe next practice or mock result shows whether the insight is resolved, still active, or needs escalation.
InputPractice and Mock outcomes create trustworthy evidence.
DiagnosisAnalytics finds the score-limiting pattern.
ActionRevision Helper turns the insight into daily or n-day work.
ProofThe next PYQ or mock result proves whether the pattern improved.

How to use Analytics as a student#

Do this when you open Analytics

1
Step 1Start with high-severity insights. These are the patterns most likely to hurt marks soon.
2
Step 2Read the observation carefully. Good insights mention numbers: wrong MCQs, late accuracy, time per question, topic accuracy, or score gap.
3
Step 3Ask: is this a knowledge gap, revision decay, trap, speed issue, negative-marking issue, or stamina issue?
4
Step 4Use the action button or Revision Helper handoff instead of manually deciding what to do.
5
Step 5After finishing the action, check later Practice or Mock outcomes to confirm the issue improved.

Best routines#

After every full mock

1
Step 1Open Analytics or the post-test AI Insights panel before checking only rank/score emotionally.
2
Step 2Find the biggest lost-mark bucket: negative marking, fatigue, subject imbalance, repeated mistakes, or weak high-ROI topics.
3
Step 3Create a post-mock recovery session in Revision Helper and finish it before your next mock.

Every 2-3 practice sessions

1
Step 1Check whether the same topic or mistake fingerprint is repeating.
2
Step 2If the issue repeats, stop doing random volume and open a targeted Revision Helper or Mistake Review action.
3
Step 3Return to Practice PYQs only after the concept, trap, or timing rule is repaired.

Weekly strategy review

1
Step 1Run or refresh Analytics once you have enough new attempts.
2
Step 2Look at high-severity unresolved insights first.
3
Step 3Convert one major insight into a 7-day recovery plan rather than trying to fix everything at once.

What good usage looks like#

  • You do not chase every weak topic. You fix the highest-ROI weakness first.
  • You do not take mocks only for a score. Every mock produces a recovery action.
  • You do not call repeated mistakes "silly" forever. You identify the mistake fingerprint and repair it.
  • You do not over-attempt low-confidence MCQs. You build skip discipline before exam day.
  • You do not let insights become passive reading. You convert them into Revision Helper, PYQ, or Mock actions.
  • You review whether the next outcome improved. That is how Analytics becomes a coach, not a dashboard.
ઉપર પાછાવિભાગ ખોલો