The CDE Folder Builder creates a consistent folder structure for a common data environment (CDE) without starting from a blank page. Choose the ISO 19650 CDE template to organise information containers by state (Work in Progress, Shared, Published and Archived), with a folder for each task team. Or choose Trade packages to organise the project by phase, with one package per MasterFormat division.
Every folder in the tree can be renamed, moved or deleted, and each one carries a suggested access level you can take into your BIM Execution Plan. When the structure is agreed, export it as a script that creates the folders on Windows, macOS or Linux, as a CSV for review or bulk import, or as JSON for an API integration with your CDE platform.
ISO 19650 describes a common data environment where information moves through four states: Work in Progress (WIP), Shared, Published and Archived. A folder structure that mirrors those states, with a WIP and Shared folder for each task team, makes it clear who can edit, review and rely on each piece of information.
Any of them. The builder is platform-agnostic: use the PowerShell or Bash script to create the empty structure and upload it to Autodesk Construction Cloud, Procore, Trimble Connect, SharePoint or a file server, or hand the JSON export to a developer to create folders through your platform's API.
No. The builder runs entirely in your browser. Nothing you enter is sent to a server, and the setup is not saved between visits.
Yes. The CDE Folder Builder is free to use. If you need a version built around your own standards or platform, VDC Stack.io can build a custom tool for your team.
We build CDE templates, naming tools and project setups around your own standards and platform. Send a request or a suggestion to improve this builder.
Disclaimer. The CDE Folder Builder is a reference tool provided for guidance only. VDC Stack.io is not responsible for incorrect results, omissions, or misalignment with project, client, contractual or standards requirements. Outputs are not contractual and do not form part of any agreement or scope of work. Verify all folder structures, permissions and naming conventions against your project's information requirements before use.