Slides, photos of the whiteboard, handwritten pages and reading excerpts — scattered across your phone and laptop — into one organized, searchable semester PDF. A system you set up once and reuse for every course.
One PDF per course per semester, in lecture order. Start with a cover page (course code, course name, term, your name), then a one-page contents list of lecture titles, then one section per lecture: the slides for that lecture, your notes for that lecture, and any reading excerpt for that lecture — in that order. Add page numbers throughout, and finish with a final page of your own summary notes. That single file is what you revise from, what you search, and what you back up. The raw material — individual slide decks, phone photos, loose scans — stays in a separate archive folder, untouched, so the organized file never becomes a dumping ground.
Fact: PDF is an ISO 32000 open standard, which is why a PDF made today opens identically on a phone, a library computer and a professor's laptop decades from now. That durability is exactly why lecture notes belong in PDF rather than in a proprietary note app that can change format, paywall your export, or vanish. Your semester's work deserves a format that outlives the app you made it in.
The discipline is the system: fifteen minutes after each lecture beats a panicked weekend of sorting before exams, because the context is still fresh and the gaps are still visible. A missing lecture shows up immediately as a gap in the sequence — and a gap you notice in week 5 can still be filled from a classmate, while a gap you notice in exam week cannot.
Handwriting is the weak point of any notes PDF: a scan of handwriting is a picture, not searchable text, so searching for "monetary policy" finds nothing even when the words are on the page. The fix is cheap: add a short typed summary page at the start of each lecture section, listing the lecture title, the key terms and one line per major point. That page makes the whole section findable by text search, and writing it doubles as a first revision pass. Keep the summaries honest — three to five lines per lecture, not a rewrite of the notes — or the system collapses under its own weight by week 4.
For diagrams and formulas, photograph at good light and keep the original photo in your archive; the PDF page can be a compressed version. If a diagram is central to an exam topic, add a typed caption under it in the summary page ("Figure: IS-LM shift after a tax cut") so the search finds it too. Over a semester, these small captions become the index of your own textbook.
A semester of notes scanned at 300 DPI in colour can easily pass 200 MB — too big to email, slow to open on a phone, and painful to back up. The fixes, in order: scan handwriting in greyscale (colour only where it carries meaning), photograph at 200 DPI for whiteboard shots, and compress the merged course file with a PDF compressor before the exam period. Aim for a course file you can email to yourself and open on any device — tens of megabytes, not hundreds.
Backups follow the same rule as everything academic: two copies, in two places. Keep the organized course PDF in your cloud drive and on a USB stick or second device, and keep the raw archive (original photos and slide decks) somewhere separate. If a merged file is ever corrupted, the archive rebuilds it in an afternoon. And when study groups share notes, share the organized file, not the raw folder — your classmates get a usable document, and your messy originals stay private.
Most online PDF tools want your documents on their servers — and lecture notes are personal: your handwriting, your annotations, sometimes your student ID on a cover page. A browser-only tool merges, reorders, numbers and compresses on your device, so none of that ever leaves the tab. The check is simple and worth doing once: open the Network tab, run the tool, and watch whether anything uploads. With ours, nothing does. Our safety guide walks through the check. For a student, that privacy is not abstract — it is the difference between your notes living on your laptop and living on a stranger's server.
One PDF per course per semester, in lecture order, with a cover page naming the course and term, page numbers throughout, and a short contents list at the front. That single file replaces a folder of loose slides, photos and handouts.
Yes, in lecture order: the slide deck for the lecture, then your handwritten notes for that lecture, then the reading excerpt. Grouping by lecture beats grouping by format, because revision follows lectures, not file types.
A scan alone is a picture, not searchable text. Add a short typed summary page at the start of each lecture section with the key terms, so the file is findable by search even when the handwriting itself is not machine-readable.
Scan or photograph notes at 200–300 DPI in greyscale where colour is not needed, then compress the merged PDF. A full semester of notes should compress to a file you can email or store on a phone without worry.
Course code, then term, then topic: for example ECON101_Fall2026_Lecture05_MonetaryPolicy.pdf. The pattern sorts itself alphabetically, and you can find any lecture without opening a file.
One per course per semester is the best balance: small enough to open fast and share, large enough that revision does not mean hunting through dozens of files. Keep the per-lecture files as your raw archive, and the merged course file as the one you actually revise from.
Slot them into the same lecture position in the merged file, and mark the section 'borrowed notes — verify'. Gaps in the sequence are worse than imperfect notes, because a missing lecture breaks the revision flow for the whole topic chain.