30% off your first 3 months

Get the deal

Reviewing a whole semester for a cumulative final

by DuckyHelperNov 12, 20265 min read
Exam prep

TL;DR:

  • Start with the big ideas, not the chapter list. A semester usually reduces to about five.

  • Review each idea twice in spaced passes, and use old tests and quizzes as practice material.

  • Finish with timed mixed practice so you can tell which idea a problem belongs to.

A cumulative final covers a whole semester, which feels impossible to review. Fifteen chapters, hundreds of pages, and a vague sense that you knew it all in October. The mistake is trying to review chapter by chapter. The better move is to compress the semester into a few big ideas and review those.

Why big ideas first

Chapters are how the book is organised, but exams ask how things connect. If you can say that forces explain motion, and energy offers a shortcut when forces get messy, you can place almost any problem. A student who sees five big ideas has hooks for the details. A student who sees fifteen chapters has fifteen piles.

What you need

  • The syllabus or table of contents.

  • Old tests, quizzes and homework, with your marks.

  • Two weeks, ideally, and a calendar.

  • Paper for a one-page map.

The steps

  1. Make the map: Skim the syllabus and your notes. Write the semester as about five big ideas, each with two or three key tools.

  2. Rate each idea: Use old tests: which ideas cost you marks?

  3. First pass: one idea per day: Rebuild the idea from memory, then do problems from old work.

  4. Second pass: mixed and spaced: Return to each idea a few days later with different problems.

  5. Finish with timed mixed practice: Do whole old tests or a mix, under time, and mark what is weak.

Worked example: mapping a semester into five big ideas

A first-semester physics course. The textbook has many chapters, but the semester reduces to five ideas.

Big idea

Key tools

1. Describing motion

Position, velocity, acceleration; the constant-acceleration equations; graphs

2. Forces explain motion

Free-body diagrams; ΣF = ma; friction; tension

3. Energy is a shortcut

Work; kinetic and potential energy; conservation; power

4. Momentum and collisions

p = mv; impulse; conservation in collisions

5. Circular motion and gravity

a = v²/r; centripetal force; orbits

Each idea is something you could explain in a minute.

Now the two-week plan. Days 1 to 5 are the first pass, one idea per day. Days 6 to 10 are the second pass, with different problems. Days 11 and 12 are timed mixed tests. Days 13 and 14 are light: sleep, a short skim of the map, and rest. That is 5 + 5 + 2 + 2 = 14 days.

Days

What

Minutes per day

1 to 5

First pass: rebuild one idea from memory, then redo old problems

60

6 to 10

Second pass: the same ideas, new problems, plus the idea you missed most

45

11 to 12

Timed mixed practice with an old test, then mark it

90

13 to 14

Light: read your one-page map, rest

30 or less

The study time, leaving the light days aside, is 5 × 60 + 5 × 45 + 2 × 90 = 300 + 225 + 180 = 705 minutes, or 11 hours 45 minutes over twelve days. That is under an hour a day, which is far easier to keep up than a weekend of cramming.

Inside a first-pass session on idea 3, say, you close the notes and write what energy conservation says and when to use it. Then you redo two or three old problems on it, including one you lost marks on. Mark the gaps. The second pass returns to energy with a problem that mixes it with forces, because the final will.

How to rebuild an idea from memory

For the first pass, take a blank page and write the idea's title. Without opening anything, write what it says, the tools that belong to it, and a tiny example. Then compare it with your notes in a second colour. What you missed is the review. That ten minutes will teach you more than reading the chapter again, and you can see how much is left to do.

Do the same for the connections: how does idea 2 lead to idea 3? In this course, energy conservation is what you reach for when the forces vary along a path and the force method gets messy. Writing links like that is what turns a list of ideas into a map.

Using old tests well

Old tests show how your teacher asks questions. Do them without notes, in the time allowed, and mark them strictly. Sort each miss under a big idea. If most of your misses sit under one idea, that idea gets extra time in the second pass.

If you do not have old tests, write your own questions from the map, or use the end-of-chapter problems in the book that mix topics.

If something is brand new to you

Sometimes the review shows a topic you never really understood. Do not let it sit. Go back to the original explanation, do two or three basic problems, then rejoin the plan. If it is a large gap, use your light days for it, or ask your teacher in office hours, using the stuck-step method from how to ask a good question in class or office hours.

Mistakes to avoid

  • Reviewing in chapter order and running out of time before the last chapters.

  • Reading notes over and over instead of testing yourself.

  • Doing every old problem. Pick the ones that cover your weak ideas.

  • Skipping the mixed practice, so you cannot tell which tool a problem needs.

  • Starting too late for the spacing to work.

Your plan for this week

  1. Make the one-page map of big ideas today.

  2. Rate each idea against an old test.

  3. Schedule the 14 days, even if only on paper.

  4. Do day 1 tomorrow.

Frequently asked questions

What if the course has more than five ideas?

Use six or seven. The point is to group chapters under ideas you can explain, not to hit an exact number.

What if I only have a week?

Compress the plan: one pass per idea, then two mixed tests. See also the ten-day plan in finals week: a plan for the last ten days.

Get started

DuckyHelper can
do more

It sees your screen and works in any app you use. Try it for 10 minutes, no card.

Get it for Mac, Windows or Linux

Share

Questions and jobs

Do anything

Ask it a question or hand it a job, in any app.

Doing jobs for you is in early access on Mac. Asking works on Mac, Windows and Linux.