A weekly timetable can look organised and still produce very little improvement.
Monday is assigned to Quantitative Aptitude, Tuesday to English, Wednesday to Reasoning and Sunday to a mock test. The candidate completes every scheduled activity, but the mock reveals the same calculation errors, uncertain General Awareness attempts and unfinished sections as the previous week.
The missing element is feedback.
A useful SSC CGL study plan should not contain seven unrelated study days. Each day should prepare for, respond to or verify the results of another day.
The following routine uses PYQs to diagnose weaknesses, focused practice to repair them and a full mock to check whether the corrections work under pressure.
Table of Contents
Set One Measurable Goal for the Week
Begin by reviewing your latest test report or previous paper.
Choose one main performance goal, such as:
- Reduce incorrect General Awareness guesses.
- Complete Quantitative Aptitude within the applicable section time.
- Improve English accuracy from 78% to 85%.
- Stop spending too long on arrangement questions.
- Reduce calculation mistakes.
- Improve vocabulary recall.
- Complete every section without panic.
A goal such as “study more maths” is too broad.
Your weekly target should describe a visible change in test behaviour.
Monday: Use PYQs to Diagnose the Problem
Monday should establish what deserves attention.
Select recent, year-wise SSC CGL PYQs from one or two priority areas. Avoid solving a complete historical paper unless you need an overall baseline.
For each question, record:
- Topic
- Correct or incorrect response
- Time taken
- Method used
- Reason for the error
- Whether the question should have been attempted
Classify incorrect responses as:
- Concept gap
- Recall gap
- Slow method
- Careless execution
- Poor question selection
- Uncontrolled guess
Finish Monday by choosing the two weaknesses that caused the greatest score or time loss.
Tuesday: Repair the Underlying Concepts
Tuesday is not another testing day.
Return to the exact rule, method, formula, vocabulary area or General Awareness topic connected with Monday’s errors.
Keep the task specific.
Instead of writing:
Revise percentages.
Write:
Review successive percentage change, compare the direct and base-value methods, and solve eight relevant questions.
Instead of:
Improve English.
Write:
Review subject–verb agreement errors and solve fifteen sentence-correction questions without changing answers casually.
End the session with a short closed-book recall test. The purpose is to check whether the concept can be produced independently.
Wednesday: Complete a Timed PYQ Section
On Wednesday, combine authentic questions into a timed sectional set.
Use the latest applicable SSC timing rules rather than the original timing from an old paper. Historical questions remain valuable, but obsolete time conditions should not shape current strategy.
During the section, practise one behavioural rule:
- Leave a problem when no clear method appears.
- Avoid a General Awareness attempt unless the answer is known or sensible elimination is possible.
- Do not change an English response without a specific grammatical reason.
- Check signs and units before submitting a calculation.
- Start with quick, familiar Reasoning questions.
After the timer ends, record attempts, accuracy and unfinished questions.
A timed section reveals whether Tuesday’s revision works when mixed with other topics.
Thursday: Analyse the Section and Build a Repair Queue
Thursday converts Wednesday’s result into action.
Use a table such as:
| Error | Cause | Repair Task | Retest |
| Two geometry questions unfinished | Method too slow | Compare shorter methods and solve five PYQs | Friday |
| Three GA answers incorrect | Guessing | Tighten attempt threshold | Saturday |
| English answer changed incorrectly | Low decision confidence | Review rule and apply no-change condition | Saturday |
| Reasoning set took too long | Poor exit decision | Practise two timed sets | Friday |
Do not revise every incorrect topic equally.
Prioritise weaknesses that:
- appear repeatedly,
- cost several marks,
- consume excessive time,
- affect multiple question types,
- or create negative marking.
Thursday should finish with three clear tasks, not a long list of worries.
Friday: Retest Without Looking at the Solutions
Return to selected errors after a short delay.
First, reattempt the original questions without opening the answer explanations. Then solve a few fresh questions requiring the same concept or decision.
A correction is reliable only when you can:
- recognise the method,
- solve without a hint,
- stay within a reasonable time,
- and avoid the original mistake.
When the same question still goes wrong, do not hide it inside another full paper. The concept or strategy needs further repair.
Friday should be a moderate study day. Preserve enough energy for the complete mock.
Saturday: Attempt a Full Current-Pattern Mock
Saturday is the main simulation day.
Choose an SSC CGL Mock Test that reflects the current official structure, timing and marking rules.
Attempt it in one uninterrupted sitting.
During the mock:
- Follow the timer strictly.
- Do not consult notes.
- Apply the question-selection rules practised during the week.
- Avoid emotional guessing after a difficult section.
- Record any section that feels unusually easy or difficult.
- Treat the mock as a test of the week’s corrections.
The objective is not merely to beat the previous total score.
Ask whether the specific weekly goal improved.
Did uncertain attempts fall? Was Quant completed? Did the same grammar error return? Were fewer answers changed without reason?
Sunday: Analyse, Recover and Plan Again
Sunday should contain two separate stages.
Stage One: Detailed Analysis
Review:
- Total score
- Section-wise accuracy
- Incorrect attempts
- Unattempted questions
- Time problems
- Questions answered correctly through guessing
- Repeated weaknesses
- Corrections that worked
Do not review only the red answers. A lucky correct answer can hide an unresolved weakness.
Stage Two: Light Recovery and Planning
After the analysis, reduce the study intensity.
Update the error log, select the following week’s main target and organise the required PYQ sets. Avoid forcing another full mock into the same day.
This lighter block helps keep the routine sustainable.
A predictable sequence also supports reducing exam uncertainty through regular paper practice. When testing, reviewing and correction happen in a familiar order, the mock becomes a routine learning activity rather than a weekly judgement.
Keep Daily Maintenance Short
The main daily task should receive most of your attention, but a few areas benefit from frequent short review.
Add:
- 15–20 minutes of vocabulary
- 20–30 minutes of current affairs or General Awareness revision
- 10 minutes of calculation practice
- brief formula or rule recall
These maintenance blocks should not replace the day’s main purpose.
Monday is still diagnostic. Tuesday is still corrective. Saturday is still the full-test day.
Weekly Schedule at a Glance
| Day | Main Purpose | Recommended Activity |
| Monday | Diagnose | Topic-wise or mixed PYQs |
| Tuesday | Repair | Concept revision and drills |
| Wednesday | Rehearse | Timed PYQ section |
| Thursday | Analyse | Error classification and repair queue |
| Friday | Retest | Delayed reattempt and fresh questions |
| Saturday | Verify | Full current-pattern mock |
| Sunday | Review | Mock analysis, recovery and next-week plan |
This schedule starts with one full mock each week.
Candidates in the final preparation phase may add another full mock, but the additional test should not remove analysis and correction time.
Adapt the Plan for Working Aspirants
A working candidate may have only two or three focused weekday hours.
Use this compressed version:
Monday to Thursday
- 60 minutes: main PYQ, revision or sectional task
- 30 minutes: error analysis
- 20 minutes: General Awareness
- 15 minutes: vocabulary or formulas
Friday
Complete the delayed retest and organise Saturday’s mock.
Saturday
Take the full mock and complete an initial review.
Sunday
Perform detailed analysis, revise the largest weakness and plan the next week.
Avoid copying a full-time candidate’s seven- or eight-hour schedule. A shorter routine completed consistently is more useful than an extreme timetable abandoned after ten days.
A Realistic Weekly Scenario
Consider Ravi, a working aspirant whose Quantitative Aptitude score remains low.
On Monday, he solves recent arithmetic PYQs and discovers that percentages are accurate, but time-and-work questions take too long.
Tuesday is used to compare methods and solve six basic questions.
On Wednesday, Ravi completes a timed Quant section. He gets the time-and-work questions right but spends too long on one geometry problem.
Thursday’s review shows that question selection, not arithmetic knowledge, is now the larger issue.
On Friday, he practises leaving questions when no clear method appears.
During Saturday’s full mock, Ravi’s total score rises by only three marks. Yet he completes Quantitative Aptitude and avoids two lengthy questions that would previously have consumed his section.
The week has worked.
The total score may improve more slowly than the underlying decisions, but those decisions are what eventually stabilise performance.
Avoid the Most Common Weekly Mistake
The most common mistake is treating the Saturday mock as the end of the week.
Candidates check the score, compare the rank and begin an unrelated topic on Monday.
That breaks the feedback loop.
The mock should determine:
- which PYQs are selected,
- which concept is revised,
- which strategy is rehearsed,
- and which error is retested.
Without that connection, the next week may repeat the previous one under a different timetable.
Use a Simple Weekly Dashboard
Track five indicators:
| Indicator | What to Look For |
| Accuracy | Is it stable or improving? |
| Incorrect attempts | Are guesses and careless errors falling? |
| Section completion | Can every section be handled within its timer? |
| Repeated errors | Are corrected mistakes returning? |
| Retest success | Can revised questions be solved independently? |
Rank can provide context, but personal trends should guide weekly study decisions.
Frequently Asked Questions
Is one full mock per week enough?
It is a practical starting point while the syllabus and weak areas are still being developed. Increase the frequency closer to the examination when every test can still be analysed properly.
Should PYQs be solved every day?
Short PYQ sets can be used frequently, but they should have a clear purpose. Avoid solving random historical questions merely to increase the count.
Where should current affairs fit into the plan?
Use a short daily review block and one weekly consolidation session. Do not allow General Awareness notes to replace timed question practice.
What should happen after a poor mock score?
Identify the largest concept and strategy losses. Select related PYQs, revise those areas and complete a sectional retest before taking another full mock.
Can the same schedule be used for Tier II?
The diagnose–repair–verify structure remains useful, but the subjects, sessions, depth and applicable timing should be adjusted to the current Tier II scheme and the candidate’s target posts.
Let One Week Teach the Next
A useful timetable does more than divide seven days into study blocks.
Monday should respond to the last mock. Saturday should test the corrections made during the week. Sunday should decide what happens next.
When every paper changes the following study decision, the timetable stops being a calendar and becomes a preparation system.
