Using Process Recipes to export files, there is great flexibility in terms of file routing. First, it's important to understand how a Process Recipe ends up with the path that it is given.
The two tools for file routing
Every Capture One document, be it a session or catalog, has two tools that affect how a Process Recipe will route an output file: the Output Location, which generates the topmost level and the Process Recipe which determines the final path. Let's look at each of these and how cumulatively they contribute to the full processed file output path.
The Output Location tool sets the document's (that is, the particular session or catalog) Output folder. In the session workflow, by default, this is the Output folder in the hierarchy when the session is first created. In a catalog workflow, this has to be chosen by the user.
In the sample above, the session's Output Location is set to a folder called Output. This is determined by the Destination. Changing the Destination will change the root folder where processed files for the entire document. Clicking the arrow highlighted in red will open a Finder or File Explorer window to the corresponding location on the disk. This is helpful if your files are not going to where you'd expect to find them.
In this example, the Sub Folder field has the Image Date (yy-MM-dd) token inserted. This will create a subfolder within Output for the date that each image was captured. The date value is determined by the image's EXIF data. If there are images with multiple capture dates, Capture One will create corresponding sub folders without any user interaction. It is also possible to use static/plain text in this field, which will create a sub folder based on the text input.
Even Deeper Sub Folders
As with any Sub Folder fields, you can use the "/" forward slash (on macOS) or "\" backslash (on Windows) to denote another level of child folders within. In the example above, the Recipe Name token is used to create another level of folders within the Image Date (yy-MM-dd) folder. Again, no input is needed; Capture One will create any sub folders that are needed and route the files to those locations. You can use as many forward or backslashes that you may need.
The Process Recipe's File tab routes the processed file to the final destination. This is beneficial as it's possible to route different filetypes to different locations. For example, TIFs to a folder called TIF, JPGs to a folder called JPG, etc. To do so, simply alter the particular recipe's File options to fit. Recipes operate independently of each other.
The Root Folder determines the topmost folder where the file will be sent. By default, this is Output Location, the full path created in the Output Location tool that we looked at earlier. It is also possible to specify Image Folder, which is the folder where the original folder resides, or to any specific folder. These two options completely ignore the Output Location's values. Again we see the small arrow to the right-clicking this will open the folder in Finder or File Explorer.
The Sub Name is a field that allows you to put in arbitrary text, or use another token. This is used in conjunction with the Sub Name token in the Sub Folder field. It's not necessary to use the Sub Name field. The example above will send files from that recipe to a folder based on the image's rating.
As we saw in the previous example, the Sub Folder field will create folders within the Root Folder. Again, the back or forward slash can be used to create deeper levels in the folder hierarchy.
Combining all these options together, we can end up with a complex output routing path unique to each recipe without user input.
Given the above sample, processing with this particular recipe will result in processed files arriving in the Session's output folder/a subfolder of the image's date/a subfolder of the recipe's name/a subfolder of the original image's folder name/a subfolder of the image's color tag.
This is an extreme but demonstrative example of the powerful output path control from Capture One. Used correctly, this will minimize any time spend re-organizing processed files.