Build a Study Plan

You turn a goal and a deadline into a weekly plan the learner can actually follow: every topic covered, the most time on what matters most and is weakest, reviews spaced out so learning lasts, and slack for real life. The plan is built from the official syllabus and the learner's honest timetable, and it changes every week based on what they can actually do.

When to use

• "Make me a study plan for [exam / course]."
• "I have 12 weeks until my [exam]. Where do I start?"
• "I want to learn [skill] in my spare time."
• "I keep falling behind. Help me get organised."
• Start of a term or course.

What you need

• The goal: exam or qualification name, board or institution, level, date; or the skill and what "good enough" looks like by when.
• The official syllabus or specification and any weightings or assessment objectives. Find them on the exam board's or institution's site with web_search and web_extract; do not rely on memory for what is examined.
• The learner's timetable: school, work, travel, sport, family, sleep. Their calendar through the Google Calendar connected app, or ask with clarify.
• Current level: recent marks, mock results, teacher feedback, or a short diagnostic quiz (see also make-practice-questions).
• Resources they have: textbooks, class notes, course platform, past papers.
• For a child: agree the plan with the parent or guardian (the owner) as well as the learner.

Method

1. Fix the target and the date. Write the goal in one line with the date and the grade or standard aimed for. Confirm exam dates on the official timetable.
2. Break the syllabus into topics. 15 to 40 topics for a typical course, each small enough to study in 1 to 3 sessions. Record each topic's exam weighting where the specification gives it, or its share of the course.
3. Rate each topic. The learner rates confidence red, amber or green (or 1 to 5). Check the ratings against evidence (quiz results, past marks) because self-ratings are often too high.
4. Count real hours. Hours available per week after commitments, sleep and rest. Plan to use about 80 percent of them; life interrupts. A plan that needs every free evening fails in week two.
5. Allocate time. Priority = weight x weakness. Red, heavily weighted topics get the most sessions; green topics still get reviews. Use the calculator in references/plan-calculator.md. If the total exceeds the hours available, tell the learner and the owner which topics will get lighter coverage, or extend the time; do not silently squeeze.
6. Design sessions. 25 to 50 minutes of focused work, then a short break. Each session: 5 minutes of retrieval on an earlier topic first, then the new material, then a few practice questions without notes. Hard topics go at the time of day the learner concentrates best.
7. Schedule spaced reviews. After first learning a topic, review it at growing intervals: roughly 1 day, 3 days, 1 week, 2 to 3 weeks, then monthly. Reviews are short self-tests, not rereading.
8. Interleave. Once a few topics are learned, mix practice across them so the learner has to choose the method, not just repeat the last one.
9. Add buffers and checkpoints. One lighter week every 4 to 6 weeks to catch up; a short checkpoint test every 2 to 3 weeks; past papers in the final third of the plan.
10. Put it in the calendar. With approval, add sessions through the Google Calendar connected app, or produce an .ics file (code in references/plan-calculator.md). Set a cronjob for a weekly check-in.
11. Review weekly. What got done, what slipped and why, checkpoint results, then adjust next week. Re-rate topics after each checkpoint. Save progress in memory.

Learning methods to build in

Use the methods with the strongest evidence, and steer the learner away from the weakest:

• Practice testing (self-quizzing, past questions, flashcards) and spaced practice were rated the most useful techniques in a large review of learning research (Dunlosky and colleagues, 2013).
• Interleaving and elaborating (asking why and how, explaining to someone) help next.
• Rereading and highlighting feel productive but were rated low usefulness. Allow them only as a first pass.
• Worked examples help beginners in procedural subjects; fade them as skill grows.

Output

• One-page plan summary: goal, date, hours per week, topics by priority.
• Topic table: topic, weight, confidence, sessions allocated, first-study week, review dates.
• Week-by-week calendar (and the .ics file or calendar entries once approved).
• Session template.
• Weekly check-in template. Put the summary and this week's sessions on a show_card. Template in references/plan-calculator.md.

Checks before you finish

• Topics come from the official, current syllabus.
• Planned hours fit within about 80 percent of real availability.
• Every topic is scheduled at least once plus reviews.
• Weak, heavy topics get more time; the allocation is visible.
• Buffers, checkpoints and past papers are scheduled.
• Calendar entries were added only after the learner (and owner, for a child) agreed.

Pitfalls

• Perfect-week planning. Plans that assume full energy every day collapse. Leave slack.
• Equal time for everything. Spend more on what is weighted heavily and is weak.
• Front-loading new content with no review. Without spaced reviews, early topics are forgotten by the exam.
• Rereading as revision. Replace it with self-testing.
• Ignoring rest and sleep. Sleep matters for memory; never schedule study by cutting it.
• Plans nobody revisits. The weekly check-in is what keeps the plan real.