Why folder structure matters more than you think
ISO 19650 defines how information should be managed throughout the lifecycle of a built asset. At the heart of it is the Common Data Environment (CDE) — and your CDE's folder structure is the foundation that everything else builds on: permissions, workflows, naming conventions, and audit trails.
Get the folder structure wrong and you'll spend the rest of the project fighting permission conflicts, hunting for misplaced files, and explaining to auditors why your CDE doesn't match your BIM Execution Plan.
The challenge with Autodesk Forma is that while it provides the storage infrastructure, it doesn't enforce or suggest a specific folder structure. Every project starts as a blank canvas. That flexibility is powerful — but it also means inconsistency is the default unless you actively prevent it.
The ISO 19650 CDE status model
ISO 19650 defines four information container states. Your folder hierarchy should reflect these:
Work in Progress (WIP)
Information being developed by the task team. Not visible to other parties.
Shared
Information shared with other task teams for review and coordination.
Published
Approved information available to the appointing party and wider team.
Archive
Project records retained for the asset lifecycle and compliance.
Recommended folder hierarchy for Forma
Here's a battle-tested folder structure that maps ISO 19650 concepts onto Forma's project file system. This template works for projects of all sizes — scale the discipline sub-folders based on your project scope.
Numbered prefixes keep CDE states in logical order in Forma's alphabetical file browser.
Discipline sub-folders in WIP map to task teams, making permission assignment straightforward.
Separate Published sub-folders by deliverable type, not discipline — because published information serves the whole team.
The real challenge: consistency across projects
Creating this folder structure once is straightforward. The hard part is deploying it identically across 10, 20, or 50 projects — and keeping it consistent as new projects are created.
Common failures:
- Project A has "01 - WIP", Project B has "WIP", Project C has "Work In Progress"
- New projects skip the Archive folder because "we'll add it later" (they won't)
- Someone creates an ad-hoc "Misc" folder that becomes a dumping ground
Automating folder deployment with Foreman
Foreman's Project Matrix includes a folder template system built specifically for this problem. You define your folder structure once as a template, then deploy it to any project in your Forma account with a single action.
Define your template
Use the folder template builder to create your ISO 19650 hierarchy. Foreman includes pre-built templates for common standards, or build your own from scratch.
Deploy to projects
Select target projects and deploy. Foreman creates every folder in the hierarchy, preserving the exact naming and nesting. Run it on one project or fifty.
Validate ongoing compliance
Schedule automated folder validation to detect drift — missing folders, unexpected additions, or naming deviations. Get notified before an auditor finds them.
Folder validation catches drift before auditors do
Foreman can run scheduled checks against your template, flagging any project where the folder structure has deviated. This is the difference between passing a compliance audit and scrambling to fix it the night before.
Pairing folder structure with permissions
A folder hierarchy is only half the equation. ISO 19650 requires that WIP folders are restricted to the originating task team, Shared folders are visible to coordinating parties, and Published folders are accessible to the appointing party.
When you define folder templates in Foreman, you can also define permission rules tied to your role hierarchy. "Structural Engineers get Edit access to 01 - WIP/Structural, View-only access to 02 - Shared, and no access to other discipline WIP folders." Deploy the template and both folders and permissions are configured together.
Key takeaway
ISO 19650 compliance starts with folder structure, but it's maintained through consistency and validation. Define your hierarchy once, deploy it automatically, and validate it continuously. That's how you build a CDE that passes audits and actually works day-to-day.