Who this module is for
Practice this before offering the skill.
Best for aspiring VAs doing admin, operations, content, coaching support, or client onboarding work.
Tools to open while practicing
- Google Drive
- Dropbox
- Google Docs
- Notion
- Loom
Full VA training module
File Organization and SOPs Full Module
Learn how to organize files safely and write simple SOPs that make repeat tasks easier to follow.
Mock client brief
Use this messy input as your training scenario.
Imagine a client sends you the items below and asks you to handle it. Your job is to turn the mess into organized work, clear decisions, and proof you can explain.
- Final logo.png
- final logo new.png
- Invoice March client copy.pdf
- Screenshot 2026-08-01 at 9.14 AM.png
- Client notes random.docx
- Weekly report FINAL final.pdf
- Zoom recording link in an email thread
- Template - onboarding checklist.docx
Module workbook
Learn the skill, then prove it with finished work.
This page is meant to be worked through, not skimmed. Read the lesson, complete the action steps, then build the final project at the bottom.
Learning objectives
- Create a folder system that is simple, searchable, and safe.
- Use file naming rules that make versions and dates clear.
- Archive files without deleting important client materials by accident.
- Write SOPs that another beginner could follow without extra explanation.
Key terms to know
- Archive
- A place for old or inactive files that should be kept but removed from active working folders.
- Version
- A file stage, such as draft, final, approved, or v2, that helps prevent confusion.
- SOP
- Standard operating procedure: a repeatable process written step by step.
- Quality check
- The list of things that must be true before a task is marked done.
Guided lessons
Work through each part in order.
Each lesson has a concept, a VA action, and a small proof task. Do all three before going to the final assignment.
1
Part 1
Organize without deleting risk
A beginner VA should never delete or rename important files without understanding the client's rules.
Action 1
Ask the client what should be archived, deleted, or kept.
Action 2
Create an Archive folder before removing old files from active folders.
Action 3
Mark older versions clearly instead of guessing what can be removed.
Proof task
Apply this part to the mock client brief above and save one clear example you could show in a portfolio or explain in an interview.
2
Part 2
Create a simple folder system
Folders should match how the business works, not how fancy the structure looks.
Action 1
Start with Admin, Clients, Marketing, Finance, Projects, Templates, and Archive.
Action 2
Use naming conventions that sort well: YYYY-MM-DD - Client - Project - Version.
Action 3
Keep active files easy to find within 2-3 clicks.
Proof task
Apply this part to the mock client brief above and save one clear example you could show in a portfolio or explain in an interview.
3
Part 3
Write SOPs people can actually follow
An SOP is useful when another person can complete the task without asking you to explain every step again.
Action 1
Include purpose, tools, access needed, frequency, steps, quality check, and blocker instructions.
Action 2
Write steps as actions, not vague reminders.
Action 3
Add screenshots or Loom videos when a visual would prevent confusion.
Proof task
Apply this part to the mock client brief above and save one clear example you could show in a portfolio or explain in an interview.
Walkthrough
Follow this process from messy input to finished output.
This is the exact practice flow learners should complete before marking the module done.
- 1Group the raw files into Admin, Clients, Marketing, Finance, Projects, Templates, and Archive.
- 2Rename files using a consistent pattern that includes date, client, project, and version when useful.
- 3Choose which files should be active and which should be archived, but do not delete anything.
- 4Write a folder map explaining where future files should go.
- 5Create an SOP for one repeat task, including steps, tools, access, quality check, and blocker instructions.
Copy-ready resource
Simple SOP template
This is not filler. Use it as the learner's working template, then customize it for the client, task, and tone.
SOP Title: [Task name]
Purpose: [Why this task matters]
Tools needed: [Apps/accounts]
Frequency: [Daily/weekly/as needed]
Steps:
1. [Action]
2. [Action]
3. [Action]
Quality check:
- [What must be true before marking done]
If blocked:
- Ask [person] for [specific info]
Last updated: [Date]Hands-on practice lab
Build a Drive system and SOP
A small coaching business needs folders for clients, invoices, content, templates, and weekly operations.
Practice tasks
Final project requirements
Submit these outputs to yourself as proof. If a learner cannot explain these, they are not done with the module yet.
- A folder map for a small client business.
- A file naming guide with 5 renamed examples.
- An archive rule explaining what not to delete.
- One complete SOP for scheduling a client meeting or publishing a post.
Checkpoint quiz with answers
Why should beginners archive before deleting?
Archiving lowers the risk of permanently removing files the client may still need.
What makes a file name useful?
It includes enough context to identify date, client, project, content, and version without opening the file.
What should every SOP include?
Purpose, tools, access needed, frequency, steps, quality check, blocker instructions, and last updated date.
Avoid these mistakes
- Deleting files without permission.
- Creating too many folder layers.
- Using inconsistent file names.
- Writing SOPs that skip access, tools, or quality checks.
Quality rubric
- Folder names are simple and business-relevant.
- Old files are archived, not randomly deleted.
- File names include useful dates, client names, project names, or versions.
- The SOP has steps, quality checks, and blocker instructions.
Portfolio proof
- Drive folder map
- File naming guide
- One complete SOP
Resume bullets after practice
- Organized shared folders using clear naming conventions, archive rules, and business-friendly folder structures.
- Created SOP documentation with tools, process steps, quality checks, and blocker instructions for repeatable tasks.