Great discussion here. I figured I would chime in from another perspective because we also automate our folder creation but do so a different way which doesn't rely on any operators.
We utilize Enfocus Switch for much of our automation and we use a common live jobs folder as the common repository for jobs files. The folder structure is the following: 'Live Jobs/{job_number}_{customer_name}' (Live Jobs/123456_My Customer/). As jobs move throughout Switch, we use the job number (often taken from the file name) to query our MIS for job information (in this case, the customer name). We then use those two variables to build the live jobs location path to reference that directory. The first time this path is used is in the creation of the job folder (similar to your case here). In Switch terms, this is called archive hierarchy.
In our MIS, we have a way to create a file whenever we convert a quote to a job, or create a new job. Switch watches for that file, and when found, kicks off the initial folder creation and setup, adding a few empty subfolders to the directory for prepress operators. When files are uploaded by the client, and assigned to job numbers, the originals are then saved to the same directory, in an 'originals' subfolder. Moments later, our preflight system finished preflighting the originals, and then the preflights are delivered to the location as well. Finally, the originals themselves are unpacked and placed into a folder which contains the authoring application (~Source InDesign 2015, for example). Later in the jobs lifecycle, the prepress operator creates and sends proofs via Switch, which also saves proofs to this directory in a 'PDF Proofs' subfolder. If the job is destined for an online storefront, thumbnails and storefront placement documents are generated and make their way to this directory. This is only possible because we can resolve the path to the live jobs files whenever we know the job number.
Later on, these files are automatically archived and can be retrieved via an automated system via Switch as well, also using this archive location path which stems from knowing the job number.