Method of organizing project directories and files

Quite often, the question is raised of who and how calls organizes files (this is not about version storage systems, but about the way files and directories are organized). Or does not call, and stores as it should. Just yesterday, a colleague at the Useful Club asked a similar question. I, perhaps, will record my answer here again, all of a sudden someone else will be able to save our time.
Here it is still important to understand this - this is your internal notation, the customer by and large doesn’t care what the file name is. Therefore, the organization should be as convenient for you and your colleagues.

We use the following format: ABC.Phase.SubLabel.State.0.01.doc, where:

1. ABC
   Project code to account for logs within the company and project tickets. Also used in letters, reports, and any other places where a project is mentioned to customize filters. Generated by spell under stress. Example: the project has the name “Ozon”, then its code will be OZN.
   
   
2. Phase
   The current phase of the project. The main phases and types of documents are regulated, but depending on the project, their set may vary. The general list of phases is as follows:
   
   • Presale
     It contains all the possible data found out in the course of presale preparation: presentations, contacts of stakeholders, client briefs, advertising materials and all that.
     ')
     
   • Research
     Market research, subject area, established practices, competitors;
     
     
   • Analysis
     Company survey data: goals and objectives, user classes, company structure, business model and internal / external processes, system requirements and all that.
     
     
   • Concept
     Conceptual vision of the project: wireframes, IA, scripts, characters, list and brief description of the functional;
     
     
   • Project
     Directly setting a task for development, design, testing, content, integration;
     
     
   • Wbs
     Decomposition of work on the project;
3. Sublabel
   The name of the part of the phase. For example, if the current phase is Analysis, then SubLabel may be an indication of the content: Rival, UserClasses, Scope.
   
   
4. State
   The current status of the phase. There are two types: draft or stable. Affects the use of the document within the company. Outward (to the client) only stable is given, and the next phase follows from it. Draft is an intermediate result that circulates only between designers and managers.
   
   
5. Major version
   Answers the question: how many times the document was sent for approval to the customer. If the figure is more than 3-5, then this usually means that someone is lying on the project: the previous phase is poorly performed and the data is not complete, the manager does not cope with task routing, the designer has poorly designed the functionality, which caused additional questions and, as a result, a few more cycles. The version is always installed by the manager.
   
   
6. Minor version
   The number of changes made to the project. It is used only inside designers: for example, to check the quality of documentation, prototypes. If the result is not complete (something is missed), then the minor version is incremented and the document is sent for revision. It is installed only by the designer or the head of the design department.

Directory called on the current phase. Prototypes based on a similar principle: ABC.Concept.Prototype.Stable.0.01 or ABC.Project.Prototype.Draft.0.01

Our scheme, at first glance, looks a bit monstrous, but it is logical, readable and, most importantly, tested over the years.