Run a short weekly review of your coursework files

Start from the next week

Look at the official module timetable and assignment information, then list the digital materials needed for the next few tasks. Keep the list concrete: the reading for a seminar, the dataset for a practical or the draft due for feedback. Do not begin by reorganising every file you have ever downloaded.

Open the current version of each active assignment and confirm its location. Note a specific next action so you can resume without rereading the whole draft. If several copies appear equally current, compare them now and identify the authoritative one before more edits create a larger reconciliation problem.

Sort incoming material by purpose

Review recent downloads and attachments relevant to active modules. Move or link permitted material into the approved course location using clear names. Keep the original source details where needed for referencing. An article file called download is harder to use later than one linked to an accurate reference record.

Do not copy restricted material into a personal account for convenience. If an attachment belongs to a group project, place it through the agreed shared workflow and confirm the right people can reach it. Keep unrelated personal receipts or documents out of the coursework folder so the project remains easy to share appropriately if required.

Preserve meaningful milestones

Mark versions that represent a substantive stage, such as feedback received, revised draft or submitted copy. Use the application's supported version history where appropriate and retain required exports separately. Avoid making a new final file for every minor spelling change. Too many undifferentiated snapshots can hide the milestone you actually need.

Keep feedback connected to the draft it concerns. Write a short response plan that identifies the changes to make rather than copying comments into several places. When a revision is complete, check that the feedback has been addressed accurately. A folder label saying reviewed should describe a real action, not an intention.

Check access and pending saves

Look for unresolved sync or upload warnings in the approved storage service. Open essential material through the expected route and prepare any files needed offline using the provider's supported controls. Resolve an account or permissions problem while there is time to contact university support. Do not let a week-old warning become normal background decoration.

If working across devices, confirm the latest draft on the device you will use next. Keep track of unsynchronised offline edits and compare conflicts deliberately. Avoid deleting a conflicting copy before understanding what it contains. The review should reduce uncertainty about the work, not remove inconvenient evidence of a saving problem.

Close with a small action list

Finish with a short list of actual gaps: obtain one missing reading, resolve a software entitlement or ask which dataset version to use. Assign each a next step. Stop reorganising once current work is findable and the next tasks are prepared. The routine should support study rather than consume the time reserved for it.

Retain submitted files and receipts according to course requirements, and review older material at an appropriate term boundary. Additional storage or devices are only relevant to a demonstrated need. A useful weekly review usually consists of a few clear decisions about location, version and next action using the equipment you already own.

Your next steps

• Begin with upcoming course tasks.
• Confirm one authoritative draft per active assignment.
• Keep feedback tied to the correct version.
• Resolve pending saves and finish with concrete next actions.

Keep planning

• Prepare coursework for a journey without dependable Wi-Fi
• Set up group-project files so everyone can work
• Understand OneDrive file status before clearing laptop space
• Reduce a coursework presentation file without losing essential content