Loading page
About this tool
Log every study doubt, who resolved it and whether you retested yourself, with resolution-time and retest-rate stats.
This log tracks every study doubt from the day it is raised to the day it is resolved — and, crucially, whether you retested yourself on it afterwards. It applies the testing effect from cognitive psychology (Roediger & Karpicke, 2006): a doubt is only truly closed when you can re-solve a similar problem without help, so the log reports a retest rate alongside resolution time. Built for coaching students and self-study aspirants who want to stop the same doubts resurfacing in mock tests.
Open Doubt Resolution Log on AltFTool — it loads instantly in your browser.
Fill in 'Add a doubt' — subject, the doubt in one line, and date raised (blank = today) — then press 'Add doubt'.
When a doubt is cleared, click 'Mark resolved today', and click 'Mark retested' only after you re-solve a similar problem without help.
Watch the retest rate, doubts stale past 7 days and the per-subject Open/Resolved/Retested table, then click 'Copy summary'.
Separates 'someone explained it' from 'I can now do it myself'.
Doubts open longer than 7 days — one coaching cycle — are flagged before they pile up.
See whether faculty, peers or online videos are actually clearing your doubts.
Because retrieval, not re-reading, is what makes material stick — the testing effect shown by Roediger and Karpicke's 2006 experiments found actively recalling material beats restudying it for long-term retention. Watching someone solve your doubt feels like understanding, but only re-solving a similar problem yourself confirms it.
This log flags any doubt open for more than 7 days, on the logic that most coaching schedules run weekly cycles of tests and doubt sessions. A doubt that misses one full cycle usually gets forgotten rather than resolved, so escalate it to a teacher or mentor at that point.
No. Entries are stored only in your own browser's local storage and never sent to a server. Clearing site data or switching browsers erases the log, so copy the summary out first if you need it elsewhere.
Resolved means someone or something gave you a satisfactory explanation; closed means you then re-solved a similar problem on your own and marked it retested. The gap between the two — shown here as the retest rate — is where most exam-day errors hide.