When three documents are called “final,” choosing a file becomes a memory test. A course filing system should answer two questions quickly: what is this document, and what stage has it reached? Start with the files you use this week. Reorganizing several years of downloads can wait.
Create one folder for the term and a folder within it for each course. Use names that you will recognize later, including a course code if it is helpful. Avoid an elaborate numbering scheme you cannot remember. The folder should still make sense when it appears in a search result outside its original location.
Separate instructions from your work
Keep the assignment brief, marking guidance and related course instructions together. Record where the current official version lives, especially if staff may update it. A downloaded copy is useful for reference, but check the course platform before relying on an old deadline or a detail that may have changed.
Give a substantial assignment its own folder. Inside, separate source material from working drafts and the copy actually submitted. The exact folder names are your choice. What matters is that a reference PDF cannot easily be mistaken for your own writing and a submitted file cannot be silently replaced by a later experiment.
For short weekly tasks, a simpler arrangement may be enough. One folder with dated filenames can work better than twenty nearly empty subfolders. Choose the smallest structure that makes retrieval dependable. Add a level only when a real ambiguity appears.
Name the draft before you edit it
A filename such as “history-map-commentary-2026-10-14-draft” says more than “essay-new.” Put the assignment name first and use a consistent date format when dates matter. Avoid relying on a file’s last-modified time to explain its status; copying or exporting can make that timestamp less informative.
If you work with other students, agree on names and a shared location before exchanging drafts. Use the platform’s revision tools where appropriate and confirm that everyone understands which document is current. Do not send a separate copy merely to avoid learning the agreed workflow; that copy may later reappear as competing work.
Keep a brief note when a filename alone cannot explain a version. “Changed the example after seminar; conclusion still needs checking” gives you a starting point next time. This note belongs in your private working materials, not automatically in the document you submit.
Close the loop at submission
Export the required format and open the exported file. Check that pages, images and text appear as intended. Follow the course’s submission instructions, then retain the confirmation or receipt it provides. Do not assume a file is submitted because it exists in a synchronized folder.
Keep an exact copy of the submitted version in its own location. If you revise it afterward for another purpose, make that distinction explicit. Store feedback with the related assignment so you can connect a comment to the work it describes instead of remembering only a grade.
At the end of term, archive the course folder and retain what you are permitted and need to keep. Remove redundant downloads only after checking that the useful originals and submissions remain available. Test your backup arrangement by opening a file from it. A tidy folder that exists in only one fragile location has not finished the job.