In short: a project management folder structure template is a standard set of folders and sub-folders you reuse for every project, so every file has one obvious home. This guide explains the template we use and why a consistent structure matters — and includes a free ZIP download to get your whole team started.
What’s inside: 15 numbered top-level folders, each with its own sub-folders, ready to copy for every new project. It works on Windows, Mac, SharePoint, OneDrive, Google Drive and Dropbox, and there’s no sign-up.
Company Projects/
└── Year-YYYY/ one folder per start year
└── 000-Template-Project/ copy this for every new project
├── 001-Pre-Project/
├── 010-Project-Initiation-Documents/
├── 020-RFI/
├── 030-Requirements-Design/
├── 040-ITT/
├── 040-Project-Financial-Accounting/
├── 050-Contracts/
├── 060-Project-Plan/
├── 100-Work-Packages/
├── 150-QA-Integration-Testing/
├── 200-Change-Control-Requests/
├── 300-Stakeholder-Communications/
├── 400-Service-Transition-to-BaU/
├── 900-Project-Logs/
└── 999-Project-Closure/The numbers keep the folders in lifecycle order in any file browser. 040-ITT and 040-Project-Financial-Accounting share a number in the ZIP and simply sort side by side. Each folder is explained in Step 5 below.
The project folder structure at a glance
What goes in each top-level folder, and the free ITM101 template that belongs there. No folder sits more than three levels below the project folder.
| Folder | What goes in it | Matching template |
|---|---|---|
001-Pre-Project | Business case and project brief, filed before the project is approved | Business case, project brief |
010-Project-Initiation-Documents | The signed-off PID and success criteria | PID template |
020-RFI | Request for Information: supplier research and indicative quotes, one sub-folder per supplier | — |
030-Requirements-Design | Functional and non-functional requirements | — |
040-ITT | Invitation to Tender: tender documents and all supplier correspondence | — |
040-Project-Financial-Accounting | Budget (current and baseline archive), purchase orders, supplier invoices | Purchase order template |
050-Contracts | Signed supplier contracts, one sub-folder per supplier | — |
060-Project-Plan | Project schedule and budget plan, with baseline archives | Project plan, Gantt chart |
100-Work-Packages | One sub-folder per work package (WBS) | WBS template |
150-QA-Integration-Testing | Integration and smoke-test evidence | — |
200-Change-Control-Requests | Change requests and their approval decisions | Change request form |
300-Stakeholder-Communications | Stakeholder directory, RACI, board and steering group reports, communications plans | Stakeholder analysis, communication plan |
400-Service-Transition-to-BaU | Handover plans, operational readiness, acceptance, training, warranty documents | Handover template |
900-Project-Logs | Issue log and risk log | Risk register, RAID log |
999-Project-Closure | Closure report, forward commitments, final financials and contracts | Lessons learned template |
Why do you need a project management folder structure to keep your files organised?
When you start running projects of any size and complexity you will understand the importance of keeping your project files well organised. As a busy Project Manager, you need a filing system which will help you be as productive as possible. The best practice is to create a template directory structure and use the same arrangement of directories and sub-directories for each of your projects. In this article, I present my Template project management folder structure and provide a free zip file download of this directory structure to get you started.
Ideally, any filing system should be specific enough that when faced with storing any specific file there is only one obvious home for it. This has to be balanced with creating a folder structure which is too large and complex for people to understand and adopt.
From time to time, projects may be subject to audit or legal review. Having a well-structured project filing system will help to demonstrate that the project is being professionally managed using industry best practices. As a Project Manager, keep in mind that part of your job is to plan for the worst as well as the best outcome. If the project goes badly the filing system and documents, you have stored will be a vital trail of evidence that you followed best practices and allow people to see why the project failed. On the other hand, if the project is successful you will leave behind a well-structured file of information for others to refer to in the future.
While simple, the free zip file download presented in this article is quite possibly the best free project management tool available to get fast results across your team.
Template Folder Structure for Project Management Office (PMO)
As explained above, for a single Project Manager to be productive they will need a well-organised filing system. The same is true of the Project Management Office where you will be tracking multiple simultaneous projects across several Project Managers. Knowing where all your projects are documented is essential. Equally, however, having a project folder, and having each of your Project Managers follow a standard filing structure, greatly helps you check the status of a project.
Many PMOs provide Project Support in the form of Project Administrators to assist busy Project Managers. If you have staff working across multiple projects, having a standard folder structure will greatly help them be productive.
Over time as a business, you will be able to see which project file structures work best for your business. It’s best not to change the standard all the time, otherwise, you will cause more confusion and just annoy all your project managers. However, holding an annual review, or lessons learnt and tweaking the standard template your business uses each year is not a bad idea. Business, staff, and compliance change all the time, so changing your template on an annual basis isn’t a criticism of the previous version but just an acknowledgement that change is really the only constant.
In summary, your project management folder structure should incorporate all previous learning and best practices from your business, address any compliance requirements and be well documented so that you can onboard new Project Managers and make them productive from day one.
Getting started with our project folder structure
Step 1: Download
Download this zip file containing the template project file structure. Once you have this on your PC or Mac you can unzip it. On a Mac just double click the zip file to unzip it. You will then see the project folder templates shown here. Click here to download the template zip file.
Step 2: Document Management Decision
If you are working on your own, you may want to keep this folder structure on your own PC. A better choice is to place it on a cloud storage provider’s server and use something like OneDrive, iCloud, Google Drive or Dropbox. This has the advantage of making sure your files are backed up into the cloud and available from anywhere. This sets you up nicely as your business scales to allow you to add more collaborators on the project. If a small team has no cloud service or Microsoft 365, a small network drive (NAS) in the office can act as the shared project drive instead — see the kit section below.
If you are working on your own, create a top-level main folder called something like “My Projects” and drop the template structure into that folder.
If you are working in a company with Microsoft 365 then you might want to create this folder structure on SharePoint or OneDrive as these will make it easier to share documents and benefit from additional services such as versioning and collaborative editing.
Watch the path length. In SharePoint and OneDrive the whole decoded path, including the file name, can’t exceed 400 characters, and Word, Excel and PowerPoint desktop apps can’t open a file whose full path is over 260 characters, even when it is synced locally (Microsoft’s file path limits). Keep the top-level folder and project names short, and avoid adding extra layers inside the template.
If you are working as part of a larger company then create a top-level folder named something like “Project Management Office” or “Company Projects” and drop the template structure into that folder. For the company-wide drive your project folders sit inside, see our company shared drive folder structure, where this folder is called 80 Projects.
Step 3: Review the top-level folder structure
At the highest level, there is one folder for each year, named “Year-YYYY”. The ZIP includes an example “Year-2022” folder, so just rename it to the year your project starts. Create a new year folder at the start of each year. The year is the year the project started, so a six-month project that begins in December stays in that year’s folder even though most of the work happens the following year. This convention helps people know where to look for projects. Don’t be tempted to move ongoing projects at the end of the year, that would just cause confusion and probably break links and bookmarks.
I have provided a template project folder called “000-Template-Project”. Look through this and see if you need to add or remove any standard folders for your business.
When people start a new project, they will be instructed to copy this template folder.
Step 4: Starting a new project: Creating the Project Folder
Now it is time to think about what you want to call the project. I recommend coming up with a project file naming convention which incorporates the start date, the project number and a brief descriptive project name. Try year-month-projectNumber-Descriptive Name, for example:
YYYY-MM-001-Build-New-OfficeYYYY-MM-002-New-Company-WebsiteYYYY-MM-003-Laptop-Replacement-ProjectYYYY-MM-004-Attend-Business-Conference
I recommend establishing a top-level PMO Project tracker with a row for each project number. You can do this in Excel and keep it in your top-level Projects or PMO Folder.
To start a new project you need to create a new folder. To do this simply copy the 000-Template-Project folder. On a Mac, you can right-click and select Duplicate. You then rename the duplicate and give it a folder name of the project name we worked through above.
Step 5: Start using your new project folders.
The names and sequence of the folders are loosely based on PRINCE2 and best practices from many different project management methodologies and projects I have worked on.
001-Pre-Project
This folder contains two subfolders (also known as subdirectories). As a project manager, you should have been given a copy of the Business Case and the Project Brief. Normally these will be things like a high-level Profit and Loss statement setting out the business case for a project. The Project Sponsor will have had to present documents and make a case to the board or at least the PMO to secure funding and support to have the project run. Try and obtain copies of these pre-project documents and make sure they are filed in the pre-project folders.
These folders may be set-up by the PMO (Project Management Office) before a Project Manager is appointed and before the project has received final approval.
010-Project-Initiation-Documents
Often the first task for the project manager is to raise the Project Initiation Document (PRINCE2® calls it the Project Initiation Documentation, or PID; PMI’s PMBOK® Guide uses the term Project Charter). This should set out who the project is being sponsored by, the goals of the project, and the project’s constraints such as timescales, budgets, quality, and key success criteria.
I recommend creating this document, socialising it to make sure it’s right and to head off any surprises, and then call the first Project Board Meeting to get this formally signed off by the Project Board.
Within this folder, we have separate folders for the PID and Success Criteria. Generally, try and keep all the details on the PID and only create a separate Success Criteria document if the project is of sufficient size and complexity.
These documents are the foundation on which successful projects are built. Once these have been signed off at the first Project Board, they should not be changed without going through the Change Control Request Process. Any late additions to the project’s success criteria are likely to affect the cost and timescale.
020-RFI (Request for Information)
Many projects can’t start until you have done some research and contacted potential suppliers, seen presentations, and received indicative quotes. Although you should go into this stage with a high-level view of the requirements it is acceptable for the requirements to be written after this research stage.
030-Requirements-Design
All projects should have a clearly defined set of deliverables otherwise known as requirements.
The requirements should be drawn from the outline given in the PID, research from the RFI stage, and business systems analysis conducted with the project stakeholders.
Many projects, especially website design, and software development are likely to fail if you don’t have well-documented requirements. Requirements themselves can be broken down into Functional and Non-Functional Requirements. For example, “Customers will be able to download invoices in Excel and PDF formats” is a functional requirement, whereas “Invoice downloads will be available to customers 24 hours a day” is a non-functional requirement, because it describes how well the system must perform rather than what it does. Commercial terms such as a supplier warranty belong in the contract rather than the requirements.
Also see our Web Browser Compatibility Requirements policy document, which you may find helpful when developing requirements for your own online projects.
040-ITT (Invitation to Tender)
If you are running a formal tender, create an ITT (Invitation to Tender) document and send it to the potential suppliers. Some organisations are highly regulated and RFIs and ITTs must be conducted following strict processes. In these businesses, it is not uncommon for unsuccessful suppliers to appeal the decision and look for breaches of due process.
Even if your business is not highly regulated, make sure you treat all suppliers the same in all respects. Capture a copy of all correspondence with suppliers into these folders.
040-Project-Financial-Accounting
The Project Manager is responsible for tracking the budget on the project. What has been committed, what has been invoiced by suppliers and forecasting the cost to complete the project. On large projects this also involves tracking the spend based on the phase or stage of the project, as too high a spend early in the project can be a red flag, indicating that the project will go over budget before the end.
Within this folder, I have provided sub-folders for Budget, Purchase Orders and Supplier Invoices.
Within the budget sub-folder there is a sub-folder to hold archived copies of the budget. It is always good to keep copies as they are signed off and approved by the Project Board. These become baseline documents against which change can be measured. If there are any Change Control Requests which affect the cost of the project, an update to the budget should be issued showing the deviation from the baseline.
When I manage projects, I insist on approving all Purchase Orders before they are sent to suppliers, otherwise, it is difficult to control costs. I keep a copy of all the Purchase Orders I have approved in the Purchase Orders sub-folder. I know many companies will have great financial systems which let you do project accounting, but I’ve seen these go wrong, or go offline just when you need them for an important meeting, so really there’s no substitute for keeping your own copy of these important documents.
Likewise I insist on suppliers sending their invoices to me, so that I can match them off against the Purchase Orders (POs) that I have approved. You would be surprised how often suppliers make mistakes on their invoices. Letting them know you are on the ball and watching, and picking up on unexpected discrepancies helps ensure success.
You will want to create yourself a Project budget tracker spreadsheet in the top-level 040-Project-Financial-Accounting folder.
050-Contracts
Once the ITT has been conducted one or more suppliers will be contracted to build the project for you or to supply goods & services to enable someone else to do the build. Copies of all the contracts should be stored in this folder. If you have more than one supplier I recommend creating a sub-folder for each supplier and storing a copy of each individual contract for that supplier in this one location.
060-Project-Plan
The Project Manager is responsible for creating a time-based plan, to show when the project will be delivered and the key activities. They will usually be required to also produce a budget plan as well to show when major project costs will be incurred. After these documents have been presented to the Project Board and signed off, keep a baseline copy of these in the Archive sub-folders.
Even if your project plans to follow the Agile methodology, senior management will want to see a high-level time-based plan. This is not incompatible with Agile, as it can show the timeboxed sprints.
For most simple to moderate projects, you can develop a simple Gantt chart in Excel or use the Action Review Meeting (ARM) Template approach to drive progress.
The project plan should be broken down into individual work packages known as a work breakdown structure (WBS)
100-Work-Packages
The Project Manager is responsible for dividing the project into sensibly sized Work Packages. These can be thought of as mini-projects. Each work package may be contracted to a different supplier and allocated to a different manager or team in house.
I recommend that you create a subfolder for each work package and follow the file name convention WBS-year-month-projectNumber-workPackageNumber-Descriptive Name, for example:
WBS-YYYY-MM-002-001-Anti-Virus Software
WBS-YYYY-MM-002-002-Disk Encryption
WBS-YYYY-MM-002-003-Patching Policy
WBS-YYYY-MM-002-099-Deliver to end-users
WBS-YYYY-MM-002-100-User Training
Treat each work package like a mini project and make sure the requirements are clearly captured and managed through a change management process. The work package should include success criteria and QA for example.
150-QA-Integration-Testing
Assuming each work package has been delivered to specification the project manager needs to ensure that all the packages are integrated and work as a whole. For this reason, while we like to treat work packages as mini-projects, it is important that Work Package managers communicate with each other to ensure that what they are doing is what the other package managers are expecting.
When I run projects, I like to arrange what I call a smoke test, to test the integration of all the work packages as early as possible. This is often possible before all the detailed work on individual packages has been completed. Generally, in project management, the earlier in a project you know about a problem, the cheaper it will be to fix.
200-Change-Control-Requests
Change is a constant factor, but it can derail projects if not carefully managed. On one hand, if a requirement needs to be changed or a new one added to make the project a success then it would probably be silly to refuse it. On the other hand, many projects have failed due to excessive or late change requests. For this reason, you need to establish a procedure for receiving Change Control Requests (CRs) and a process for getting these approved or rejected.
Generally, all changes should be reviewed by the Project Manager and the Project Steering Group. If this group cannot agree on a change, or the person requesting the change disagrees with their decision, it will be taken to the Project Board for a final decision.
300-Stakeholder-Communications
Stakeholders’ sub-folder. This contains a subfolder for Directory, in which you should just store an Excel document detailing all the stakeholders, their role and their contact details. The other subfolder is for a RACI Matrix. You won’t need a RACI (Responsible, Accountable, Consulted and Informed) on every project, but always consider this on sensitive projects or those with more than 7 to 10 stakeholders.
For board reporting, use our free project on a page template and our free weekly or monthly project status report template for Word.
You should record the minutes of the Project Board and Project Steering Group meetings. We have a minutes template here.
400-Service-Transition-to-BaU
This folder is used to store any documents which relate to the handover from the Project Team to the Business as Usual Operations Team or Customer. These may be things like user guides, maintenance schedules, support diagrams etc.
900-Project-Logs
The project manager will be responsible for maintaining the Issues Log and Risk Management Log and any other logs mandated by your methodology or organisation. Please note that we choose to have Change Management as a top-level folder rather than as a sub-folder under Project Logs; we did this to emphasise the important nature of Change Management to the success of your project.
Free templates to file here: our risk register template, a combined RAID log template (risks, actions, issues, decisions), an action log template and a decision log template. For the thinking behind the risk log, see strategies for managing risk out of your projects.
999-Project-Closure
At the end of the project, the project manager is responsible for compiling a lessons learnt report and listing any recommendations for future projects. There will often be forward commitments at the end of the project such as deferred change control requests for a phase two project.
The final set of contracts for any ongoing support with the suppliers should be included in this sub-folder.
Step 6: Train the project managers and project teams.
I recommend running a Project Documentation training session when you get together all the team members and explain the new folder structure template to them. Pick a few key project documents and make sure they all know which specific folder the document should be filed in.
Ready to set it up? Download the template, rename the year folder, copy 000-Template-Project for your first project, then run the training session above with your team.
Kit that makes a project filing system stick
A folder template only works if paper and digital records end up in the same place. These are the things that help most in practice — for scanning the paperwork, labelling the archive, and giving a small team a shared drive.
Disclosure: as an Amazon Associate, IT Management 101 earns from qualifying purchases. If you buy through the links below we may receive a small commission, at no extra cost to you.

ScanSnap iX2500 document scanner
ScanSnap
For getting signed contracts, delivery notes and wet-ink approvals into 050-Contracts and the closure folder. Fast double-sided scanning straight to your PC, Mac or cloud storage.
View on Amazon
Brother
Label archive boxes and lever-arch files with the same 000–999 codes as the digital folders, so paper and electronic records match.
View on Amazon
Bankers Box storage boxes (pack of 10)
Bankers Box
Stackable lidded boxes for the paper side of 999-Project-Closure, when records must be retained for audit after the project ends.
View on Amazon
Synology
For a small team without SharePoint: a shared project drive with user permissions and remote access. Note that it is supplied without drives — budget for two.
View on Amazon
Tiago Forte
The PARA method (Projects, Areas, Resources, Archives) is the same idea as a project folder template, applied to everything you file. A good read for whoever owns the structure.
View on Amazon
David Allen
Allen’s system for separating project reference material from actions is still the clearest thinking on why a predictable filing structure saves time.
View on AmazonProduct availability on Amazon can change.
Frequently Asked Questions
How do I organise folders in project management?
Give every project its own parent folder and copy the same set of numbered sub-folders into it each time, one per lifecycle stage or function: initiation, requirements, procurement, finance, contracts, plan, work packages, change control, communications, handover, logs and closure. Because the arrangement is the same for every project, each file has one obvious home.
What is the best folder structure for a project?
The best structure is consistent rather than complicated. Use a small set of clearly named, numbered top-level folders that follow the project lifecycle, keep nesting to no more than three levels, and agree the standard across the team so everyone files documents the same way. The template on this page follows that pattern.
What is the difference between a project folder and a project directory?
None in practice. Directory is the older, technical term (used in Windows command prompts, Linux and macOS Terminal) and folder is the everyday term used in File Explorer, Finder, SharePoint and Google Drive. A project directory structure and a project folder structure are the same thing.
Should project folders be organised by phase or by function?
Most PMOs use a mix. Things that run the whole length of the project, such as finance, change control, communications and logs, work best as fixed top-level folders, while stage-specific work such as requirements, tenders and work packages sits in its own numbered folder. This template uses that mix.
Can I use this folder structure on SharePoint, OneDrive or Google Drive?
Yes. Unzip the download and upload the folder tree to a SharePoint document library, OneDrive, Google Drive or a shared network drive. In SharePoint, copy the 000-Template-Project folder for each new project so every project site starts with the same structure.
Can the template be used with an existing project?
Yes. Create the new project folder as described above and move the existing files into it. It is worth doing on a project that is nearer its start than its end. On a project that is nearly finished, the disruption usually outweighs the benefit.
Is the project folder structure template free?
Yes. The ZIP download is free for commercial use as long as the readme.txt file stays with the folders. Unzip it and copy the template folder for each new project.














