Picture this: the crew is working on a major project, and they’re struggling to keep everyone aligned on the latest information. Folks are working off three different drawing versions, RFIs are buried in inboxes, and no one’s sure which approval is final. Meanwhile, someone prints a drawing set that’s already outdated, and another team builds off a revision no one else has seen.
This constant back-and-forth to find, verify, and reconcile information slows everything down and raises the risk of rework, delays, and mistakes.
As an industry, we can agree that teams shouldn’t have to chase down information just to do their jobs, which is why contractors are increasingly shifting from disconnected file-based workflows to digital, cloud-based systems.
That being said, having shared folders and drives doesn’t mean you have an effective common data environment (CDE). Too often, teams rely on tools like SharePoint or local servers without clear workflows, naming standards, or governance.
While these systems are a step up from manual processes, they have limitations and teams can still end up guessing which information to trust.
A CDE goes beyond file storage. It brings structure, governance, and clear workflows to how information is created, reviewed, approved, and shared across the entire project.
A common data environment is a structured, governed place for all project information. While CDEs are often associated with BIM standards, the concept has always centered on how project information is organized, shared, reviewed, and approved across teams.
A project-ready CDE defines workflows, approvals, and version control so teams know what’s current, what has been reviewed, and what’s ready to use. It gives teams a way to manage drawings, models, contracts, site documentation, RFIs, and change orders with the structure needed to support project delivery.
A CDE is not a shared drive, a cloud folder, or a place to dump files. If there are no clear workflows, approvals, or version controls in place, it’s not a CDE. Storing information is easy. Managing it in a way teams can trust is what actually makes the difference.
A CDE doesn’t just provide a central place to manage files and documents. It gives contractors several benefits that directly impact how projects run day to day. Consider the following:
The benefits of a common data environment can’t be understated, and adopting a CDE is a no-brainer. That being said, successful adoption starts with culture and change management. Here’s how to get it right.
Start by answering the question, “What’s in it for them (i.e., CDE users)? Use that answer to craft your communication strategy around the change.
Don’t lead with features. Lead with what the CDE fixes. Talk about fewer headaches, less rework, and not having to second-guess drawings. When field teams see how a CDE makes their day easier, they’re far more likely to buy in and use it.
Having technology champions is one of the best ways to drive adoption on the ground. If you’re looking to build momentum early, start by identifying CDE champions for various roles, including PM, VDC, supers, precon, operations, and IT.
From there, give them ownership, involve them in decisions, and let them lead by example on projects.
Ease folks into the CDE with a pilot project where the stakes are manageable, and the team is open to trying something new. Use it to test workflows, gather feedback, and make adjustments. The goal isn’t perfection. It’s learning what works, fixing what doesn’t, and building a playbook you can roll out in the future.
Consistency matters more than perfection. Set clear expectations around naming conventions, approvals, and where information lives. Reinforce those habits in meetings, check-ins, and day-to-day work. Over time, what feels new starts to feel like the standard way of working.
If you want to enact change and get it to stick, calling people out for doing it wrong isn’t nearly as effective as showing them a better way and supporting them through the shift. So, focus on coaching, not policing. Give teams the support they need, recognize progress, and make it safe to ask questions and learn as they go.
A CDE sits at the center of how project information is created, reviewed, and shared. As such, teams must be intentional about building a strong, well-defined foundation. The following steps will help you do just that.
Iron out how your team actually works today. Map out each workflow step by step, from creation to review to approval. Where do handoffs happen? Where do things get stuck or lost?
This exercise helps you spot gaps, redundancies, and inconsistencies. Once you have that clarity, you can design workflows that are cleaner, faster, and easier to follow inside your CDE.
A CDE only works if everyone follows the same rules. Set clear standards for how information is organized and managed. Keep them easy to follow so teams don’t default back to old habits. These include:
Define how information moves from draft to final. Who reviews it? Who signs off? What happens if changes are needed? Clear approval flows remove guesswork and prevent teams from acting on incomplete or unverified information. It also creates accountability, so nothing slips through the cracks.
Don’t rely on tribal knowledge. Write down your workflows, standards, and expectations in an internal playbook. Make information scannable and easy to reference in the field. This becomes the blueprint for how projects run in your CDE. It also makes onboarding new team members faster and helps keep everyone aligned as your projects scale.
Note: Defining standards is only half the job. The real impact comes from applying them consistently across every project. That means reinforcing expectations in day-to-day work, holding teams accountable, and making it easy to follow the process.
When standards are actually used, not just documented, your CDE becomes reliable. And that’s when teams stop second-guessing the data and start trusting it.
If you’ve read this far, you already know that a common data environment is more than a place to store files. It depends on clear workflows, standards, and shared ways of working. Once those foundations are in place, Forma Data Management helps contractors put their CDE approach into practice with a connected, governed environment for organizing, managing, and sharing project information across teams, workflows, and phases.
Here’s how.
Start by setting up Forma Data Management as your central hub for project information. Whenever possible, begin with a standardized project template so you’re not reinventing the wheel each time. This gives your team a consistent starting point and helps reinforce your standards from day one.
Structure your folders to reflect how your team works. Mirror your operational workflows so it’s intuitive for everyone to find what they need. Make sure naming conventions are intuitive and predictable, so no one has to guess where files live or what they’re looking at.
Align access with real project roles. Use role-based or company-based permissions to control who can view, edit, and approve information. Protect sensitive folders while still giving field teams the visibility they need to do their jobs without delays.
Apply naming conventions that match your internal standards. That way, files stay organized at every turn. Use attributes and metadata to make filtering, searching, and reporting easier. This helps teams quickly find the right information without having to dig for it.
Use built-in workflows to route documents through the right review and approval steps. Clearly separate work in progress from published or for construction documents so teams always know what’s ready to use and what’s still in review.
Forma Data Management becomes the connected foundation for your design and field workflows. It links tools like Forma Build, Forma Design Collaboration, and others, so everyone works from the same data.
Instead of downloading files and creating local copies, teams can work from connected data. That keeps information consistent across design, coordination, and construction, and reduces the risk of working from outdated files.
As mentioned earlier, it’s best to roll out your CDE on a pilot project first. During the pilot period, pay attention to how teams use the system, where they get stuck, and where permissions or workflows need adjusting. Use those insights to refine your setup.
As you roll out your CDE, make sure you guide your teams through the change and set them up for success. Some of the ways you can do this include
A CDE changes how projects run from the ground up. Instead of chasing files and second-guessing information, teams work from data they can trust.
Now, that shift doesn’t happen overnight. It starts with understanding what a CDE really is, getting your people aligned, and building the right foundation. From there, tools like Forma Data Management help bring it all together.
Ready to get started? We recommend keeping it simple. Choose one pilot project and stand up your first CDE in Forma Data Management.
