A new hire's first week is the only time anyone will ever look at your file system with fresh eyes. Most businesses waste it. They grant access to everything, say "it's all in the drive," and lose the one chance to find out what's actually confusing.
Treat onboarding as a two-way process: they learn where things are, and you learn what a stranger can't figure out.
Before day one: the orientation document
Write one file, 01 Admin/HR/Onboarding/FILE SYSTEM ORIENTATION.md. It takes forty minutes once and you reuse it for every hire and every contractor.
# Where things are
## The top level
00 Inbox — your own subfolder; anything you don't know where to file
01 Admin — the company itself: legal, insurance, HR, policies
02 Finance — money in, money out, tax. Restricted access.
03 Clients — one folder per client, all identical inside
04 Products — everything we sell that isn't custom work
05 Marketing— brand, content, campaigns
06 Archive — finished and closed. Read-only.
## Every client folder looks like this
01 Contracts | 02 Briefs & Notes | 03 Working | 04 Deliverables | 05 Invoices
Final files the client received are ALWAYS in 04. Nothing else goes there.
## Three naming rules
1. Dates first, always YYYY-MM-DD
2. No initials or personal shorthand
3. Versions are v01, v02 — never "final"
## Where NOT to put things
- Not in chat threads. Files in chat are lost files.
- Not on your desktop. Not in downloads.
- Not in your personal drive space once it's shared with anyone.
## Who to ask
Clients folder — Priya
Finance — Dana
Everything else — MarcusThat's the whole document. It fits on two pages, it can be read in five minutes, and it answers the questions people are too new to ask.
Access on a schedule, not all at once
Grant progressively. It's better security, and it's better learning — a new person handed access to everything explores nothing, because there's no shape to it.
Day one: their inbox folder, the orientation document, the SOP library, and read access to one live client folder they'll work on.
Week one: edit access to their actual projects. Software seats they need. The shared calendar.
Week two to four: additional clients as work requires. Marketing and brand assets if relevant.
Never automatic: finance, HR files, contracts for clients they don't work on, admin roles on any platform.
Record each grant in your access register as you make it, with the date. Doing this during onboarding rather than reconstructing it later is the difference between a clean offboarding and a guess.
The first-week assignments
Three tasks, in order. Each one teaches the system by using it.
Task one: find five specific things. Give them a list — last year's tax return, the current logo in print format, the contract for one client, the SOP for onboarding a client, the brand colour hex codes. Ask them to note how long each took and what was confusing.
This takes them an hour and it's the most valuable diagnostic you'll ever run on your own file system. Anything that takes them more than two minutes is something you'd struggle with too under pressure.
Task two: file something new correctly. Have them create a client folder from the template, or file a batch of receipts, or add a piece to the content calendar. Watch what they do without correcting immediately. Where they hesitate is where your structure is ambiguous.
Task three: fix or write one SOP. Whatever process they learned in week one, they document it or correct the existing document. New people are the only ones who notice the undocumented steps, because everyone else has stopped seeing them.
Ask them to keep a confusion log
A running text file, one line per moment of "wait, which one is this?" No filtering, no politeness.
At the end of week two, read it together. Some entries reveal that they missed something in the orientation — fix the orientation. Some reveal genuine structural problems — fix the structure. Both outcomes are worth the fifteen minutes.
This log is more useful than any audit you could run yourself, because the things that confuse a newcomer are exactly the things you've stopped noticing. And it expires: by week four they've absorbed the system's quirks and can no longer see them.
Assign a person, not a document
The orientation document handles the map. It doesn't handle "is this the kind of thing that goes in the client folder or the archive?" — which is judgment, and judgment transfers by asking.
Name one person as the file-system contact for the first month, and tell the new hire explicitly that asking is expected. In the absence of that permission, new people guess, and guesses become filing habits that are hard to unwind six months later.
What onboarding reveals about your system
Watch for these signals in the first two weeks:
They can't find something you thought was obvious. Your folder name makes sense to you because you named it. Rename it.
They ask "which one is current?" Your versioning is failing. This is the most common finding.
They put something in a reasonable place that isn't your place. Two reasonable answers means the structure is ambiguous, and the fix is usually merging two folders or clarifying a name.
They ask a question that isn't in any SOP. That's your next SOP, and you should write it while the question is fresh.
They need access to something and it takes you twenty minutes to work out how to grant it. Your permissions are structured around history rather than roles.
Fix these during onboarding. It's the only time you'll have both the information and the motivation.
Set the offboarding groundwork now
Two things done at onboarding make departure clean, and both take a minute:
Create everything in shared space, not personal space. Explain on day one that documents made in their personal drive area may belong to their account rather than the company. This is a real and common problem — files created by a departing employee's account can become inaccessible when that account is deactivated. Say it once, early, and it becomes their default.
Start their access register row on day one. Every grant, dated. When they eventually leave — and everyone eventually leaves — the offboarding checklist writes itself.
The one-hour version
For a contractor or a part-time hire where a full onboarding is overkill:
- Send the orientation document.
- Grant only the folder they're working in.
- Give them the three naming rules.
- Tell them who to ask.
- Add the row to the access register with an expiry date.
Twenty minutes of your time, and it prevents the most common contractor outcome: work delivered in a folder structure only they understand, named in a way only they can search, with the source files still on their laptop.
Next in this series: How to Organize Business Email With Labels and Filters