Naming Files and Folders

Your most boring habit will become your biggest time-saver

Why Consistent Naming Matters

You may not realize it now, but six months from today when you're looking for "that dashboard for the Canadian client from 2022" — your naming convention will either save you in 10 seconds, or cost you 30 minutes.

This blog outlines a simple yet powerful way to name and organize Power BI project files and folders — so that things are clear, sorted, and future-proof.

✅ File and Folder Naming Format

Always use this format:

yyyymmdd Country ClientName ProjectType

Country should be a 2–3 letter code like:USA, IND, CA, AUS, UK

Examples:

• 20250424 USA MapleTech SalesDashboard.pbix

• 20231009 UK NovaHealth FinanceModel.pbix

• 20220813 IND EcoPro InventorySnapshot.pbix

This format tells you:

• When it was worked on

• Where the client is based

• Who the client is

• What the project is about

📂 Folder Naming

Name the entire project folder using the same rule:

Example Folder Name:

20240117 CA LumiData HRAnalytics

This becomes the root folder for all assets related to that project.

🗂 Folder Structure Inside

Once inside the project folder, use this clean structure:

1. Requirement.docx

   • A Word file where you document the original brief and any notes

2. Logo

   • If there are multiple logo or brand kit files, store them here

3. Files

   • All raw Excel, CSV, or Google Sheet exports used for Power BI

4. Supporting Files

   • Any extra materials not used in the final project (e.g., sample exports, archived feedback)

5. Delivery

   • This contains the final PBIX file(s) that you deliver to the client

   
   
   
   

📌 Naming the PBIX File

The PBIX file name should match what the client prefers.Don’t try to enforce your own naming logic here — just make sure the file sits inside a well-named folder.

That way, the project is still trackable by your system, even if the file name is more client-facing.

🔁 When Revisiting an Old Project

Let’s say you’re working again with LumiData for a new request — either a revision or an entirely new purpose.

Here’s how you handle it:

1. Create a new folder using today’s date:

   20240801 CA LumiData FinanceRefresh

   
   

2. Inside that, add a subfolder that’s a copy of the previous project folder, renamed exactly as it was:

   20240117 CA LumiData HRAnalytics

   
   

Now you’re maintaining full continuity while keeping the new scope clearly separated.

📅 Why yyyymmdd Works Best

This is non-negotiable if you're serious about staying organized.

1. It sorts chronologically by default in both Windows and Mac

2. You can quickly scroll through old projects and jump to “that client we worked on in late 2022”

3. It avoids the confusion and inconsistency of ddmmyyyy or mmddyyyy

   
   

Compare these two:

Wrong (ddmmyyyy):

• 24082023

• 15032021

• 07092022

Correct (yyyymmdd):

• 20210315

• 20220907

• 20230824

The second version is sortable, searchable, and structured.

Final Thoughts

You don’t need to be fancy — you need to be consistent.

Use the yyyymmdd Country Client ProjectType format for both folders and files, and stick to the internal folder structure outlined above.

This one habit will:

• Save you from confusion later

• Make collaboration easier

• Give your work a professional, system-driven polish