# How to Use Loksewa Old Questions to Review Your Preparation

> A practical method to organize past questions, track timing, and identify topics to revisit.

Canonical: https://gyanudaan.com/blog/loksewa-old-questions-practice-strategy/
Last updated: 2026-10-07

Language: en
Author: GyanUdaan Team
Published: 2026-02-10
Updated: 2026-10-07

Solving old questions is not revision.

Old questions are a measurement system. If you are only checking right and wrong, you are wasting the most valuable dataset you have.

## What this guide solves

This guide is for candidates who solve many questions but still feel stuck.

Use old papers as a review loop to track:

- speed
- accuracy
- topic prioritization

## What are old questions actually good for?

Old questions help you identify:

- repeated concept families
- actual exam pressure points
- trap patterns in options
- chapters that look easy but leak marks

They do not replace syllabus study, but they tell you where syllabus effort should go.

## The 4-step old question system

## Step 1: Classify

Tag each question by chapter, subtopic, and difficulty.

Without tagging, you cannot see patterns.

## Step 2: Measure

Track accuracy and time per set.

Do this every week using the same format so trends are visible.

## Step 3: Diagnose

Every wrong answer must get one reason code:

- concept gap
- memory gap
- careless error
- time pressure error

If you do not label errors, you cannot fix them.

## Step 4: Repair and retest

Use targeted revision for weak clusters, then retest the same cluster in 3-5 days.

No retest means no proof of improvement.

## The 70-20-10 study allocation

- 70% high-frequency repeated patterns
- 20% medium-frequency topics
- 10% low-frequency long tail

This 70-20-10 split is an optional planning example, not an official distribution or proven formula. Adjust it to the current syllabus and your own results.

## Weekly practice cadence

- Day 1-3: topic blocks
- Day 4: mixed timed set
- Day 5: error review and note compression
- Day 6: weak-topic drill
- Day 7: retest and score comparison

A regular schedule makes it easier to compare practice results over time.

## What we tried that failed

- solving without a timer
- collecting score but not error reasons
- changing question source every few days

These habits can make it harder to notice which topics need more review.

## Known limitations

- old papers may not fully reflect new pattern tweaks
- current affairs coverage still needs separate daily input
- deep conceptual weak areas need textbook-level repair, not only MCQ grinding

## How to apply this today

Start with one recent paper and build your first error log.

Then run this system for two weeks before changing any study strategy.

For daily mobile practice, use:
[GyanUdaan Loksewa app and study resources](https://gyanudaan.com/links/)

## FAQ

## How many years of old questions should I solve first?

Start with recent years first, then go backward only after patterns stabilize.

## Should I review solved questions I got correct?

Yes, especially if you guessed. Lucky correct answers create false confidence.

## What metric should I track weekly?

Track both accuracy and average time per question. Improving one while the other collapses is not real progress.

## Related topics
- [Study plans and practice](https://gyanudaan.com/blog/topics/study-methods/)

## Related

- [Home](https://gyanudaan.com/)