Document organisation

How to Create Project Folders Automatically

Every new project needs somewhere for the brief, working files and finished work. Creating that structure by hand is a small job that gets repeated. A simple workflow can create it when a project is approved and put the link back into your project list.

By Automations For BusinessPublished October 21, 20265 min read

Key takeaways

Start when a project is approved.

Use a stable project reference and save the folder link.

Complete missing folders safely when a run repeats.

The short answer

Use one approved project record to start the setup. Give the project a unique reference, check whether its folder already exists, create only the missing folders, and save their link. Test access using the accounts that will actually use them.

Approve the project
Check for its folder
Create missing folders
Save and test the link

Agree a small folder structure first

Choose a recent completed project and look at the files people needed. Start with a few folders that have a clear purpose. For a design job, Brief, Working and Approved may be enough. Use names the team already understands.

Keep internal cost or staff information separate from anything a customer can open. Creating a folder and deciding who can see it are different jobs. Record both in your plan.

Avoid adding empty folders for every possible future step. A structure that people can understand is easier to keep useful.

Choose a clear starting point

Start after someone has approved the project, rather than on every enquiry. Your project list needs a reference, a name, an owner and a setup status. It also needs a place for the folder link.

For example, project P1042 might be called Spring brochure. Use a folder name such as P1042 Spring brochure. The reference keeps it distinct from another job with the same name.

Decide what happens if the customer or project name changes later. Keeping the reference stable and retaining the saved folder link avoids creating a new folder just because someone corrects a spelling mistake.

Build the steps around one project record

Example: a small studio marks P1042 as Approved. The workflow reads the reference and checks its folder-link field. If a valid folder is already recorded, it leaves that folder in place.

If no folder exists, it creates P1042 Spring brochure in the agreed project area. It then creates Brief, Working and Approved underneath it. Finally, it writes the main folder link back to P1042 and marks setup as Ready.

The team opens the folder from the project record. They do not need to search through an email conversation to find it. The record also shows who owns the work.

Use the folder action in your existing tools

In Microsoft Power Automate, the SharePoint connector includes a Create new folder action. A setup can use an approved list item, the chosen site and document library, and the planned folder path.

The exact starting event depends on your project system. If a flow runs whenever a record changes, add a check for approval and unfinished folder setup. Otherwise, saving the folder link can start the same work again.

Check the available actions, access and plan limits before building. The worksheet can be used with other storage tools too, but their folder and sharing rules may differ.

Make a repeat run safe

A connection can fail after the main folder exists but before all its children are created. The next run should inspect what is already there and complete the missing work. It should not create a second project folder.

Check the project reference and saved folder identifier where your tool supports it. A name match by itself can be misleading if people can rename folders or create the same name elsewhere.

If two runs can start together, use your workflow tool’s run controls or a setup lock to prevent both creating the structure. Ask the person building it to demonstrate this with two closely timed test events.

Check access before calling the setup finished

Open the folder as a regular team member. Check that they can do their work without extra access. If a customer receives a link, test that customer access separately and confirm internal files stay private.

Use the business’s normal access rules. Do not create public links just to make a test pass. Keep any wider sharing decision with the person responsible for the project.

Also test a missing project reference, an existing partial structure, an unavailable storage connection and a renamed project. A failed setup should remain visible on the project record with a person assigned to fix it.

Try one project type first

Use the worksheet to name the folders, starting event and access rules. Run the first version with test records and harmless sample files. Check that each project has one working link and a complete structure.

After the trial, ask the team which folder names caused confusion. Adjust the template before using it for more project types.

If you want help connecting a project list to your file storage, send Automations For Business your proposed structure through WhatsApp. Share a blank example rather than private project documents.

Your ready-to-use checklist

0 of 5 checked

Start when a project is approved.Use a stable project reference and save the folder link.Complete missing folders safely when a run repeats.Keep internal files separate from customer access.Test using normal team and customer accounts.

Make the next step clear.