| Block | When | Length | One job |
|---|---|---|---|
| Early morning — protected | before work | 90–120 min | new material (the current topic) |
| Commute | both ways | 20–60 min | revision, on your phone |
| Lunch | midday | 15–20 min | one short PYQ set |
| Evening — second block | after dinner | 60–90 min | writing · feedback · revision |
A realistic UPSC study plan for a working professional is 3–4 focused hours on weekdays and 6–8 hours on each weekend day — roughly 25–35 hours a week, with one weekend evening completely off.
The weekday structure that survives contact with a real job: a protected early-morning block before work, revision on your phone during the commute, a short PYQ set at lunch, and one honest evening block. Weekends carry the heavy lifting.
And the route through the syllabus is one loop, run topic by topic — map the topic, learn it, practice its questions, write from it, get it evaluated, revise it — side by side, before moving to the next. There are no phases. Prelims and Mains grow together from your very first topic.
That's the whole answer. The rest of this post is the detail: the hour-by-hour template, the loop, what to cut, and what to do on the weeks when work detonates.
Fewer than the mythology says. Start with the feeling behind the question, because every working aspirant has done this arithmetic at midnight: others study ten hours a day; I have three. How is this ever supposed to work?
Here is how. The "10 focused hours a day" figure is mostly a myth even for people with empty calendars; nobody sustains it for a year. A widely used planning estimate puts a serious preparation cycle at somewhere around 1,200–1,500 focused hours; nobody can measure this precisely, so treat it as a compass, not a contract.
At around 30 hours a week (which the structure below delivers), that's roughly 10 to 12 months of preparation. The arithmetic works. It just doesn't forgive waste.
Which means the question worth asking is "how do I stop leaking the hours I have?" Three focused hours retain more than nine distracted ones, because the exam tests understanding and recall under pressure, and both are built by focused repetition.
The plan below optimises for focus density. Each block has one job.
Here is the weekday template, assuming a roughly 9-to-6 job. Shift the clock to fit yours; keep the structure.
Early morning: the protected block (90–120 min). This is your deep-work slot, and it is non-negotiable in a specific sense: nothing else is allowed to book it, meetings and "quick" email checks included. This is where new material gets read: your current topic in the loop, learned properly.
Morning, because it's the slot no meeting can reach and your willpower hasn't been spent yet. If 5:30 sounds brutal, start at 6 and take 90 minutes. The time matters less than the protection.
Commute (20–60 min). The commute is where most aspirants doom-scroll current affairs and call it study. Flip it: this is revision time, on your phone. Yesterday's topic, last week's topics, quick recall of what you've already learned.
Revision is the highest-leverage activity in this exam and the one that fits worst into desk time, so give it the slot that's worst for desks. (This is the gap BLOOM's visual notes were built for: 144 live GS1 topic notes designed to be revised on a phone in stolen minutes instead of re-read at a desk.)
Lunch: one short PYQ set (15–20 min). Skip the reading and the videos: ten to fifteen previous-year questions on whatever topic you're currently in the loop with, attempted honestly, with one line noted about what you got wrong and why.
Prelims is a coverage exam, not a cleverness exam: most questions simply test whether you know the thing outright, and daily low-friction retrieval builds that kind of fast, sure recall. Twenty minutes at lunch, most working days, compounds into a permanent PYQ habit. The Arena has all 1,300 real PYQs from 2013–2025, organised for this kind of daily set.
Evening: the second block (60–90 min). After dinner, one more focused block. This is where the loop's writing step usually lives: an answer outlined or written from memory on the topic you're studying, or evaluated feedback acted on, or revision. Be honest about your evening energy. If you're useless after 9:30, do 60 minutes and sleep.
A shorter block you complete beats a longer one you fight through at half attention.
Then stop. Sleep is part of the plan: recall is consolidated during sleep, and a professional running on six hours is quietly giving away marks.
Weekends are where a working aspirant's week is won, so treat them accordingly: 6–8 hours on Saturday and 6–8 hours on Sunday (12–16 hours across the weekend), with one evening of the two kept completely off.
We won't hand you a fixed weekend timetable, because your weekend is yours: family, errands, and rest all have claims on it, and a plan that pretends otherwise dies in week three. What we will give you is the shape that the hours need to contain:
Long deep-work blocks. The weekend exists for what 90-minute fragments can't do: the dense chapters, full topics learned end to end, a complete pass through a topic's PYQs, full answers written properly. Run your loop hard here; a working aspirant can often take a whole topic from map to written and evaluated inside a single weekend.
One consolidation stretch. Somewhere in the weekend, revisit everything the week touched: the topics, the wrong answers from your lunch sets, the feedback on your written answers. This is where the week's fragments become one piece of knowledge.
Timed practice as coverage grows. Once you have a stock of topics behind you, weekends are where full-length timed PYQ papers and mocks enter, attempted under exam conditions and then analysed for longer than they were attempted.
A short planning close (15–30 min). Before the weekend ends: what moved this week, and what are next week's topics and blocks? Look at your work calendar while you do it. If Thursday is meeting-heavy, declare it a light day now, and the week won't shatter when Thursday arrives.
One evening completely off. No syllabus, no guilt. The off evening is load-bearing: this exam is a long endurance event, and the most common way working aspirants lose is burning out after weeks of seven-day grinding. The off evening is the guard against it.
Arrange these however your life allows. The non-negotiables are only three: the hours are real (6–8 per day, counted honestly), the deep blocks are unbroken, and the one evening off happens.
One loop, run topic by topic. No phases.
Most plans you'll find split preparation into stages (months of reading first, then questions, then tests, then revision). We think that route quietly builds the working aspirant's worst nightmare: a year of consumption, with the scary parts (questions, writing, being evaluated) postponed to a future that keeps receding.
If you've ever closed a finished book feeling productive and then gone blank in front of an answer sheet, you know the gap we mean. The route created that freeze, and the route can remove it.
So BLOOM's route is different. The whole syllabus is segregated into topics (GS1 alone is 144 live, more rendering), and every topic runs the complete loop before you move on:
Map it. Read the syllabus lines and the real PYQs of the topic first, before studying it. Ten minutes of this tells you the topic's true shape: how deep UPSC actually goes and what it repeatedly asks. You start oriented instead of anxious.
Learn it. One source, one honest pass. Not perfect: understood well enough to explain to a colleague.
Practice it. The topic's MCQs and PYQs, the same week — while the material is warm and the questions can still teach you how UPSC thinks about it.
Write from it. At least one answer or outline, produced from memory. This is the step most plans postpone and the one the exam most rewards, because Mains pays for what you can produce. DOJO exists to make this step small enough to happen — guided, from a single line upward, never from a terrifying blank page.
Evaluate it. Honest marks on what you wrote, and one concrete fix carried into the next answer. This is PRISM's job: the truth about your answer, delivered kindly enough that you'll come back for more of it.
Revise it. Spaced returns on your phone (the commute, the queue, the ten minutes before bed) until recall of that topic is fast and boring.
Which topic first? Your choice. We deliberately do not prescribe an order.
The exam record (our PYQ analysis) tells you which subjects carry the most weight, and that's useful information for choosing. But the order is yours, because a route you chose is a route you'll keep. What is not optional is the loop itself: whatever topic you pick up, it goes through all six steps before it's called done.
Notice what this route does for you structurally. Prelims and Mains grow together from topic one; there is no month in your preparation where you haven't written anything, because writing lives inside the unit of study.
A working professional's plan is defined less by what's in it than by what's been cut. Three cuts, all uncomfortable, all correct. Each one is hard for a reason, because the anxiety underneath it is real.
Cut multiple sources. The fear says: the other book has something extra. It does. It's not worth your hours.
Each added source resets your revision count toward zero, and it is revision count that the exam rewards. Roughly three-quarters of Prelims comes from the static syllabus that standard sources cover; depth of retention beats breadth of exposure almost everywhere. One source per subject, revised until it's boring, then revised again.
Cut note-making perfectionism. Beautiful, comprehensive notes feel safe and study badly. Make notes only where they compress (formulas, timelines, confusable pairs, your own recurring mistakes), keep them ugly and short, or use notes already engineered for fast revision and spend your hours on recall instead. If your notes are longer than the chapter, you've made a second book you now also can't finish.
Cut current-affairs hoarding. The 40-page compilations, the six saved videos: a backlog you're going to "catch up on." Hoarding feels like preparation and functions as postponement. Current affairs matters, but it's a fraction of the paper against a static core that's roughly three-quarters of it.
One source, about 30 minutes a day inside your commute-plus-lunch time, one consolidation sitting a month. Delete the backlog. The backlog was never going to be read, and carrying its guilt costs more than its content was worth.
It will. A release, a client escalation: some weeks the hours simply do not exist. And this is the moment that decides more preparations than any book choice, because of what usually follows: miss three days, feel the guilt, conclude the plan has failed, abandon it entirely.
The plan didn't fail. It just had no fallback state.
So build one in: the minimum viable day — 45 minutes. When work detonates, you drop to this, with zero guilt:
| Piece | Minutes |
|---|---|
| Revision, on your phone | 20 |
| PYQs, one small set | 15 |
| Current affairs, one source | 10 |
| Minimum viable day | 45 |
That's it. Nothing new gets added, and you don't try to "make up" the lost hours later; making up is a myth. The deficit is gone, let it go. The point of the minimum viable day is only partly the 45 minutes of learning, though the recall practice is useful.
Its main job is keeping the thread unbroken: in a long campaign, the difference between "I studied every day, some days lightly" and "I stopped for two weeks in March" is enormous. Momentum, once fully lost, costs weeks to rebuild. Forty-five minutes is the price of never losing it.
Two rules govern the fallback.
Hours logged won't tell you. Three checks, monthly:
If you'd rather not assemble the machinery yourself (phone-first revision notes, daily sets from the 1,300-question PYQ bank, a guided writing path, honest evaluation), that's the gap BLOOM's programs were built to fill, by someone who ran this structure alongside a full-time job. But the structure above works with any tools.
What it can't survive without: the protected morning, the daily PYQs, the answer written from every topic, and the one evening off.
The plan is not impressive. That's deliberate. Impressive plans are abandoned by week six; this one is designed to still be running in month fourteen, which is the only metric that matters.
⬇ The working-week planner (PDF)
Did this leave a question open? Tell us. We reply, and the best questions quietly improve this page. No comment section, no audience — just correspondence.
Write to us