How Concert Handles File Management

For years, project teams have used subdirectories in file management systems like ACC and Procore to distribute files for specific deliverables. Common examples include folders labeled “Code Review_20231019” or “Construction Documents vFinal.” These folders do not contain new content—they simply duplicate files already stored elsewhere.

Many teams believe this method provides:

• A secure snapshot for legal or audit purposes
• A foolproof way to preserve specific versions
• An easy way to organize files for external review

🚨 Although this method was once favored, it no longer works best for managing project data.

Why Subdirectories Cause Problems

Rather than improving security, subdirectories introduce serious challenges:

• They fracture version control. Once copied, files lose their connection to the original. Updates do not sync automatically, which leads to miscommunication, outdated information, and costly rework.
• They create unnecessary duplicates. Large projects generate multiple copies of the same file, increasing storage demands and making file management more complex.
• They fail to provide real security or legal protection. You can alter or delete files and subdirectories at any time without a verifiable record.
• They disrupt integrations. Concert registers files using digital fingerprints. Manually duplicated files appear as a completely new document. As a result, the system loses the ability to track the file’s history reliably.

How Concert Solves This Problem

Instead of duplicating files, Concert keeps a single authoritative version of each file with secure tracking and verifiable audibility.

• Integrated Directories: When external systems (e.g., ACC, Procore) connect to Concert, they create data directories in the Assets section. These folders include a special integration symbol for easy identification.
• Non-Integrated Directories: These are manually created folders that do not sync with external platforms.
• Single-Source Storage: Concert enforces structured versioning, so files retain their identity across updates. This eliminates confusion and prevents unnecessary copies.

🎯 What’s Next? Future updates may introduce symlink-based structures to mirror external file directories more closely. However, our current approach prioritizes efficiency, security, and clarity by maintaining one authoritative version of each file.

How Collections Improve File Management

A Collection in Concert functions as a curated set of files for external sharing—without the risks of subdirectories. Conversely, Collections pull files from any part of a project, whether from an integrated directory or a manual upload.

• They are actively versioned. Teams can include updates, revisions, or new additions with a single click.
• Blockchain technology ensures security. Every Collection is memorialized on the blockchain, making it tamper-proof—something subdirectories cannot provide.
• The Bottom Line

Using Collections instead of subdirectories, your teams gain:

• Clarity – No duplicate files or outdated versions.
• Security – A blockchain-backed record prevents tampering.
• Efficiency – A streamlined way to share files externally without version conflicts.