- Foundation
- About 15 min
- 5 practice questions
Your first realistic weekly plan and how to review it each Sunday
Put the earlier steps together into one weekly timetable with a focused-hours budget per subject, then review planned against done and change one thing each week.
If something looks wrong, please tell us.
This lesson joins everything into one working plan and then adds the step most students skip: the weekly review. A first timetable is never perfect. What makes it work is checking it every week and making one sensible change at a time, so that after a month the plan fits your life closely.
Eight steps to a first weekly plan
- Keep a time log for a few days (lesson 1).
- Work out fixed and free hours, and set desk time at about two-thirds of free hours (lesson 2).
- Choose slot lengths and breaks, and work out how many focused hours your desk time gives (lesson 3).
- Split the focused hours between subjects, giving more to weak or important ones.
- Place subjects into slots with rotation (lesson 4).
- Keep a small weekly review slot inside the plan.
- Write each slot's task in specific words, such as 'Ratio: 25 questions'.
- Put the timetable where you will see it every day.
Worked example 1: Meena's first plan
Meena (lessons 2 and 3) set 2.5 desk hours on weekdays and 5 on weekend days, 22.5 hours a week. On weekdays her 150 minutes give 120 focused minutes. On weekend days she plans 300 minutes with 60 minutes of breaks, giving 240 focused minutes. Focused hours = 5 x 120 + 2 x 240 = 600 + 480 = 1,080 minutes = 18 hours.
She splits the 18 hours. Quantitative aptitude is weakest, so it gets the most.
| Subject | Focused hours per week | Main slots |
|---|---|---|
| Quantitative aptitude | 6 | Early Pomodoros on Mon, Wed, Fri and most of Saturday |
| Reasoning | 4 | Early Pomodoros on Tue, Thu and Sunday morning |
| English | 4 | Later Pomodoros on Mon, Wed, Fri and part of the weekend |
| General Studies | 3 | Later Pomodoros on Tue, Thu and part of the weekend |
| Weekly review and planning | 1 | Sunday evening |
| Total | 18 |
Check: 6 + 4 + 4 + 3 + 1 = 18 hours, equal to her focused total. Desk time stays 22.5 hours; the other 4.5 hours are breaks.
The weekly review
Once a week, ideally at the same time, fill in a small table: planned hours, hours done, and the reason for any gap. Then work out your completion rate = hours done / hours planned. A rough guide: if you keep finishing well below about three-quarters of the plan for two weeks running, the plan is too heavy or badly placed, so reduce or move slots. If you finish everything easily week after week, add a little. Change one thing at a time so you can see what helped.
Worked example 2: Meena's first review
| Subject | Planned (h) | Done (h) | Reason for gap |
|---|---|---|---|
| Quantitative aptitude | 6 | 5 | Saturday morning started late |
| Reasoning | 4 | 4 | |
| English | 4 | 2.5 | Thursday: family function |
| General Studies | 3 | 1.5 | Phone during evening Pomodoros |
| Review and planning | 1 | 1 | |
| Total | 18 | 14 |
Done: 5 + 4 + 2.5 + 1.5 + 1 = 14 hours. Completion: 14 / 18 = 0.78, about 78%. That is a good first week. Looking at reasons, the clearest pattern she can control is the phone in the evening. One change: the phone stays in the kitchen during evening Pomodoros. She also notes that the family function was a one-off, not a pattern, so she does not redesign the plan around it.
Compare Rohit, who planned 35 focused hours when his free hours were only 25 and finished 12 hours (12 / 35, about 34%). His problem is not discipline but arithmetic: the plan was bigger than his week. His one change is to rebuild the plan from his free hours.
Plan, do, review, change one thing. A timetable is a draft you improve every week.
Key takeaways
- Build the plan from the log, free hours, slot lengths and subject needs, in that order.
- Budget focused hours per subject and check the total matches what your desk time gives.
- Review weekly: planned, done, reason, completion rate.
- Look for patterns you can control, not one-off events.
- Change one thing at a time; reduce a plan that keeps failing rather than blaming yourself.
Check your understanding
-
1. Meena's weekday session gives 120 focused minutes and each weekend day gives 240. How many focused hours is that in a week?
- 15 hours
- 18 hours
- 22.5 hours
- 20 hours
Show answer
Answer: B. 5 x 120 + 2 x 240 = 600 + 480 = 1,080 minutes = 18 hours. 22.5 is her desk time including breaks.
-
2. A student planned 20 focused hours and did 15. What is the completion rate?
- 66%
- 80%
- 133%
- 75%
Show answer
Answer: D. Completion = done / planned = 15 / 20 = 0.75 = 75%.
-
3. What should a weekly review end with?
- One specific change to try next week
- A completely new timetable every week
- A promise to study twice as long
- Nothing; the review is only for recording
Show answer
Answer: A. The review finds a pattern and makes one change, so you can see whether it helped. Rebuilding everything or doubling hours makes it impossible to learn what works.
-
4. Rohit planned 35 focused hours but had only 25 free hours and completed 12. What is the main problem?
- He chose the wrong subjects
- He needs longer breaks
- His plan was larger than the time he had
- His review slot was too short
Show answer
Answer: C. 35 planned hours cannot fit into 25 free hours, so the plan was bound to fail. He should rebuild it from his free hours.
-
5. In Meena's week 1, which reason for a gap is a one-off rather than a pattern?
- Using the phone during evening Pomodoros
- A family function on Thursday
- Starting late on Saturday mornings
- Skipping GS whenever it is in the last slot
Show answer
Answer: B. A family function happens once; she should not redesign the plan around it. The others repeat and can be fixed by a change in the plan.
Sign in to keep track of the lessons you finish.