How Students Can Organize Notes and Assignments as PDFs

By week six of a semester most students have handouts in a downloads folder, photos of a whiteboard in a camera roll, and a slide deck in an email thread. None of it is lost exactly, but finding a specific diagram the night before an exam takes twenty minutes it should not take.

One folder per module

Resist the urge to build a hierarchy. A folder per module, with everything inside it, is enough — the module code and the week number belong in the filename, not in nested subfolders. CS201-week03-recursion-notes.pdf tells you everything without a single click.

Deal with photographed notes weekly

Whiteboard and textbook photos are the biggest source of drift, because they live in a camera roll rather than a folder. Once a week, crop them, run them through image compression, convert them to a PDF in date order, and name the result. It takes about five minutes per module and turns forty loose images into four findable documents.

1. Crop each photo to the page or board area.
2. Compress the images — a phone photo of a whiteboard does not need eight megapixels.
3. Convert them to a single PDF, keeping chronological order.
4. Name it with the module code, week and topic.

Merge at the end of a topic

When a topic finishes, merge the slides, your notes and the tutorial sheet into one PDF for that topic. Revision then means opening one file per topic rather than assembling context from four sources every time you sit down.

Before you submit

• Check the page count against the brief.
• Confirm the file opens on a device other than the one you made it on.
• Check the file size against the portal's limit, and compress if needed.
• Check the document properties — an exported file may carry a machine account name you would rather not submit.
• Name it exactly as the brief requires. Some portals reject anything else automatically.

A compressed scan can become unreadable at exactly the wrong moment. Open the final file and read one full page before submitting.

Keep it cheap to maintain

The system only survives if the weekly step is genuinely short. Five minutes per module, once a week, is sustainable. An elaborate scheme with tags, colour codes and cross-references is not, and abandoning it halfway through leaves you worse off than never starting.

Conclusion

One folder per module, descriptive filenames, a weekly five-minute tidy, and a merge at the end of each topic. That is the whole system, and it still works in week twelve.