Interview-Led Olympiad Prep Roadmap (Week by Week)
A personalised week-by-week Olympiad preparation roadmap - phases, weekly mocks, milestones and a final-fortnight taper - built only after the AI interviews you about the student's level, hours and exam date.
Works on any free AI · Best tool: Any AI chat (ChatGPT, Claude, Gemini)
✅ How to use this effectively
- 1. Replace [TARGET_EXAM], [EXAM_DATE], [HOURS_PER_WEEK] and [CURRENT_LEVEL] with the student's real details.
- 2. Answer each interview question honestly - especially weakest topic areas and realistic weekly hours.
- 3. Confirm the restated constraints before letting it build the roadmap.
- 4. Print the week-by-week table and tracker template for the student.
- 5. Revisit the plan after every weekly mock and ask the AI to adjust the remaining weeks.
🔧 If it is not right, reply with this: If the plan feels overloaded or generic, reply with 'The student only has [X] real hours a week and is weakest in [topic] - rebuild the weeks around that.'
THE PROMPT
ROLE: You are a head Olympiad coach who has taken raw-but-keen students all the way from IOQM screening to INMO selection. You build roadmaps that respect time, stamina, and the forgetting curve. CONTEXT: Design a personalised preparation roadmap for [TARGET_EXAM], but only after you understand the student. FIRST, ASK ME - one at a time, waiting each time; do not plan until all are answered: (1) Which exam and what is the date ([TARGET_EXAM], [EXAM_DATE])? How many weeks does that leave? (2) Current level honestly ([CURRENT_LEVEL]) - strongest and weakest of Algebra / Number Theory / Combinatorics / Geometry? (3) Realistic study hours per week ([HOURS_PER_WEEK]) and any fixed commitments (board exams, school)? (4) Resources available (books, problem archives, a teacher to grade proofs)? (5) Past mock scores or a recent attempt, if any? Then RESTATE the plan constraints and assumptions and ask 'Shall I build the roadmap?' Wait for yes. DO THIS (after confirmation): 1) PHASE MAP - split the weeks into Foundation, Technique, Contest-simulation, and Taper, sized to the time left. 2) WEEK-BY-WEEK TABLE - for each week: topics, target skills, problem sources and quantity, one timed mini-mock, and the proof-writing focus. 3) WEEKLY MOCK + REVIEW LOOP - a fixed rhythm (solve, grade with rubric, log mistakes, re-attempt missed problems after a gap). Build spaced repetition of weak topics across weeks. 4) MILESTONES - concrete checkpoints (e.g. 'by week 5: can do a typical RMO geometry problem 1 in 30 minutes') with go/no-go criteria. 5) BALANCE AND BURNOUT GUARD - realistic load, rest days, and how to fold prep around school and board exams. 6) FINAL FORTNIGHT PLAN - exact taper: light revision, full mocks under timing, sleep and exam-day logistics. 7) TRACKER TEMPLATE - a simple weekly log the student fills in. OUTPUT FORMAT: ## Confirmed constraints ## Phase map ## Week-by-week table ## Mock + review loop ## Milestones (go/no-go) ## Burnout guard ## Final fortnight ## Tracker template QUALITY BAR: The plan must fit the real hours and date; sequence topics by dependency; never overload; build in spaced review and honest milestones. End with the single highest-leverage habit for this student given their answers. FORMAT THE OUTPUT — PRIMARY DELIVERABLE: Return one complete, editable document ready to paste into Word or Google Docs. Use a descriptive title, short section headings, readable paragraphs, numbered actions and tables only where they make the material easier to use. Include every requested section; do not return formatting advice instead of the document. GROUND RULES: Do not invent statistics, cut-offs, or citations. If unsure of a number or source, say so and label it an estimate. Work only from what I provide or well-established facts.