How to Review Notes Effectively

Effective review is not rereading the notebook until every line looks familiar. If you already have lecture notes, a useful session has two jobs, and they are not the same.

First, repair the notes while you still remember what the lecture meant: expand the abbreviation, restore which example belonged where, and turn a heading into a question you can answer later.

Second, retrieve from those notes with the page covered. Produce the idea from a cue, then uncover the page to check. Come back later and do that again.

Rereading, highlighting, and recopying neatly can all feel like studying. They can produce familiarity without testing whether you can recall the ideas. When the notes are in front of you, the ideas feel known. Covering the page and trying to produce the idea is a better check of what you will still have later.

Retrieval practice tends to support longer-term retention better than extra rereading of the same material. That does not make rereading useless for a first pass or for checking after an attempt. It does mean a review session that never leaves the page is a weak test.

You do not need a new note-taking system. You need a session that owns the lifecycle: after class, later, and in exam week.

What reviewing notes actually is

Reviewing notes means using the notebook as a source to test against, not as a script to read.

A real review produces evidence: you tried to reconstruct a mechanism, a distinction, or a definition without looking, then you checked.

A false review produces a feeling: the page looks highlighted, the handwriting is neater, you have seen every heading from the top.

In a survey of 177 Washington University undergraduates, rereading notes or the textbook was the most commonly reported study strategy; relatively few reported self-testing as a primary method. That sample is not “all students worldwide.” It is a useful picture of the default habit.

Reading from the top

Opening the notebook at lecture one and reading down the page is restudying. Recognition is easy when the next sentence is visible. It is a poor guide to what you can produce tomorrow.

Highlighting as the session

A major review of study techniques rated practice testing and spaced practice as high-utility. Rereading and highlighting, though popular, were rated low-utility as primary methods. Highlighting can mark what you will test later. It is not the test.

Recopying verbatim

Copying the lecture into a prettier notebook is usually extra rereading with a pen. You are looking at the source the whole time.

Reorganizing in your own words can help — condensing, grouping, turning headings into questions — if the rewrite ends with the original closed and a self-test. If the session ends when the new copy looks tidy, you recopied. You did not review.

Two jobs: repair the notes, then retrieve from them

These jobs get mashed into one sitting called “reviewing my notes.” They fail for different reasons.

Repair is a notes problem. After a lecture, LDR / CC and a half-drawn diagram still make sense. Two days later they often do not. A same-day pass is useful because lecture context fades quickly — abbreviations, which example belonged where — not because 24 hours is a magic memory number. Useful spacing depends on how long you need to remember the material. A same-day pass is often valuable for repairing notes.

Retrieve is a memory problem. Once the notes are usable, the question is whether you can produce the ideas without looking. That is retrieval practice with notes, not another read-through. The technique depth lives there; here it is one job inside a session.

Repair without retrieval leaves a clean notebook you still cannot speak from. Retrieval from broken notes tests a garbled source. Sequence them.

How to run a review session

One sitting, one bounded unit. Not the whole notebook.

1. Bound the unit. One lecture, one section, or one mechanism. Messy 12-page weeks are normal. Review the photosynthesis lecture, not “all of biology.”
2. Name the job. Are the notes still a capture problem, or are they good enough to test against?
3. Do that job.
   • Repair: fill gaps, restore examples, turn headings into questions. Do not write the answers next to the cues. Then do a short recitation of the main points with the page covered.
   • Retrieve: cover the notes, use a cue, produce the idea (speak, write, or sketch), uncover, and check.
4. Judge the attempt, not the page. Did you produce the idea, produce it with holes, or only recognize it once it was visible? Recognition after uncovering is not the same as recall.
5. Decide the next action. Fix the note. Return later. Stop. Do not immediately reread the whole unit to soothe a miss. Check the failed part, then leave.

In experiments with study passages, generating and answering questions outperformed rereading. You do not need a huge homemade question bank if a few good cues exist. A heading can work; a question is usually sharper. “Photosynthesis” is a weak cue. “How do the light-dependent reactions differ from the Calvin cycle?” is a better one. Leave the answer in the notes, not in the cue column.

If you already have some context, asking why an idea is true can deepen a review. It is not a substitute for trying to retrieve the idea.

After class, later, and exam week

Same notebook. Different session. Use one running example: Tuesday’s biology lecture on photosynthesis. Your notes say PS = plants make sugar, LDR / CC, H2O → O2, ATP+NADPH → Calvin.

After class: repair, then a short recitation

Spend the pass on capture.

Expand the abbreviations into ordinary lecture-note language. PS becomes plants making sugar. LDR and CC become light-dependent reactions versus the Calvin cycle. H2O → O2 becomes oxygen coming from water. ATP+NADPH → Calvin becomes those products being used to fix carbon.

If the page is thin — you wrote LDR / CC and cannot reconstruct the lecturer’s example — that is information. The after-class pass is when you notice a capture problem, while you can still ask a classmate, check the slide, or add the missing example. Waiting until exam week to discover that the notes never contained the mechanism is too late.

Turn the headings into questions. Do not recopy the lecture into a second notebook as the whole session.

Then cover the page and recite the three or four main points. Fix what you missed on the note itself. This recitation can be short. Its job is to confirm the repaired notes are usable, not to finish learning photosynthesis.

Later reviews: retrieval first

When you return — the next day or later in the week — do not start by reading from the top.

Cover the notes. Use a cue: “Explain light-dependent reactions versus the Calvin cycle.” Produce it. Uncover.

Maybe you remember both names and mix up which one is where oxygen comes from water. That miss is the session. Correct it. Do not reward yourself with a full reread of Tuesday’s lecture.

Reviewing across several sessions usually beats doing all the reviewing at once. Exact intervals are not one-size-fits-all. For how to space returns without turning every page into a flashcard, see spaced repetition for notes. The forgetting curve is a reminder that one successful retrieval does not guarantee you will still be able to produce the idea later; it is not a schedule.

If a few cues exist, use them. If they do not, the title of the lecture is enough to start talking, then check.

Exam week: diagnose misses

Exam week is not the time to start at page one of the notebook.

Use the cue list — or lecture titles — as a diagnostic. Produce. Check. The units that fail are the work. Reread only the failed parts, then cover again.

Rereading the entire stack produces familiarity and a false sense that you have “seen this.” You want a list of ideas you still cannot produce: what LDR and CC distinguished; what H2O → O2 and the ATP/NADPH line were capturing.

Cramming everything into one long reread is the opposite of this. Several shorter retrieval sessions tend to beat one marathon pass over the same pages.

Cornell recitation: Recite, not the boxes

Cornell notes become a review system when you cover the notes and answer from the cue column. The printed layout alone is not the method.

Record can happen in class. Reduce (cue questions) and Recite are the review. If you filled the left column with questions and then reread the right column, you used Cornell paper to restudy.

Cornell’s advice to spend a short weekly pass on older notes is instructional guidance, not a measured effect size. Use it as a reminder to return, not as a law.

You do not need Cornell paper to recite. Cover any notes. Use headings or questions as cues. Produce. Check. You can also space those returns without flashcards.

When rereading still helps

Rereading is the right tool when you do not yet have something to retrieve, and when you are checking after an attempt.

First encoding. If the lecture did not land, you need to understand the page before you can test it. Read to encode. Then close it and try.

Checking after a failed retrieval. Uncovering the note after a miss is how you correct the gap. That is rereading in the service of a test, not instead of one.

Repair. Reading your own messy notes in order to rewrite a garbled line is capture work.

What usually does not help as the whole session: another top-to-bottom pass because the page looks important.

Common mistakes

Calling familiarity a review. The page looks known. You have not produced the idea.

Verbatim recopying. Neatness is not recall.

Highlighting as the work. Marks are cues for later. They are not later.

Reading from the top every time. Especially in exam week.

Writing answers next to cues. The cue column becomes a cheat sheet.

Reviewing the whole notebook as one unit. Bound it.

Skipping the after-class repair. Later you will test notes that no longer make sense.

Treating a same-day pass as the only review. Repair is not a substitute for returning later.

How Yuhimo fits this workflow

Yuhimo keeps the page as the unit. A lecture note can stay a normal page. Learning is optional: you can turn a page into a learning page when you want it to return, not because every note must be memorized.

Reviews are built for the retrieve job: you usually see the page title, review questions, and answers if they exist; try to recall first, then reveal answers or open the original page to check. Questions are optional cues. Yuhimo does not auto-grade. You assess your own recall as Forgot, Barely, Remembered, or Easily. Yuhimo uses that rating to schedule the next review; the ratings are scheduling signals, not scores.

That matches the session architecture: the note remains the source; the attempt is yours; Yuhimo schedules the next visit from your self-assessment. The after-class repair still happens on the page itself — expand the abbreviation, add the missing example, turn a heading into a question — before you treat the page as something to retrieve.

How long should a review session last?

Long enough to finish one bounded unit with a real attempt. Stop when you have repaired the page and recited it, or when you have retrieved, checked, and decided the next action. A session that keeps going because there are more pages to reread is the habit this article is replacing.

Do I need to turn my notes into flashcards?

No. Recitation uses the notes you already have. Cards can help when you need many small, precise items. They are not a requirement for reviewing lecture notes.