File chaos is a client relationship problem disguised as an organizational problem. When a client can’t find the latest version of a deliverable, they don’t think “we need better file organization.” They think “working with this person is messy.” When you send a link that goes to the wrong folder, you look disorganized. When you ask the client to resend an asset you already have, you look unprepared.
A shared workspace isn’t about being tidy. It’s about removing friction from every handoff, review, and approval. The client should be able to find what they need in 15 seconds. You should be able to find any file from any project, past or present, in under a minute.
Build the structure once. Duplicate it for every new client. The 30 minutes you spend on Day 1 eliminates dozens of “where’s the latest version?” messages over the course of a project.
The 5-Folder Structure
This structure works in Google Drive, Dropbox, Notion, OneDrive, and any other file-sharing tool. The folder names are the logic, the tool is just the container.
Folder 1: Assets & Brand
Everything the client gives you that you didn’t create. Logos (all formats: SVG, PNG, EPS), brand guidelines, font files, color palettes, approved photography, existing templates, style guides.
Subfolders:
/Logos, all logo variations and formats/Fonts, font files or links to licensed fonts/Brand Guidelines, the PDF or Notion doc/Approved Photography, licensed images the client owns/Templates, existing documents they want you to match
This folder is read-only for you and owned by the client. You pull from it; you don’t add to it without flagging. When assets are updated, the client drops new files here and you pull the update.
Folder 2: Deliverables
Everything you create. Two mandatory subfolders:
/Drafts, all in-progress work, named with version numbers/Final, client-approved work only
The rule: nothing enters /Final until the client explicitly approves it in writing (email “looks great, approved” or equivalent). This folder is the source of truth for what’s been completed and signed off.
Naming inside Deliverables: YYYY-MM-DD_ProjectName_Description_v1.ext. Example: 2026-05-10_AcmeCo_HomepageCopy_v2.docx. This makes chronological sorting automatic and version history clear.
Folder 3: References & Research
All source material: competitive examples, inspiration links (as PDFs or screenshots), research documents, industry reports, personas, audience data. This is your thinking folder, it shows your work and gives the client context for your decisions.
When you say “I based this approach on X competitor’s positioning,” the supporting screenshot lives here. When a client asks why you made a particular creative choice, the reference that informed it is in this folder.
The References folder does something subtle but important: it shows clients that your work is informed, not improvised. A well-organized references folder is better for your positioning than any portfolio piece.
Folder 4: Meeting Notes
One file per meeting, named with the date: 2026-05-10_Kickoff-Notes.md or 2026-05-17_WeeklySync-Notes.docx. Every meeting note has the same structure: attendees, key decisions made, action items (with owner and due date), open questions.
This folder is searchable project history. When a client says “I thought we decided X in Week 2,” you open the meeting notes from that week. Decision is either there or it isn’t. No debate about what was said in a Zoom call three weeks ago.
Make it a habit: meeting notes written and uploaded within 2 hours of every meeting. Even 5-minute phone calls get a brief note: “Quick call 5/10, confirmed Sarah is the copy approver, target turnaround 48 hrs.”
Folder 5: Admin & Contracts
Project proposal, signed contract, invoices, change requests, and signed approval emails. This folder lives on the client-shared workspace so they always have access to their own documents. You keep a local copy too, but the shared version means they can’t say they lost the contract.
Naming here: 2026-05-01_AcmeCo_Proposal-v2.pdf, 2026-05-05_AcmeCo_Contract-Signed.pdf, 2026-05-10_AcmeCo_Invoice-001.pdf.
Access Permissions: Who Sees What
The structure above is designed for a shared workspace. But not everything should be equally accessible:
- Assets & Brand: Client edits, you read
- Deliverables/Drafts: You edit, client comments (not edits, unless you’re using a collaborative tool like Google Docs where version history tracks changes)
- Deliverables/Final: You write (on approval only), client reads
- References & Research: You write, client reads
- Meeting Notes: You write, client reads
- Admin & Contracts: Both read, neither edits (use view-only PDFs)
If using Google Drive: set sharing to “Editor” for the client on the workspace-level, then restrict individual folders to “Viewer” or “Commenter” where appropriate. If using Dropbox: use Dropbox Paper for meeting notes with comment permissions.
The 30-Minute Setup Checklist
Do this at the very start of a new engagement, before the first deliverable is created:
Minutes 0-5: Create the folder structure
- Create project parent folder:
[ClientName]-[ProjectType]-[Year] - Create the 5 subfolders
- Create the Drafts and Final subfolders inside Deliverables
Minutes 5-15: Upload existing materials
- Upload signed contract to Admin & Contracts
- Upload proposal to Admin & Contracts
- If client sent brand assets in onboarding, upload to Assets & Brand
- Upload your project plan to Admin & Contracts
Minutes 15-20: Set permissions
- Share the workspace link with the client
- Set folder-level permissions as described above
- Confirm the client can access it (ask them to open it and confirm in Slack/email)
Minutes 20-25: Create your first meeting note
- Create a file in Meeting Notes:
[Date]_Kickoff-Notes - Pre-populate with the meeting agenda so you have a structure for note-taking
Minutes 25-30: Send the workspace introduction
- Send the client a brief message: “I’ve set up your project workspace at [link]. The five folders are: Assets & Brand (drop logos/fonts here), Deliverables (I’ll post all drafts and final versions here), References, Meeting Notes, and Admin. Let me know if you need access adjustments.”
This message does double duty: it confirms access and it educates the client on the structure so they know how to use it.
Naming Conventions: The Rule You Must Enforce
File naming is the most commonly violated convention and the most consequential. Enforce these three rules:
1. Date first, always. YYYY-MM-DD_ at the start of every filename. This makes files sort chronologically by default in any file system.
2. Increment versions, never overwrite. If you have v1, save the next iteration as v2. Never save over a file. Clients will ask for previous versions at the worst possible time.
3. FINAL means approved. Reserve the word FINAL for files the client has explicitly approved in writing. “FINAL_v3” is not FINAL. _FINAL is FINAL. This distinction prevents “I thought this was the approved version” conversations.
Matching Tools to Clients
The workspace structure works in any tool, but tool choice affects adoption:
Google Drive: Best for clients already in Google Workspace. Familiar, easy sharing, strong search. Use Google Docs for meeting notes to enable real-time collaboration.
Dropbox: Best for design-heavy projects with large file transfers. Slower search than Drive but better for large files. Dropbox Paper for meeting notes.
Notion: Best for clients who want a single knowledge base, deliverables, notes, tasks, and references in one place. Higher setup time and learning curve. Use only if the client is already comfortable with Notion.
OneDrive / SharePoint: Best for enterprise clients in Microsoft 365 environments. Match their existing tools, fighting a corporate IT environment is always a losing battle.
The rule: match what the client already uses. Your workspace preference is irrelevant. If they live in Drive and you prefer Notion, use Drive. The best workspace is the one the client opens.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
