How to Make an Exam Revision Plan You Can Actually Follow

Write down the exam date, the format, the topics it covers, and any official weighting or guidance. Then look at what else is already in your week before you start filling the calendar. Time-management research links planning habits like these with better performance and well-being [1]. Your plan still has to fit your own course and your own life.

Sample your starting point

Try a few typical questions from across the syllabus. Mark which topics you can already explain, which need practice, and which you haven't studied yet. One unusually hard question doesn't tell you much about a whole subject. Use the sample to decide where extra effort will pay off most.

Come back to each topic more than once

Give important topics more than one slot in the schedule. Research on distributed practice supports coming back to material over time [2]. With two weeks to revise, you might learn or clarify a topic early on, practise it later, and go back over your mistakes just before the exam. Keep some time unscheduled for the things that turn out harder than expected.

Turn topics into sessions

In FocusCrew, add tasks such as "solve four probability questions and check the method." Use next actions so each session is easy to start, and a Pomodoro study session when a fixed block of time helps you focus. Let the task and the time you have decide how long a session runs.

Revise the plan as you learn

After each session, note what needs another attempt. Once you know how long things really take, update your estimates. Don't cram missed work into every evening. If the schedule stops fitting, drop optional work and ask your tutor what to prioritise.

References

1. Aeon, B., Faber, A., & Panaccio, A. (2021). Does time management work? A meta-analysis. PLOS ONE, 16(1), e0245066. Read the article.
2. Cepeda, N. J., Pashler, H., Vul, E., Wixted, J. T., & Rohrer, D. (2006). Distributed practice in verbal recall tasks: A review and quantitative synthesis. Psychological Bulletin, 132(3), 354–380. Read the article.