Open-Book Exam Prep: Build a Tabbed Index From Your YouTube Lectures

Published 2026-10-05 · Francesco Masciopinto

"It's open-book" sounds like good news until you're forty minutes into the exam, flipping through a stack of printouts, and you still haven't found the slide where the professor explained the exception that question 6 is clearly about. Open-book exams rarely test whether you own the material. They test whether you can find, apply, and cite it under time pressure. If most of your course lives in YouTube lectures, the material is scattered across hours of video, and video is the worst possible format to search mid-exam.

The fix is not more notes. It's an index: a short, tabbed document that turns "I know this was covered somewhere" into "Topic C, row 4, page 11, lecture 7 at 23:40." This article walks through building one from a semester of YouTube lectures in a few focused sessions.

Why open-book exams go wrong

Students who do badly on open-book exams usually make one of three mistakes:

They bring everything. Full transcripts, every slide deck, three textbooks. More material means slower lookup, and lookup speed is the real bottleneck.
They study less. "I can look it up" becomes an excuse to skip review, so they don't know what to look up or recognize which concept a question is pointing at.
They organize by lecture, not by question. Notes sorted "Lecture 1, Lecture 2, Lecture 3" mirror how the course was taught, not how the exam asks. Exam questions cut across lectures.

An index fixes all three. It forces you to decide what's worth bringing, it makes you review while you build it, and it's organized around the questions you expect, not the order the videos were uploaded.

What goes into the index

Think of the index as a routing table. Each row answers: if a question looks like this, where do I go? A good row has five fields:

Field	Example
Trigger (what the question will say)	"elasticity", "% change in quantity"
Core claim or rule (one line)	Price elasticity = %ΔQ / %ΔP; elastic if magnitude > 1
Where it lives in your notes	Notes p. 11, box 3
Lecture source + timestamp	Lecture 7, 23:40
Trap or exception	Use midpoint formula when the problem gives two prices

The trigger column matters most. Exams rarely say "apply concept X." They describe a situation. Your triggers should be the words and setups that signal a concept, which is exactly what you hear your instructor emphasize in the lecture.

The timestamp column is a backup, not the main path. You probably won't be rewatching video during a timed exam, and many exams ban devices anyway. It's there for the study phase, when a row feels thin and you need to go back to the source before the exam.

Step 1: Map the exam's scope before touching a video

Start with whatever the instructor gave you: the syllabus, a list of exam topics, past papers, or a review-session recording. Write down 6–12 topic tabs. These become the top-level sections of your index. If the course has past exams, skim them and note how questions are phrased. That's your raw material for triggers.

Don't skip this. Without scope, you'll index everything evenly and end up with a forty-page "index" that's just your notes again.

Step 2: Pull the structure out of each lecture

Now go through the lecture playlist, but don't rewatch at full length. For each video you want three things: the chapter structure (what's covered and when), the key claims (definitions, rules, formulas, named frameworks), and the emphasis moments where the instructor says "this is important," "people always get this wrong," or "this will be on the exam."

This is where an on-page summarizer saves real hours. A tool like SummarizAI sits next to the YouTube video and gives you a summary with timestamped chapters while the lecture stays on screen. You can skim the chapter list, click into the two or three sections that matter for your tabs, and copy the timestamps straight into your index rows. Whatever tool you use, check the generated summary against the video for anything you'll rely on. A summary is a map to the lecture, not a replacement for it.

For each claim you pull out, ask: which topic tab does this belong to? Drop it into that tab as a rough row. Don't polish yet.

Step 3: Write triggers, not titles

Go back through each rough row and rewrite the first column as a trigger: the phrase or situation a question would use. Compare:

Title: "Lecture 5: Consumer surplus"
Trigger: "area under demand curve", "willingness to pay minus price", "welfare effect of a price ceiling"

One concept can have several triggers. Write them all. During the exam you'll scan the trigger column for words that match the question in front of you, so the more realistic the phrasing, the faster you'll land.

A good source of triggers is the lecture itself. Instructors repeat their own phrasing on exams far more than students expect. If the professor kept saying "the binding constraint," that's a trigger.

Step 4: Add the trap column

Every topic has a predictable mistake: the sign error, the exception to the rule, the case where the default formula doesn't apply. Lectures are full of these, usually flagged with "careful here" or a worked example that goes wrong on purpose.

Put each one in the trap column. On an open-book exam, the question that costs you points is rarely the one you can't find. It's the one where you found the rule and applied it without spotting the exception. A one-line reminder next to the rule catches that.

Step 5: Cross-reference your physical materials

If your exam allows printed notes or a textbook, add page numbers to every row and tab the physical pages with sticky flags in the same colors as your index tabs. The point is a two-hop lookup: question, index row, page. Never more than that.

If the exam is digital and allows files, use the same structure in a single document with a linked table of contents. Avoid relying on Ctrl+F alone. You'll search for the word the question uses, and your notes may use a different one, which is exactly why the trigger column exists.

Step 6: Stress-test the index with timed questions

An index you haven't used under time pressure is a guess. Take a past paper or practice questions and do them only through the index: read the question, find the row, go to the page, answer. Time each lookup.

Watch for three failure signals:

No matching trigger. Add one, phrased the way the question was.
Row found, but the note is too thin to answer. Go back to the lecture timestamp, rewatch that segment, and strengthen the note.
Lookup took over a minute. Your tabs are too broad. Split the topic.

Two rounds of this usually cut lookup time in half, and you'll notice you need the index less each round. That's the hidden benefit: building and testing it is studying.

A realistic schedule

For a course with 20–30 hour-long YouTube lectures, a workable plan looks like this:

Session 1 (60–90 min): Scope and tabs from the syllabus and past papers.
Sessions 2–4 (90 min each): Pull chapters, claims, and emphasis moments from the lectures, about 8–10 videos per session using summaries and targeted rewatching.
Session 5 (60 min): Rewrite triggers, add traps, add page numbers.
Sessions 6–7 (60 min each): Timed stress tests and fixes.

That's roughly eight to ten hours spread over a week or two, far less than rewatching the course, and you walk in with a tool built for exactly how the exam works.

Common questions

How long should the index be? Aim for 2–5 pages. If it's longer, you're copying notes rather than routing to them.

Should I include full worked examples? Only as pointers ("worked example: notes p. 14, Lecture 9 at 31:05"). Full solutions belong in your notes, not the index.

What if the exam allows only one cheat sheet? Same process, but stop at Step 4 and compress the core-claim and trap columns onto the sheet. The trigger thinking still helps you recognize what each question wants.

The takeaway

Open-book exams reward the student who can get from a question to the right rule in under a minute and apply it without falling for the trap. Organize your YouTube lectures around how questions are asked, not how videos were uploaded, and test the index before the exam does.

If your course lives on YouTube, SummarizAI can speed up the extraction step with on-page summaries and timestamped chapters, so you spend your time building the index instead of scrubbing through video.

Frequently asked questions

How long should the index be?

Aim for 2–5 pages. If it's longer, you're copying notes rather than routing to them.

Should I include full worked examples?

Only as pointers ("worked example: notes p. 14, Lecture 9 at 31:05"). Full solutions belong in your notes, not the index.

What if the exam allows only one cheat sheet?

Same process, but stop at Step 4 and compress the core-claim and trap columns onto the sheet. The trigger thinking still helps you recognize what each question wants.

Related guides

Try SummarizAI on your next lecture

SummarizAI is a Chrome extension that adds a summary, chapters, and Study flashcards on the YouTube watch page. The free plan is a student trial—no need to leave the lecture tab.

Start the free student trial

Students · Closed-book quiz · Install