top of page

How to Use UPSC PYQs to Track Your 1-Year Prep Progress

Writer: Exam Marg
Exam Marg
Oct 9
8 min read
A student analyzes a 12-month UPSC timeline and Previous Year Questions (PYQs) at a busy desk with study materials, a phone, and a laptop.

UPSC previous year questions (PYQs) show your progress when you write down your results every time you solve them. Track your accuracy, how many questions you attempt, your time, and the type of mistakes you make. Then compare these numbers with a target for each stage of your year.


Most aspirants solve PYQs and move on. They do not know if they improved since last month. This guide shows what to measure, when to measure it, and how to act on the results.


Why PYQs Are the Best Progress Tracker in UPSC Preparation

PYQs are the only questions that come straight from the exam you will write. This makes them a fair test of where you stand. Coaching mock tests can be easier or harder than the real paper, but PYQs show the real standard.


Here is why they work well for tracking:

  • Same difficulty every time. A paper from 2019 stays the same. If your score rises when you solve it again, you have improved.

  • Trends are visible. Looking across many years shows which topics UPSC asks about often.

  • Wrong options teach you too. Many later questions are built on concepts found in the wrong options of older papers.


PYQs have limits. They cannot test fresh current affairs, and they cannot build the stamina of a full mock test. Use both, but treat PYQs as your main measuring tool.


What to Track: 5 Metrics From Every UPSC PYQ Session

Track five things after every session: accuracy, attempt rate, time, error type, and topic strength. Together they tell you where you lose marks and why. A raw score alone hides all of this.


Accuracy and Attempt Rate

Accuracy is the share of attempted questions you got right. Attempt rate is how many questions you tried out of the total. In prelims, GS Paper I has 100 questions of 2 marks each, and each wrong answer costs one-third of the marks of that question, about 0.67.


Example: you attempt 80 questions, get 60 right and 20 wrong.

  • Marks gained: 60 × 2 = 120

  • Marks lost: 20 × 0.67 ≈ 13.3

  • Final score: about 106.7

  • Accuracy: 60 ÷ 80 = 75%

  • Attempt rate: 80%


If your accuracy is below 60% on attempted questions, guessing is costing you more than it gains.


Time per Question (prelims) and Time per Answer (mains)

GS Paper I gives 120 minutes for 100 questions, so you get about 1 minute 12 seconds per question on average. Record how long a full paper takes and how many minutes you need for the last 20 questions. If you rush at the end, your pace is the problem.


For mains, IAS officer Anisha Shrivastav suggests about 7 minutes for a 10-mark question and 11 minutes for a 15-mark question. Use these as a starting point and adjust to your speed.


Error Type Breakdown: concept gap, factual gap, misread question, guess failure

Mark every wrong answer with one of four labels:


  1. Concept gap: you did not understand the idea.

  2. Factual gap: you knew the idea but forgot a name, date, or number.

  3. Misread question: you missed words like "not," "only," or "incorrect."

  4. Guess failure: you guessed and the guess was wrong.


Each type needs a different fix, so this label matters more than the score.


Topic-wise Strength Map

Group your results by subject: Polity, Economy, Geography, History, Environment, Science and Technology, and so on. Calculate accuracy for each. A simple colour code helps: green above 75%, yellow from 55% to 75%, red below 55%. Update the map once a month.


12-Month UPSC PYQ Tracking Plan (Phase by Phase)

Use PYQs differently in each phase of the year. Early on, they teach. Later, they test. Near the exam, they train speed and nerves.


Phase

Months

What to do with PYQs

What to track

Foundation

1-3

Solve topic-wise PYQs right after finishing each subject

Accuracy by topic, error types

Build

4-6

Finish a full topic-wise cycle; take one year-wise paper as a baseline

Baseline score, weak topics

Consolidate

7-9

Re-solve weak topics; start timed full papers

Score trend, time per paper

Final stretch

10-12

Timed papers plus mocks; revise PYQ-linked notes

Score, attempt rate, errors


Keep the roles clear in your mind. In months 1–3, a low score is normal. You are learning, not testing. In the last phase, topper Saurabh Bhawania advises focusing almost entirely on PYQs, mock tests, and revision of PYQ-linked notes.


When to Start Solving UPSC PYQs and How Many Years to Cover

Start solving PYQs right after you finish each topic, not after you finish the whole syllabus. For coverage, aim for at least the last 10 years of prelims papers, and more if time allows.


Solving a topic's questions right after reading it works like a quick quiz. It shows you what UPSC actually asks from that topic, so you can adjust your reading while it is fresh.


Toppers give different advice on volume. One IAS topper suggests solving a minimum of 5,000 questions before prelims. Another, Anisha Shrivastav, did not solve every question and only worked on the ones she felt a need to. Here is how to choose:


  • Beginners: Solve most questions. You need to learn the style.

  • Repeaters: Skip topics where you are already above 80%. Spend time on red topics.


Papers before 2011 were in a different style, so use them only for extra practice. For timed full papers, the last 10 years are enough. One preparation guide suggests re-solving the last 10 years at least three times before the exam.


Benchmarks: What Is a Good PYQ Score at Each Stage?

A good PYQ score is one that sits comfortably above the prelims cutoff by the time exam month arrives. The cutoff changes every year with paper difficulty, so use a range, not one number.


Only GS Paper I marks decide the prelims cutoff. The General category cutoff was 92.66 in 2025, 87.98 in 2024, and 75.41 in 2023. The 2023 figure was unusually low because the paper was hard. Always check the latest official numbers on the UPSC website.


A safe goal is to score 15 to 20 marks above the likely cutoff. That means about 110 or more in your final phase. The table below shows suggested targets for timed GS Paper I attempts. These are guides, not official numbers.


Stage

Suggested score range (out of 200)

First baseline paper (months 4–6)

60–85

Consolidate phase (months 7–9)

85–100

Final stretch (months 10–12)

105–120+


Do not panic over one low score. A hard year's paper can lower your marks even when you have improved. Look at the average of three papers and the direction of the trend. Also remember the CSAT paper: you need 33% (66 out of 200) to qualify. Solve CSAT papers in the same way and track them in the same sheet.


How to Build a Simple UPSC PYQ Tracker and Error Log

A tracker is a table with one row per practice session. You can make it in a notebook or a spreadsheet. It takes about five minutes to fill after each session and pays off at every monthly review.


Use these columns: date, paper or topic, attempted, correct, wrong, time taken, main error type, and one fix.


Sample rows:


Date

Paper/Topic

Attempted

Correct

Wrong

Time

Main error

Fix

12 Mar

Polity (Fundamental Rights)

20

14

6

22 min

Misread question

Underline "not" and "only"

26 Mar

2021 GS Paper I

82

52

30

125 min

Guess failure

Skip if cannot cut two options



For the error log, add a separate page. For each wrong question, write the correct answer, why you missed it, and one line of the right concept. Do not copy the whole explanation.


Follow this review routine:

  • Weekly: look at the error types and redo wrong questions.

  • Monthly: update the topic strength map and compare against last month.


How to Track UPSC Mains PYQ Progress

Track mains progress by writing real answers to past questions and scoring them against a short checklist. You cannot judge mains by reading alone, so writing practice matters from the middle of the year.


Mains GS papers have 20 questions: 10-mark questions with a word limit of about 150 and 15-mark questions with about 250. Practise within these limits.


After each answer, give yourself a mark out of 5 on:

  1. Structure: introduction, body, short conclusion

  2. Keywords: important terms from the syllabus

  3. Examples: a case, report, data point, or scheme

  4. Relevance: answered what was asked, nothing extra


Suggested frequency: 2-3 answers a week in the first half, then 1 timed paper section a week in the second half. Ask a mentor or friend to review a few of them, as it is hard to judge your own writing. Mains PYQs also show repeated themes, which helps in both exams.


What to Do If Your PYQ Progress Stalls

If your scores stay flat for three or more sessions, look at your error types before doing anything else. The most common error tells you the fix.


  • Mostly concept gaps: Stop solving new papers. Go back to the standard book or notes for those topics, then re-solve the same questions.

  • Mostly factual gaps: Your revision is too thin. Make short notes from the PYQs and revise them more often.

  • Mostly misread questions: Slow down for the first read. Underline negative words and recheck what the question asks.

  • Mostly guess failures: Raise your rule for guessing. Only guess when you can remove at least two options.

  • Time problems: Practise sets of 25 questions in 30 minutes, then build up.


Sometimes the issue is the plan itself. If one subject stays red for a month, give it extra revision hours rather than more questions. Solving more without fixing the cause only repeats the same mistakes.


Common Mistakes When Using UPSC PYQs to Measure Progress

The most common mistake is solving without a review, which wastes most of the learning. Attempting questions without reviewing your mistakes reduces their value. The other mistakes are easy to avoid once you know them:


  • Tracking only the score. Accuracy, time, and error types explain why the score moved.

  • Using only year-wise papers. Topic-wise sets show weak areas better.

  • Starting only in the last months. Use PYQs through the whole year, not only for revision.

  • Memorising answers. Learn why each option is right or wrong.

  • Using one source for papers. Check answers against the official key, because solutions on some sites contain errors.

  • Comparing your score to others. Compare with your own last result.


FAQs About UPSC Previous Year Question Papers


How many UPSC PYQs should I solve in one year?

There is no fixed number. A practical aim is all topic-wise prelims PYQs for the last 10 years, plus 10 full timed papers. Toppers differ on volume, so match it to your level and time.


Are UPSC questions repeated from previous years?

Exact questions rarely repeat. Topics and concepts repeat often, and sometimes a wrong option in one year becomes the main question in another.


How often should I re-solve PYQs?

Re-solve wrong questions within a week, and revisit each topic once every month or two. Redo full papers at least two or three times across the year.


Should I solve PYQs before completing the syllabus?

Yes, but topic by topic. Solve a topic's PYQs right after you read it. Save full timed papers for the middle of the year.


How do I track CSAT progress with PYQs?

Solve CSAT papers on a fixed schedule, such as one every two weeks. Record your marks, time, and weak areas. Your goal is to stay safely above the 66-mark qualifying line.


Is a PYQ book enough to clear prelims?

No. PYQs show what UPSC asks, but you still need standard books, current affairs, and mock tests. Use the PYQ book to guide what you study.


How do I know my preparation is on track?

Check three signs: your score trend over the last three papers is rising, your red topics are getting fewer, and your repeat errors are going down. If all three improve, you are on track.


Conclusion

PYQs help only when you measure them. Log accuracy, attempt rate, time, and error types, then compare them with phase targets and the recent cutoffs.


This week, take one full prelims PYQ paper in exam conditions as your baseline. Set up your tracker, record the result, and review your errors. That first row gives you a starting point to improve from.

Comments


bottom of page