·8 min read

How to study for an exam in a week (a day-by-day plan)

Listen to article 8:22

If you're wondering how to study for an exam in a week, the good news is that it's very doable. It's not ideal, and you won't walk in knowing every detail, but seven well-used days are enough to pass almost any course you've more or less kept up with in lectures. What doesn't work is the week most of us try the first time: rereading from slide one and realizing on Thursday that we're only halfway through.

The trick is to split the week by task, not by page count. One day to figure out what's on the exam, three days to understand the material, one day to practice under exam conditions, one day to review what went wrong, and the last day to show up rested.

Here's the plan I use as a final-year computer engineering student, with a real example: an Operating Systems midterm covering eight topics and about three hundred lecture slides.

Day 1: map out the exam

You don't study on day one. You build the map, and it's the day that saves you the most time.

  1. Get all your material in one place. Every lecture's slides, your notes, the problem sets and, if they exist, past papers. If something's missing, ask for it today, not on Thursday.
  2. Figure out what's actually on the exam. The syllabus, what the professor said in the last lecture, any study guide they posted. Cross off what isn't covered, guilt free.
  3. List the topics. In my case: processes, threads, scheduling, synchronization, deadlocks, memory, virtual memory and file systems.
  4. Color-code each one. Green if you already get it, yellow if it rings a bell but you couldn't explain it, red if you have no idea. Be honest: this list is for you.
  5. Spread the topics across days 2, 3 and 4. Reds and the heaviest topics first, mixed with a green here and there so you're not fighting all day.

If there are past exams, look at them today even if you can't solve them yet. They tell you what kind of questions the professor asks and how much each topic is worth, and that changes how you study everything else.

Days 2 to 4: one full pass, for understanding

These three days are the core of the plan. The goal is to get through every topic once, understanding it, not memorizing it. Two or three topics a day, depending on how heavy they are.

For each topic, the same routine:

What to avoid: highlighting everything, rewriting slides neatly, or making gorgeous summaries. It feels productive and it isn't. In a week, there's no time for things that only feel productive.

A week is enough if you spend every hour trying to recall or understand, not watching slides go by.

Day 5: practice like it's the real exam

On day five you stop looking at the material and start pulling it out of your memory. It's the hardest day and the one that pays off the most: the testing effect (trying to recall something instead of rereading it) is one of the most solid findings about how we learn.

By the end of the day your color list should look different. Whatever's still red is what you study tomorrow.

Day 6: review what you missed, not everything

The temptation on day six is to reread everything from the start "just to refresh." Don't. Rereading what you already know feels reassuring, but it's time stolen from what you don't know.

Coming back to a topic after a few days, instead of cramming it all at once, is what makes it stick. That's why what you covered on Tuesday gets reviewed on Saturday, not left for 3 a.m. the night before.

Day 7: the day before the exam

The last day is for consolidating, not learning new things. If a topic you've never seen shows up now, it's better to let it go than to steal hours from your sleep.

How to structure each day

A plan is useless if every day slips away between your phone and hour-long breaks. Here's what works for me:

If you fall behind midweek, don't cut day 5 or day 6. It's better to cover one topic fewer in depth and practice than to skim everything and walk in without having answered a single question.

A tool for studying from slides

Almost all my course material comes as slide decks, and days 2 to 4 were always the slowest: three-word slides I had to rebuild on my own. That's why I built Filmina, an app that explains your lecture slides and PDFs out loud, slide by slide, pointing at the part of the page it's talking about. And for day 5 it has Practice: questions on what you've already studied that level up or down depending on how you're doing, and come back over the following days. It's all in practice and review. It runs in your browser, on any computer or phone.

Without any app, the plan works just the same: what matters is how you structure the week, not the tool.

Frequently asked questions

Is one week enough to study for an exam?

For most exams, yes, as long as you've roughly kept up with the course and use all seven days well. If you've never seen the material or the course is huge, a week is enough to pass but not to master it.

How many hours a day should I study the week before an exam?

It depends on the course and on what you already know, but four to six hours of real studying a day is a good range. More hours don't help if they're spent rereading: what matters is how much of that time you spend trying to recall or solve problems.

What if I fall behind on my study plan?

Cut topics, not practice days. Pick the topics that carry the most weight and show up most in past papers, study those properly, and leave the rest for a quick pass if you have time.

Should I review everything the day before the exam?

No. The day before, review only what you got wrong and what you can't forget, then get a good night's sleep. Rereading everything feels reassuring but does little, and showing up tired costs you what you already knew.

Keep reading

·7 min

How to use past papers to study (not just read them)

How to use past papers and old exams: when to start, how to sit them under real conditions, what to log from every mistake and what they can't tell you.

Start with
just one slide

Drop in that PDF you've been putting off and hear it explained. Thirty seconds is enough to know whether it's for you.

No card · In the browser, nothing to install