Three weeks before exams, most revision plans collapse into the same activity: rewatching recordings at 1.75x while highlighting a document. It feels like work. It produces the sensation of familiarity, which the brain is happy to mistake for knowledge right up until the moment someone asks a question.
Revision is not one task. It is at least three, and they need different materials.
The three jobs
Orientation — knowing how a module fits together, so individual facts have somewhere to live.
Reference — a written record you can search and reread without scrubbing a timeline.
Retrieval — being asked questions and having to produce answers, which is the part that actually moves material into memory.
Most students build only the second one, then wonder why rereading it six times did not work.
Building a pack, per lecture
About ten minutes each, on any recording with captions. Paste the URL at xyzyoutube.com — or type xyz in front of it — and run three formats on the same video.
Mind Map first, for orientation. Two minutes. You are looking for the branch structure, not the detail. Do this before you read anything else, because the map is what the detail will attach to.
Lecture Notes second, for reference. Headings, sub-points, definitions. This is the document you will actually revise from. It took a minute instead of an evening.
Q&A pairs third, for retrieval. Open questions, no multiple-choice options to recognise. These go into Anki or Quizlet and get reviewed on your phone between now and the exam.
Do this for twelve lectures and you have an afternoon's work and a complete revision system — one that is stronger than what most people produce over three weeks, because it includes the part everyone skips.
Sequencing across the term rather than cramming
The pack is more valuable if it exists in week three than in week ten. Two habits make that realistic:
Generate notes the same day as the lecture. It takes a minute, so there is no reason to defer it. The record exists while your memory of the session is still fresh enough to spot anything the transcript garbled.
Take the quiz cold, a week later. Not right after the lecture, when everything is still in working memory. A week later, when forgetting has begun and retrieval is actually difficult. Difficulty is the mechanism. See generating a quiz from any video for why the timing matters.
Pulling several lectures together
Near the exam you want one document per topic rather than one per lecture. The practical move is to generate notes for each relevant recording and then merge them by theme in whatever tool you use — the output is plain text specifically so it drops into Notion, Obsidian, or Docs without fighting you.
At that stage, the mind maps are useful a second time: comparing the maps of four lectures shows you which concepts recur across the module, and concepts that recur are what gets examined.
Filtering the reading list
Not everything on a supplementary list deserves a study pack. Bullet Points tells you in two minutes whether a video adds anything the textbook did not, so you can spend your ten-minute packs on the four videos that matter instead of the fourteen that were suggested.
Two things to watch
Auto-captions mangle technical vocabulary and numbers — exactly the content that carries marks in a science module. Skim generated notes for anything that reads wrong and check it against the recording.
And notes reflect what was said, not what was drawn. Derivation-heavy lectures where the lecturer narrates loosely over a whiteboard produce thin notes. That is the transcript being honest, and those sessions still need watching.
Pick the module you are most behind on and build one pack tonight. Map, notes, questions. Start here.