An export folder is not an archive, it is a handover point: this is where whatever the shop floor, the customer or the supplier needs is waiting. Yet many teams treat it as both at once, and then the familiar thing happens: next to "PDF" appears "PDF_old", then "PDF_final", and inside that a subfolder called "newest".
Whoever is looking for a file should not have to reason about a colleague's habits. A good export folder structure for drawings explains itself: the same tree for every order, a hard split between work exports and sent packages, and never again three folders that all claim to be final. This article lays out that structure, including an example tree and the way a toolbox like Thundercad makes exports land in the right place by themselves.
How export folders derail
It starts innocently: the export dialog remembers the last-used folder, and that folder is different for everyone. One person exports into the project folder, another into a personal working folder, a third onto the desktop "to mail it quickly". Within a few weeks the same files sit in four places, in different stages.
Nobody dares to delete, because that old folder might still be good for something. So a new folder appears next to it, with a reassuring name. That is how the three final folders are born: not from sloppiness, but from caution without an agreement. The bill comes later: searching costs minutes every single time, and now and then a file from the wrong folder goes to production. That last risk, old revisions floating around, is something we covered earlier in Cleaning up old exports, so production never builds from revision A; here we tackle the structure that invites those accidents.
Feel free to run the numbers, with your own assumptions: four searches a day, three minutes each, and you are at an hour per person per week. Not dramatic, but structural. And the real risk is not the lost time, but the moment a search goes wrong without anyone noticing.
Five rules for a structure that explains itself
- One fixed place per order. All exports for an order live under one order folder, nowhere else. Not on the engineer's own drive, not in a mail folder.
- The same tree everywhere. Whoever knows one order knows them all. The structure is a team agreement, not personal taste.
- Folder names describe function, not status. "PDF" and "DXF" say what is inside. Words like "final", "new" or "old" are banned as folder names: status belongs in the file name and in your revision process.
- Work and sent are separate worlds. What is internal may be overwritten; what has left the building is untouchable.
- Three levels deep at most. Every extra layer is another place to get lost. Whoever wants to go deeper usually has a naming problem, not a folder problem.
An example tree per order
This is what a tree that follows those rules looks like. The numbers lock the order, so the folders sort the same way everywhere:
- 01_work: the running exports during the project, split into PDF, DXF and STEP. Overwriting is allowed here; there is only ever one current set.
- 02_sent: one subfolder per shipment, named after date and purpose, for example "quote customer" or "package laser cutter". Nothing in here ever changes: it is the copy of what the receiver got.
The split between 01 and 02 is the core. Work exports are disposable: when in doubt, throw them away and export again from the model. Sent packages are the opposite, they are evidence: when a discussion starts about what the laser cutter received, you want to show the exact package, not the current state of the model.
Keep the tree for small orders too. A rush job of three parts gets the same folders as a machine of a thousand parts; it is precisely the exceptions that wreck a structure. Also agree what happens when a project wraps up: 01_work may be emptied, 02_sent stays put as the record of what was delivered.
Agreeing on a structure is step one; sticking to it is step two. Let your exports land in the agreed tree automatically, and sticking to it takes care of itself.
Try 30 days freeAutomatically in the right place
The weakest point of any agreement is the moment of exporting itself: the dialog is open, the deadline is pressing and the last-used folder is one click away. That is exactly where tooling helps. With Export Folder from Thundercad you export into a fixed folder structure: the tool places PDF, DXF and STEP files in the agreed folders by itself, the same way every time, for every colleague. The difference between the careful colleague and the rushed one disappears: the structure is locked into the tool, not into anyone's discipline of the day.
Finding things back becomes as easy as writing them away. With Go To Folder you jump from Inventor straight to the folder of the open file, so you never have to click through the tree by hand to check what is already there. And the folders you need daily, such as the export folder of the current order, sit within reach through Frequent Folder.
Keeping the structure alive
Introducing a structure takes an afternoon; keeping it alive is behaviour. Three things make the difference. First: make starting correctly easier than deviating.
Second: make the structure part of onboarding new colleagues, and when someone deviates, point at the agreement rather than the person. Third: walk through the tree with the team every so often; a structure that no longer fits the work gets ignored, so adjust it as the work changes.
Mind the boundary of this story too: it is about exports, the files that leave the department. The structure of your CAD source files, with workspace, libraries and project file, is a subject with rules of its own; you can read more in Order in your Inventor project folders: workspace, libraries and project file.
Frequently asked questions
Where should the export tree live: with the CAD files or somewhere else?
Inside the order folder, but next to your CAD workspace, not inside it. That keeps exports and source files from getting entangled, keeps the workspace clean for Inventor and Vault, and lets you share the export tree with colleagues who never open CAD.
What about old projects in the old structure?
Leave them. Migrating finished projects costs a lot and returns little; the gain sits in everything still to come. Introduce the new tree from the next order onwards and only move current projects you still work in weekly.
How much time does introducing such a structure take?
As an assumption, count on an afternoon: agree the tree, prepare the template folder and point the export tools at it. After that, every avoided search pays it back. The automatic part, exporting into fixed folders, is easy to try in your own environment with the free trial month of Thundercad.