File Naming Convention Best Practices

File Naming Convention Best Practices

Joe CullenMay 2014

What’s Broken

• Too long in general• Get longer with versions• Hard to manage versions• No protocol for naming• Poor use team’s time

• Too long in general• Get longer with versions• Hard to manage versions• No protocol for naming• Poor use team’s time

COPYRIGHT 2014 CATALYST. ALL RIGHTS RESERVED. April 7, 2023 | PAGE 2

What We Can Fix


How We Can Fix It – Internal File Naming


Brand nameDeliverable nameVersion, e.g.,V1Initials of last person to update fileDate not needed

Brand nameDeliverable nameVersion, e.g.,V1Initials of last person to update fileDate not needed

31 Characters + Spaces

Chippos Mobile Tech Audit V3 MP.xlsxChippos Mobile Tech Audit V3 MP.xlsx

If you update the file, update the V#.

When the File Ships External


Brand nameDeliverable nameCut Version #Cut initials of last person to update fileAdd the date to the end

Brand nameDeliverable nameCut Version #Cut initials of last person to update fileAdd the date to the end


Chippos Mobile Tech Audit 020714.xlsxChippos Mobile Tech Audit 020714.xlsx

When We Enter the QA Phase


Brand nameDeliverable nameReplace delivery date with “QA” Add R1 to the end

Brand nameDeliverable nameReplace delivery date with “QA” Add R1 to the end


Chippos Mobile Tech Audit QA R1.xlsxChippos Mobile Tech Audit QA R1.xlsx

Only Catalyst updates the R#.

Examples: Not Great () Vs. Much Better ()


Mmm, Chippos.

How We Can Abbreviate Deliverable Names


Future State: The Evolution of a File Name


Thank You!

Questions?

File Naming Convention Best Practices

Business

Transcript of File Naming Convention Best Practices