Skip to main content
The error tracking system helps you identify patterns in your mistakes. By categorizing and reviewing errors, you can target weak areas and avoid repeating the same mistakes in future tests.

​
Error categories

ChaosPrep uses four mistake types:
  • Concept: Fundamental misunderstanding of the topic
  • Silly: Careless mistakes like misreading the question
  • Calculation: Arithmetic or algebra errors
  • Time Management: Ran out of time or rushed the problem
Each category helps you diagnose why you got a question wrong, not just that you got it wrong.

​
Logging an error

1

Navigate to Error Tracking

Click Stats in the navigation, then select Error Tracking from the dropdown menu.
2

Select subject and chapter

  • Choose the subject from the dropdown (Physics, Chemistry, Maths/Biology)
  • Select the chapter where the error occurred
  • Or choose “Custom” to enter a custom chapter name
3

Pick error type

Click one of the four error type pills: Concept, Silly, Calculation, or Time Management.
4

Add question details

  • Enter the question number (e.g., “Q47”)
  • Add notes about the error (optional but recommended)
  • Example: “Confused centripetal with centrifugal force”
5

Submit the error log

Click Log Error. The error is saved and appears in your error list immediately.

​
Chapter selection

ChaosPrep includes the full JEE and NEET syllabus structure:
  • JEE: Physics (28 chapters), Chemistry (23 chapters), Maths (27 chapters)
  • NEET: Physics (28 chapters), Chemistry (23 chapters), Biology (32 chapters)
When you select a subject, the chapter dropdown automatically populates with relevant chapters for your exam type (set in Settings). If your error is from a chapter not in the standard syllabus, select “Custom” and type the chapter name manually.

​
Error review and analysis

The error list displays all logged mistakes in reverse chronological order (newest first). Each error card shows:
  • Subject and chapter (with chapter-colored badges)
  • Error type (badge with icon)
  • Question number
  • Notes
  • Date logged
  • Delete button

​
Filtering errors

Use the subject filter pills above the error list to show only errors from specific subjects. This helps you focus on one subject’s weak areas at a time. Filter options:
  • All: Shows errors from all subjects
  • Physics: Only physics errors
  • Chemistry: Only chemistry errors
  • Maths/Biology: Only maths or biology errors

​
Error statistics

The error tracking view displays aggregate statistics:
  • Total errors logged: Count of all mistakes recorded
  • Errors by type: Breakdown showing percentage of each error category
  • Errors by subject: Subject-wise error distribution
These stats help you identify patterns:
  • High “Silly” errors → slow down during tests
  • High “Concept” errors → review fundamentals
  • High “Time Management” errors → practice speed-solving
Common mistake patterns: If you see the same error type repeatedly in a specific chapter, that’s a red flag. Prioritize revisiting that chapter’s fundamentals before moving to advanced problems.

​
Error review workflow

Use this systematic approach:
  1. Log immediately: Right after checking a test, log all errors while they’re fresh
  2. Review weekly: Filter by subject and review all errors from the past week
  3. Identify patterns: Look for chapters or error types that repeat
  4. Targeted practice: Solve additional problems from high-error chapters
  5. Re-test: Take another mock covering the same chapters to verify improvement

​
Deleting error logs

Click the trash icon on any error card to delete it. This is useful if you:
  • Logged the same error twice by mistake
  • Realized the error was actually correct after reviewing
  • Want to clear old errors after mastering the concept
Don’t delete errors just to make your stats look better. The error log is a diagnostic tool—honest tracking leads to better results.

​
Integration with syllabus tracker

When you log errors in specific chapters, use the Syllabus Tracker to mark those chapters for revision. This creates a feedback loop:
  1. Log error in Chapter X
  2. Mark Chapter X as “In Progress” in syllabus
  3. Revise Chapter X
  4. Update syllabus status to “Revised”
  5. Take another test and verify no errors in Chapter X

Build docs developers (and LLMs) love

Get started for freeTalk to us