Is re-reading my notes enough for general awareness?

Re-reading feels productive but produces weak retention. Self-testing — closing the book and answering from memory, or using short quizzes — forces retrieval, which is what the exam actually demands. Use notes as a source to test from, not as the main activity.

How often should I revise the same topic?

First review within a day or two, then again after about a week, then after two to three weeks, and again before the exam. The gap should grow each time the topic feels easy. Cramming everything in the last week cannot replace this spread-out schedule.

What belongs in an error log from mock tests?

Every question you got wrong or guessed correctly, with the fact or rule you missed, why you missed it in your own words, and one line on how you will test yourself on it again. Reread the log weekly; that rereading is where patterns become fixable habits.

Revision and retention: spaced repetition, active recall and error logs

Most candidates treat revision as re-reading notes until the pages look familiar. Familiarity on the couch is not the same as recall under a forty-second timer. Research on learning consistently shows that retrieval practice — pulling an answer from memory — beats passive review for long-term retention. The sections below translate that into a practical system for SSC CGL and RRB NTPC, where general awareness, static GK and mixed subjects must stay sharp for months.

Active recall: test yourself before you feel ready

After you read a chapter or finish a current-affairs block, close the material and write or say what you remember: three causes of inflation, the main function of NITI Aayog, last month’s important appointments. Check only after you have tried. Wrong or blank answers mark what needs another short session, not another full read.

Useful formats:

Blank-page summaries — one side of paper, no looking back.
Question lists — turn headings into “What is…?” / “Who heads…?” prompts.
Short quizzes — the site daily quiz is built for quick retrieval reps between longer study blocks; treat it as practice, not entertainment.

Re-reading the same highlight for the fifth time is easier than testing; that ease is exactly why it underperforms on exam day.

Spaced repetition: widen the gap each time

Memory sticks when reviews are spread out, not massed on one day. A simple schedule that works for most topics:

Review	When (approx.)	What to do
1	Same day or next morning	Active recall on the new material only
2	5–7 days later	Recall + check one-page notes
3	2–3 weeks later	Mixed with other subjects (see interleaving)
4	Pre-exam fortnight	Full syllabus sweep from notes and error log

You do not need an app for this if you maintain a dated list in your study plan. Mark each topic with the next review date; when the date arrives, test — do not reread first.

Interleaving: mix subjects in one sitting

Blocking three hours on “only polity” trains recognition within one context. Exams mix polity, economy, history and science in one paper. Interleave: forty minutes polity recall, then economy, then science, then back to polity. It feels harder; that difficulty is the point.

For railways and SSC breadth, pair static blocks with the approach in static GK for SSC and railways — short clusters per subject, rotated through the week rather than one subject until “done”.

Build an error log from every mock

Your mocks already show what you cannot retrieve. An error log turns that into revision targets. One running document (notebook or file). For each miss:

The fact or rule you needed (one line).
Why you missed it — never attempted, confused two similar terms, outdated current affair.
Next test — how you will quiz yourself on it in three days.

Rules that make it work:

Include lucky guesses; if you were not sure, it belongs in the log.
Write reasons in your own words, not topic labels only.
Reread the log weekly and add failed items back into your spaced schedule.

This is the same discipline described for quant in many guides; it applies equally to GA and reasoning slips. Pair the log with how to analyse a mock test so review time is structured, not vague.

One-page notes per topic

Long notebooks are hard to revise. For each finished topic, maintain a single dense page: definitions, lists, one diagram or table, and five self-test questions. Economy basics might point to a fuller primer such as Indian economy basics for competitive exams; your one-pager is the extract you will actually re-test from.

If a page grows past one sheet, split into two subtopics. The limit forces prioritisation — what examiners ask repeatedly, not everything in a textbook.

Weekly and pre-exam revision cycles

Weekly cycle (fits alongside a job or college):

New learning on four or five days — small chunks with same-day recall.
One mock or large sectional — timed, exam rules including negative marking strategy.
One analysis block — update the error log; schedule re-tests.
One “revision only” day — no new syllabus; interleaved recall from one-pagers and log.

Pre-exam fortnight:

Shift weight from new topics to log + one-pagers + weak areas.
Daily short retrieval (including daily quiz).
Two or three full mocks with full analysis; stop collecting new resources.

For GA specifically, layer current affairs on top of static notes using general awareness for railway and SSC — static recall daily, affairs in smaller daily doses, both in the interleaved mix.

What to stop doing

Highlighting without testing — colour on a page is not memory.
Revision marathons the night before — they raise anxiety, not stable recall.
Ignoring “easy” static — it is the fastest marks per minute when retrieval is automatic.

Revision is not a moral virtue; it is a schedule of tests at widening intervals, fed by mocks and one-page notes. Build that system once in your study plan and let ordinary bad weeks adjust dates rather than abandoning the whole method.