Your CDE Is Great. Your Spreadsheets Are the Problem.
You invested in a CDE. It’s working well for what it does: managing documents, controlling versions, enforcing access, maintaining audit trails.
But somewhere on your projects, someone’s running a spreadsheet.
Maybe it’s tracking which cages have been prefabricated. Maybe it’s reconciling design changes against the schedule. Maybe it’s recording site progress against planned milestones. Maybe it’s compiling evidence for compliance.
It shouldn’t exist. But it does. And you know why.
CDEs (whether it’s Aconex, BIM 360, ProjectWise, Procore, or others) solve a specific problem brilliantly: document control.
But document control requires rigidity. You need stable folder structures, predictable naming conventions, fixed workflows, controlled versioning. That rigidity is a strength.
The problem: project delivery isn’t rigid. It changes constantly.
Plans change. Design gets revised. Scope shifts. Site conditions emerge. Compliance requirements evolve. Teams adapt.
When reality doesn’t fit the CDE’s rigid structure, teams do what they’ve always done: they work around it. They grab the data from the CDE and put it in Excel so they can manipulate it, restructure it, and respond to changes.
A CDE isn’t designed to answer: - “How much rebar have we actually prefabricated vs. what was planned?” - “Which design changes from this week triggered what downstream impacts?” - “Are we on track for handover given what we’ve actually done?” - “Where are the compliance gaps right now?”
A CDE is designed to answer: - “Where’s the latest design document?” - “Who has access to this folder?” - “What version is current?” - “Who changed what and when?”
These are fundamentally different questions. The CDE solves document governance. Projects need data governance. So teams create a parallel system: spreadsheets.
You now have two systems of record: - CDE: The official design and documents (rigid, controlled, slow to change) - Spreadsheets: The actual project reality (flexible, unofficial, fragmented across teams)
What this creates: - Data lives in two places (inconsistency inevitable) - Nobody’s quite sure which version is true (conflicts on decisions) - Updates happen in one place but not the other (data drift) - Multiple teams create their own spreadsheets (no consistency across projects) - Planners spend hours transcribing between systems (manual, error-prone) - Compliance evidence is scattered (audit nightmare) - Handover prep is a scramble to reconcile everything (crisis at the end)
You’ve got document control (good). You don’t have data governance (problem).
CDEs are rigid because they have to be. But project delivery needs flexibility.
You need to: - Customize tracking to match your delivery method (prefab workflow, phasing, supply chain) - Adapt as plans change without rebuilding the entire structure - Quickly reconfigure how you measure progress (by cage type, by location, by schedule phase) - Add new tracking categories as the project evolves (surge in scope, new compliance requirement, supply chain pivot) - Let non-technical teams (planners, site managers, QS staff) make these changes without calling CAD support
CDEs can’t do this. They’re not designed for it. And that’s fine—it’s not their job.
Your job is to fill the gap.
You keep your CDE. It stays your single source of truth for design and documents.
But you add a flexibility layer that: - Integrates with your CDE (reads design data, requirements, documents) - Lets you define custom tracking structures (no code, no CAD expertise required) - Automatically links site data back to the design model - Coordinates across planning systems, HSEQ platforms, field tools, and asset management - Eliminates the need for spreadsheets because you’ve got the flexibility you actually need
This is eviFile’s CDE integration module.
It doesn’t replace your CDE. It works alongside it. Your CDE stays rigid and controlled (good). eviFile provides the flexibility that let teams stop using spreadsheets.
Before (CDE + Spreadsheets): - Design data in CDE (rigid structure) - Site progress in spreadsheet (manual updates, inconsistent) - Compliance tracking in another spreadsheet (fragmented) - Planning status in yet another spreadsheet (out of sync) - Result: Multiple systems, data drift, manual reconciliation, handover scramble
After (CDE + eviFile): - Design data in CDE (single source of truth for documents) - Site progress linked automatically (flexible structure, coordinated) - Compliance data validated against requirements in real-time (continuous) - Planning status live-updated from site activity (no manual entry) - Result: One digital standard, coordinated data, confident handover
1. Connect Your CDE eviFile reads design requirements, asset classifications, and document structure from your CDE. Your CDE stays untouched.
2. Define Your Flexibility Without touching your CDE, you define how your teams track delivery: prefab cages, site milestones, compliance checks, supply status, whatever you need. Customizable by planners, not developers.
3. Coordinate Everything Else Site data, planning updates, HSEQ records, field reports—they all flow in. They automatically link to the design model. They stay coordinated. No spreadsheets needed.
Your CDE still manages documents. eviFile manages the data coordination that your CDE can’t flex to handle.
With CDE only: - Design model has rebar cages (good) - CDE structure is rigid: folders by section, documents by cage type - Site team prefabricates cages, but tracking needs are custom: by cage type, by location, by supplier, by date prefabricated - None of this fits the CDE’s folder structure - Workaround: Spreadsheet. Now you’re managing two systems.
With CDE + eviFile: - Design model has rebar cages (in CDE) - eviFile lets you define flexible tracking: prefab status by cage type, location, supplier, date—whatever your delivery method needs - Site team records prefab completion in eviFile - Data automatically links back to design model - Planners see live progress: “X cages complete, Y ready for install, Z still to fabricate” - No spreadsheet needed - Result: One coordinated system, flexible structure, no manual transcription
A true digital standard isn’t just “put everything in the CDE.” It’s “all your data coordinates, whether it lives in one system or many.”
CDEs are one part of that. Your planning tool is another. Your HSEQ system is another. Your field tools are another.
A digital standard means they all talk to each other. Requirements flow through. Decisions cascade. Site activity updates plans. Compliance is continuous. Handover is ready.
This isn’t possible with rigidity. It requires flexibility—the ability to adapt to how your teams actually work, not force them into the CDE’s structure.
Teams running parallel systems (CDE + spreadsheets) spend time transcribing and reconciling. They’re reactive. Gaps in compliance are found at handover. Decisions are made with incomplete information.
Teams running a true digital standard (CDE + coordinated flexibility) have real-time visibility. They’re proactive. Compliance is continuous. Decisions are made with complete, verified information.
The gap is weeks of effort per programme. It’s measurable.
eviFile integrates with Aconex, BIM 360, ProjectWise, Procore, and others. The specifics of which CDE you use don’t matter.
What matters: you’ve got a document control system (that’s your CDE). You need a data coordination system (that’s eviFile). Together, they create a digital standard that actually works.
Your CDE isn’t the problem. The spreadsheets are. And you eliminate them by adding flexibility that your CDE was never designed to provide.
Schedule a 20-minute discovery call and let’s map how to create a true digital standard for your projects—without ripping out your CDE.