5 GB free storage. No credit card needed. Start free
Storage

How to organise cloud storage for client projects

A reusable folder template for client work: incoming, working and delivered, a naming convention that sorts itself, and a tidy way to close projects.

, Product Manager, dosya.dev team 5 min read

Most client storage starts tidy and ends up as a folder called Work with four hundred items in it. The cause is not laziness; it is that every project invents its own structure under deadline pressure.

The fix is a template: one structure, decided once, copied for every new project. This post gives you one, explains each part, and shows how to close a project without losing anything.

The template

Clients/
  Northwind Bakery/
    _admin/
    2026-09 Autumn campaign/
    2026-11 Winter menu/
      01-incoming/
      02-working/
      03-delivered/
      README.txt
  Harbour Physio/
    _admin/
    2026-10 Brand film/
Archive/
  2025/

Copy the empty project structure into a _template folder, and duplicate it every time a new project starts. It takes ten seconds and removes a decision you would otherwise make badly at 6 pm.

What each part is for

Clients/ at the top. One folder per client, named the way you would say it out loud. Everything for that client lives here.

_admin/ per client. Contracts, quotes, invoices and contact details. The underscore sorts it to the top and separates business paperwork from project files. If you share a project folder with the client, _admin stays private.

Dated project folders. 2026-11 Winter menu sorts chronologically in every file browser and makes three different jobs the client calls “the menu” distinguishable.

01-incoming. Everything the client sends you, untouched. It is the record of what you were given and when. Point upload links here.

02-working. Your drafts, source files and exports in progress. Organise inside it however suits your craft.

03-delivered. Exactly what the client received, in the form they received it. When someone asks what was sent, this folder answers.

README.txt. Two or three lines: what the project is, who the contact is, anything unusual. Future you will thank present you.

Archive/ by year. Closed projects move here, out of the daily view.

A naming convention for files

Folder structure does most of the work, but file names still matter, especially in 03-delivered:

  • Date, then description: 2026-11-14 Winter menu - print.pdf.
  • No “final”. final_v2_REAL.pdf is a symptom. Use dates or version numbers (v01, v02) instead.
  • Keep camera and designer filenames for originals in 01-incoming.
  • Mark review copies with REVIEW so they are never mistaken for deliverables.

A convention is a habit, not an automation. Write it into your _template folder as a short text file so collaborators follow it too.

The folder structure itself, though, can be automated. With Zapier, a new client or a signed proposal can create the client folder, the dated project folder with its three subfolders, and the intake upload link, all before you have opened the brief. If you prefer workflows you host yourself, the n8n node creates folders and share links in the same way.

Connecting the structure to how files move

The folders become most useful when the links you send map onto them:

  • Collect with an upload link pointed at 01-incoming. The client drops files in a browser, without an account, and they land in the right place. See the client file upload checklist for what to ask for.
  • Deliver with a share link pointed at 03-delivered. Add later revisions to the folder and the client’s existing link shows them.
  • Collaborate by sharing 02-working with a contractor, or inviting them to the client’s workspace, rather than sharing the whole client folder.

On dosya.dev, file requests and share links can both target a specific folder, which is what makes the template work without extra steps.

Permissions without surprises

Before you share anything, check what is inside what. A link to a client’s top-level folder includes _admin and every past project. A link to 03-delivered includes only deliveries. Share the narrowest folder that does the job.

If you work with a team, roles do the rest: our guide to folders, roles and permissions covers who should be able to see and change what.

Closing a project without accidents

When the work is delivered and paid:

  1. Check 03-delivered matches what the client has.
  2. Close links. Shut the upload link and revoke or shorten share links. Our guide to closing access after a project has the full checklist.
  3. Remove finished collaborators.
  4. Prune 02-working. Keep source files you may reuse; delete renders, caches and duplicates.
  5. Move the project to Archive/<year>/. Moving is safer than deleting, and it keeps the active list short.

If you ever delete something by mistake, a trash with a sensible retention window is the safety net. On paid dosya.dev plans, deleted files stay in the trash for 30 days.

Finding things later

A consistent structure also makes search work better, for people and for tools. If you use an AI assistant such as Claude or ChatGPT, the dosya.dev connector gives it read-only access to search your folders, so “find the logo Northwind sent in September” lands in Northwind Bakery/2026-09 Autumn campaign/01-incoming because that is where it could only be.

How this fits with the freelancer setup

This template is the folder-level detail of the broader setup in cloud storage for freelancers, which covers separating clients, estimating storage and choosing access. Use that for the big decisions and this for the day-to-day structure.

Start next month clean

The best time to adopt a template is at the start of a month, with the next new project. Do not reorganise five years of folders this weekend. Use the template from now on, move old projects into Archive/ as you touch them, and within a few months the mess will have quietly aged out.

Frequently asked questions

What is a good folder structure for client projects?

One top-level folder per client, one folder per project inside it named with the date, and the same subfolders in every project: incoming for what the client sends, working for your files in progress, and delivered for exactly what the client received.

How should I name client project folders?

Start with the year and month, then a short project name, for example 2026-11 Winter menu. Dates sort chronologically in every file browser and distinguish jobs that a client calls by the same name.

What should I do with client folders when a project ends?

Confirm the delivered folder matches what the client has, close upload and share links, remove collaborators who are finished, delete disposable working files, and move the project to an archive folder rather than deleting it outright.