How to Organize Your Course Files Using Google Drive

Open Google Drive and create a new folder. Name it with your course title and the year -- something like "Mindful Movement Foundations 2026." The year matters because you may run this course again with updated content, and you want to tell the versions apart at a glance. This master folder is the single container for everything related to this course. Nothing lives outside it.

Inside the master folder, create one subfolder for each module. Name them with a number prefix: "01 -- Foundations," "02 -- Core Practice," "03 -- Teaching Live Sessions," and so on. The number prefix forces alphabetical sorting to match your course sequence, which Google Drive doesn't do on its own.

Inside each module folder, store every asset for that module: the lesson script, the slide deck, the recorded video, any downloadable PDFs, and the thumbnail image. Add three more folders at the top level:

• Brand Assets -- your logo, brand fonts, color palette reference, and any templates you reuse across modules
• Admin -- enrollment lists, partner agreements, launch checklists, financial tracking
• Drafts -- work-in-progress files that haven't yet been assigned to a module

Name every file using this pattern: Module01_Lesson03_Script_v2. The structure is: module number, lesson number, asset type, and version. Use two-digit numbers so that Module 1 sorts before Module 10. Separate each segment with an underscore.

Common asset types to include in the name: Script, Slides, Video, Worksheet, Thumbnail, Transcript. Pick one word for each type and use it consistently. If you call it "Worksheet" in Module 1, don't switch to "Handout" in Module 4. This convention eliminates the most common file management problem: opening three files called "lesson script final" and not knowing which one is actually final.

Append _v1, _v2, _v3 to each file as you revise it. Never use "final," "final2," or "FINAL_REALLY_FINAL." Version numbers are unambiguous. The highest number is the current version.

For Google Docs and Slides, you can also rely on the built-in version history (File > Version history > See version history). But for uploaded files like videos and PDFs, the version number in the filename is your only reliable indicator. When you upload a re-recorded video, name it Module02_Lesson01_Video_v2.mp4 and keep the v1 file in place until you've confirmed the new version works on your course platform.

Right-click any folder and choose Share. Add collaborators by email and choose their permission level: Viewer (can see but not edit), Commenter (can suggest changes), or Editor (full access). Permissions cascade downward -- sharing a module folder shares every file inside it.

A practical setup for a course with a small team: share the full master folder with your co-instructor as an Editor. Share individual module folders with your video editor as an Editor. Share the Admin folder with your VA as a Viewer. Avoid sharing your entire Google Drive or using "Anyone with the link" for folders that contain student data or financial documents.

When a module is fully built and uploaded to your course platform, download a backup. Right-click the module folder and choose Download. Google Drive compresses it into a zip file. Store that zip on an external drive or a second cloud service.

This step matters more than most course creators realize. Google Drive is reliable, but accidental deletions happen -- especially when multiple people have edit access. A local backup of your finished course means that even in the worst case, you're not rebuilding from scratch.

Right-click any folder and choose "Add to Starred." Starred items appear in the left sidebar under Starred, giving you one-click access. If you're actively building Module 3, star that folder so you can reach it without navigating through your entire course structure every time. Unstar it when you move to the next module.

Native Google Docs files have two advantages over uploaded Word documents: they don't count against your storage quota, and they support real-time collaboration. If you're writing lesson scripts, write them in Google Docs rather than creating a Word file and uploading it. The content is the same, but the workflow is smoother.

When you replace a file -- say, you re-record a video -- don't delete the old version immediately. Move it to an "Archive" subfolder inside the module folder. This keeps your active files clean while preserving the originals. After a full course run, review the archive and delete anything you're certain you won't need.

Google Drive's 15 GB of free storage fills up quickly if your course includes video. A single hour of 1080p video is roughly 3-5 GB depending on the codec. If you're building a video-heavy course, expect to either upgrade your storage or upload finished videos to your course platform and remove the Drive copies to free space.

Drive doesn't offer built-in project management. You can organize files and share them, but you can't assign tasks, set deadlines, or track production status within Drive itself. For that, you need a separate tool like Trello or Notion.

Search works well for filenames but poorly for content inside uploaded PDFs and images. If you need to search the text of a document, it should be a native Google Doc, not an uploaded PDF.