Project Folder Structure: A Simple, Copyable Template

A useful project folder structure gives every file a predictable home and makes the current version easy to recognize. Start with one folder for each project, then repeat a short set of subfolders: Start Here, Brief and Decisions, Inputs, Working, Review, Delivery, and Archive. Copy the template below, remove folders your project does not need, and add new ones only when a real type of work needs its own home.

This setup works for a freelance client deliverable, a class assignment, or a small team project. Keep the folder names stable across projects so you can spend your attention on the work instead of remembering where a file went.

Copy this project folder structure template

Use the tree as a starter, not a filing rule you have to follow forever. If you are working alone, you may only need the brief, working, and delivery folders. If several people review files, keep Review and Decisions visible. Give one project a clear root folder, then copy the same small skeleton when similar work begins.

Project name/
├── 00 Start Here/
│   └── README.md
├── 01 Brief and Decisions/
│   ├── Brief/
│   └── Decisions/
├── 02 Inputs/
│   ├── From client or instructor/
│   └── Reference/
├── 03 Working/
│   ├── Drafts/
│   └── Source files/
├── 04 Review/
│   ├── Round 01/
│   └── Feedback log.md
├── 05 Delivery/
│   ├── Approved/
│   └── Handoff notes.md
└── 06 Archive/

Organize the outside folders by client, course, or project

Put the repeatable project structure inside a larger folder that matches how you look for work. A freelancer who remembers clients first can start with Clients, then a client folder, then one folder per project. A student can start with a course and term, then a folder for each paper or presentation. A person managing a one-time event can start directly with the project name.

Microsoft’s file organization guide compares client, date, project, department, and hybrid structures. Its practical lesson is to choose a route that matches the way you already retrieve work, then apply it consistently. Google Drive’s help center also recommends clear names and folders that stay simple enough to navigate. Those guides explain the tradeoffs; the template here applies them to one project at a time.

Microsoft 365: 11 ideas for organizing digital files · Google Drive: organize files and folders.

Name project files so they sort and scan clearly

A filename should answer the questions you still have after you see its folder: what is this, which project does it belong to, and which version or stage is it? One workable pattern is:

YYYY-MM-DD_project_asset_stage_v01.ext
2026-10-28_northstar-homepage_hero-copy_review_v02.docx
2026-10-28_northstar-homepage_hero-copy_approved_v03.pdf

• Use a date only when it helps sort or distinguish the file. Write it as year-month-day so the order stays predictable.
• Keep the project or client name short and consistent. If the folder already supplies that context, use the space for the specific asset instead.
• Use a small set of stage words, such as draft, review, approved, and delivered. Pick terms everyone understands.
• Use a version number when you need to preserve separate snapshots. Avoid names like final-final or newest-copy.
• Write down the pattern in the README so a new collaborator can follow it.

File naming guidance from Harvard’s Data Management program describes names as a framework for showing what a file contains and how it relates to other files. It recommends documenting the components and any abbreviations when several people use the system. You do not need a research lab’s level of detail for everyday projects; borrow the useful idea of agreeing on the parts before files multiply.

Harvard Medical School: file naming conventions.

Keep drafts, reviews, and final files clear

A folder structure cannot tell people which draft is approved unless the team agrees on that signal. For a small project, keep one active working file and use the document’s version history when it is available. For a review that needs a fixed snapshot, save a copy in the review folder and label the round. Put the accepted export in Delivery, then update the README with what was delivered and where it went.

• One current working copy: make the source of truth clear before multiple people edit.
• One review checkpoint: save a dated or numbered copy when reviewers need to comment on a stable version.
• One approved delivery: label the recipient-ready file approved or delivered and do not leave competing files with the same claim.
• One archive decision: keep older files only when they help explain the work or meet your retention needs.

Make the project folder easy to hand off

The Start Here file should help someone take the next step without searching through every document. Keep it short and update it when ownership or status changes.

PROJECT
Goal:
Owner:
Status:
Next action:
Next check-in:
Current working file:
Approved delivery:
Key links:
Naming rule:
Access or retention notes:

Before sharing a folder, check its access settings and remove private material from the handoff location. If the work has contractual, legal, or organizational retention rules, follow those rules before archiving or deleting files.

For a client project, a brief and scope document helps prevent a handoff from becoming a memory test. See the freelance project brief template and the freelance project tracker template. For research or a class presentation, use the research notes guide to keep source evidence connected to the draft.

Adapt the template to your kind of project

For research notes that are ready to become slides, the separate guide to turning notes into a presentation shows how to move from sources and claims to a storyboard. Keep the folder system responsible for files; use your project tracker or calendar for tasks and dates.

Set up a project folder in five steps

1. Choose the one top-level route you will remember: client, course, or project.
2. Copy the folder tree and remove sections you do not need yet.
3. Create the README with the project goal, owner, status, next action, and naming rule.
4. Put original inputs in Inputs and make a separate working copy before editing when the original must stay intact.
5. Check access, review the current file names, and archive only when the project is complete.

Project folder structure questions

What is a good folder structure for a project?

A good project folder structure has one clear project root, a small set of stable folders for the brief, inputs, active work, review, delivery, and archive, plus file names that make status easy to understand. Remove any folder your project does not use.

Should I organize files by client or by project?

Use client first if you regularly retrieve work by client and each client has several projects. Use project first if people usually discuss and search for a project by its name. Choose one main path and use shortcuts or links when a second route is useful; duplicated copies can drift apart.

How many levels should project folders have?

Keep the hierarchy shallow enough that a person can guess where a file belongs. Add a new level only when a folder contains several distinct types of work that people need to browse separately. If a folder holds only one or two files, a subfolder may add more clicks than clarity.

Should I use dates or version numbers in project filenames?

Use dates when chronology matters, such as weekly reports or dated exports. Use version numbers when you need to distinguish snapshots of the same deliverable. If your file platform provides trustworthy version history and people edit the same source, avoid making a separate copy for every small change.

Keep the project moving

The best project folder is a small map people can follow. Give each file a likely home, keep the current working version obvious, and leave a short handoff note for the next person. Use the copyable tree as a starting point, then change it only when your actual work shows what is missing.

Sources and related guides

• Google Drive Help: Organize files and folders — file and folder features, naming, and basic organization.
• Microsoft 365: 11 ideas for how to organize digital files — choosing among client, date, project, department, and hybrid structures.
• Harvard Medical School Data Management: File naming conventions — agreeing on file-name components and documenting a shared convention.