How can a small team keep one shared project folder organized?

Use a small set of top-level folders that answers the first question someone is likely to have: is this current work, supporting material, or something finished? For example:

Project Name/
  00-Start-Here/
  01-Active/
  02-Reference/
  03-Completed/

Put a short overview in 00-Start-Here: the folder’s purpose, who coordinates it, and where to put new files. Use 01-Active for work still being drafted or reviewed, 02-Reference for material people consult but do not usually edit, and 03-Completed for deliverables or decisions that are no longer changing.

If the team has separate workstreams, add a small number of subfolders under 01-Active, such as Planning and Communications. Avoid creating a folder for every meeting or file type unless people actually need to browse that way. The structure should reflect how your team looks for work, not an idealized filing system.

Set one rule for each kind of file and make its status easy to infer. For example: drafts stay in the relevant 01-Active folder; background material goes in 02-Reference; approved deliverables move to 03-Completed. If something is under review, keep it in the active folder and label that status in the name or a short note.

Use names that describe the content rather than vague labels such as latest, new, or final-final. A reusable pattern is:

ProjectOrTopic_DocumentType_YYYY-MM-DD_Status

For instance, a team preparing a sample project plan might name a draft WebsiteRefresh_ProjectPlan_2025-03-08_Draft. Treat the date as the date of the file or review, not as a claim that it was approved. When a deliverable is approved, use the agreed status, such as Approved, and move it to 03-Completed. If your file service shows version history, a clear name can still help people choose the right document.

Agree on a few behaviors, not a long policy. Decide who can create top-level folders, who checks that completed work is filed, and what people should do when they cannot tell where something belongs. A practical default is to put uncertain items in the relevant active folder and ask the project coordinator to place them, rather than making a new top-level folder.

For documents with several contributors, identify the working copy clearly and say where comments or review notes belong. Do not keep parallel copies named after each person unless that is genuinely part of your process; it can make it harder to tell which copy the team should use. If two files may look alike, include the topic, date, or status in the name. Put decisions that affect where work lives in 00-Start-Here, so new or returning teammates do not have to guess.

Make maintenance part of work that already happens. When a deliverable is approved or a workstream ends, its owner can move finished material into 03-Completed and leave a brief note if someone will need context later. At a regular project check-in, spend a few minutes on three questions: are there files nobody can identify, are there duplicate working copies, and is completed work still sitting among active drafts?

Here is a compact set of rules you can copy and adapt:

1. Put drafts and ongoing work in 01-Active.
2. Put background material in 02-Reference.
3. Move approved or finished deliverables to 03-Completed.
4. Name files with topic, document type, date when useful, and status.
5. Ask [folder coordinator] before adding a top-level folder.
6. At [project check-in], move completed work and resolve unclear files.

Replace the bracketed items with your team’s choices. Keep the structure flexible: if a folder stays empty or people consistently look somewhere else, discuss one small change rather than adding several new layers.