If you want to use Studio for managing files and folders, you will need to have as many project templates as many customers you have or otherwise you must name each project with a unique number to have a full control on what is where. For me completely unpractical with over 200 customers in the list and some 20 which whom I work on regular basis.

Every single project management software will create separate folders for separate customers, which in my opinion is the best way to work. Managing files and folders is simply very essential for a translator job, even though many newbies simply store everything on the cloud. A huge number of problems people have with Studio is the result of a completely screwed up files and folders management.

Thanks Jerzy Czopik.  I was only giving an example, but out of interest how do you manage that when working with Studio then?  Do you just change the path manually each time you create a project?  Or do you create your projects with another project management tool using the API for Studio?

Thanks Jerzy Czopik.  I was only giving an example, but out of interest how do you manage that when working with Studio then?  Do you just change the path manually each time you create a project?  Or do you create your projects with another project management tool using the API for Studio?

I do indeed adapt the path manually during each project creation. This is the only way to manage projects for me. In certain situations, when I have to deal with several packages from the same customer, I create receive the packages in separate folders, created for each job by TranslationOffice 3000, and then create a common project for all the packages. In Studio project I add subfolders for these packages. This way I can profit from cross file repetitions and internal fuzzy matches not only in one customer project, but in all of those.

If you organize your files and folders in a decent way, this works like a charm. And you can show the ISO auditor all what he wants. Quick, simple and efficient.